4.5 Information Management

4.5 Information Management #

4.5.1 - The repository shall specify minimum information requirements to enable the Designated Community to discover and identify material of interest. #

Response #

SP’s Designated Community should be able to discover and identify specific objects easily within the repository. For this reason, each Provider agreement specifies minimum metadata requirements to be included in the SIP, based on the needs and expectations of the Designated Community.

Content Note - Journals #

After ingest, all descriptive metadata stored in the ejournals database is indexed, and searchable by the Designated Community. In addition to search, SP provides interface functionality to allow users to browse by journal title and volume/issue.

Responsibility #

  • Digital Preservation Librarian
  • Metadata Librarian

Documents #

  1. Designated Community
  2. Provider Agreement or License

4.5.2 - The repository shall capture or create minimum descriptive information for each AIP. #

Response #

SP preserves the Descriptive Information supplied by the Provider at the time of deposit for each Content Data Object. The repository then captures selected Descriptive Information within the preservation metadata of each AIP, as well as generates new Descriptive Information.

Responsibility #

  • Digital Preservation Librarian
  • Metadata Librarian

Documents #

  1. Definition of AIP
  2. Metadata Specifications
  3. Provider Agreement or License
  4. Workflow Charts

4.5.3 - The repository shall create bi-directional linkages between each AIP and its descriptive information. #

Response #

At the core of every SP AIP is the preservation metadata which contains a version of the CDO’s Descriptive Information. A unique URI is used to locate the preservation metadata in the TDR database, the same URI can also be used to retrieve the full Descriptive Information of the AIP located in the database.

Responsibility #

  • Digital Preservation Librarian
  • Metadata Librarian

Documents #

  1. Definition of AIP
  2. Workflow Charts
  3. URI & File Naming Plan
  4. System Architecture

4.5.3.1 - The repository shall maintain the bi-directional associations between its AIPs and their descriptive information over time. #

Response #

SP’s bi-directional associations between its AIPs and their Descriptive Information are linked through identical URIs. These URIs remain the same throughout the AIP’s life, unless the AIP is replaced or reloaded, in which case the URI change is performed systematically and recorded in the preservation metadata.

The relationship between the CDO and the Descriptive Information cannot be broken as both are part of the same file.

Responsibility #

  • Digital Preservation Librarian
  • Metadata Librarian

Documents #

  1. URI & File Naming Plan
  2. System Architecture
https://tdrdocs.scholarsportal.info/audit-criteria/4.5_Information_Management/
tdrdocs.scholarsportal.info
crawl=CC-MAIN-2022-40
22969
application/http; msgtype=response
sha1:HRWIBLUIS7BHL6N3BNG4SH4D6AURR5GO
<urn:uuid:c01ea9a6-4c6d-4f93-9618-0d7b695012d7>
2022-09-26T10:22:37Z
142.1.121.22
text/html
sha1:KGUIIN4W64D6IC66TN3ELPS2ZIJ4NRNU
<urn:uuid:74de6cbd-5e5a-40c7-bd8c-4e69df6b0930>
https://tdrdocs.scholarsportal.info/audit-criteria/4.5_Information_Management/
response
<urn:uuid:837c899e-5125-4835-95e1-581d1c543d7f>
isPartOf: CC-MAIN-2022-40
publisher: Common Crawl
description: Wide crawl of the web for September/October 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-194
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/