Feature #10218

Capture File and AIP UUID information in EAD XML and CSV exports and imports

Added by Dan Gillean over 5 years ago.

Status:NewStart date:08/18/2016
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Sponsored:No Tested version:2.2.1, 2.3, 2.4

Description

Currently when Archivematica passes DIP objects to AtoM, the file UUID and the originating AIP's UUID are included in the digital object metadata area of the user interface. However, this information is not included in an export, meaning that any attempt to use EAD XML or CSV to migrate to a different system would lose the relationship to the AIP captured in AtoM.

Similarly, if users wish to import descriptions related to digital objects preserved by another system and keep a record of the original file and AIP UUID in AtoM, there is no way to do so - this information is only captured during the DIP upload process from Archivematica.

This feature request would see several changes made to allow this information to be preserved during import and export.

For EAD XML export, capturing this information in an additional <unitid> element with a @type value of "fileUUID" and "aipUUID" seems the most logical way - the <unitid> element is intended to be used to capture "Any alpha-numeric text string that serves as a unique reference point or control number for the described material." On EAD XML import, if a <unitid> is found with one of the @type attributes suggested above, it could be mapped to these digital object metadata fields, allowing UUIDs from different preservation systems to be maintained in AtoM.

The CSV import/export could function similarly, adding fileUUID and aipUUID columns when DIP objects are part of an archival description CSV export. The columns could also be added on import by users, and mapped to the appropriate digital object metadata fields. Similarly, the digital object import task's basic CSV should also support the inclusion of this information, so that users who are mass uploading objects can also capture this information. Finally, the DIP object import command-line task introduced in AtoM 2.4 should also be investigated to see if it already captures AIP and File UUID information on import, or if this should be considered for modification as well.

Also available in: Atom PDF