CINXE.COM

<!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-gb" lang="en-gb" dir="ltr" > <head>  <script> (function(w, d, s, l, i) { w[l] = w[l] || []; w[l].push({ 'gtm.start': new Date().getTime(), event: 'gtm.js' }); var f = d.getElementsByTagName(s)[0], j = d.createElement(s), dl = l != 'dataLayer' ? '&l=' + l : ''; j.async = true; j.src = 'https://www.googletagmanager.com/gtm.js?id=' + i + dl; f.parentNode.insertBefore(j, f); })(window, document, 'script', 'dataLayer', 'GTM-WCBLL2H'); </script>  <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <meta name="HandheldFriendly" content="true" /> <meta name="apple-mobile-web-app-capable" content="YES" /> <meta http-equiv="X-UA-Compatible" content="IE=edge" /> <meta charset="utf-8" /> <meta charset="utf-8"> <meta name="twitter:card" content="summary"> <meta property="og:type" content="article"> <meta property="og:url" content="https://www.dpconline.org/handbook/technical-solutions-and-tools/fixity-and-checksums"> <meta property="og:title" content="Fixity and checksums - Digital Preservation Handbook"> <meta name="generator" content="Joomla! - Open Source Content Management"> <title>Fixity and checksums - Digital Preservation Handbook</title> <link href="https://www.dpconline.org/handbook/technical-solutions-and-tools/fixity-and-checksums" rel="canonical"> <link href="https://dpconline.b-cdn.net/favicon.ico" rel="icon" type="image/vnd.microsoft.icon"> <link href="https://dpconline.b-cdn.net/templates/handbook/html/com_jcomment/default/style.css?4f7520&1717497718" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/media/vendor/joomla-custom-elements/css/joomla-alert.min.css?0.2.0&1730834454" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/plugins/content/jw_allvideos/jw_allvideos/tmpl/Responsive/css/template.css?v=6.1.0&1717497707" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/media/plg_system_jcemediabox/css/jcemediabox.min.css?2c837ab2c7cadbdc35b5bd7115e9eff1&1728378850" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/plugins/system/jce/css/content.css?badb4208be409b1335b815dde676300e&1717497712" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/templates/system/css/system.css" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/templates/handbook/foundation/normalize.css?1717497718" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/templates/handbook/foundation/foundation.min.css?1717497718" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/templates/handbook/css/app.css?1717497718" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/templates/handbook/css/responsive-tables.css?1717497718" rel="stylesheet"> <link href="https://dpconline.b-cdn.net/templates/handbook/css/cookiebar.css?1717497718" rel="stylesheet"> <script src="https://dpconline.b-cdn.net/media/vendor/jquery/js/jquery.min.js?3.7.1&1730834434"></script> <script src="https://dpconline.b-cdn.net/media/legacy/js/jquery-noconflict.min.js?504da4&1730834444"></script> <script src="https://dpconline.b-cdn.net/media/mod_menu/js/menu.min.js?4f7520&1730834448" type="module"></script> <script src="https://dpconline.b-cdn.net/components/com_jcomment/js/main.js?4f7520&1717497494" defer></script> <script src="https://dpconline.b-cdn.net/components/com_jcomment/js/ajax.js?4f7520&1717497494" defer></script> <script type="application/json" class="joomla-script-options new">{"joomla.jtext":{"ERROR":"Error","MESSAGE":"Thank you","NOTICE":"Notice","WARNING":"Warning","JCLOSE":"Close","JOK":"OK","JOPEN":"Open"},"system.paths":{"root":"","rootFull":"https://www.dpconline.org/","base":"","baseFull":"https://www.dpconline.org/"},"csrf.token":"0e1ab9a6398f0d783b00da0de3d80df9"}</script> <script src="https://dpconline.b-cdn.net/media/system/js/core.min.js?2cb912&1730834448"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/alert.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/button.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/carousel.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/collapse.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/dropdown.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/modal.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/offcanvas.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/popover.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/scrollspy.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/tab.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/vendor/bootstrap/js/toast.min.js?5.3.3&1730834450" type="module"></script> <script src="https://dpconline.b-cdn.net/media/system/js/messages.min.js?9a4811&1730834448" type="module"></script> <script src="https://dpconline.b-cdn.net/plugins/content/jw_allvideos/jw_allvideos/includes/js/behaviour.js?v=6.1.0&1717497707"></script> <script src="https://dpconline.b-cdn.net/media/plg_system_jcemediabox/js/jcemediabox.min.js?2c837ab2c7cadbdc35b5bd7115e9eff1&1728378850"></script> <script src="https://dpconline.b-cdn.net/templates/handbook/js/placeholder.min.js?1717497718"></script> <script src="https://dpconline.b-cdn.net/templates/handbook/js/jquery.cookiebar.js?1717497718"></script> <script src="https://dpconline.b-cdn.net/templates/handbook/js/jquery.nicescroll.min.js?1717497718"></script> <script>window.addEventListener('DOMContentLoaded', function(event){window.jcomment=new JComment(110,'com_content','/component/jcomment');jcomment.setList('comments-list');});</script> <script>window.addEventListener('DOMContentLoaded', function(event) {jcomment.setAntiCache(0,0,1);});</script> <script type="application/ld+json">{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://www.dpconline.org/#/schema/Organization/base","name":"Digital Preservation Coalition","url":"https://www.dpconline.org/"},{"@type":"WebSite","@id":"https://www.dpconline.org/#/schema/WebSite/base","url":"https://www.dpconline.org/","name":"Digital Preservation Coalition","publisher":{"@id":"https://www.dpconline.org/#/schema/Organization/base"}},{"@type":"WebPage","@id":"https://www.dpconline.org/#/schema/WebPage/base","url":"https://www.dpconline.org/handbook/technical-solutions-and-tools/fixity-and-checksums","name":"Fixity and checksums - Digital Preservation Handbook","isPartOf":{"@id":"https://www.dpconline.org/#/schema/WebSite/base"},"about":{"@id":"https://www.dpconline.org/#/schema/Organization/base"},"inLanguage":"en-GB"},{"@type":"Article","@id":"https://www.dpconline.org/#/schema/com_content/article/110","name":"Fixity and checksums","headline":"Fixity and checksums","inLanguage":"en-GB","isPartOf":{"@id":"https://www.dpconline.org/#/schema/WebPage/base"}}]}</script> <script> var _gaq=[["_setAccount","UA-48292982-3"],["_trackPageview"]]; (function(d,t){var g=d.createElement(t),s=d.getElementsByTagName(t)[0];g.async=1; g.src=("https:"==location.protocol?"//ssl":"//www")+".google-analytics.com/ga.js"; s.parentNode.insertBefore(g,s)}(document,"script")); </script> <script async src="//static.getclicky.com/101386350.js"></script> </head> <body lang="en" class="CS_Document">  <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-WCBLL2H" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>  <div id="header"> <div class="row" data-equalizer> <div class="small-12 medium-6 columns" data-equalizer-watch> <a href="http://www.dpconline.org"><img class="logo" src="https://dpconline.b-cdn.net/templates/handbook/images/style/dpc_logo.gif" alt="Digital Preservation Coalition logo" /></a> </div> <div class="small-12 medium-6 columns" data-equalizer-watch> <p class="logo_text">Digital Preservation <strong>Handbook</strong></p> </div> </div> </div> <div class="row"> <div class="small-12 medium-4 large-3 columns no_pad_left no_pad_right"> <div class="scroll_nav"> <h4>Explore the Handbook</h4> <div class="max_height"> <ul class="mod-menu mod-list nav "> <li class="nav-item item-772 alias-parent-active"><a href="/handbook" >Home</a></li><li class="nav-item item-480"><a href="/handbook/contents" >Contents</a></li><li class="nav-item item-481 parent"><a href="/handbook/introduction" >Introduction</a></li><li class="nav-item item-507 parent"><a href="/handbook/digital-preservation" >Digital preservation briefing</a></li><li class="nav-item item-510"><a href="/handbook/getting-started" >Getting started</a></li><li class="nav-item item-522 parent"><a href="/handbook/organisational-activities" >Organisational activities</a></li><li class="nav-item item-511 parent"><a href="/handbook/institutional-strategies" >Institutional strategies</a></li><li class="nav-item item-533 active deeper parent"><a href="/handbook/technical-solutions-and-tools" >Technical solutions and tools</a><ul class="mod-menu__sub list-unstyled small"><li class="nav-item item-534"><a href="/handbook/technical-solutions-and-tools/tools" >Tools</a></li><li class="nav-item item-535 current active"><a href="/handbook/technical-solutions-and-tools/fixity-and-checksums" aria-current="page">Fixity and checksums</a></li><li class="nav-item item-536"><a href="/handbook/technical-solutions-and-tools/file-formats-and-standards" >File formats and standards</a></li><li class="nav-item item-537"><a href="/handbook/technical-solutions-and-tools/information-security" >Information security</a></li><li class="nav-item item-538"><a href="/handbook/technical-solutions-and-tools/cloud-services" >Cloud services</a></li><li class="nav-item item-539"><a href="/handbook/technical-solutions-and-tools/digital-forensics" >Digital forensics</a></li><li class="nav-item item-540"><a href="/handbook/technical-solutions-and-tools/persistent-identifiers" >Persistent identifiers</a></li></ul></li><li class="nav-item item-1535 parent"><a href="/handbook/tool-demos" >Tool Demos</a></li><li class="nav-item item-541 parent"><a href="/handbook/content-specific-preservation" >Content-specific preservation</a></li><li class="nav-item item-545"><a href="/handbook/glossary" >Glossary</a></li></ul> </div> <div class="social"> <ul class="small-block-grid-4"> <li> <a class="square_box_med facebook" alt="Share on Facebook" target="_blank" onclick="javascript:window.open(this.href, '', 'menubar=no,toolbar=no,resizable=yes,scrollbars=yes,height=300,width=600');return false;" title="Share on Facebook" href="https://www.facebook.com/sharer/sharer.php?u=https://www.dpconline.org/handbook/technical-solutions-and-tools/fixity-and-checksums"> <span class="content"> <svg viewBox="0 0 512 512"> <path d="M211.9 197.4h-36.7v59.9h36.7V433.1h70.5V256.5h49.2l5.2-59.1h-54.4c0 0 0-22.1 0-33.7 0-13.9 2.8-19.5 16.3-19.5 10.9 0 38.2 0 38.2 0V82.9c0 0-40.2 0-48.8 0 -52.5 0-76.1 23.1-76.1 67.3C211.9 188.8 211.9 197.4 211.9 197.4z"/> </svg> </span> <span class="hidden">Share on Facebook</span> </a> </li> <li> <a class="square_box_med twitter" alt="Twitter" onclick="window.open('http://twitter.com/share?url=https://www.dpconline.org/handbook/technical-solutions-and-tools/fixity-and-checksums&text=Fixity and checksums - Digital Preservation Handbook', '_blank', 'width=800,height=300')" title="Share on Twitter" href="javascript:void(0);"> <span class="content"> <svg viewBox="0 0 512 512"> <path d="M419.6 168.6c-11.7 5.2-24.2 8.7-37.4 10.2 13.4-8.1 23.8-20.8 28.6-36 -12.6 7.5-26.5 12.9-41.3 15.8 -11.9-12.6-28.8-20.6-47.5-20.6 -42 0-72.9 39.2-63.4 79.9 -54.1-2.7-102.1-28.6-134.2-68 -17 29.2-8.8 67.5 20.1 86.9 -10.7-0.3-20.7-3.3-29.5-8.1 -0.7 30.2 20.9 58.4 52.2 64.6 -9.2 2.5-19.2 3.1-29.4 1.1 8.3 25.9 32.3 44.7 60.8 45.2 -27.4 21.4-61.8 31-96.4 27 28.8 18.5 63 29.2 99.8 29.2 120.8 0 189.1-102.1 185-193.6C399.9 193.1 410.9 181.7 419.6 168.6z"/> </svg> </span> <span class="hidden">Share on Twitter</span> </a> </li> <li class="hide_for_touch"> <a class="square_box_med" title="Print page" rel="nofollow" onclick="window.open(this.href,'win2','status=no,toolbar=no,scrollbars=yes,titlebar=no,menubar=no,resizable=yes,width=800,height=480,directories=no,location=no'); return false;" href="https://www.dpconline.org/handbook/technical-solutions-and-tools/fixity-and-checksums?tmpl=component&print=1&page="> <span class="content"> <svg viewBox="0 0 512 512"> <path d="M432.5,112H400V64H112v48H80.5C62.9,112,48,125.8,48,143.3v158.4c0,17.5,14.9,32.3,32.5,32.3H112V208h288v126h32.5 c17.6,0,31.5-14.8,31.5-32.3V143.3C464,125.8,450.1,112,432.5,112z"/> <rect x="128" y="224" width="256" height="224"/> </svg> </span> <span class="hidden">Print page</span> </a> </li>  </ul> </div> </div> </div> <div class="small-12 medium-8 large-9 columns"> <div id="system-message-container" aria-live="polite"></div> <div class="com-content-article item-page"> <meta itemprop="inLanguage" content="en-GB"> <div class="page-header"> <h1> Fixity and checksums </h1> </div> <div class="com-content-article__body"> <p style="text-align: center;"><img src="https://dpconline.b-cdn.net/images/businesscontinuity.png" alt="" /></p> <h6 style="text-align: center;">Illustration by Jørgen Stamp digitalbevaring.dk CC BY 2.5 Denmark</h6> <h2>Fixity</h2> <p> </p> <p><span lang="EN-US">“Fixity, in the preservation sense, means the assurance that a digital file has remained unchanged, i.e. fixed.” (<a href="#ref">Bailey, 2014</a>). Fixity doesn’t just apply to files, but to any digital object that has a series of bits inside it where that ‘bitstream’ needs to be kept intact with the knowledge that it hasn’t changed. Fixity could be applied to images or video inside an audiovisual object, to individual files within a zip, to metadata inside an XML structure, to records in a database, or to objects in an object store. However, files are currently the most common way of storing digital materials and fixity of files can established and monitored through the use of checksums.</span></p> <p> </p> <h2><span lang="EN-US">Checksums</span></h2> <p> </p> <p><span lang="EN-US">A checksum on a file is a ‘digital fingerprint’ whereby even the smallest change to the file will cause the checksum to change completely. Checksums are typically created using cryptographic techniques and can be generated using a range of readily available and open source tools. It is important to note that whilst checksums can be used to detect if the contents of a file have changed, they do not tell you where in the file that the change has occurred. </span></p> <p><span lang="EN-US">Checksums have three main uses:</span></p> <ol><ol> <li><span style="line-height: 1.3em;">To know that a file has been correctly received from a content owner or source and then transferred successfully to preservation storage</span></li> <li>To know that file fixity has been maintained when that file is being stored.</li> <li>To be given to users of the file in the future so they know that the file has been correctly retrieved from storage and delivered to them.</li> </ol></ol> <p><span lang="EN-US">This allows a ‘chain of custody’ to be established between those who produce or supply the digital materials, those responsible for its ongoing storage, and those who need to use the digital material that has been stored. In the OAIS reference model </span><span style="font-size: 1em;">(</span><a href="#ref" style="font-size: 1em;">ISO, 2012</a><span style="font-size: 1em;">) </span><span lang="EN-US" style="font-size: 1em;">these are the producers, </span><span style="font-size: 1em;">the OAIS itself is the repository, and the </span><span style="font-size: 1em;">consumers.</span></p> <p> </p> <h2>Application in digital preservation</h2> <p> </p> <p><iframe src="https://www.youtube.com/embed/qx3YQRRKwqw" width="560" height="315" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""></iframe></p> <p> <strong>A short video explaining the basics of Integrity (Fixity) Checking in Digital Preservation</strong></p> <p><span lang="EN-US">If an organisation has multiple copies of their files, for example as recommended in the <a href="/component/content/article/storage?catid=78&Itemid=501">Storage</a> section, then checksums can be used to monitor the fixity of each copy of a file and if one of the copies has changed then one of the other copies can be used to create a known good replacement. The approach is to compute a new checksum for each copy of a file on a regular basis and compare this with the reference value that is known to be correct. If a deviation is found then the file is known to have been corrupted in some way and will need replacing with a new good copy. This process is known as ‘data scrubbing’. </span></p> <p><span lang="EN-US">Checksums are ideal for detecting if unwanted changes to digital materials have taken place. However, sometimes the digital materials will be changed deliberately, for example if a file format is migrated. This causes the checksum to change. This requires new checksums to be established after the migration which become the way of checking data integrity of the new file going forward.</span></p> <p><span lang="EN-US">Files should be checked against their checksums on a regular basis. How often to perform checks depends on many factors including the type of storage, how well it is maintained, and how often it is being used. As a general guideline, checking data tapes might be done annually and checking hard drive based systems might be done every six months. More frequent checks allow problems to be detected and fixed sooner, but at the expense of more load on the storage system and more processing resources.</span></p> <p><span lang="EN-US">Checksums can be stored in a variety of ways, for example within a <a href="/component/content/article/glossary?catid=78&Itemid=501">PREMIS</a> record, in a database, or within a ‘manifest’ that accompanies the files in a storage system. </span></p> <p><span lang="EN-US">Tool support is good for checksum generation and use. </span><span style="font-size: 1em;">As they are relatively simple functions, checksums are integrated into many other digital preservation tools. </span><span style="font-size: 1em;">For example, generating checksums as part of the ingest process and adding this fixity information to the Archive Information Packages generated, or allowing manifests of checksums to be generated for multiple files and for the manifest and files to be bundled together for easy transport or storage. In addition md5sum and md5deep provide simple command line tools that operate across platforms to generate checksums on individual files or directories.</span></p> <p><span lang="EN-US">There are several different checksum algorithms, e.g. MD5 and SHA-256 that can be used to generate checksums of increasing strength. The ‘stronger’ the algorithm then the harder it is to deliberately change a file in a way that goes undetected. This can be important for applications where there is a need to demonstrate resistance to malicious corruption or alteration of digital materials, for example where evidential weight and legal admissibility is important. However, if checksums are being used to detect accidental loss or damage to files, for example due to a storage failure, then MD5 is sufficient and has the advantage of being well supported in tools and is quick to calculate.</span></p> <p><span lang="EN-US">The Handbook follows the </span><span style="font-size: 1em;">National Digital Stewardship Alliance (NDSA) </span><span style="font-size: 1em;">preservation levels (</span><a href="#ref" style="font-size: 1em;">NDSA, 2013</a><span style="font-size: 1em;">) in recommending four levels at which digital preservation can be supported through file fixity and data integrity techniques. Many of the benefits of fixity checking can only be achieved if there are multiple copies of the digital materials, for example allowing repair if integrity of one of the copies has been lost.</span></p> <p><span lang="EN-US"></span></p> <table border="1" class="class" style="width: 650px; border: 1px solid #000000; background-color: #f0ffff;"> <tbody> <tr id="id" dir="dir" lang="lang" style="background-color: #7fffd4;"> <td> <h4>Level</h4> </td> <td> <h4>Activity</h4> </td> <td> <h4>Risks addressed and benefits achieved</h4> </td> </tr> <tr id="id" dir="dir" lang="lang" style="background-color: #f0ffff;"> <td> <p><span style="color: #07675b; font-family: Arial, Verdana, sans-serif; font-size: 1.4em; line-height: 18px; text-align: left;">1</span></p> <h4> </h4> </td> <td> <ul> <li><span style="font-size: 1em; line-height: 18px;">Check file fixity on ingest if it has been provided with the content.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Create fixity info if it wasn’t provided with the content.</span></li> </ul> </td> <td> <ul> <li><span style="font-size: 1em; line-height: 18px;">Corrupted or incorrect digital materials are not knowingly stored.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Authenticity of the digital materials can be asserted.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Baseline fixity established so unwanted data changes have potential to be detected.</span></li> </ul> </td> </tr> <tr id="id" dir="dir" lang="lang" style="background-color: #f0ffff;"> <td> <p><span style="font-size: 1.4em; line-height: 18px; text-align: left;">2</span></p> <h4> </h4> </td> <td> <ul> <li><span style="font-size: 1em; line-height: 18px;">Check fixity on all ingests</span></li> <li><span style="font-size: 1em; line-height: 18px;">Use write-blockers when working with original media</span></li> <li><span style="font-size: 1em; line-height: 18px;">Virus-check high risk content.</span></li> </ul> </td> <td> <ul> <li><span style="font-size: 1em; line-height: 18px;">No digital material of unconfirmed integrity can enter preservation storage. Evidential weight supported for authenticity.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Assurance can be given to all content providers that their content has been safely received. Original media is protected.</span></li> <li><span style="font-size: 1em; line-height: 18px;">No malicious content can enter preservation storage.</span></li> </ul> </td> </tr> <tr id="id" dir="dir" lang="lang" style="background-color: #f0ffff;"> <td> <p><span style="font-size: 1.4em; line-height: 18px; text-align: left;">3</span></p> <h4> </h4> </td> <td> <ul> <li><span style="font-size: 1em; line-height: 18px;">Check fixity of content held on preservation storage systems at regular intervals.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Maintain logs of fixity info and supply audit on demand.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Ability to detect corrupt data.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Virus-check all content.</span></li> </ul> </td> <td> <ul> <li><span style="font-size: 1em; line-height: 18px;">Protection from wide range of data corruption and loss events. Problems with storage are detected earlier.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Data corruption or loss does not go undetected due to ‘silent errors’ or ‘undetected failures'. Digital materials are not in a state of ‘unknown’ integrity.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Ongoing evidential weight can be given that digital materials are intact and correct.</span></li> </ul> </td> </tr> <tr id="id" dir="dir" lang="lang" style="background-color: #f0ffff;"> <td> <p><span style="color: #07675b; font-family: Arial, Verdana, sans-serif; font-size: 1.4em; line-height: 18px; text-align: left;">4</span></p> <h4> </h4> </td> <td> <ul> <li><span style="font-size: 1em; line-height: 18px;">Check fixity of all content in response to specific events or activities</span></li> <li><span style="font-size: 1em; line-height: 18px;">Ability to replace/repair corrupted data</span></li> <li><span style="font-size: 1em; line-height: 18px;">Ensure no one person has write access to all copies.</span></li> </ul> </td> <td> <ul> <li><span style="font-size: 1em; line-height: 18px;">Failure modes that threaten digital materials are proactively countered. All copies of digital materials are actively maintained.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Assurance to users of the integrity and authenticity of digital materials being accessed.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Effectiveness of preservation approach can be measured and demonstrated.</span></li> <li><span style="font-size: 1em; line-height: 18px;">Compliance with standards, e.g. ISO 16363 Audit and certification of trustworthy digital repositories.</span></li> </ul> </td> </tr> </tbody> </table> <p><span lang="EN-US"></span></p> <h2><span lang="EN-US">Write-blocking</span></h2> <p><span lang="EN-US"></span></p> <p><span lang="EN-US">Note that the </span><span style="font-size: 1em;">National Digital Stewardship Alliance (</span><span style="font-size: 1em;">NDSA) recommends the use of write-blockers at level 2. This is to prevent write access to media that digital materials might be on prior to being copied to the preservation storage system. For example, if digital material is delivered to an organisation on a hard disc drive or USB key then a write blocker would prevent accidental deletion of this digital material when the drive or key is read. Digital material might not be on physical media, e.g. it could be on a legacy storage server or delivered through a network transfer, e.g. an ftp upload. In these cases write blockers wouldn't apply and other measures would be used to make the digital material 'read only' on the source and hence immutable before confirmation that the digital material has been successfully transferred to preservation storage. Write blockers also don't exist for all types of media. If a write-blocker is applicable then the costs/skills required to use them should be balanced against the risk of damage to the original digital material or the need to have rigorous data authenticity. Therefore, some organisations might consider use of write blockers to be unnecessary or a level 3 or level 4 step.</span></p> <p> </p> <h2>Resources</h2> <p><img src="https://dpconline.b-cdn.net/images/bv_icon_publication.png" alt="" /></p> <h4>Bailey, J., 2014, Protect Your Data: File Fixity and Data Integrity, The Signal, Library of Congress.</h4> <p><a href="http://blogs.loc.gov/thesignal/2014/04/protect-your-data-file-fixity-and-data-integrity/">http://blogs.loc.gov/thesignal/2014/04/protect-your-data-file-fixity-and-data-integrity/</a></p> <h4>Checking Your Digital Content: What is Fixity and When Should I Be Checking It?</h4> <p><a href="http://digitalpreservation.gov/ndsa/working_groups/documents/NDSA-Fixity-Guidance-Report-final100214.pdf?loclr=blogsig">http://digitalpreservation.gov/ndsa/working_groups/documents/NDSA-Fixity-Guidance-Report-final100214.pdf?loclr=blogsig</a></p> <p>Many in the preservation community know they should be checking the fixity of their content, but how, when and how often? This document published by NDSA in 2014 aims to help stewards answer these questions in a way that makes sense for their organization based on their needs and resources (7 pages).</p> <p><img src="https://dpconline.b-cdn.net/images/bv_icon_tools.png" alt="" /></p> <h4>AVPreserve Fixity Tool</h4> <p><a href="http://www.avpreserve.com/tools/fixity/">http://www.avpreserve.com/tools/fixity/</a></p> <h4>MD5</h4> <p><a href="https://tools.ietf.org/html/rfc1321">https://tools.ietf.org/html/rfc1321</a></p> <h4>SHA-1</h4> <p><a href="http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf">http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf</a></p> <h4>SHA-256</h4> <p><a href="https://csrc.nist.gov/csrc/media/projects/cryptographic-standards-and-guidelines/documents/examples/sha256.pdf">https://csrc.nist.gov/csrc/media/projects/cryptographic-standards-and-guidelines/documents/examples/sha256.pdf</a></p> <h4>Md5deep and hashdeep</h4> <p><a href="http://coptr.digipres.org/Md5deep_and_hashdeep">http://coptr.digipres.org/Md5deep_and_hashdeep</a></p> <h4>md5sum</h4> <p><a href="http://coptr.digipres.org/Md5sum_Unix_command">http://coptr.digipres.org/Md5sum_Unix_command</a></p> <p><img src="https://dpconline.b-cdn.net/images/bv_icon_video.png" alt="" /></p> <h4>The "Checksum" and the Digital Preservation of Oral History</h4> <p><a href="https://www.youtube.com/watch?v=Emom_ncMqu0">https://www.youtube.com/watch?v=Emom_ncMqu0</a></p> <p>A good short overview not limited to oral history, this video provides a brief introduction to the role of the checksum in digital preservation. It features Doug Boyd, Director of the Louie B. Nunn Center for Oral History at the University of Kentucky Libraries. (3 mins 25 secs)</p> <p>  <div class="avPlayerWrapper avVideo"> <div class="avPlayerContainer"> <div id="AVPlayerID_0_db8303af30d32ecf7e3353d9dca19d63" class="avPlayerBlock"> <iframe src="https://www.youtube.com/embed/Emom_ncMqu0?rel=0&fs=1&wmode=transparent" width="400" height="300" allow="autoplay; fullscreen; encrypted-media" allowfullscreen="true" frameborder="0" scrolling="no" title="JoomlaWorks AllVideos Player"></iframe> </div> </div> </div>  </p> <h2><a id="ref"></a>References</h2> <p> </p> <p>Bailey, J., 2014. Protect Your Data: File Fixity and Data Integrity.<em>The Signal</em>. [blog]. Available: <a href="http://blogs.loc.gov/thesignal/2014/04/protect-your-data-file-fixity-and-data-integrity/">http://blogs.loc.gov/thesignal/2014/04/protect-your-data-file-fixity-and-data-integrity/</a></p> <p>ISO, 2012. ISO 14721:2012 - <em>Space Data and Information Transfer Systems – Open Archival Information System (OAIS) – Reference Model, 2nd edn</em>. Geneva: International Organization for Standardization. Available:<a href="https://www.iso.org/standard/57284.html">https://www.iso.org/standard/57284.html</a></p> <p>NDSA , 2013. <em>The NDSA Levels of Digital Preservation: An Explanation and Uses, version 1 2013</em>. National Digital Stewardship Alliance. Available: <a href="http://www.digitalpreservation.gov/ndsa/working_groups/documents/NDSA_Levels_Archiving_2013.pdf">http://www.digitalpreservation.gov/ndsa/working_groups/documents/NDSA_Levels_Archiving_2013.pdf</a></p> <p> </p> </div> </div> <div id="jc"> <div id="comments"></div> <div id="comments-form-link"> <a id="addcomments" class="showform" href="#addcomments" data-viewname="article" onclick="jcomment.showForm(110, 'com_content', 'comments-form-link', 'article'); return false;">Add comment</a> </div> </div> </div> </div> <div id="footer"> <div class="row" data-equalizer> <div class="small-12 medium-6 columns"> © 2024 Digital Preservation Coalition </div> <div class="small-12 medium-6 columns"> <ul class="mod-menu mod-list nav "> <li class="nav-item item-1015"><a href="/privacy" >Privacy Policy</a></li></ul> <p class="svg"> <svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 85 85" enable-background="new 0 0 85 85" xml:space="preserve"> <path display="inline" fill="#474341" d="M52.7,70.2v-7.8c0,0,0.3-9.4-10.8-9.4c-10.6,0-10.2,9.2-10.2,9.2l0,7.6 c0,6.9-5.9,6.3-5.9,6.3h-7.3c-6.5,0-5.4-6.7-5.4-6.7V46.7H7.8c0,0-5.6,0,1.7-7.4L32.9,14c0,0,3.8-5.1,8.5-5.1c4,0,5.7,2.6,8.5,5.7 l6.4,7.6l-0.3-7.8c0,0,0.2-4.4,6.7-4.4c0,0,6.8-0.1,6.8,4.9l-0.3,17.1l6.8,7.4c6.6,6.6,0.9,6.8,0.4,6.8c-0.5,0-6,0-6,0v24.2 c0,5.8-5.2,5.5-5.2,5.5l-7.7,0C57.7,76,52.7,76.8,52.7,70.2z"/> </svg> University Gardens, University of Glasgow, G12 8QQ </p> <p class="svg"> <svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 85 85" enable-background="new 0 0 85 85" xml:space="preserve"> <path display="inline" fill="#474341" d="M57.6,14.3H27.5c-3.9,0-7.1,3.2-7.1,7.1v51c0,3.9,3.2,7.1,7.1,7.1h30.1 c3.9,0,7.1-3.2,7.1-7.1v-51V8.1c0,0-0.1-2.4-2.2-2.4c-3,0-2.7,2.5-2.7,2.5v6.1L57.6,14.3z M36.8,74.8h-5.9v-5h5.9V74.8z M36.8,68.2 h-5.9v-5h5.9V68.2z M36.8,61.5h-5.9v-5h5.9V61.5z M45.8,74.8h-5.9v-5h5.9V74.8z M45.8,68.2h-5.9v-5h5.9V68.2z M45.8,61.5h-5.9v-5 h5.9V61.5z M54.9,74.8h-5.9v-5h5.9V74.8z M54.9,68.2h-5.9v-5h5.9V68.2z M54.9,61.5h-5.9v-5h5.9V61.5z M56.5,51.1H28.6V21.2h27.9 V51.1z"/> </svg> +44 (0) 141 330 2252 </p> <p class="svg"> <svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" x="0px" y="0px" viewBox="0 0 85 85" enable-background="new 0 0 85 85" xml:space="preserve"> <path fill="#474341" d="M15.2,22.6l27.5,26.4L70,22.6c0.1-0.1,0.2-0.1,0.3-0.2c-1.3-1-2.9-1.6-4.6-1.6H19.4c-1.7,0-3.3,0.6-4.6,1.6C14.9,22.4,15.1,22.5,15.2,22.6z"/> <path fill="#474341" d="M72,59c0.3,0.1,0.5,0.3,0.7,0.5c0.3-0.9,0.5-1.8,0.5-2.8V28.3c0-0.5-0.1-0.9-0.1-1.3L56.4,43.2C63.1,50.3,70.4,57.7,72,59z"/> <path fill="#474341" d="M52.5,47l-8,7.7c-0.5,0.5-1.2,0.8-1.9,0.8c-0.7,0-1.3-0.2-1.8-0.7l-8.2-7.9L16,63.4c1,0.5,2.2,0.8,3.4,0.8h46.3c1.2,0,2.3-0.3,3.4-0.8C66.9,61.9,62.7,57.6,52.5,47z"/> <path fill="#474341" d="M12,26.9c-0.1,0.5-0.1,0.9-0.1,1.4v28.4c0,1,0.2,1.9,0.5,2.8l16.5-16.4L12,26.9z"/> </svg> info (at) dpconline.org </p> </div> </div> </div> <script type="text/javascript" src="https://dpconline.b-cdn.net/templates/handbook/foundation/foundation.min.js?1717497718"></script> <script type="text/javascript"> $(document).foundation(); $(document).ready(function() { // $("input, textarea").placeholder(); }); </script> <script type="text/javascript" src="https://dpconline.b-cdn.net/templates/handbook/js/general.js?1717497718"></script> <script type="text/javascript" src="https://dpconline.b-cdn.net/templates/handbook/js/responsive-tables.js?1717497718"></script> </body> </html>