Modify deposit loader to send metadata from a content-deposit in raw format from to ERMDS
Closed, MigratedEdits Locked
Actions

Assigned To

Authored By

	moranegg
	Sep 30 2020, 11:59 AM

Description

To be coherent between the metadata-only deposit and the regular content deposit.

At the moment a parsed json file is added to the revision and sent to the ERMDS (Extrinsic Raw MetaData Storage).

We need to change that and send only raw input to the ERMDS.

Note that metadata can be sent in multiple deposit-request and were aggregated as a single json file.
We still want to keep the metadata as a single logical object even if we received multiple inputs.
With the XML, we need to verify if using on XML file for all XML inputs works well..

content-metadata references
https://forge.softwareheritage.org/source/swh-loader-core/browse/master/swh/loader/package/deposit/loader.py$85-87
https://forge.softwareheritage.org/source/swh-deposit/browse/master/swh/deposit/api/private/__init__.py$53-57
only-metadata references
https://forge.softwareheritage.org/source/swh-deposit/browse/master/swh/deposit/api/deposit_update.py$270-271

Revisions and Commits

rDENV Development environment
	Closed		D4106 conf/deposit: Drop no longer used configuration
rDDEP Push deposit
		D4101	rDDEPe15f23dc0a5e Simplify and document actual information returned to the loader
		D4100	rDDEP2ecb65d4f534 Transit raw metadata to the loader to unify with metadata update scenario
rDLDBASE Generic VCS/Package Loader
		D4105	rDLDBASE777ea4468ad3 deposit: Adapt loader to send extrinsic raw metadata to the metadata storage
rSPSITE puppet-swh-site
		D4117	rSPSITE61f9b6d87096 deposit: Clean up no longer used deposit config