<?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: Educating our systems</title>
	<atom:link href="http://copac.ac.uk/development-blog/2008/12/educating-our-systems/feed/" rel="self" type="application/rss+xml" />
	<link>http://copac.ac.uk/development-blog/2008/12/educating-our-systems/</link>
	<description>What's happening behind the scenes at Copac</description>
	<lastBuildDate>Fri, 27 Jan 2012 19:08:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: bethan</title>
		<link>http://copac.ac.uk/development-blog/2008/12/educating-our-systems/comment-page-1/#comment-72</link>
		<dc:creator>bethan</dc:creator>
		<pubDate>Thu, 04 Dec 2008 15:04:14 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=142#comment-72</guid>
		<description>I have to say that I thought the title of the workshop was rather misleading - very little was actually said throughout the day about &#039;competing with Google&#039;.  The theme that really stood out for me was that of giving users various paths to resource discovery, and allowing them to choose those which are best for them - including Google.  Several libraries mentioned that they are exposing their journal holdings to Google Scholar, to give students access to quality information in an environment they are comfortable and familiar with.  On re-reading my post, I see that I managed to completely leave this aspect out, for which I apologise!

Regular readers of this blog will know that we at Copac have been working to open up our content to Google through spidering - we are aiming to get the maximum possible exposure for our content, and are perfectly willing to exploit Google to get it :)

Unfortunately, I think any developments in library resource searching will reference Google (at least for the foreseeable future), just as anything a little bit interactive is &#039;library 2.0&#039;.  We have to accept that people will use these terms as easy contextualisation tools, even when they are not actually accurate descriptions of what is under discussion.

Quite a long-winded way of basically agreeing with you!</description>
		<content:encoded><![CDATA[<p>I have to say that I thought the title of the workshop was rather misleading &#8211; very little was actually said throughout the day about &#8216;competing with Google&#8217;.  The theme that really stood out for me was that of giving users various paths to resource discovery, and allowing them to choose those which are best for them &#8211; including Google.  Several libraries mentioned that they are exposing their journal holdings to Google Scholar, to give students access to quality information in an environment they are comfortable and familiar with.  On re-reading my post, I see that I managed to completely leave this aspect out, for which I apologise!</p>
<p>Regular readers of this blog will know that we at Copac have been working to open up our content to Google through spidering &#8211; we are aiming to get the maximum possible exposure for our content, and are perfectly willing to exploit Google to get it <img src='http://copac.ac.uk/development-blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Unfortunately, I think any developments in library resource searching will reference Google (at least for the foreseeable future), just as anything a little bit interactive is &#8216;library 2.0&#8242;.  We have to accept that people will use these terms as easy contextualisation tools, even when they are not actually accurate descriptions of what is under discussion.</p>
<p>Quite a long-winded way of basically agreeing with you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen Stephens</title>
		<link>http://copac.ac.uk/development-blog/2008/12/educating-our-systems/comment-page-1/#comment-71</link>
		<dc:creator>Owen Stephens</dc:creator>
		<pubDate>Thu, 04 Dec 2008 13:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=142#comment-71</guid>
		<description>Although the development of new search products for library resources is defintely interesting, I find it slightly worrying that this is being thought of in terms of &#039;competing with Google&#039;. We should rather be thinking of how we can best exploit Google and other search engines. Systems like Primo et al should open up new possibilities for this but supporting &#039;cool Uris&#039; for records and allowing output of records and results sets in web friendly formats like RSS. 

Amazon has a search engine, sure - but it doesn&#039;t treat this as &#039;competition&#039; to google. If you search for a book title in google, you are much more likely to get the amazon page for that book at the top of the results list than any library record - this is something libraries need to look at exploiting their systems, data and techniques like SEO (search engine optimization), sitemaps, and website analytics</description>
		<content:encoded><![CDATA[<p>Although the development of new search products for library resources is defintely interesting, I find it slightly worrying that this is being thought of in terms of &#8216;competing with Google&#8217;. We should rather be thinking of how we can best exploit Google and other search engines. Systems like Primo et al should open up new possibilities for this but supporting &#8216;cool Uris&#8217; for records and allowing output of records and results sets in web friendly formats like RSS. </p>
<p>Amazon has a search engine, sure &#8211; but it doesn&#8217;t treat this as &#8216;competition&#8217; to google. If you search for a book title in google, you are much more likely to get the amazon page for that book at the top of the results list than any library record &#8211; this is something libraries need to look at exploiting their systems, data and techniques like SEO (search engine optimization), sitemaps, and website analytics</p>
]]></content:encoded>
	</item>
</channel>
</rss>

