<?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: Googlizing a Digital Library</title>
	<atom:link href="http://journal.code4lib.org/articles/43/feed" rel="self" type="application/rss+xml" />
	<link>http://journal.code4lib.org/articles/43</link>
	<description></description>
	<lastBuildDate>Sat, 11 May 2013 17:16:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: The Code4Lib Journal &#8211; Googlizing a Digital Library &#187; Web Design</title>
		<link>http://journal.code4lib.org/articles/43/comment-page-1#comment-5971</link>
		<dc:creator>The Code4Lib Journal &#8211; Googlizing a Digital Library &#187; Web Design</dc:creator>
		<pubDate>Wed, 14 Mar 2012 22:40:42 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/43#comment-5971</guid>
		<description><![CDATA[[...] The Code4Lib Journal &#8211; Googlizing a Digital Library [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The Code4Lib Journal &#8211; Googlizing a Digital Library [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Theobald</title>
		<link>http://journal.code4lib.org/articles/43/comment-page-1#comment-1272</link>
		<dc:creator>Matthew Theobald</dc:creator>
		<pubDate>Tue, 16 Dec 2008 04:46:54 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/43#comment-1272</guid>
		<description><![CDATA[The deep, invisible and hidden web are the common terms.  More recently the idea of the &quot;structured&quot; web has risen.  ISEN.org has a solution for cataloging digital libraries coming from a library and information science perspective.  You might investigate our project and feel free to ask questions.]]></description>
		<content:encoded><![CDATA[<p>The deep, invisible and hidden web are the common terms.  More recently the idea of the &#8220;structured&#8221; web has risen.  ISEN.org has a solution for cataloging digital libraries coming from a library and information science perspective.  You might investigate our project and feel free to ask questions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurie Phillips</title>
		<link>http://journal.code4lib.org/articles/43/comment-page-1#comment-1270</link>
		<dc:creator>Laurie Phillips</dc:creator>
		<pubDate>Mon, 15 Dec 2008 15:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/43#comment-1270</guid>
		<description><![CDATA[You say:
&quot;While directed query engines are an area of intense research...&quot;
I am doing some research on the deep web and can&#039;t find any recent references to the term &quot;directed query engine&quot;. Is this a common concept that is usually called by another name?
Thanks in advance.]]></description>
		<content:encoded><![CDATA[<p>You say:<br />
&#8220;While directed query engines are an area of intense research&#8230;&#8221;<br />
I am doing some research on the deep web and can&#8217;t find any recent references to the term &#8220;directed query engine&#8221;. Is this a common concept that is usually called by another name?<br />
Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jody DeRidder</title>
		<link>http://journal.code4lib.org/articles/43/comment-page-1#comment-44</link>
		<dc:creator>Jody DeRidder</dc:creator>
		<pubDate>Tue, 25 Mar 2008 19:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/43#comment-44</guid>
		<description><![CDATA[Hi Joe!
  Very cool. I&#039;m surprised you&#039;re not having them index the full text, however.  Why not?  It will maximize the access to your information. Ours was using DLXS12.  Is Google using your browse pages at all?  Our static ones really made a difference in our hits, and I think the hidden metatags helped too, though I know it&#039;s difficult to add those using the dynamic system.  
  I&#039;d also thought about using rewrites of URLs to redirect the crawlers...]]></description>
		<content:encoded><![CDATA[<p>Hi Joe!<br />
  Very cool. I&#8217;m surprised you&#8217;re not having them index the full text, however.  Why not?  It will maximize the access to your information. Ours was using DLXS12.  Is Google using your browse pages at all?  Our static ones really made a difference in our hits, and I think the hidden metatags helped too, though I know it&#8217;s difficult to add those using the dynamic system.<br />
  I&#8217;d also thought about using rewrites of URLs to redirect the crawlers&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Shubitowski</title>
		<link>http://journal.code4lib.org/articles/43/comment-page-1#comment-42</link>
		<dc:creator>Joseph Shubitowski</dc:creator>
		<pubDate>Tue, 25 Mar 2008 15:20:01 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/articles/43#comment-42</guid>
		<description><![CDATA[Jody - most interesting as are working through all the same issue here with our DLXS collections. We have version 13 up now and find that we can submit sitemaps to Google with URLs in the form of:
http://archives.getty.edu:8082/cgi/f/findaid/findaid-idx?c=utf8a;idno=US::CMalG::90.R.11
that go directly to the correct dynamic page in DLXS. We have tweaked the title tags so that we get the title we want Google to see and index, and after a week, we are seeing good results and relatively high rankings.

Previously, we were on version 11a and had generated static cached pages that we used for both indexing and retrieval (as DLXS speed was a problem). The switch to 13 allowed us to dump all that staic work. Tom Burton-West did all that work here at GRI before going to UMich last year to join the DLPS/DLXS team.

Great article! Thanks for sharing all the detail and the research.

Joe Shubitowski]]></description>
		<content:encoded><![CDATA[<p>Jody &#8211; most interesting as are working through all the same issue here with our DLXS collections. We have version 13 up now and find that we can submit sitemaps to Google with URLs in the form of:<br />
<a href="http://archives.getty.edu:8082/cgi/f/findaid/findaid-idx?c=utf8a;idno=US" rel="nofollow">http://archives.getty.edu:8082/cgi/f/findaid/findaid-idx?c=utf8a;idno=US</a>::CMalG::90.R.11<br />
that go directly to the correct dynamic page in DLXS. We have tweaked the title tags so that we get the title we want Google to see and index, and after a week, we are seeing good results and relatively high rankings.</p>
<p>Previously, we were on version 11a and had generated static cached pages that we used for both indexing and retrieval (as DLXS speed was a problem). The switch to 13 allowed us to dump all that staic work. Tom Burton-West did all that work here at GRI before going to UMich last year to join the DLPS/DLXS team.</p>
<p>Great article! Thanks for sharing all the detail and the research.</p>
<p>Joe Shubitowski</p>
]]></content:encoded>
	</item>
</channel>
</rss>
