<?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"
	>
<channel>
	<title>Comments on: Is Enterprise Search an Application or a Feature?</title>
	<atom:link href="http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/</link>
	<description>One foot in the muck, the other in utopia</description>
	<pubDate>Fri, 29 Aug 2008 23:18:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Lynda Moulton</title>
		<link>http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-183433</link>
		<dc:creator>Lynda Moulton</dc:creator>
		<pubDate>Thu, 29 May 2008 22:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-183433</guid>
		<description>Decades ago enterprise content was collected, indexed and shared through whatever technology the corporate library could get its hand on. Search was embedded and, as the gatekeepers for enterprise content, information specialists maintained metadata to make it searchable. That model is fading but the need for embedded search is still present. Knowledge workers tend to work within a framework of technologies and for most of their critical information needs will look for content within that framework.

However, there is always a superset of enterprise content that need access by all, and it requires its own management tools. Ideally, intranet portals will provide search access to all shareable content without the need for security, and access to selected application content with requisite security. This may be done with federated search tools that can leverage content results from embedded search engines.

Doing this well and with thoughtful build-out requires governance and a chief information architect who really understands the nuances of all the content, its security attributes and how it needs to be accessed.

A single enterprise search engine, given the right packaging and deployment can do it all, but it requires human guidance.</description>
		<content:encoded><![CDATA[<p>Decades ago enterprise content was collected, indexed and shared through whatever technology the corporate library could get its hand on. Search was embedded and, as the gatekeepers for enterprise content, information specialists maintained metadata to make it searchable. That model is fading but the need for embedded search is still present. Knowledge workers tend to work within a framework of technologies and for most of their critical information needs will look for content within that framework.</p>
<p>However, there is always a superset of enterprise content that need access by all, and it requires its own management tools. Ideally, intranet portals will provide search access to all shareable content without the need for security, and access to selected application content with requisite security. This may be done with federated search tools that can leverage content results from embedded search engines.</p>
<p>Doing this well and with thoughtful build-out requires governance and a chief information architect who really understands the nuances of all the content, its security attributes and how it needs to be accessed.</p>
<p>A single enterprise search engine, given the right packaging and deployment can do it all, but it requires human guidance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: People Over Process &#187; MuleCon Wrap-up: Rouge IT, Open Source in the Water, Support Response Time, and Reputation</title>
		<link>http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-165438</link>
		<dc:creator>People Over Process &#187; MuleCon Wrap-up: Rouge IT, Open Source in the Water, Support Response Time, and Reputation</dc:creator>
		<pubDate>Thu, 03 Apr 2008 01:35:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-165438</guid>
		<description>[...] brush up this problem frequently when it comes to enterprise search: things just don&#8217;t seem to be working out as brilliantly as we&#8217;d hoped for when it [...]</description>
		<content:encoded><![CDATA[<p>[...] brush up this problem frequently when it comes to enterprise search: things just don&#8217;t seem to be working out as brilliantly as we&#8217;d hoped for when it [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yegor Kuznetsov</title>
		<link>http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-164498</link>
		<dc:creator>Yegor Kuznetsov</dc:creator>
		<pubDate>Mon, 31 Mar 2008 15:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-164498</guid>
		<description>Michael, great analysis!

You are absolutely right in saying that search is becoming a feature in other software. 

Yes, now you can use the search function in a array of applications. In some cases, you can make the most of the search technology without entering queries manually. 

For example, Brainware’s Intelligent Data Capture solution IDC-distiller™ (http://www.brainware.com/data_capture.php)  uses the embedded fuzzy search function to automatically match invoice content with a vendor list and a purchase order, even if there is no exact match. 

This ‘unmanned’ search function greatly increases the proportion of payment documents that can be processed without any human ever touching them.</description>
		<content:encoded><![CDATA[<p>Michael, great analysis!</p>
<p>You are absolutely right in saying that search is becoming a feature in other software. </p>
<p>Yes, now you can use the search function in a array of applications. In some cases, you can make the most of the search technology without entering queries manually. </p>
<p>For example, Brainware’s Intelligent Data Capture solution IDC-distiller™ (http://www.brainware.com/data_capture.php)  uses the embedded fuzzy search function to automatically match invoice content with a vendor list and a purchase order, even if there is no exact match. </p>
<p>This ‘unmanned’ search function greatly increases the proportion of payment documents that can be processed without any human ever touching them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Krugler</title>
		<link>http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-164384</link>
		<dc:creator>Ken Krugler</dc:creator>
		<pubDate>Sun, 30 Mar 2008 23:11:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-164384</guid>
		<description>Sorry in advance for the long comment, but your post got me looking through some old notes on this issue of enterprise search.

William is right, in that internal web sites are more about just getting the content out of people's heads and into documents/wikis/records, while external web sites are all about being findable via Google/Yahoo/MSN - which means good linking, good keywords, good titles.

There's another aspect, though, which has to do with the type of searching being done.

There's search as a substitute for bookmarking, which is how I think many people use an internal search system...they know the page is there, so they just need a quick way of finding it. Because of this, tuning search results based on the user's search history (and that of other internal users) has significant value for enterprise search. But in the end it doesn't add all that much value.

Other types of searching, such as exploratory search, wind up having highly variable value, depending on the type of work an employee does. For many people with fairly stable routines at work, these other uses of search have little value.

On the other hand, a true knowledge worker can get a lot of value out of a search system that supports learning and exploration.

This last point is one that I'm extrapolating from our experience with developers, but it feels like it fits a general class of employees who do in fact need to be constantly learning and solving problems - in other words, the more highly compensated and valuable people in an organization.

Which is why good search can be the most effective way for a company to get more out of its key employees.

-- Ken</description>
		<content:encoded><![CDATA[<p>Sorry in advance for the long comment, but your post got me looking through some old notes on this issue of enterprise search.</p>
<p>William is right, in that internal web sites are more about just getting the content out of people&#8217;s heads and into documents/wikis/records, while external web sites are all about being findable via Google/Yahoo/MSN - which means good linking, good keywords, good titles.</p>
<p>There&#8217;s another aspect, though, which has to do with the type of searching being done.</p>
<p>There&#8217;s search as a substitute for bookmarking, which is how I think many people use an internal search system&#8230;they know the page is there, so they just need a quick way of finding it. Because of this, tuning search results based on the user&#8217;s search history (and that of other internal users) has significant value for enterprise search. But in the end it doesn&#8217;t add all that much value.</p>
<p>Other types of searching, such as exploratory search, wind up having highly variable value, depending on the type of work an employee does. For many people with fairly stable routines at work, these other uses of search have little value.</p>
<p>On the other hand, a true knowledge worker can get a lot of value out of a search system that supports learning and exploration.</p>
<p>This last point is one that I&#8217;m extrapolating from our experience with developers, but it feels like it fits a general class of employees who do in fact need to be constantly learning and solving problems - in other words, the more highly compensated and valuable people in an organization.</p>
<p>Which is why good search can be the most effective way for a company to get more out of its key employees.</p>
<p>&#8211; Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cote'</title>
		<link>http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-163423</link>
		<dc:creator>Cote'</dc:creator>
		<pubDate>Wed, 26 Mar 2008 15:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-163423</guid>
		<description>William. Yeah, you're probably right on that. It's hard to use crowd-AI to figure out what the right match is when there's a tiny, fire-wall trapped crowd to go off of.</description>
		<content:encoded><![CDATA[<p>William. Yeah, you&#8217;re probably right on that. It&#8217;s hard to use crowd-AI to figure out what the right match is when there&#8217;s a tiny, fire-wall trapped crowd to go off of.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William V.</title>
		<link>http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-162894</link>
		<dc:creator>William V.</dc:creator>
		<pubDate>Mon, 24 Mar 2008 18:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2008/03/24/is-enterprise-search-an-application-or-a-feature/#comment-162894</guid>
		<description>How about the fact that intranet search simply doesn't work? It's not Google 2008 (pagerank), it's Altavista 1999 (keyword search). And people expect Google-like levels of relevance in their search results.

It's all the linking that takes place on the Web that allows Google to provide ranked results that work. In most intranets, there isn't much linking going on. A lot of the docs are PDF, DOC, PPT, XLS with almost no links. And even HTML content tends to be link-poor (other than same-site links) compared to what you find on the real Web.

To take your example of the list of company holidays, how many pages on the company's intranet typically point to the HR page with that information? Not many. Which is why that page is hard to find on search results (unless it is one of the common queries that has been manually configured by the search team). It is buried among pages such a question from a solutions architect in Poland asking how to configure Polish holidays in the CRM product. Back to "keyword search" level of relevance. Feels like the stone age.

Another benefit of internal blogging: making the intranet search engine smarter.</description>
		<content:encoded><![CDATA[<p>How about the fact that intranet search simply doesn&#8217;t work? It&#8217;s not Google 2008 (pagerank), it&#8217;s Altavista 1999 (keyword search). And people expect Google-like levels of relevance in their search results.</p>
<p>It&#8217;s all the linking that takes place on the Web that allows Google to provide ranked results that work. In most intranets, there isn&#8217;t much linking going on. A lot of the docs are PDF, DOC, PPT, XLS with almost no links. And even HTML content tends to be link-poor (other than same-site links) compared to what you find on the real Web.</p>
<p>To take your example of the list of company holidays, how many pages on the company&#8217;s intranet typically point to the HR page with that information? Not many. Which is why that page is hard to find on search results (unless it is one of the common queries that has been manually configured by the search team). It is buried among pages such a question from a solutions architect in Poland asking how to configure Polish holidays in the CRM product. Back to &#8220;keyword search&#8221; level of relevance. Feels like the stone age.</p>
<p>Another benefit of internal blogging: making the intranet search engine smarter.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
