Problem: metadata mappings between Archivematica and DSpace are hardcoded

[jhsimpson]

There is a workflow in Archivematica that integrates ArchivesSpace, Archivematica and DSpace (described here http://journal.code4lib.org/articles/12105)

In this workflow, when a user creates an AIP and stores it in DSpace, the Storage Service looks for a dublin core dmdSec in the AIP's METS file, and pulls 6 values out of that dmdSec and modifies the names of the properties before adding them as metadata properties to the DSpace Item where the AIP will be posted.

The metadata mapping used is buried in the code of the Archivematica Storage Service, and is not configurable by an end user, or even easily discoverable. The mapping should be configurable in some way by an enduser.

Here is where the mapping code lives in the Storage Service, to read from the dublinc core dmdSec and map to DSpace dc properties:
https://github.com/artefactual/archivematica-storage-service/blob/stable/0.11.x/storage_service/locations/models/dspace.py#L127-L134

A spreadsheet describing the current mappings used is here:
https://docs.google.com/spreadsheets/d/1wMi5nWakdREWsLFvqEPmGCRAeYAhbCQwrEBx3CcI6JU/edit?usp=sharing (relevant for #18 and #19 ).

[J4bbi]

For the DSpace REST API space this has been solved by:
https://github.com/artefactual/archivematica-storage-service/blob/8863492193a8f07e89fa6f1a27ad9889be4de822/storage_service/locations/models/dspace_rest.py#L182

Although I am not 100% sure on standard adherence here.