Scholars Portal Quality Control Specifications
1. Policy Statement
Scholars Portal is committed to its role as an accessible and trusted digital repository, and therefore must ensure that the integrity of digital objects within the repository and quality of access are maintained. These are achieved in the following ways:
- Thorough records are kept of the entire process from publisher submitted SIP to the final AIP.
- Comprehensive preservation and descriptive metadata are created for each article.
- Active monitoring of all access management issues.
2. Implementation
2.1. Ingest to AIP process:
- Every time an item is ingested into the SP repository, it is automatically recorded in the downloaded file log. The SIP is then saved in a 60 day backup.
- The SIP is decompressed and any errors are recorded automatically in an error log and also recorded in the publisher problem directory.
- The successfully extracted files are moved to the correct destination in the Ejournals directory in Pillar, their location is automatically recorded. Here the files stay in their publisher format.
- The files are then retrieved from Pillar and normalized to NLM XML format and placed in the Marklogic database, where they are automatically given their own URI which is recorded, and are now accessible to the designated communities.
- The TDR script then retrieves the files from the Marklogic database and writes preservation and descriptive metadata, which is recorded and kept in the TDR database.
2.2. Preservation and Descriptive Metadata
- For every article, preservation and descriptive metadata are automatically created by the TDR script. This metadata includes the provenance information, context information and fixity information.
2.3 Access Management
- If a user encounters access problems with the SP Ejournals website, they can email the link “contact support” at the bottom left of the each web page.
- This email goes directly to the Metadata Librarian and is remedied as soon as possible, whether it is a user problem or a problem within the SP system.
- All “access denial” incidents are logged automatically in the JIRA log, which is regularly reviewed by SP technical staff.
3. Document History
Version |
Date |
Change |
Author |
0.1 |
09/22/11 |
Draft created |
Aurianne Steinman |
0.2 |
09/27/11 |
More added |
Aurianne Steinman |
0.3 |
09/29/11 |
Formatted |
Aurianne Steinman |
|
|
|
|
|
|
|
|
|
|
|
|