Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

4.1.2 - The repository shall clearly specify the information that needs to be associated with specific Content Information at the time of its deposit.

Supporting TextIntroduction

This is necessary in order that there is a clear understanding of what needs to be acquired from the Producer.

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

Transfer requirements; producer-archive agreements. Workflow plans to produce the AIP.Scholars Portal is not dependent on, nor restricted to any particular file formats upon producer deposit, it aims to use well-known, widely accepted formats that support long-term preservation. If a publisher wants to use a specific format not meeting these criteria, an agreement must be reached between the producer and SP. The repository does, however, require producer-supplied XML or SGML (in a format agreed upon between SP and the producer) containing extensive descriptive metadata.

Documents explaining this in greater detail are available below.


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

  1. Definition of SIP
  2. Producer Agreements and Licenses
  3. Workflow Charts