Archivematica - User contributions [en]

Validation check micro-service

2018-07-04T10:27:12Z

HrafnMalmquist:

In the [https://github.com/artefactual/archivematica-storage-service/pull/388 Github pull-request for DSpace REST API] there is functionality for connecting and depositing to the DSpace 6.x REST API.

To allow for greater flexibility it is possible to designate the uuids of the destination collections in the transfer metadata.csv/json but if there is any problem with the configuration (collection doesn't exist, insufficient user permissions, wrong password, server down etc.) you wouldn't know about it until at the very end of the process, when the AIP/DIP get's stored.

==User story==
Before a SIP is created I want to know if the ArchivesSpace and DSpace identifiers that are included in a json file with a transfer are valid. I want to know this early on in the pipeline, before a SIP has been created.

==Solution==
Create an early Store AIP/DIP validation microservice where all supplied arguments are tested for validity.

DSpace REST API version check

2018-07-04T10:15:22Z

HrafnMalmquist:

In the [https://github.com/artefactual/archivematica-storage-service/pull/388 Github pull-request for DSpace REST API] there is functionality for connecting and depositing to the DSpace 6.x REST API.

The thing is that between each major version of DSpace there have been made changes to the REST API. Specifically [https://wiki.duraspace.org/display/DSDOC6x/REST+API#RESTAPI-Index/Authentication how user authentication is done between 5 and 6] and there will be differences between 6 and 7 I believe.

DSpace 4 REST API is read only so for versions 5 => SWORD will have to be used.

==User story==
If the DSpace REST API changes with a new version of DSpace, I want Archivematica to be configured to work with that new version.

== Solution ==
One solution is to add support for DSpace to the [https://github.com/artefactual-labs/agentarchives agentarchives] library. We're already using it for ArchivesSpace.