TRIM exports

Main Page > Development > Development documentation > DSpace 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

A SIP generated from a TRIM export

Verifying manifest

The contents of the transfer must be verified agains 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 and structMaps

• 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
• 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 logical structMap TYPE attribute for the container and files will be used to populate the RAD Level of description field in AtoM