4.2.3.1 - The repository shall follow documented procedures if a SIP is not incorporated into an AIP or discarded and shall indicate why the SIP was not incorporated or discarded.
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.
Examples of Ways the Repository can Demonstrate it is Meeting these Requirements
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).Introduction
All received SIPs are recorded in the Scholars Portal FTP downloaded LOG file. If there is an error with the SIP during ingest it is documented in an error log and an email is sent to the loader. If the error is irreparable, the SIP is deleted and the Provider is notified.
Responsibility
Software Developer - Responsible for the creation of loader scripts.
Digital Preservation Policy Librarian - Ensures proper functioning of overall system.
Metadata Librarian - Authors NIH metadata crosswalk, if necessary.
System and Web Development Analyst - Receives notification of failed loader scripts.
Relevant Documents
System Logs?
SIP relationship to AIP?