Page tree
Skip to end of metadata
Go to start of metadata

3.3.5 - The repository shall define, collect, track, and appropriately provide its information integrity measurements.

Introduction

SP uses a number of techniques and tools to safeguard the integrity of information. These procedures are defined and documented in the Quality Control Specifications and Fixity Check Procedures. Records of these actions are stored in system log files and the preservation metadata for each object. Once an object has been successfully ingested into the respoitory, all integrity checking is tracked using PREMIS Event entities and made visible to users in a 'TDR Status' view for each journal article.

Responsibility

Digital Preservation Policy Librarian

Potential Risks

SP is in the process of generating digest values for content that was ingested before the repository adopted its fixity procedures. Until this process is complete, some files do not have digest values and are not candidates for regular fixity testing.

SP does not generate digest values for its preservation metadata files. In other words, there is no fixity check for the fixity values. It should be noted, however, that these files are subject to the MarkLogic database's internal consistency checking.

Monitoring Commitments

SP operates a rolling test of digest values. Fixity tests that produce a mismatch are automatically reported to staff through the repository's issue tracking system. See 5.1.1.3.1 for more information. SP staff monitor developments in mechanisms to measure the integrity of digital information and will upgrade the repository's procedures if necessary.

Relevant Documents

  1. Quality Control Specifications
  2. Fixity Check Procedures
  • No labels