Date: Fri, 29 Mar 2024 05:16:50 -0400 (EDT) Message-ID: <1095508827.590.1711703810774@spatlassian.scholarsportal.info> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_589_1721380675.1711703810774" ------=_Part_589_1721380675.1711703810774 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Introduction
In order to ensure the long-term integrity and reliability of informatio= n, SP uses a number of tools and procedures to detect bit corruption or los= s. The repository uses widely accepted hashing techniques to generate diges= t values for new content and carries out regular, automated fixity checks o= n archived content. For each journal article, the repository generates and = records MD5, SHA-1, and CRC32 values for each file associated with the arti= cle, including the bibliographic metadata. Digest values are stored in the = preservation metadata, which is separate from the article's files. SP also = records file sizes at byte scale.
In addition, the Pillar Axiom storage array has health-monitoring, diagn= ostic, and error-correction tools. The storage controllers will automatical= ly report errors to the University of Toronto Libraries' Information Techno= logy Services staff. The MarkLogic database performs consistency checks on = bibliographic and preservation metadata.
Please see the complete text of the Fixity Check Procedures document for additional informati= on. The R= isk Analysis and Management Strategies document contains information ab= out the Pillar array's health-monitoring and error-correction functionality= .
Responsibility
Digital Preservation Policy Librarian
Potential Risks
SP is in the process of generating digest values for content that was in= gested before the repository adopted its fixity procedures. Until this proc= ess is complete, some files do not have digest values and are not candidate= s 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 b= e noted, however, that these files are subject to MarkLogic's internal cons= istency 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 issu= e tracking system.
Relevant Documents