<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>A Digital Outrigger&#187; Digital Preservation</title>
	<atom:link href="http://librarydigitalprojects.com/tag/digital-preservation/feed/" rel="self" type="application/rss+xml" />
	<link>http://librarydigitalprojects.com</link>
	<description>supporting research in digital libraries &#038; usability</description>
	<lastBuildDate>Sun, 07 Aug 2011 20:35:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>PLE: Curation Micro-Services</title>
		<link>http://librarydigitalprojects.com/2011/01/03/ple-curation-micro-services/</link>
		<comments>http://librarydigitalprojects.com/2011/01/03/ple-curation-micro-services/#comments</comments>
		<pubDate>Mon, 03 Jan 2011 20:43:56 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Libraries]]></category>
		<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[Curation Micro-Services]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=430</guid>
		<description><![CDATA[Over the next year I'm creating a plan for investigating and implementing digital curation micro-services in some form. A first step in this project is a learning environment on the topic.]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=PLE: Curation Micro-Services&amp;rft.source=A Digital Outrigger&amp;rft.date=2011-01-03&amp;rft.identifier=http://librarydigitalprojects.com/2011/01/03/ple-curation-micro-services/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Libraries&amp;rft.subject=Digital Preservation"></span>
<p>Over the next year I&#8217;m creating a plan for investigating and implementing digital curation micro-services in some form. A first step in this project is a learning environment on the topic.</p>
<p><a href="http://www.netvibes.com/stevemtzn#curation_micro-services_news">http://www.netvibes.com/stevemtzn#curation_micro-services_news</a></p>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2011/01/03/ple-curation-micro-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bookmark: Archivematica</title>
		<link>http://librarydigitalprojects.com/2010/11/10/bookmark-archivematica/</link>
		<comments>http://librarydigitalprojects.com/2010/11/10/bookmark-archivematica/#comments</comments>
		<pubDate>Wed, 10 Nov 2010 16:16:23 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[micro-services]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=428</guid>
		<description><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Bookmark: Archivematica&amp;rft.source=A Digital Outrigger&amp;rft.date=2010-11-10&amp;rft.identifier=http://librarydigitalprojects.com/2010/11/10/bookmark-archivematica/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation"></span>
Archivematica is an open source digital preservation platform using the micro-services design idea &#8220;that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model&#8221;.]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Bookmark: Archivematica&amp;rft.source=A Digital Outrigger&amp;rft.date=2010-11-10&amp;rft.identifier=http://librarydigitalprojects.com/2010/11/10/bookmark-archivematica/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation"></span>
<p><a href="http://archivematica.org/wiki/index.php?title=Main_Page" target="_self">Archivematica</a> is an open source digital preservation platform using the <a href="http://www.netvibes.com/stevemtzn" target="_blank">micro-services</a> design idea &#8220;that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model&#8221;.</p>
<p><a href="http://archivematica.org/wiki/index.php?title=Main_Page"><img class="alignnone" title="Archivematica" src="http://archivematica.org/logo.png" alt="" width="394" height="82" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2010/11/10/bookmark-archivematica/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Guide to Distributed Digital Preservation</title>
		<link>http://librarydigitalprojects.com/2010/03/11/guide-to-distributed-digital-preservation/</link>
		<comments>http://librarydigitalprojects.com/2010/03/11/guide-to-distributed-digital-preservation/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 18:10:11 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Preservation]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=378</guid>
		<description><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Guide to Distributed Digital Preservation&amp;rft.source=A Digital Outrigger&amp;rft.date=2010-03-11&amp;rft.identifier=http://librarydigitalprojects.com/2010/03/11/guide-to-distributed-digital-preservation/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation"></span>
The MetaArchive Cooperative has released a Guide to Distributed Digital Preservation: This volume is devoted to the broad topic of distributed digital preservation, a still-emerging field of practice for the cultural memory arena. Replication and distribution hold out the promise of indefinite preservation of materials without degradation, but establishing effective organizational and technical processes to [...]]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Guide to Distributed Digital Preservation&amp;rft.source=A Digital Outrigger&amp;rft.date=2010-03-11&amp;rft.identifier=http://librarydigitalprojects.com/2010/03/11/guide-to-distributed-digital-preservation/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation"></span>
<p>The <a href="http://www.metaarchive.org/" target="_blank">MetaArchive Cooperative</a> has released a <a href="http://www.metaarchive.org/GDDP" target="_blank">Guide to Distributed Digital Preservation</a>:</p>
<blockquote><p>This volume is devoted to the broad topic of distributed digital  preservation, a still-emerging field of practice for the cultural memory  arena. Replication and distribution hold out the promise of indefinite  preservation of materials without degradation, but establishing  effective organizational and technical processes to enable this form of  digital preservation is daunting. Institutions need practical examples  of how this task can be accomplished in manageable, low-cost ways.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2010/03/11/guide-to-distributed-digital-preservation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scanned Master Files Compared</title>
		<link>http://librarydigitalprojects.com/2009/07/08/scanned-master-files-compared/</link>
		<comments>http://librarydigitalprojects.com/2009/07/08/scanned-master-files-compared/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 17:15:50 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Libraries]]></category>
		<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[digitization]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=319</guid>
		<description><![CDATA[Here's a quick chart that specifies the amount of disk space a single scanned 8.5" x 11" master file will take up.]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Scanned Master Files Compared&amp;rft.source=A Digital Outrigger&amp;rft.date=2009-07-08&amp;rft.identifier=http://librarydigitalprojects.com/2009/07/08/scanned-master-files-compared/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Libraries&amp;rft.subject=Digital Preservation"></span>
<p>Here&#8217;s a quick chart that specifies the amount of disk space a single scanned 8.5&#8243; x 11&#8243; master file will take up. Pixels per inch (PPI) and bit levels were taken largely from the <a href="http://bcr.org/dps/cdp/best/digital-imaging-bp.pdf" target="_blank">BCR best practices document</a>. These estimates were generated with PhotoShop CS4.</p>
<table style="border-collapse: collapse; height: 107px;" border="0" cellspacing="0" cellpadding="0" width="464">
<col style="width: 103pt;" width="137"></col>
<col style="width: 45pt;" width="60"></col>
<col style="width: 50pt;" span="4" width="67"></col>
<tbody>
<tr style="height: 12.75pt;" height="17">
<td style="height: 12.75pt; width: 103pt; font-size: 10pt; color: #010000; font-weight: 700; text-decoration: none; font-family: Arial;" width="137" height="17">8.5&#8243; x   11&#8243; Original</td>
<td style="width: 45pt; font-size: 10pt; color: #010000; font-weight: 700; text-decoration: none; font-family: Arial;" width="60">72 ppi</td>
<td style="width: 50pt; font-size: 10pt; color: #010000; font-weight: 700; text-decoration: none; font-family: Arial;" width="67">150 ppi</td>
<td style="width: 50pt; font-size: 10pt; color: #010000; font-weight: 700; text-decoration: none; font-family: Arial;" width="67">300 ppi</td>
<td style="width: 50pt; font-size: 10pt; color: #010000; font-weight: 700; text-decoration: none; font-family: Arial;" width="67">400 ppi</td>
<td style="width: 50pt; font-size: 10pt; color: #010000; font-weight: 700; text-decoration: none; font-family: Arial;" width="67">600 ppi</td>
</tr>
<tr style="height: 12.75pt;" height="17">
<td style="background: #e5e0ec none repeat scroll 0% 0%; height: 12.75pt; width: 103pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="137" height="17">2 bit (B &amp;   W)</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 45pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="60">60k</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">258k</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">1.0 MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">1.7 MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">3.9 MB</td>
</tr>
<tr style="height: 12.75pt;" height="17">
<td style="height: 12.75pt; width: 103pt;" width="137" height="17">8 bit   (Grayscale)</td>
<td style="border-top: medium none; border-left: medium none; width: 45pt;" width="60">473k</td>
<td style="border-top: medium none; border-left: medium none; width: 50pt;" width="67">2   MB</td>
<td style="border-top: medium none; border-left: medium none; width: 50pt;" width="67">8.0   MB</td>
<td style="border-top: medium none; border-left: medium none; width: 50pt;" width="67">14.0   MB</td>
<td style="border-top: medium none; border-left: medium none; width: 50pt;" width="67">31.4   MB</td>
</tr>
<tr style="height: 12.75pt;" height="17">
<td style="background: #e5e0ec none repeat scroll 0% 0%; height: 12.75pt; width: 103pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="137" height="17">16 bit   (Grayscale)</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 45pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="60">947k</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">4 MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">16.1   MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">27.9   MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">62.9   MB</td>
</tr>
<tr style="height: 12.75pt;" height="17">
<td style="height: 12.75pt; width: 103pt;" width="137" height="17">24 bit   (Color)</td>
<td style="border-top: medium none; border-left: medium none; width: 45pt;" width="60">1.4   MB</td>
<td style="border-top: medium none; border-left: medium none; width: 50pt;" width="67">5.9   MB</td>
<td style="border-top: medium none; border-left: medium none; width: 50pt;" width="67">23.6   MB</td>
<td style="border-top: medium none; border-left: medium none; width: 50pt;" width="67">41.9   MB</td>
<td style="border-top: medium none; border-left: medium none; width: 50pt;" width="67">94.3   MB</td>
</tr>
<tr style="height: 12.75pt;" height="17">
<td style="background: #e5e0ec none repeat scroll 0% 0%; height: 12.75pt; width: 103pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="137" height="17">48 bit (Color)</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 45pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="60">2.7 MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">11.8   MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">47.2   MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">83.8   MB</td>
<td style="border: 0.5pt solid #010000; background: #e5e0ec none repeat scroll 0% 0%; width: 50pt; font-size: 10pt; color: #010000; font-weight: 400; text-decoration: none; font-family: Arial;" width="67">188.6   MB</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2009/07/08/scanned-master-files-compared/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JHOVE and Reconstructibility</title>
		<link>http://librarydigitalprojects.com/2009/03/23/jhove-and-reconstructibility/</link>
		<comments>http://librarydigitalprojects.com/2009/03/23/jhove-and-reconstructibility/#comments</comments>
		<pubDate>Tue, 24 Mar 2009 01:31:18 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Preservation]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=268</guid>
		<description><![CDATA[Garry McGath has an interesting post up over at File Formats Blog arguing for a little wiggle room within file format preservation:]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=JHOVE and Reconstructibility&amp;rft.source=A Digital Outrigger&amp;rft.date=2009-03-23&amp;rft.identifier=http://librarydigitalprojects.com/2009/03/23/jhove-and-reconstructibility/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation"></span>
<p>Gary McGath has an interesting post up over at File Formats Blog arguing for a little wiggle room within <a href="http://fileformats.blogspot.com/2009/03/reconstructability-and-digital.html" target="_blank">file format preservation</a>:</p>
<blockquote><p>JHOVE 1.x takes a &#8220;one strike, you&#8217;re out&#8221; approach to compliance, with certain exceptions. &#8230; JHOVE2 improves on this by introducing the concept of <em>assessment</em>. &#8230; What I&#8217;m proposing here is that a metric of assessment should be <em>reconstructability</em>, the degree to which a file can be reconstructed in spite of non-standard aspects in its content or structure.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2009/03/23/jhove-and-reconstructibility/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UConn Survey on JPEG2000 Use</title>
		<link>http://librarydigitalprojects.com/2009/02/02/uconn-survey-on-jpeg2000-use/</link>
		<comments>http://librarydigitalprojects.com/2009/02/02/uconn-survey-on-jpeg2000-use/#comments</comments>
		<pubDate>Mon, 02 Feb 2009 07:00:53 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Libraries]]></category>
		<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[jpeg 2000]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=244</guid>
		<description><![CDATA[Found this posted earlier last week via Digital Koans: Digital Project Staff Survey of JPEG 2000 Implementation in Libraries]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=UConn Survey on JPEG2000 Use&amp;rft.source=A Digital Outrigger&amp;rft.date=2009-02-02&amp;rft.identifier=http://librarydigitalprojects.com/2009/02/02/uconn-survey-on-jpeg2000-use/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Libraries&amp;rft.subject=Digital Preservation"></span>
<p>Found this posted earlier last week via <a href="http://digital-scholarship.org/digitalkoans/2009/01/28/digital-project-staff-survey-of-jpeg-2000-implementation-in-libraries/" target="_blank">Digital Koans</a>:</p>
<p><a href="http://digitalcommons.uconn.edu/libr_pubs/16/" target="_blank">Digital Project Staff Survey of JPEG 2000 Implementation in Libraries</a></p>
<p>The data is presented in an xls, that includes all survey questions and comments from those who volunteered information. What I thought was most interesting was that only 60% of respondents (out of 173 total) were using <a href="http://en.wikipedia.org/wiki/JPEG_2000" target="_blank">JPEG2000</a> in any way. The followup question was &#8220;if not, why not&#8221;, and the general themes include the lack of tools, adoption, and understanding of the format.</p>
<p>For digital preservation, or archival uses, only 20% were making use of the format. There are a lot of very interesting tidbits in this spreadsheet.</p>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2009/02/02/uconn-survey-on-jpeg2000-use/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Effects of Open Source on Preservation</title>
		<link>http://librarydigitalprojects.com/2009/01/05/effects-of-open-source-on-preservation/</link>
		<comments>http://librarydigitalprojects.com/2009/01/05/effects-of-open-source-on-preservation/#comments</comments>
		<pubDate>Mon, 05 Jan 2009 16:34:46 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[management]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=201</guid>
		<description><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Effects of Open Source on Preservation&amp;rft.source=A Digital Outrigger&amp;rft.date=2009-01-05&amp;rft.identifier=http://librarydigitalprojects.com/2009/01/05/effects-of-open-source-on-preservation/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation"></span>
David Rosenthal has a detailed and useful analysis of the value of open format specifications for preservation: If we plot the quality achieved by a newly created renderer for a format against the cost of creating it we will get an S curve. A certain amount of money is needed to get to a barely [...]]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Effects of Open Source on Preservation&amp;rft.source=A Digital Outrigger&amp;rft.date=2009-01-05&amp;rft.identifier=http://librarydigitalprojects.com/2009/01/05/effects-of-open-source-on-preservation/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation"></span>
<p><span>David Rosenthal has a detailed and useful analysis of the </span><a href="http://blog.dshr.org/2009/01/are-format-specifications-important-for.html" target="_blank">value of open format specifications for preservation</a>:</p>
<blockquote><p><span class="fullpost">If we plot the quality achieved by a newly created renderer for a format against the cost of creating it we will get an S curve. A certain amount of money is needed to get to a barely functional renderer. Beyond that, quality increases rapidly at first but after a while the law of diminishing returns sets in. Getting from 99% to 99.9% is very expensive; the cost of getting to 100% is infinite. &#8230; </span><span class="fullpost"><strong>It seems clear that preserving the specification for a format is unlikely to have any practical impact on the preservation of documents in that format.</strong> If, during the currency of the format, it acquires an open source renderer there is no significant risk of ever ending up without a functional renderer. The need for a new one to be created from the specification is extremely unlikely ever to arise. If that unlikely event ever happened, it is hard to believe that resources on the scale needed to do the job would be available. And in the unlikely event that they were, it is unreasonable to believe that the combination of the preserved specification and the available resources would be enough to create a renderer that would satisfy those who reject Open Office because of minor rendering flaws.</span></p>
<p>Don&#8217;t let the perfect be the enemy of the good.</p>
<p><span class="fullpost">Clearly, formats with open source renderers are, for all practical purposes, immune from format obsolescence. &#8230; </span></p></blockquote>
<p><span class="fullpost">[emphasis mine]</span></p>
<p><span class="fullpost">&#8212;</span></p>
<p>Addendum:</p>
<p><span class="fullpost">Chris Rusbridge <a href="http://digitalcuration.blogspot.com/2009/01/specifications-again.html" target="_blank">makes some good points</a> and offers a summary of the <a href="http://digitalcuration.blogspot.com/2009/01/specifications-again.html" target="_blank"><a href="http://digitalcuration.blogspot.com/2009/01/email-discussion-on-usefulness-of-file.html" target="_blank">DCC email thread</a><br />
</a></span></p>
<p><span class="fullpost"><br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2009/01/05/effects-of-open-source-on-preservation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Usability Over Time</title>
		<link>http://librarydigitalprojects.com/2009/01/01/usability-over-time/</link>
		<comments>http://librarydigitalprojects.com/2009/01/01/usability-over-time/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 20:20:44 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=199</guid>
		<description><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Usability Over Time&amp;rft.source=A Digital Outrigger&amp;rft.date=2009-01-01&amp;rft.identifier=http://librarydigitalprojects.com/2009/01/01/usability-over-time/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation&amp;rft.subject=Usability"></span>
Found this useful idea by Chris Rusbridge from a year-end review by Jill Hurst-Wahl: It’s not just the language that makes digital preservation unconvincing to the decision maker. Part of the problem is that digital preservation describes a process, and not an outcome. &#8230; So I would argue that outcome-related phrases like &#8220;long term accessibility&#8221; [...]]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Usability Over Time&amp;rft.source=A Digital Outrigger&amp;rft.date=2009-01-01&amp;rft.identifier=http://librarydigitalprojects.com/2009/01/01/usability-over-time/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Preservation&amp;rft.subject=Usability"></span>
<p>Found this <a href="http://digitalcuration.blogspot.com/2008/07/digital-preservation-term-considered.html" target="_blank">useful idea </a>by Chris Rusbridge from a year-end review by <a href="http://hurstassociates.blogspot.com/2008/12/digitization-101-2008-year-in-review.html" target="_blank">Jill Hurst-Wahl:</a></p>
<blockquote><p>It’s not just the language that makes digital preservation unconvincing to the decision maker. Part of the problem is that digital preservation describes a process, and not an outcome. &#8230; So I would argue that outcome-related phrases like &#8220;long term accessibility&#8221; or &#8220;usability over time&#8221; are better than the process-oriented phrase &#8220;digital preservation&#8221;.</p></blockquote>
<p>This makes good sense to me, sorry I missed it earlier in the year.</p>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2009/01/01/usability-over-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blue Ribbon Task Force on the coming &#8220;Data Deluge&#8221;</title>
		<link>http://librarydigitalprojects.com/2008/12/17/blue-ribbon-task-force-on-the-coming-data-deluge/</link>
		<comments>http://librarydigitalprojects.com/2008/12/17/blue-ribbon-task-force-on-the-coming-data-deluge/#comments</comments>
		<pubDate>Wed, 17 Dec 2008 16:56:44 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Libraries]]></category>
		<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[digitization]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=179</guid>
		<description><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Blue Ribbon Task Force on the coming &#8220;Data Deluge&#8221;&amp;rft.source=A Digital Outrigger&amp;rft.date=2008-12-17&amp;rft.identifier=http://librarydigitalprojects.com/2008/12/17/blue-ribbon-task-force-on-the-coming-data-deluge/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Libraries&amp;rft.subject=Digital Preservation"></span>
Reading a press release out of UCSD, this comment  from the Blue Ribbon Task Force on Sustainable Digital Preservation and Access [pdf] caught my eye: A recent study by the International Data Corporation (IDC) said that in 2007, the amount of digital data began to exceed the amount of storage to retain it, and will [...]]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Blue Ribbon Task Force on the coming &#8220;Data Deluge&#8221;&amp;rft.source=A Digital Outrigger&amp;rft.date=2008-12-17&amp;rft.identifier=http://librarydigitalprojects.com/2008/12/17/blue-ribbon-task-force-on-the-coming-data-deluge/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Libraries&amp;rft.subject=Digital Preservation"></span>
<p>Reading a <a href="http://ucsdnews.ucsd.edu/newsrel/general/12-08BRTF.asp" target="_blank">press release out of UCSD</a>, this comment  from the <em>Blue Ribbon Task Force on Sustainable Digital Preservation and Access </em>[<a href="http://brtf.sdsc.edu/biblio/BRTF_Interim_Report.pdf" target="_blank">pdf</a>] caught my eye:</p>
<blockquote><p>A recent study by the International Data Corporation (IDC) said that in 2007, the amount of digital data began to exceed the amount of storage to retain it, and will continue to grow faster than storage capacity from here on. <strong>The IDC study predicts that by 2011, our “digital universe”</strong> &#8230; <strong>will be 10 times the size it was in 2006.</strong></p></blockquote>
<p>That sounds about right, and is a little alarming. The University of Montana Mansfield Library recently digitized a run of Salish-Kootenai tribal newspapers called the <a href="http://skclibrary.skc.edu/charkoosta.html" target="_blank">Char-Koosta News</a>.  While this was a relatively small project, it still amounted to the creation of 26,633 files at 253 GB of storage (and that doesn&#8217;t include what&#8217;s available on the public website.) If we are able to ramp up production 10x by 2011, we&#8217;re looking at an additional 2.5TB of data and possibly 270k files that will need to preserved, both compressed and uncompressed, from that point forward. It&#8217;s a bit staggering.</p>
<p>The report has a list of coming challenges seem spot on to me:</p>
<ul>
<li>Inadequacy of funding models to address long-term access and preservation needs.</li>
<li>Confusion and/or lack of alignment between stakeholders, roles, and responsibilities with respect to digital access and preservation.</li>
<li>Inadequate institutional, enterprise, and/or community incentives to support the collaboration needed to reinforce sustainable economic models.</li>
<li>Complacency that current practices are “good enough.”</li>
<li>Fear that digital access and preservation is too big to take on.</li>
</ul>
<p>The last two bulletts will be the two I&#8217;ll be focusing on initially here at worrk.</p>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2008/12/17/blue-ribbon-task-force-on-the-coming-data-deluge/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building a Scanning Studio from Scratch</title>
		<link>http://librarydigitalprojects.com/2008/12/09/building-a-scanning-studio-from-scratch/</link>
		<comments>http://librarydigitalprojects.com/2008/12/09/building-a-scanning-studio-from-scratch/#comments</comments>
		<pubDate>Tue, 09 Dec 2008 20:00:07 +0000</pubDate>
		<dc:creator>Steve McCann</dc:creator>
				<category><![CDATA[Digital Libraries]]></category>
		<category><![CDATA[Digital Preservation]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://librarydigitalprojects.com/?p=165</guid>
		<description><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Building a Scanning Studio from Scratch&amp;rft.source=A Digital Outrigger&amp;rft.date=2008-12-09&amp;rft.identifier=http://librarydigitalprojects.com/2008/12/09/building-a-scanning-studio-from-scratch/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Libraries&amp;rft.subject=Digital Preservation"></span>
I&#8217;ve been asked by a small-sized museum / special library to make a suggestion on what kind of equipment a start-up digitization studio would need while operating under a budget of approximately $3,200. This studio would need the cabability of digitizing photos, and possibly some text, post-processing the scans, hosting the images on an existing [...]]]></description>
			<content:encoded><![CDATA[<span class="Z3988" title="ctx_ver=Z39.88-2004&amp;rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&amp;rfr_id=info%3Asid%2Focoins.info%3Agenerator&amp;rft.type=&amp;rft.format=text&amp;rft.title=Building a Scanning Studio from Scratch&amp;rft.source=A Digital Outrigger&amp;rft.date=2008-12-09&amp;rft.identifier=http://librarydigitalprojects.com/2008/12/09/building-a-scanning-studio-from-scratch/&amp;rft.language=English&amp;rft.aulast=McCann&amp;rft.aufirst=Steve&amp;rft.subject=Digital Libraries&amp;rft.subject=Digital Preservation"></span>
<p>I&#8217;ve been asked by a small-sized museum / special library to make a suggestion on what kind of equipment a start-up digitization studio would need while operating under a budget of approximately $3,200. This studio would need the cabability of digitizing photos, and possibly some text, post-processing the scans, hosting the images on an existing web server, and then preserving the master scans. It&#8217;s an interesting project, and one that can easily be accomplished within a tight budget. By putting the recommendation online, I&#8217;m hoping that others will find this and make further recommendations on the following:<span id="more-165"></span></p>
<p>Here are the criteria for the digitization studio:</p>
<ol>
<li>Budget of $3,200</li>
<li>Manageable by a staff of basically one, with minimal to no technical support</li>
<li>Capable of digitizing photos &amp; text according the best practices per the <a href="http://www.bcr.org/cdp/best/index.html" target="_blank">BCR Digital Imaging</a> document</li>
<li>Capable of long-term preservation of master files</li>
<li>Capable of public access to the resulting web-ready scans</li>
</ol>
<p>Here are some recommendations using the lowest prices (found via <a href="http://www.google.com/products" target="_blank">Google Product Search</a>) as of this writing:</p>
<h3>Scanning</h3>
<p>Computer-Baseline: <strong>$600</strong></p>
<p>What&#8217;s amazing to me is that a baseline studio-ready PC can be had for as little as $600, maybe less. While it&#8217;s easy to spend more, as long as it has a minimum of 2GB memory and 100GB+ hard drive you&#8217;re good to go. Upgrade options here include a larger monitor and more memory. Macs will be more expensive, but can be a good solution.</p>
<p>Scanner-Baseline: <strong>$735</strong></p>
<p><a href="http://www.plustek.com/product/book4600.asp" target="_blank">PlusTek OpticBook 4600</a>: I&#8217;ve used the OpticBook 3600 previously and was very happy with it. It offers a scanning area that is good enough for 8 1/2&#8243; x 11&#8243; photos while also being configured to drape books over the side in a way that won&#8217;t break the binding and still allows you to get deep into the gutter of the page.</p>
<p><a href="http://www.plustek.com/product/book4600.asp"><img class="alignnone size-medium wp-image-166" title="PlusTek OpticBook4600" src="http://librarydigitalprojects.com/wp-content/uploads/2008/12/book4600.jpg" alt="" width="300" height="214" /></a></p>
<p>Upgrade option &#8211; <a href="http://www.epson.com/cgi-bin/Store/consumer/consDetail.jsp?BV_UseBVCookie=yes&amp;oid=46048262" target="_blank">Epson 10000XL Photo</a>: $2,500. This scanner has excellent dynamic range, which for photos is paramount but comes at a price. Other options include a digital camera, but if you go in this direction you&#8217;ll need to worry about lighting and dealing with RAW files. For a start-up studio that may be more trouble than it&#8217;s worth.</p>
<h3>Post-Processing and Quality Control</h3>
<p>Image-processing baseline: <strong>$176</strong></p>
<p><a href="http://en.wikipedia.org/wiki/Adobe_Photoshop " target="_blank">Photoshop CS3</a> is probably your best option. The latest version is <a href="http://www.adobe.com/products/photoshop/photoshop " target="_blank">CS4</a>, but for a start-up studio the earlier version is going to work fine. This software will be used to run the scanner for capturing master images and to create derivative files that are web-ready. Price: $150</p>
<p>Alternately, the open-source software <a href="http://www.gimp.org/ " target="_blank">Gimp</a> is an excellent solution. It will do almost everything that Photoshop can do. The only downside is if your just learning image manipulation, most of the tutorials available are for Photoshop. Price: Free</p>
<p><strong>Tutorials</strong>: Ben Willmore&#8217;s <a href="http://www.amazon.com/Adobe-Photoshop-CS3-Studio-Techniques/dp/0321510461/ " target="_blank">Photoshop CS3 Studio Techniques</a> is an invaluable resource. It will walk you through everything you need to know to make web-ready derivatives: straightening, cropping, adjusting levels, sharpening, resizing, etc. Price: $26</p>
<p><strong>File Name Editing</strong>: <a href="http://www.bulkrenameutility.co.uk/Main_Intro.php " target="_blank">Bulk Rename Utility</a> is a good resource for renaming an entire directory-worth of files. This is an invaluable resource and free.</p>
<p><strong>Image Quality Control</strong>: I find <a href="http://www.irfanview.com/ " target="_blank">IrfanView</a> to be an excellent, light-weight, and fast image viewer. This is crucial if you need to browse through a couple thousand images quickly and easily. It also has the capability to do some simple image editing, like cropping. Price: Free</p>
<p><strong>Optical Character Recognition</strong>: OCR will give you the capability to convert images of text to actual text. This will allow you to create PDFs as well as text files of the scans. Most scanners come with the Sprint version of <a href="http://www.abbyyusa.com/shop/ " target="_blank">Abbyy FineReader</a>, which is fine for starting out. Upgrade to the Pro version is a good idea when the studio expands its capabilities. Price: Free ($179 for an upgrade to Pro)</p>
<h3><strong>Public Image Presentation</strong></h3>
<p>Hosting Baseline: <strong>Free</strong> (as in &#8220;free puppy&#8221;)</p>
<p><a href="http://www.greenstone.org/ " target="_blank">Greenstone</a> is open-source hosting software designed with the small institution in mind. As long as you have a web server to place files on, you&#8217;re good to go. Alternately, you can go with <a href="http://www.oclc.org/contentdm/ " target="_blank">CONTENTdm</a>, which has either a hosted option or a version that you host yourself. Fees for this can be quite steep, so moving to this later may be an option. One caveat: if technical support is not available to you, getting content you&#8217;ve placed on Greenstone into CONTENTdm is not trivial. Plan on rebuilding your collections from scratch with any migration. Price: Free</p>
<h3>Long-Term Preservation</h3>
<p>Preservation Baseline: <strong>$749</strong></p>
<p>This is about ensuring that the master files created in a digitization studio can be kept indefinitely, at least on a bit bit level. Migration, emulation, etc. is another issue entirely. (Most istitutions are taking the attitude that we&#8217;ll burn that bridge when we come to it.) For a small institution without a network, what&#8217;s needed is redundant storage that&#8217;s easy to maintain. Data Robotics has an elegant solution in its <a href="http://www.drobo.com/" target="_blank">Drobo</a> product. It accepts cheap and easily purchased hard drives which it monitors for you to guard against bit rot (which is inevitable, eventually). If a drive goes bad, you simply replace it and Drobo manages the reformatting and transfer for you. With this setup two copies would be kept: one on the scanning computer, and one on the Drobo. If it&#8217;s also possible to keep another copy on a network, that would help spread the risk.</p>
<h3>Grand Total: $2,260</h3>
<p>That&#8217;s about $1,000 below budget, which will give you room to maneuver. Upgrading from here I&#8217;d recommend getting as large a monitor as possible, upgrading the ram of the computer to 4GB, and possibly finding a scanner somewhere between the OpticBook and the Epson.</p>
<p>Comments and suggestions are welcome.</p>
]]></content:encoded>
			<wfw:commentRss>http://librarydigitalprojects.com/2008/12/09/building-a-scanning-studio-from-scratch/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

