TRIM exports
Jump to navigation
Jump to search
Main Page > Development > Development documentation > TRIM exports
This page documents ingest of TRIM exports based on requirements for VanDocs ingest at City of Vancouver Archives.
TRIM export contents
A TRIM export consists of
- 1 or more containers
- A manifest of the transfer (manifest.txt)
- XML schema documentation for all xml files in the transfer (container, location and document xml metadata)
- Location metadata (Location.xml)
- Container metadata (ContainerMetadata.xml)
- Document metadata (eg DOC_2012_000100_Metadata.xml)
- Documents (eg DOC_2012_000100.docx)
Processing a TRIM export
Parsing contents to the SIP
- Each container becomes a single transfer OR each transfer is broken into one SIP per container
- manifest.txt is copied to /metadata/submissionDocumentation
- Location.xml is copied to /metadata
- All schema documentation is copied to /metadata
- The relevant ContainerMetadata.xml is copied to /metadata
- The relevant document metadata files are copied to /metadata
- All documents are copied to /objects
Verifying manifest
The contents of the transfer must be verified against the manifest.txt file during the "Verify transfer compliance" micro-service.
Verifying checksums
Each document metadata file contains an md5 checksum for the document:
This checksums must be verified during the "Verify transfer checksums" micro-service.
The AIP METS file
dmdSecs
- Each container will have one dmdSec consisting of Dublin Core metadata derived from the TRIM export metadata
- Each file will have one dmdSec consisting of Dublin Core metadata derived from the TRIM export metadata
amdSecs
- Each container will have an amdSec consisting of:
- A rightsMD with an xpointer reference to the AccessControl element in metadata/ContainerMetadata.xml
- A digiprovMD with an xpointer reference to the Container element in metadata/ContainerMetadata.xml
- A digiprovMD with an xpointer reference to the LocationList element in metadata/Location.xml
- Each file will have an amdSec consisting of:
- A rightsMD with an xpointer reference to the AccessControl element in the relevant document metadata xml file
- A digiprovMD with an xpointer reference to the Document element in the relevant document metadata xml file
- A techMD and digiprovMDs generated by Archivematica during processing
fileSec and structMaps
- Each METS file will have two structMaps, the Archivematica default structMap and a logical structMap for hierarchically arranging the container into a file and its child items
- The container and file div TYPE elements will map to the RAD level of description field in AtoM
