Difference between revisions of "TRIM exports"
Jump to navigation
Jump to search
| Line 61: | Line 61: | ||
==The AIP METS file== | ==The AIP METS file== | ||
| + | ===dmdSecs and structMaps=== | ||
| + | |||
| + | *Each container and 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 | ||
| + | |||
| + | </br> | ||
| + | |||
| + | [[File:dmdSecsg.png|680px|thumb|center|]] | ||
| + | [[File:structMapg.png|680px|thumb|center|]] | ||
[[Category:Development documentation]] | [[Category:Development documentation]] | ||
Revision as of 17:54, 5 October 2012
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
- The md5 checksums present in each document metadata file are verified
- 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
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 and 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
