Versions Compared


  • 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.


Scholars Portal Although SP is not dependent on, nor or restricted to, any particular file formats upon producer 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 publisher Provider wants to use a specific format not meeting these criteria, an agreement must be reached between the producer Provider 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


These conditions are specified in SP's Provider Agreement or License. Please see the additional documents below for more detail.


Digital Preservation Policy Librarian

OCUL Projects Officer

Relevant Documents

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