<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" 	>
<channel>
	<title>Comments on: My big fat digital humanities preservation idea</title>
	<atom:link href="http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/feed/" rel="self" type="application/rss+xml" />
	<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/</link>
	<description>K.G. Schneider's blog on librarianship, writing, and everything else</description>
	<lastBuildDate>Thu, 18 Mar 2010 01:17:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrea GillaspyStein</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-504323</link>
		<dc:creator>Andrea GillaspyStein</dc:creator>
		<pubDate>Sat, 05 Sep 2009 04:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-504323</guid>
		<description>I believe the format migration issue is a concern.  I also believe this can be related to your post about Google pulling copies of works without copyright permission.  When we are talking about digital material, we are talking about material which is fluid.  While lots of copies can keep stuff safe, and while LOCSSdoes promise to keep the format viable - we are relying on outside technology.  The words might change, the format might change, bits might be lost over time.  Maintaining a readable format is a good idea - but consider the effect if e.e. cummings&#039; poems were reduced to the words, all left justified, andif typed in word 2007 they would all have capitals at the beginning of the lines. 
 
Now, another possible thing to consider here, as formats change, is whether that is an issue.  When we went from an oral tradition to a print tradition, I expect soem people were concerned that the words would become static.  As an erstwhile storyteller, I know this can be a problem - stories are meant to be alive and to change.  Print is not.  As we move digitally, and format can affect the content (remembering those 60&#039;s words of Marshall Macluen &quot;the medium is the message&quot;)are we reapproaching the oral era?</description>
		<content:encoded><![CDATA[<p>I believe the format migration issue is a concern.  I also believe this can be related to your post about Google pulling copies of works without copyright permission.  When we are talking about digital material, we are talking about material which is fluid.  While lots of copies can keep stuff safe, and while LOCSSdoes promise to keep the format viable &#8211; we are relying on outside technology.  The words might change, the format might change, bits might be lost over time.  Maintaining a readable format is a good idea &#8211; but consider the effect if e.e. cummings&#8217; poems were reduced to the words, all left justified, andif typed in word 2007 they would all have capitals at the beginning of the lines. </p>
<p>Now, another possible thing to consider here, as formats change, is whether that is an issue.  When we went from an oral tradition to a print tradition, I expect soem people were concerned that the words would become static.  As an erstwhile storyteller, I know this can be a problem &#8211; stories are meant to be alive and to change.  Print is not.  As we move digitally, and format can affect the content (remembering those 60&#8217;s words of Marshall Macluen &#8220;the medium is the message&#8221;)are we reapproaching the oral era?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Free Range Librarian &#8250; Bristlecone: A Practical Plan for Practical Dogfooders</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-502860</link>
		<dc:creator>Free Range Librarian &#8250; Bristlecone: A Practical Plan for Practical Dogfooders</dc:creator>
		<pubDate>Wed, 02 Sep 2009 02:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-502860</guid>
		<description>[...] response to my vision of Bristlecone &#8211; a preservation plan for literary journals &#8212; Mary Molinaro wrote, Her idea of a [...]</description>
		<content:encoded><![CDATA[<p>[...] response to my vision of Bristlecone &#8211; a preservation plan for literary journals &#8212; Mary Molinaro wrote, Her idea of a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Rusbridge</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-495861</link>
		<dc:creator>Chris Rusbridge</dc:creator>
		<pubDate>Thu, 20 Aug 2009 10:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-495861</guid>
		<description>I think this is a great idea, and LOCKSS is ideal for the task; in this case there is no particular need to create a separate LOCKSS network, as far as I can see. As JMO notes, there is already a wide LOCKSS network available for preserving journal content, and a separate one should only be created if strictly needed. For the existing network, the marginal cost of including these journals, once they have been included, is extremely low.

Before that can be achieved, however, two things are needed: first, the content development task, of identifying the desired content, persuading those who run the LOCKSS boxes to agree to include the content, and persuading the proprietors of the journals to agree to the relatively small changes that are needed to allow their content to be collected. Second, a certain amount of (not very) technical work has to be done, in the creation of LOCKSS plugins and manifest pages (if memory serves me right). Some of this is currently done by the LOCKSS team, some has to be done with or by the people who host the journal pages. This work seems to me to be a scalability limitation of LOCKSS at the moment, but with greater community involvement that limitation might go away.

LOCKSS has good capabilities for dealing with the open/closed access issues you mention. In a way, the detailed efforts to deal properly with copyright introduce some of those scalability issues.

Oh, and on the sustainability issue, highly distributed and cheap beats centralised and expensive any day. Just think of the dreadful words &quot;policy change&quot; or &quot;funding cuts&quot;. We can&#039;t rely on government to do these things. Sustainability is us!

I would strongly encourage you to be in touch with Vicky Reich of the LOCKSS team...</description>
		<content:encoded><![CDATA[<p>I think this is a great idea, and LOCKSS is ideal for the task; in this case there is no particular need to create a separate LOCKSS network, as far as I can see. As JMO notes, there is already a wide LOCKSS network available for preserving journal content, and a separate one should only be created if strictly needed. For the existing network, the marginal cost of including these journals, once they have been included, is extremely low.</p>
<p>Before that can be achieved, however, two things are needed: first, the content development task, of identifying the desired content, persuading those who run the LOCKSS boxes to agree to include the content, and persuading the proprietors of the journals to agree to the relatively small changes that are needed to allow their content to be collected. Second, a certain amount of (not very) technical work has to be done, in the creation of LOCKSS plugins and manifest pages (if memory serves me right). Some of this is currently done by the LOCKSS team, some has to be done with or by the people who host the journal pages. This work seems to me to be a scalability limitation of LOCKSS at the moment, but with greater community involvement that limitation might go away.</p>
<p>LOCKSS has good capabilities for dealing with the open/closed access issues you mention. In a way, the detailed efforts to deal properly with copyright introduce some of those scalability issues.</p>
<p>Oh, and on the sustainability issue, highly distributed and cheap beats centralised and expensive any day. Just think of the dreadful words &#8220;policy change&#8221; or &#8220;funding cuts&#8221;. We can&#8217;t rely on government to do these things. Sustainability is us!</p>
<p>I would strongly encourage you to be in touch with Vicky Reich of the LOCKSS team&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Press here &#171; Jurn blog</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-495101</link>
		<dc:creator>Press here &#171; Jurn blog</dc:creator>
		<pubDate>Wed, 19 Aug 2009 04:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-495101</guid>
		<description>[...] August 2009 in Spotted in the news    A proposal for a preservation plan for small-press literary journals.       [...]</description>
		<content:encoded><![CDATA[<p>[...] August 2009 in Spotted in the news    A proposal for a preservation plan for small-press literary journals.       [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: K.G. Schneider</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-493577</link>
		<dc:creator>K.G. Schneider</dc:creator>
		<pubDate>Sun, 16 Aug 2009 12:36:27 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-493577</guid>
		<description>Thanks, John. I&#039;m winding up to a much longer explanation of why Bristlecone would work and clarifying some of the misconceptions presented in Mary&#039;s post. 

There are really a number of existing LOCKSS networks, and if Mary is right, then none of them should exist. (But Mary is not right.) I also take issue with the pejorative use of the word &quot;lofty&quot; with respect to a last-copy proposal... but I&#039;ll wait for my longer response before addressing her post in detail. If nothing else, it&#039;s an excellent set-up for what I will next write. ;)</description>
		<content:encoded><![CDATA[<p>Thanks, John. I&#8217;m winding up to a much longer explanation of why Bristlecone would work and clarifying some of the misconceptions presented in Mary&#8217;s post. </p>
<p>There are really a number of existing LOCKSS networks, and if Mary is right, then none of them should exist. (But Mary is not right.) I also take issue with the pejorative use of the word &#8220;lofty&#8221; with respect to a last-copy proposal&#8230; but I&#8217;ll wait for my longer response before addressing her post in detail. If nothing else, it&#8217;s an excellent set-up for what I will next write. <img src='http://freerangelibrarian.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Mark Ockerbloom</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-491682</link>
		<dc:creator>John Mark Ockerbloom</dc:creator>
		<pubDate>Thu, 13 Aug 2009 14:07:21 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-491682</guid>
		<description>I&#039;ve replied to some of Mary&#039;s concerns on her blog.  (Because of moderation, the reply might not show up right away.)

In a nutshell: given that a LOCKSS journal preservation network already exists, this proposal isn&#039;t so much creating a new &quot;separate and unequal&quot; preservation system as it is integrating more literary journals into an established, working, and scalable system.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve replied to some of Mary&#8217;s concerns on her blog.  (Because of moderation, the reply might not show up right away.)</p>
<p>In a nutshell: given that a LOCKSS journal preservation network already exists, this proposal isn&#8217;t so much creating a new &#8220;separate and unequal&#8221; preservation system as it is integrating more literary journals into an established, working, and scalable system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary Molinaro</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-486709</link>
		<dc:creator>Mary Molinaro</dc:creator>
		<pubDate>Wed, 05 Aug 2009 03:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-486709</guid>
		<description>Respectfully I believe this idea limits the possibility of long term sustainability.  In order to be sustainable in the larger picture this content should be integrated into the cyberinfrastructure being developed with NSF funding to accommodate science (and other) data. More fully explained in my blog post at http://tinyurl.com/mxaptn</description>
		<content:encoded><![CDATA[<p>Respectfully I believe this idea limits the possibility of long term sustainability.  In order to be sustainable in the larger picture this content should be integrated into the cyberinfrastructure being developed with NSF funding to accommodate science (and other) data. More fully explained in my blog post at <a href="http://tinyurl.com/mxaptn" rel="nofollow">http://tinyurl.com/mxaptn</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Free Range Librarian › My big fat digital humanities preservation idea &#171; The Rejuvenation Station</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-486420</link>
		<dc:creator>Free Range Librarian › My big fat digital humanities preservation idea &#171; The Rejuvenation Station</dc:creator>
		<pubDate>Tue, 04 Aug 2009 18:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-486420</guid>
		<description>[...] Free Range Librarian › My big fat digital humanities preservation idea. [...]</description>
		<content:encoded><![CDATA[<p>[...] Free Range Librarian › My big fat digital humanities preservation idea. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Susie Lorand</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-485806</link>
		<dc:creator>Susie Lorand</dc:creator>
		<pubDate>Mon, 03 Aug 2009 12:45:53 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-485806</guid>
		<description>Thanks for naming and sharing this idea!

In the second paragraph of &lt;b&gt;Respect for publishing models&lt;/b&gt;, did you mean to continue this thought? &quot;Also, as noted earlier, the subscription model&quot;</description>
		<content:encoded><![CDATA[<p>Thanks for naming and sharing this idea!</p>
<p>In the second paragraph of <b>Respect for publishing models</b>, did you mean to continue this thought? &#8220;Also, as noted earlier, the subscription model&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miriam B.</title>
		<link>http://freerangelibrarian.com/2009/08/02/my-big-fat-digital-humanities-preservation-idea/comment-page-1/#comment-485494</link>
		<dc:creator>Miriam B.</dc:creator>
		<pubDate>Mon, 03 Aug 2009 00:01:51 +0000</pubDate>
		<guid isPermaLink="false">http://freerangelibrarian.com/?p=2225#comment-485494</guid>
		<description>Carolyn, others know more but I don&#039;t think indexing is part of the mission. The storage protection is basically having a minimum of I think six LOCKSS members each storing the particular title in their LOCKSS box-- the acronym means Lots of Copies Keeps Stuff Safe. Poking around at random, it looks like almost all titles are &quot;committed for preservation by all LOCKSS boxes.&quot; Of which there seem to be hundreds. LOCKSS preserves my teeny-tiny born digital poetry magazine http://www.lockss.org/lockss/Santa_Fe_Poetry_Broadside 
http://sfpoetry.org/LOCKSS/manifest2009.html</description>
		<content:encoded><![CDATA[<p>Carolyn, others know more but I don&#8217;t think indexing is part of the mission. The storage protection is basically having a minimum of I think six LOCKSS members each storing the particular title in their LOCKSS box&#8211; the acronym means Lots of Copies Keeps Stuff Safe. Poking around at random, it looks like almost all titles are &#8220;committed for preservation by all LOCKSS boxes.&#8221; Of which there seem to be hundreds. LOCKSS preserves my teeny-tiny born digital poetry magazine <a href="http://www.lockss.org/lockss/Santa_Fe_Poetry_Broadside" rel="nofollow">http://www.lockss.org/lockss/Santa_Fe_Poetry_Broadside</a><br />
<a href="http://sfpoetry.org/LOCKSS/manifest2009.html" rel="nofollow">http://sfpoetry.org/LOCKSS/manifest2009.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.412 seconds -->
