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:
These 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 or EAD metadata derived from the TRIM export metadata
Container metadata mapping
| TRIM element | DC element | EAD element | RAD element | Comments |
|---|---|---|---|---|
| <TypedTitle> | <dc.title> | <unittitle> | Title proper | |
| n/a | n/a | <c> Level attribute | Level of description | Level of description will be obtained from METS StructMap div TYPE |
| <HomeLocation> | <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 |
|---|---|
| PCI Compliance | Title proper: PCI Compliance |
| n/a | Level of description: File |
| IT Strategy, Business Relationships and Projects - IT | Name: IT Strategy, Business Relationships and Projects - IT |
| 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 code: CA CVA [series number]-0000070 |
Document metadata mapping
| TRIM element | DC element | EAD element | RAD element | Comments |
|---|---|---|---|---|
| <TypedTitle> | <dc:title> | <unittitle> | Title proper | |
| n/a | n/a | <c> Level attribute | Level of description | Level of description will be obtained from METS StructMap div TYPE |
| <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 |
Sample document description
| TRIM | RAD |
|---|---|
| MCPP Project Report | Title proper: MCPP Project Report |
| n/a | Level of description: Item |
| 2010-03-01T18:20:15-08:00 | Date(s) of creation: 2010-03-01 |
| Note about this document | General note: Note about this document |
| DOC/2010/000100 | Reference code: CA CVA [series number]-0000070-DOC/2010/000100 |
amdSecs
- Each container will have an amdSec consisting of:
- A digiprovMD with an xlink reference to metadata/ContainerMetadata.xml
- A digiprovMD with an xlink reference to metadata/Location.xml
- Each file will have an amdSec consisting of:
- A digiprovMD with an xlink reference to the 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
- 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
Flagging closed/open AIPs
- The container metadata file (ContainerMetadata.xml) has two fields whose values will be used to populate the PREMIS rights entity in the SIP, DateClosed and RetentionSchedule. Examples are:
- <DateClosed>2012-08-17T16:13:31-08:00</DateClosed>
- <RetentionSchedule>EV2.3.A</RetentionSchedule>
- The DateClosed field will be used to populate the termOfRestriction startDate in the PREMIS rights entity
- The DateClosed and RetentionSchedule fields will be used to calculate the termOfRestriction endDate in the PREMIS rights entity. For the examples provided above, Archivematica would calculate 5 years from the end of 2012-08-17 and then to the end of the calendar year, for a result of 2017-12-31.
- The closure period would also be captured as a standardized free text entry in the rightsGrantedNote field of the PREMIS rights entity, for example: Closed until 2012-12-31.
- Other PREMIS fields would be auto-populated for every VanDocs ingest as shown in the screenshot below.
