4.2.3.3 Add provenance to AIPs detailing the conversion of SIP components
The repository shall add provenance to AIPs detailing the conversion of SIP components into AIP components.
Supporting Text
This is necessary in order to ensure that the SIPs received have been dealt with appropriately, and in particular have not been accidentally lost. This is necessary to ensure that AIP content can be traced back to ingested SIP content.
Examples for Meeting the Requirement
System processing files; disposal records; donor or depositor agreements/deeds of gift; provenance tracking system; system log files; process description documents; documentation of SIP relationship to AIP; clear documentation of how AIPs are derived from SIPs; documentation of standard/process against which normalization occurs; documentation of normalization outcome and how the resulting AIP is different from the SIP(s), logs of conversions made to SIP contents while creating AIPs, Provenance Information within AIPs.
Discussion
The timescale of this process will vary between repositories from seconds to many months, but SIPs must not remain in an unprocessed limbo-like state forever. The accessioning procedures and the internal processing and audit logs should maintain records of all internal transformations of SIPs to demonstrate that they either become AIPs (or part of AIPs) or are disposed of. Appropriate descriptive information should also document the provenance of all digital objects. Some repositories may assign or require unique identifiers for all SIPs, but they are not required to do so. Some repositories may maintain a list (or even a copy) of every submission. However, the documented procedures of other repositories may allow for rejection of submitted items that do not meet their requirements for SIP submission without assigning an identifier to it or maintaining a copy of it.
Evidence Provided
This requirement was added in the most recent version of ISO 16363. The APTrust Certification Working Group is working on updating this page.