You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

4.1.7 - The repository shall provide the producer/depositor with appropriate responses at agreed points during the ingest processes.


Logs are created listing file names and relevent information at each point in the ingest process listed below. These are available upon request to the producer. If an error occurs the producer is notified.

  • Pull Script - after the SIP is successfully pulled into the loader, the script makes a record of the FTPed files with the file name, size and current date and adds the file name to the FTP downloaded log file. If there is an error the producer is notified.
  • Preparation of Datasets - if decompression of datasets is unsuccessful the script adds the file name in the publisher error log and in the publisher problem directory, the producer is notified.
  • Ejournals Loader - datasets are converted from the publisher XML/SGML into NLM XML, given a URI and inserted into the ejournals database. Any errors are recorded in a log file and sent to the producer.

Please see the documents below for further details.


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.

OCUL Person - Approves contract specifications.

Relevant Documents

  1. Quality Control
  2. Producer Agreements and Licenses
  3. Workflow Charts

Supporting Text

This is necessary in order to ensure that the producer can verify that there are no inadvertent lapses in communication which might otherwise allow loss of SIPs.

Examples of Ways the Repository can Demonstrate it is Meeting this Requirement

Submission agreements/deposit agreements/deeds of gift; workflow documentation; standard operating procedures; evidence of "reporting back" such as reports, correspondence, memos, or emails.

  • No labels