Hi all,
We're building a custom Archivematica–ArchivesSpace integration at WVU Libraries. As part of this workflow, after a SIP is processed, we parse the METS.xml to extract descriptive metadata (from custom dmdSec fields) and create digital objects in ArchivesSpace. This part is working well.
We're now trying to extend this to also attach access file_version entries to those digital objects — pointing to the JPEG derivatives that Archivematica generates in the DIP. Our expectation was that the METS copied into the DIP directory would contain DIP-specific information, such as a fileGrp USE="access" or similar entries describing the generated access derivatives.
However, after inspecting the METS files in both AIPsStore and DIPsStore, we found they are completely identical — the DIP METS is a straight copy of the AIP METS with no additional entries for the DIP derivatives. This makes sense given the workflow order: "Generate METS" runs before "Generate DIP", so the derivatives don't exist yet when the METS is written.
Our question: Is there a standard or recommended way in Archivematica to get DIP derivative metadata (filenames, paths, checksums, extent info, format info etc.,) in a machine-readable structured file that can be used downstream for integrations? Or is there an existing mechanism we might be missing that captures this information somewhere in the DIP package?
Thanks,
Praneeth