File fixity is a digital preservation term referring to the property of a digital file being fixed, or unchanged.[1] Fixity checking is the process of verifying that a digital object has not been altered or corrupted.[2] During transfer, a repository may run a fixity check to ensure a transmitted file has not been altered en route. Within the repository, fixity checking is used to ensure that digital files have not been affected by data rot, or other digital preservation dangers.[3] By itself, fixity checking does not ensure the preservation of a digital file. Instead, it allows a repository to identify which corrupted files to replace with a clean copy from the producer or from a backup.
In practice, a fixity check is most often accomplished by computing checksum or cryptographic hash function values for a file and comparing them to a stored value or through digital signatures.[4] File fixity figures prominently in Preservation Metadata: Implementation Strategies (PREMIS), the Government Printing Office's work on the Authenticity of Electronic Federal Government Publications,[5] and fixity checking practices are used by a range of cultural heritage organizations.[6]
References edit
- ^ "Fixity Checks: Checksums, Message Digests and Digital Signatures Audrey Novak, ILTS" (PDF). November 2006. Archived from the original (PDF) on 2015-01-11.
- ^ "fixity check". PREMIS 2.0 Preservation Events Collection. Library of Congress Standards & Research Data Values Registry.
- ^ Giaretta, David (2011). Advanced Digital Preservation. ISBN 9783642168086.
- ^ Novak, Audrey. "Fixity Checks: Checksums, Message Digests and Digital Signatures" (PDF). ILTS Digital Preservation Committee.
- ^ "Authenticity of Electronic Federal Government Publications" (PDF). U.S. Government Printing Office.
- ^ Bailey, Jefferson. "File Fixity and Digital Preservation Storage: More Results from the NDSA Storage Survey". The Signal: Digital Preservation Blog. The Library of Congress.