Release 0.4 (VanDocs only)

Main Page > Vancouver Digital Archives > Documentation > .0.4 (VanDocs only)

"VanDocs only" means that this procedure only applies to records received from RIM through VanDocs. Steps which do not apply to the VanDocs case have been deleted.


 * Assumptions


 * 1) Archives have already agreed to receive transfer
 * 2) 1 transfer = {1:many SIPs, transfer manifest}
 * 3) Submission agreements with RIM will mandate that checksum for each SIP must be included in the SIP
 * 4) There will be different ingest procedures for internal submissions from  sources other than VanDocs. Those will be addressed in future projects.


 * “Move” in the following description of implementation means cut and paste
 * TRIM metadata = PDI
 * Transfer Notice contains list of SIPs to be transferred

The following workflow diagram illustrates the steps required to ingest, store and provide access to digital objects in Archivematica 0.4:
 * Archivematica .0.4 (AD .0.4) workflow: (PDF) (OpenDocument).

AD1 Prepare Transfer


Expected Procedures

Expected procedures are ideal procedures, as would proceed without encountering exceptions

[1.1] --> [1.2] --> [1.3] --> [1.4] --> [1.5] --> [1.6] --> [1.7] --> [1.8] --> [1.9] --> [1.10] -->

[1.11] --> [1.12] --> [1.13] --> [1.16] --> End

Exceptions: Transfer fails at [1.11] Receive non-compliance notice from Archives at [1.13]

AD2 Accession SIP


Expected Procedures

Expected procedures are ideal procedures, as would proceed without encountering exceptions

AD2.2 Register Transfer
Expected Procedures

AD2.5 Audit SIP
Expected Procedures

AD2.6 Quarantine SIP
Expected Procedures

AD2.7 Profile SIP Content
Expected Procedures

AD3 Appraise SIP


Expected Procedures

Expected procedures are ideal procedures, as would proceed without encountering exceptions

AD4 Generate AIP


Expected Procedures

AD5 Store AIP


Expected Procedures