<?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: Beyond federated search?</title>
	<atom:link href="http://federatedsearchblog.com/2009/03/19/beyond-federated-search/feed/" rel="self" type="application/rss+xml" />
	<link>http://federatedsearchblog.com/2009/03/19/beyond-federated-search/</link>
	<description>Covers topics related to federated search and the deep web</description>
	<pubDate>Thu, 18 Mar 2010 00:51:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sol</title>
		<link>http://federatedsearchblog.com/2009/03/19/beyond-federated-search/comment-page-1/#comment-23341</link>
		<dc:creator>Sol</dc:creator>
		<pubDate>Fri, 10 Apr 2009 11:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/2009/03/19/beyond-federated-search/#comment-23341</guid>
		<description>Mike - I'm not disagreeing with you about what students will do when they don't find quick results. And, I don't disagree that harvest/index is great when you can get it. I'm just disturbed by the idea that students and libraries would give up valuable search results from good sources just because whoever they're getting results from doesn't include those good sources.</description>
		<content:encoded><![CDATA[<p>Mike - I&#8217;m not disagreeing with you about what students will do when they don&#8217;t find quick results. And, I don&#8217;t disagree that harvest/index is great when you can get it. I&#8217;m just disturbed by the idea that students and libraries would give up valuable search results from good sources just because whoever they&#8217;re getting results from doesn&#8217;t include those good sources.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://federatedsearchblog.com/2009/03/19/beyond-federated-search/comment-page-1/#comment-23303</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 10 Apr 2009 05:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/2009/03/19/beyond-federated-search/#comment-23303</guid>
		<description>If I or other Gen Yer's can't find what they are looking for in a matter of 1 minute, they will turn to Google and bypass the valued IP the library contains. Plain and simple. Simple discovery is a must for orgs to survive or go the way of Newspapers. Federated Search may have its place for the time being but is not the future, unified search across heterogeneous data sources is. Plain and simple.</description>
		<content:encoded><![CDATA[<p>If I or other Gen Yer&#8217;s can&#8217;t find what they are looking for in a matter of 1 minute, they will turn to Google and bypass the valued IP the library contains. Plain and simple. Simple discovery is a must for orgs to survive or go the way of Newspapers. Federated Search may have its place for the time being but is not the future, unified search across heterogeneous data sources is. Plain and simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry Bucknell</title>
		<link>http://federatedsearchblog.com/2009/03/19/beyond-federated-search/comment-page-1/#comment-22054</link>
		<dc:creator>Terry Bucknell</dc:creator>
		<pubDate>Wed, 25 Mar 2009 09:45:23 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/2009/03/19/beyond-federated-search/#comment-22054</guid>
		<description>It doesn't matter too much if a particular publisher doesn't allow Summon to harvest its content because Summon likely includes content from plenty of indexes that cover that content anyway.

And whay wouldn't publishers want to have their content included in Summon? Publishers quickly realised that by exposing their metadata to Google, usage of their articles shot up overnight. More use means more article purchases, more citations, higher impact. All the things that publishers and their authors want.

It is in publishers' best interests to make their content as discoverable as possible, whilst still maintaining access controls so that the actual content can only be viewed by subscribers/purchasers (unless it is OA).

I'd guess that technically it is much easier for publishers to expose their content to services like Summon than to implement SRU/SRW, z39.50 etc required for good federated searching.

Our users do not understand why Google can search 'everything' from a simple search box whereas our current federated search product only allows them to search up to 12 sites; has a large proportion of sites that aren't searchable at all; has some sites where the records are returned to the interface and others where you have to link out to see the results; only retrieves a small number of records from each site initially; why some resources take so long that they time out.

Federated search sends out the signal that the library is still old-fashioned and hard to use.</description>
		<content:encoded><![CDATA[<p>It doesn&#8217;t matter too much if a particular publisher doesn&#8217;t allow Summon to harvest its content because Summon likely includes content from plenty of indexes that cover that content anyway.</p>
<p>And whay wouldn&#8217;t publishers want to have their content included in Summon? Publishers quickly realised that by exposing their metadata to Google, usage of their articles shot up overnight. More use means more article purchases, more citations, higher impact. All the things that publishers and their authors want.</p>
<p>It is in publishers&#8217; best interests to make their content as discoverable as possible, whilst still maintaining access controls so that the actual content can only be viewed by subscribers/purchasers (unless it is OA).</p>
<p>I&#8217;d guess that technically it is much easier for publishers to expose their content to services like Summon than to implement SRU/SRW, z39.50 etc required for good federated searching.</p>
<p>Our users do not understand why Google can search &#8216;everything&#8217; from a simple search box whereas our current federated search product only allows them to search up to 12 sites; has a large proportion of sites that aren&#8217;t searchable at all; has some sites where the records are returned to the interface and others where you have to link out to see the results; only retrieves a small number of records from each site initially; why some resources take so long that they time out.</p>
<p>Federated search sends out the signal that the library is still old-fashioned and hard to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Rochkind</title>
		<link>http://federatedsearchblog.com/2009/03/19/beyond-federated-search/comment-page-1/#comment-21580</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Thu, 19 Mar 2009 22:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/2009/03/19/beyond-federated-search/#comment-21580</guid>
		<description>PS: And certainly there might be SOME content that is available via broadcast search but not summon. And vice versa.  Sure. For the academic research market, that's not important: What's important is we're already not being able to offer unified search of ALL content, so switching to a different set of "not all" with a much better user experience will be a win, if it's the right different set comparable in scope. 

The trick is indeed herding all that indexed metadata from many various sources. Summon's promise is that the vendor will do that for you. If it can be done reliably at an affordable price, and can encompass a range of content _comparable for our needs_ (not identical) to existing broadcast search solutions... it'll be a serious contender. 

The proof will be in the pudding of course.  From talking to SerSol folks, they know these are the hurdles they need to clear to make it a realistic product for the academic research market.  If they didn't think they had a chance of clearing them, they probably wouldn't be sending their R&amp;D money down a black hole.</description>
		<content:encoded><![CDATA[<p>PS: And certainly there might be SOME content that is available via broadcast search but not summon. And vice versa.  Sure. For the academic research market, that&#8217;s not important: What&#8217;s important is we&#8217;re already not being able to offer unified search of ALL content, so switching to a different set of &#8220;not all&#8221; with a much better user experience will be a win, if it&#8217;s the right different set comparable in scope. </p>
<p>The trick is indeed herding all that indexed metadata from many various sources. Summon&#8217;s promise is that the vendor will do that for you. If it can be done reliably at an affordable price, and can encompass a range of content _comparable for our needs_ (not identical) to existing broadcast search solutions&#8230; it&#8217;ll be a serious contender. </p>
<p>The proof will be in the pudding of course.  From talking to SerSol folks, they know these are the hurdles they need to clear to make it a realistic product for the academic research market.  If they didn&#8217;t think they had a chance of clearing them, they probably wouldn&#8217;t be sending their R&amp;D money down a black hole.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Rochkind</title>
		<link>http://federatedsearchblog.com/2009/03/19/beyond-federated-search/comment-page-1/#comment-21578</link>
		<dc:creator>Jonathan Rochkind</dc:creator>
		<pubDate>Thu, 19 Mar 2009 22:03:31 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/2009/03/19/beyond-federated-search/#comment-21578</guid>
		<description>"Until every single content provider makes the full-text of all of their documents that can be federated available for harvesting and indexing"

EVERY SINGLE content provider does NOT make their content available for federated search in the first place. Of the approximately 800 licensed databases we have listed in our collection, only about 300 are federated search-able.  The remainder are largely not there because of lack of functionality on the content provider's end, not on our fed search vendor's end. 

So that's a false comparison. 

If Summon can provide access to about the same amount of content as federated search, including our most important/most used content, it'll be a contender. 

A hybrid local index/broadcast search system is an obvious idea. But it's tricky to figure out how to search both classes of content in one search without bringing things down the lowest common denominator of fed search.</description>
		<content:encoded><![CDATA[<p>&#8220;Until every single content provider makes the full-text of all of their documents that can be federated available for harvesting and indexing&#8221;</p>
<p>EVERY SINGLE content provider does NOT make their content available for federated search in the first place. Of the approximately 800 licensed databases we have listed in our collection, only about 300 are federated search-able.  The remainder are largely not there because of lack of functionality on the content provider&#8217;s end, not on our fed search vendor&#8217;s end. </p>
<p>So that&#8217;s a false comparison. </p>
<p>If Summon can provide access to about the same amount of content as federated search, including our most important/most used content, it&#8217;ll be a contender. </p>
<p>A hybrid local index/broadcast search system is an obvious idea. But it&#8217;s tricky to figure out how to search both classes of content in one search without bringing things down the lowest common denominator of fed search.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
