Difference between revisions of "TRIM exports"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
| − | *Each container becomes a single transfer | + | *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 | *The md5 checksums present in each document metadata file are verified | ||
*manifest.txt is copied to /metadata/submissionDocumentation | *manifest.txt is copied to /metadata/submissionDocumentation | ||
| Line 30: | Line 30: | ||
*The relevant ContainerMetadata.xml is copied to /metadata | *The relevant ContainerMetadata.xml is copied to /metadata | ||
*The relevant document metadata files are copied to /metadata | *The relevant document metadata files are copied to /metadata | ||
| − | |||
Revision as of 12:01, 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
- 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