<?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/"
		>
<channel>
	<title>Comments on: Our hidden digital libraries</title>
	<atom:link href="http://scholarlypublishing.org/jpwilkin/archives/14/feed" rel="self" type="application/rss+xml" />
	<link>http://scholarlypublishing.org/jpwilkin/archives/14</link>
	<description>John's blog on libraries, library technology, and pizza</description>
	<lastBuildDate>Sun, 03 Jan 2010 16:01:13 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: theorywatch &#187; Blog Archive &#187; Thinking about collections 12</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-1119</link>
		<dc:creator>theorywatch &#187; Blog Archive &#187; Thinking about collections 12</dc:creator>
		<pubDate>Sun, 17 Aug 2008 06:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-1119</guid>
		<description>[...] of Michigan library maven John Wilkin has some very interesting thoughts about  &#8220;hidden&#8221; digital collections and making them more accessible via Google. Intriguing that we&#8217;ve so quickly come to this [...]</description>
		<content:encoded><![CDATA[<p>[...] of Michigan library maven John Wilkin has some very interesting thoughts about  &#8220;hidden&#8221; digital collections and making them more accessible via Google. Intriguing that we&#8217;ve so quickly come to this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PabloG &#187; Blog Archive &#187; links for 2008-07-31 [delicious.com]</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-1020</link>
		<dc:creator>PabloG &#187; Blog Archive &#187; links for 2008-07-31 [delicious.com]</dc:creator>
		<pubDate>Fri, 01 Aug 2008 01:31:41 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-1020</guid>
		<description>[...] John Wilkin’s blog » Our hidden digital libraries (tags: google webinvisible webdesign digitallibraries bibliothèques library DocumentNumerique crawler interface moteur searchengine) [...]</description>
		<content:encoded><![CDATA[<p>[...] John Wilkin’s blog » Our hidden digital libraries (tags: google webinvisible webdesign digitallibraries bibliothèques library DocumentNumerique crawler interface moteur searchengine) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Weinheimer</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-1008</link>
		<dc:creator>James Weinheimer</dc:creator>
		<pubDate>Wed, 30 Jul 2008 10:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-1008</guid>
		<description>I don&#039;t know if I completely agree with you that simplified text files are &quot;good enough&quot; (that may have to wait for practical tests) but I do agree that our materials must be in Google--for better or worse. Google has decided that they want XML sitemaps, and to be fair, it looks as if Google at least tried our way (OAI-PMH). 

So, why don&#039;t we give them their XML sitemaps? It seems to me easier than OAI-PMH, and we may find out that they, and you, are correct. If it doesn&#039;t work, that could be interesting as well.

In either case, it would certainly be better than our materials being left out of Google searches.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if I completely agree with you that simplified text files are &#8220;good enough&#8221; (that may have to wait for practical tests) but I do agree that our materials must be in Google&#8211;for better or worse. Google has decided that they want XML sitemaps, and to be fair, it looks as if Google at least tried our way (OAI-PMH). </p>
<p>So, why don&#8217;t we give them their XML sitemaps? It seems to me easier than OAI-PMH, and we may find out that they, and you, are correct. If it doesn&#8217;t work, that could be interesting as well.</p>
<p>In either case, it would certainly be better than our materials being left out of Google searches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google and the academic Deep Web at WoW! Wouter on the Web</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-987</link>
		<dc:creator>Google and the academic Deep Web at WoW! Wouter on the Web</dc:creator>
		<pubDate>Mon, 28 Jul 2008 14:18:15 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-987</guid>
		<description>[...] indexing of repositories? Hagendorn and Santell point the finger to Google indeed. However, John Wilkin, a colleague of them, doesn’t agree. Just as Lorcan Dempsey didn’t. And neither do [...]</description>
		<content:encoded><![CDATA[<p>[...] indexing of repositories? Hagendorn and Santell point the finger to Google indeed. However, John Wilkin, a colleague of them, doesn’t agree. Just as Lorcan Dempsey didn’t. And neither do [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jpwilkin</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-986</link>
		<dc:creator>jpwilkin</dc:creator>
		<pubDate>Mon, 28 Jul 2008 13:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-986</guid>
		<description>I should have noticed Roy Tennant&#039;s piece on this, http://hangingtogether.org/?p=475 (A Map to Destinations Uncrawled).  A great analysis of the problem and of strategies.</description>
		<content:encoded><![CDATA[<p>I should have noticed Roy Tennant&#8217;s piece on this, <a href="http://hangingtogether.org/?p=475" rel="nofollow">http://hangingtogether.org/?p=475</a> (A Map to Destinations Uncrawled).  A great analysis of the problem and of strategies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jpwilkin</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-985</link>
		<dc:creator>jpwilkin</dc:creator>
		<pubDate>Mon, 28 Jul 2008 13:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-985</guid>
		<description>You betcha.  The difference is really about maintaining the objects (there&#039;s much that you can do with them in formats that aren&#039;t native to the Web) and flexibility (e.g., you can &#039;express&#039; them in a variety of different ways).  I&#039;m sure there&#039;s a large body of literature on this by now.  I did a few pieces related to this in the early/mid-90&#039;s, including a D-Lib article (&quot;Just-in-time Conversion, Just-in-case Collections&quot;) and a couple of things for the journal Public-Access Computer Systems Review (including, for example, &quot;Using the World-Wide Web to Deliver Complex Electronic Documents: Implications for Libraries&quot;).</description>
		<content:encoded><![CDATA[<p>You betcha.  The difference is really about maintaining the objects (there&#8217;s much that you can do with them in formats that aren&#8217;t native to the Web) and flexibility (e.g., you can &#8216;express&#8217; them in a variety of different ways).  I&#8217;m sure there&#8217;s a large body of literature on this by now.  I did a few pieces related to this in the early/mid-90&#8217;s, including a D-Lib article (&#8221;Just-in-time Conversion, Just-in-case Collections&#8221;) and a couple of things for the journal Public-Access Computer Systems Review (including, for example, &#8220;Using the World-Wide Web to Deliver Complex Electronic Documents: Implications for Libraries&#8221;).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ignorance</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-982</link>
		<dc:creator>ignorance</dc:creator>
		<pubDate>Mon, 28 Jul 2008 02:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-982</guid>
		<description>Isn&#039;t there a difference between *storing* digital library as HTML and representing it that way for users to find?</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t there a difference between *storing* digital library as HTML and representing it that way for users to find?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Theobald</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-981</link>
		<dc:creator>Matthew Theobald</dc:creator>
		<pubDate>Mon, 28 Jul 2008 01:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-981</guid>
		<description>John,

You might investigate the ISEN initiative.  We&#039;re pretty quiet now, but building up a voice toward revealing the entire hidden, invisible and deep WWW.

-m@</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>You might investigate the ISEN initiative.  We&#8217;re pretty quiet now, but building up a voice toward revealing the entire hidden, invisible and deep WWW.</p>
<p>-m@</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Shaw</title>
		<link>http://scholarlypublishing.org/jpwilkin/archives/14/comment-page-1#comment-977</link>
		<dc:creator>Ryan Shaw</dc:creator>
		<pubDate>Sun, 27 Jul 2008 19:50:46 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlypublishing.org/jpwilkin/archives/14#comment-977</guid>
		<description>&quot;...too much trouble for the value of the content.&quot;

This is precisely why we must avoid putting corporations in charge of our cultural heritage: despite claims to be &quot;organizing the world&#039;s information,&quot; they really are only interested in organizing the subset of information that will bring them advertising revenues. Unless one believes that this subset is all that&#039;s worth organizing, one ought to firmly reject the idea that Google and its ilk are anything more than advertising companies that provide useful tools. Adopt SEO techniques and manipulate them to draw traffic to our resources? Certainly. Trust them as stewards of those resources? Hell no.</description>
		<content:encoded><![CDATA[<p>&#8220;&#8230;too much trouble for the value of the content.&#8221;</p>
<p>This is precisely why we must avoid putting corporations in charge of our cultural heritage: despite claims to be &#8220;organizing the world&#8217;s information,&#8221; they really are only interested in organizing the subset of information that will bring them advertising revenues. Unless one believes that this subset is all that&#8217;s worth organizing, one ought to firmly reject the idea that Google and its ilk are anything more than advertising companies that provide useful tools. Adopt SEO techniques and manipulate them to draw traffic to our resources? Certainly. Trust them as stewards of those resources? Hell no.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
