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)

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

The contents of the transfer must be verified against the manifest.txt file during the "Verify transfer compliance" micro-service.

Each document metadata file contains an md5 checksum for the document:

These checksums must be verified during the "Verify transfer checksums" micro-service.

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

TRIM element	DC element	EAD element	RAD element	Comments
<TitleFreeTextPart>	<dc.title>	<unittitle>	Title proper	Remove structured part from TitleFreeTextPart
<Creator>?	<dc.creator>	<origination>	n/a	AtoM adds a Name field linked to the Date(s) of creation field
<DateModified>	<dc.date>	<unitdate>	Date(s) of creation	Date range based on earliest and latest DateModified in document metadata
n/a	<dcterms.extent>	<physdesc> and subelement <extent>	Physical description	Count of documents in the SIP plus fixed text
<Notes>	n/a	<note>	General note
<RecordNumber>	<dc.identifier>	<unitid>	n/a	AtoM adds an identifier field to archival descriptions

Sample container description

TRIM	RAD	Comments
Information Management - IT Business Applications - Application Development and Upgrade Project Case Files - PCI Compliance	Title proper: PCI Compliance
Doe, Jane	Name: Doe, Jane
2010-03-01T18:20:15-08:00 / 2012-05-01T19:26:23-08:00	Date(s) of creation: 2010-03-01- 2012-05-01
n/a	Physical description: 184 digital objects
Note about this container	General note: Note about this container
04-4000/0000070	Reference number: 0000070

TRIM element	DC element	EAD element	RAD element	Comments
<TitleFreeTextPart>	<dc.title>	<unittitle>	Title proper
<DateModified>	<dc.date>	<unitdate>	Date(s) of creation
<Notes>	n/a	<note>	General note
<RecordNumber>	<dc.identifier>	<unitid>	n/a	AtoM adds an identifier field to archival descriptions

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 xlink reference to metadata/ContainerMetadata.xml
- A digiprovMD with an xlink reference to metadata/Location.xml

Sample amdSec for a container

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 xlink reference to the the relevant document metadata xml file
- A techMD and digiprovMDs generated by Archivematica during processing

Sample amdSec for a file

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
The structMap contains the links between containers and files and their relevant dmdSecs
The structMap also contains the link between the container and its amdSec
The files are linked to their amdSecs in the fileSec