<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Googlizing a Digital Library</title>
	<link>http://journal.code4lib.org/articles/43</link>
	<description></description>
	<pubDate>Thu, 07 Aug 2008 20:28:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Jody DeRidder</title>
		<link>http://journal.code4lib.org/articles/43#comment-44</link>
		<dc:creator>Jody DeRidder</dc:creator>
		<pubDate>Tue, 25 Mar 2008 19:34:27 +0000</pubDate>
		<guid>http://journal.code4lib.org/articles/43#comment-44</guid>
		<description>Hi Joe!
  Very cool. I'm surprised you'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's difficult to add those using the dynamic system.  
  I'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-42</link>
		<dc:creator>Joseph Shubitowski</dc:creator>
		<pubDate>Tue, 25 Mar 2008 15:20:01 +0000</pubDate>
		<guid>http://journal.code4lib.org/articles/43#comment-42</guid>
		<description>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 - 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::CMalG::90.R.11" rel="nofollow">http://archives.getty.edu:8082/cgi/f/findaid/findaid-idx?c=utf8a;idno=US::CMalG::90.R.11</a><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>
