<?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: Diagnosing federated search source problems: it&#8217;s harder than you think</title>
	<atom:link href="http://federatedsearchblog.com/2008/06/23/diagnosing-federated-search-source-problems-its-harder-than-you-think/feed/" rel="self" type="application/rss+xml" />
	<link>http://federatedsearchblog.com/2008/06/23/diagnosing-federated-search-source-problems-its-harder-than-you-think/</link>
	<description>Covers topics related to federated search and the deep web</description>
	<lastBuildDate>Thu, 15 Mar 2012 12:26:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Ian Ibbotson</title>
		<link>http://federatedsearchblog.com/2008/06/23/diagnosing-federated-search-source-problems-its-harder-than-you-think/comment-page-1/#comment-2214</link>
		<dc:creator>Ian Ibbotson</dc:creator>
		<pubDate>Wed, 25 Jun 2008 07:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/2008/06/23/diagnosing-federated-search-source-problems-its-harder-than-you-think/#comment-2214</guid>
		<description>I do feel this is the price we have to pay for letting the argument &quot;Z3950 and SRU/SRW are too hard, here, let me provide you with an alternate programatic interface&quot; win instead of making it ever easier to implement the standards the search community has agreed on. 

Those well defined standards take effort to implement, but they aren&#039;t *hard*. They take effort to implement because they define mechanisims for explicity dealing with a whole range of error conditions and edge cases like this. When a vendor comes up with a quick and dirty way to search source &#039;X&#039; it&#039;s seen as fair competitive advantage, and the pressure on source &#039;X&#039; to implement a real standard is reduced. It&#039;s really a loose-loose situation for the information network.

I think a related interesting question is what common metaphor should be used for communicating this kind of diagnostic information back to the user. It&#039;s horribly difficult to strike a balance between the google search page people first say they want, and the interface that exposes just enough information about the federation process without getting in the way of the search task itself.</description>
		<content:encoded><![CDATA[<p>I do feel this is the price we have to pay for letting the argument &#8220;Z3950 and SRU/SRW are too hard, here, let me provide you with an alternate programatic interface&#8221; win instead of making it ever easier to implement the standards the search community has agreed on. </p>
<p>Those well defined standards take effort to implement, but they aren&#8217;t *hard*. They take effort to implement because they define mechanisims for explicity dealing with a whole range of error conditions and edge cases like this. When a vendor comes up with a quick and dirty way to search source &#8216;X&#8217; it&#8217;s seen as fair competitive advantage, and the pressure on source &#8216;X&#8217; to implement a real standard is reduced. It&#8217;s really a loose-loose situation for the information network.</p>
<p>I think a related interesting question is what common metaphor should be used for communicating this kind of diagnostic information back to the user. It&#8217;s horribly difficult to strike a balance between the google search page people first say they want, and the interface that exposes just enough information about the federation process without getting in the way of the search task itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lukas Koster</title>
		<link>http://federatedsearchblog.com/2008/06/23/diagnosing-federated-search-source-problems-its-harder-than-you-think/comment-page-1/#comment-2197</link>
		<dc:creator>Lukas Koster</dc:creator>
		<pubDate>Mon, 23 Jun 2008 19:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/2008/06/23/diagnosing-federated-search-source-problems-its-harder-than-you-think/#comment-2197</guid>
		<description>1 - There is no clear unified federated search user community platform that content owners like Pubmed can communicate with, unless they contact all known federated search tool vendors (and then they do not reach customers with home grown tools)

2 - Federated search tool vendors do not have often do not have access to all sources, so they can&#039;t monitor all sources continuously

3 - Information by vendors through the federated search application’s search page works only for hosted customers, not for local installations

4 - The only way of continuous monitoring that really works is  an active and cooperative user/customer community; per federated search tool.</description>
		<content:encoded><![CDATA[<p>1 &#8211; There is no clear unified federated search user community platform that content owners like Pubmed can communicate with, unless they contact all known federated search tool vendors (and then they do not reach customers with home grown tools)</p>
<p>2 &#8211; Federated search tool vendors do not have often do not have access to all sources, so they can&#8217;t monitor all sources continuously</p>
<p>3 &#8211; Information by vendors through the federated search application’s search page works only for hosted customers, not for local installations</p>
<p>4 &#8211; The only way of continuous monitoring that really works is  an active and cooperative user/customer community; per federated search tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jakob</title>
		<link>http://federatedsearchblog.com/2008/06/23/diagnosing-federated-search-source-problems-its-harder-than-you-think/comment-page-1/#comment-2195</link>
		<dc:creator>Jakob</dc:creator>
		<pubDate>Mon, 23 Jun 2008 14:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/2008/06/23/diagnosing-federated-search-source-problems-its-harder-than-you-think/#comment-2195</guid>
		<description>Federated search is one example of loosely coupeled services. You should never expect anything from a service you use unless you checked it yourself. Use test cases, for instance a search that returns a know result, ping the server etc. and regularly run the tests.</description>
		<content:encoded><![CDATA[<p>Federated search is one example of loosely coupeled services. You should never expect anything from a service you use unless you checked it yourself. Use test cases, for instance a search that returns a know result, ping the server etc. and regularly run the tests.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

