Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

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.Although SP is not dependent on, or restricted to, any particular file formats upon Provider deposit, it nevertheless aims to use well known, widely accepted formats that support long-term preservation. The repository requires Provider-supplied XML or SGML, ideally in the NLM Journal Archiving and Interchange Tag Set, which contains descriptive (e.g. bibliographic) as well as structural (e.g. file relationships) metadata. If a Provider wants to use a specific format not meeting these criteria, an agreement must be reached between the Provider and SP. These conditions are specified in SP's Provider Agreement or License. Please see the additional documents below for more detail.

Responsibility

Digital Preservation Policy Librarian

OCUL Projects Officer

Relevant Documents

  1. Provider Agreement or License
  2. Definition of SIP
  3. Workflow Charts