<?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: Library search/discovery apps : intro</title>
	<atom:link href="http://www.nostuff.org/words/2009/library-searchdiscovery-apps-intro/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nostuff.org/words/2009/library-searchdiscovery-apps-intro/</link>
	<description>living up to its name</description>
	<lastBuildDate>Fri, 27 Nov 2009 07:48:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: 20091124 &#171; El blogsitorio</title>
		<link>http://www.nostuff.org/words/2009/library-searchdiscovery-apps-intro/comment-page-1/#comment-23399</link>
		<dc:creator>20091124 &#171; El blogsitorio</dc:creator>
		<pubDate>Tue, 24 Nov 2009 17:53:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.nostuff.org/words/?p=363#comment-23399</guid>
		<description>[...] Los OPACS del futuro (aunque fuera en Mayo), tendencias en referencia digital y unos ejemplos de [...]</description>
		<content:encoded><![CDATA[<p>[...] Los OPACS del futuro (aunque fuera en Mayo), tendencias en referencia digital y unos ejemplos de [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LILAC Conference: Day 2: New Library Catalogue Search Interfaces with Added Web 2.0 Capabilities &#171; Cabinet of Curiosities</title>
		<link>http://www.nostuff.org/words/2009/library-searchdiscovery-apps-intro/comment-page-1/#comment-18318</link>
		<dc:creator>LILAC Conference: Day 2: New Library Catalogue Search Interfaces with Added Web 2.0 Capabilities &#171; Cabinet of Curiosities</dc:creator>
		<pubDate>Thu, 28 May 2009 09:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.nostuff.org/words/?p=363#comment-18318</guid>
		<description>[...] of next generation catalogues is a blog post by Chirs Keene from the University of Sussex called Library search / discovery apps: intro, which is very up to date, having been written a couple of days [...]</description>
		<content:encoded><![CDATA[<p>[...] of next generation catalogues is a blog post by Chirs Keene from the University of Sussex called Library search / discovery apps: intro, which is very up to date, having been written a couple of days [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lukas Koster</title>
		<link>http://www.nostuff.org/words/2009/library-searchdiscovery-apps-intro/comment-page-1/#comment-18300</link>
		<dc:creator>Lukas Koster</dc:creator>
		<pubDate>Wed, 27 May 2009 22:54:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.nostuff.org/words/?p=363#comment-18300</guid>
		<description>Chris, nice overview. See also http://cccu-lib-tech.blogspot.com/2009/04/primo-alternatives.html for a list of tools (by Andy Ekins).
Couple of issues:
- All these discovery tools are not only OPAC replacements, as you rightly remark. 
- These tools use harvesting and create large local indexes, even from your own local catalogue (a number of the tools in the DLTJ list are not discovery tools); so basically no distributed metasearch (although they may offer metasearch &quot;addons&quot; like Primo)
- I personally think discovery tools are best implemented in a consortia environment or some other cooperation, not by a single library (not sure how you implemenetd Aquabrowser at Sussex)
- Obviously, the need to create large &quot;local&quot; indexes of everything is an indication of the fact that the administrative backends of our OPAC&#039;s and other Library Systems are not fit for the new digital &quot;cloud&quot; area; we need NOT ONLY sexy Front Ends, but first efficient back ends 
- The important thing here is the changing nature of the &quot;collection&quot; concept: no longer local physical collections, but global digital (see my post &quot;Collection 2.0&quot; ( http://commonplace.net/2009/02/collection-20/ )</description>
		<content:encoded><![CDATA[<p>Chris, nice overview. See also <a href="http://cccu-lib-tech.blogspot.com/2009/04/primo-alternatives.html" rel="nofollow">http://cccu-lib-tech.blogspot.com/2009/04/primo-alternatives.html</a> for a list of tools (by Andy Ekins).<br />
Couple of issues:<br />
- All these discovery tools are not only OPAC replacements, as you rightly remark.<br />
- These tools use harvesting and create large local indexes, even from your own local catalogue (a number of the tools in the DLTJ list are not discovery tools); so basically no distributed metasearch (although they may offer metasearch &#8220;addons&#8221; like Primo)<br />
- I personally think discovery tools are best implemented in a consortia environment or some other cooperation, not by a single library (not sure how you implemenetd Aquabrowser at Sussex)<br />
- Obviously, the need to create large &#8220;local&#8221; indexes of everything is an indication of the fact that the administrative backends of our OPAC&#8217;s and other Library Systems are not fit for the new digital &#8220;cloud&#8221; area; we need NOT ONLY sexy Front Ends, but first efficient back ends<br />
- The important thing here is the changing nature of the &#8220;collection&#8221; concept: no longer local physical collections, but global digital (see my post &#8220;Collection 2.0&#8243; ( <a href="http://commonplace.net/2009/02/collection-20/" rel="nofollow">http://commonplace.net/2009/02/collection-20/</a> )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Murray</title>
		<link>http://www.nostuff.org/words/2009/library-searchdiscovery-apps-intro/comment-page-1/#comment-18296</link>
		<dc:creator>Peter Murray</dc:creator>
		<pubDate>Wed, 27 May 2009 21:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.nostuff.org/words/?p=363#comment-18296</guid>
		<description>Great summary, Chris!

Aaron -- Summon is sort of like Google in that it is a large index of just about everything, but it differs in the way it gets the information to index.  As you noted, Google spiders the web for content.  Summon is more like OCLC or Ebsco or ProQuest -- information vendors give Serials Solutions a dump of information and SerSol adds it to their Summon index.</description>
		<content:encoded><![CDATA[<p>Great summary, Chris!</p>
<p>Aaron &#8212; Summon is sort of like Google in that it is a large index of just about everything, but it differs in the way it gets the information to index.  As you noted, Google spiders the web for content.  Summon is more like OCLC or Ebsco or ProQuest &#8212; information vendors give Serials Solutions a dump of information and SerSol adds it to their Summon index.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Tay</title>
		<link>http://www.nostuff.org/words/2009/library-searchdiscovery-apps-intro/comment-page-1/#comment-18287</link>
		<dc:creator>Aaron Tay</dc:creator>
		<pubDate>Wed, 27 May 2009 17:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.nostuff.org/words/?p=363#comment-18287</guid>
		<description>Wow. Very useful for me. I&#039;m doing a part-time phd on quantifying the value of OPACS using stated preference methods. E.g. Value patrons place on enhanced content (covers, tocs), faceted browsing, relevant ranking, tagging etc. Might blog about this sometime.

Your posts are interesting enough with the examples. Also they remind me that while to the user Encore (we use this)/Primo etc are replacing the OPAC, technically they are sitting on top.

Don&#039;t quite understand Summon. It&#039;s not a federated search, does that mean it indexes resources like google crawlers?</description>
		<content:encoded><![CDATA[<p>Wow. Very useful for me. I&#8217;m doing a part-time phd on quantifying the value of OPACS using stated preference methods. E.g. Value patrons place on enhanced content (covers, tocs), faceted browsing, relevant ranking, tagging etc. Might blog about this sometime.</p>
<p>Your posts are interesting enough with the examples. Also they remind me that while to the user Encore (we use this)/Primo etc are replacing the OPAC, technically they are sitting on top.</p>
<p>Don&#8217;t quite understand Summon. It&#8217;s not a federated search, does that mean it indexes resources like google crawlers?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.344 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-02-12 08:38:28 -->
<!-- Compression = gzip -->