tw4l
commented
4 years ago Hi @wfyson, this is looking good so far!
Two notes:
-
Dublin Core metadata: What we have so far looks good, but Archivematica expects that Dublin Core elements in
metadata.jsonare prefaced with the namespacedc.. See this section of the Archivematica documentation for explanation and an example. In the case of the example in the documentation, Dublin Core is being written on a file-by-file basis. Since we're writing metadata that's relevant to the entire transfer, the value for "filename" should be hardcoded to "objects/". -
MD5 hashes: So far it looks like this module is generating a new MD5 hash for each file exported. Where possible, we'd prefer to use the existing stored MD5 from the database, and only generate new hashes when there is not a recorded value. More information on the logic that should be used is in the README. The idea would be to verify that the fixity for a file on export is the same that it was when the file was uploaded to the eprints repository. It's quite possible that you're already planning to implement that and this was just the first step - if so, please forgive my eagerness!
photomedia
Initial work on the export plugin that can be used to create an Archivematica transfer. This plugin is currently called via 'Manage records' --> 'Archivematica' and then clicking the 'Export' button for the relevant Archivematica record (Archivematica records can be created via an EPrint's 'Actions' tab). The plugin can then later be integrated with the triggers when ready.