<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Digital Preservation Q&amp;A - Recent questions tagged parity</title>
<link>https://qanda.digipres.org/tag/parity</link>
<description>Powered by Question2Answer</description>
<item>
<title>Parity data for ISO images: anyone doing this? Best practices?</title>
<link>https://qanda.digipres.org/1117/parity-data-for-iso-images-anyone-doing-this-best-practices</link>
<description>&lt;p&gt;
	Earlier today I had a discussion with a colleague on possible ways to store (ISO) images of CD-ROMs and DVDs in our repository system. In addition to checksums, he suggested to also generate and store &lt;a rel=&quot;nofollow&quot; href=&quot;https://en.wikipedia.org/wiki/Parchive&quot;&gt;parity data&lt;/a&gt; for each image file (e.g. using the par2 tool: &lt;a rel=&quot;nofollow&quot; href=&quot;http://manpages.ubuntu.com/manpages/trusty/man1/par2.1.html&quot;&gt;http://manpages.ubuntu.com/manpages/trusty/man1/par2.1.html&lt;/a&gt;). This would enable one to repair files in case of bit-level corruption.&lt;br&gt;
	&lt;br&gt;
	This made me wonder how commonly parity info is used in digital archives, and if there are any best (or at least recommended) practices. E.g. what levels of redundancy are typically used? I'm not really familiar with this at all, and it's not a subject that is often mentioned in digital preservation discussions (but see &lt;a rel=&quot;nofollow&quot; href=&quot;https://twitter.com/anjacks0n/status/733281959762395139&quot;&gt;https://twitter.com/anjacks0n/status/733281959762395139&lt;/a&gt;).&lt;/p&gt;</description>
<guid isPermaLink="true">https://qanda.digipres.org/1117/parity-data-for-iso-images-anyone-doing-this-best-practices</guid>
<pubDate>Wed, 25 May 2016 13:48:28 +0000</pubDate>
</item>
</channel>
</rss>