<?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: LinkedIn name search is ridiculously bad</title>
	<atom:link href="http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/</link>
	<description>Understanding technology ... in both senses of the phrase</description>
	<lastBuildDate>Sun, 24 Jan 2010 05:45:03 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tony Lacy(-)Thompson</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-60932</link>
		<dc:creator>Tony Lacy(-)Thompson</dc:creator>
		<pubDate>Fri, 23 Jan 2009 07:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-60932</guid>
		<description>Curt,

I am honored that you used my name as a test case for searching LinkedIn. As it happens, the hyphen optional, and is more of a late 20th century addition, but especially important in the US. In the UK I could go to any theatre (theater) box office and have no difficulty picking up tickets under the name &quot;Lacy Thompson&quot;. Here in the US, picking up a prescription requires many repetitions of &quot;the last name is LACY-Thompson. Yes, look under &quot;L&quot;, etc.&quot; If only the name had come with more money...

Tony L-T</description>
		<content:encoded><![CDATA[<p>Curt,</p>
<p>I am honored that you used my name as a test case for searching LinkedIn. As it happens, the hyphen optional, and is more of a late 20th century addition, but especially important in the US. In the UK I could go to any theatre (theater) box office and have no difficulty picking up tickets under the name &#8220;Lacy Thompson&#8221;. Here in the US, picking up a prescription requires many repetitions of &#8220;the last name is LACY-Thompson. Yes, look under &#8220;L&#8221;, etc.&#8221; If only the name had come with more money&#8230;</p>
<p>Tony L-T</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Lacy(-)Thompson</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-60931</link>
		<dc:creator>Tony Lacy(-)Thompson</dc:creator>
		<pubDate>Fri, 23 Jan 2009 07:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-60931</guid>
		<description>Curt,

I am honored that you used my name as a test case for searching LinkedIn. As it happens, the hyphen optional, and is more of a late 20th century addition, but especially important in the US. In the UK I could go to any theatre (theater) box office and have no difficulty picking up tickets under the name &quot;Lacy Thompson&quot;. Here in the US, picking up a prescription requires many repititions of &quot;the last name is LACY-Thompson. Yes, look under &quot;L&quot;, etc.&quot; If only the name had come with more money...

Tony L-T</description>
		<content:encoded><![CDATA[<p>Curt,</p>
<p>I am honored that you used my name as a test case for searching LinkedIn. As it happens, the hyphen optional, and is more of a late 20th century addition, but especially important in the US. In the UK I could go to any theatre (theater) box office and have no difficulty picking up tickets under the name &#8220;Lacy Thompson&#8221;. Here in the US, picking up a prescription requires many repititions of &#8220;the last name is LACY-Thompson. Yes, look under &#8220;L&#8221;, etc.&#8221; If only the name had come with more money&#8230;</p>
<p>Tony L-T</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B McKenzie</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-49618</link>
		<dc:creator>B McKenzie</dc:creator>
		<pubDate>Wed, 03 Sep 2008 18:14:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-49618</guid>
		<description>You want bad? Netflix. Spectacularly bad if you don&#039;t know how to spell a title, plus it doesn&#039;t support any sort of compound query.

My latest example was searching for &quot;Akeelah and the Bee&quot;. Given that I got the tip verbally I had no idea how to spell Akeelah (&quot;Ach...&quot;) and &quot;Bee&quot; doesn&#039;t show it. Had to got to IMDB and then back.

Two thumbs down for NF.</description>
		<content:encoded><![CDATA[<p>You want bad? Netflix. Spectacularly bad if you don&#8217;t know how to spell a title, plus it doesn&#8217;t support any sort of compound query.</p>
<p>My latest example was searching for &#8220;Akeelah and the Bee&#8221;. Given that I got the tip verbally I had no idea how to spell Akeelah (&#8221;Ach&#8230;&#8221;) and &#8220;Bee&#8221; doesn&#8217;t show it. Had to got to IMDB and then back.</p>
<p>Two thumbs down for NF.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Weinreb</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-49484</link>
		<dc:creator>Daniel Weinreb</dc:creator>
		<pubDate>Mon, 01 Sep 2008 20:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-49484</guid>
		<description>I also asked LinkedIn to provide a way to ask &quot;Find people who worked at BOTH X and Y&quot;.  Every so often that would be useful.</description>
		<content:encoded><![CDATA[<p>I also asked LinkedIn to provide a way to ask &#8220;Find people who worked at BOTH X and Y&#8221;.  Every so often that would be useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Otis Gospodnetic</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-49144</link>
		<dc:creator>Otis Gospodnetic</dc:creator>
		<pubDate>Fri, 29 Aug 2008 02:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-49144</guid>
		<description>LinkedIn does use Lucene, but let&#039;s not even hint at *that* being the source of the problem.  It&#039;s a matter of LinkedIn using tools (like Lucene and its cousins) in clever ways, that is all.</description>
		<content:encoded><![CDATA[<p>LinkedIn does use Lucene, but let&#8217;s not even hint at *that* being the source of the problem.  It&#8217;s a matter of LinkedIn using tools (like Lucene and its cousins) in clever ways, that is all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlo</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-48875</link>
		<dc:creator>Carlo</dc:creator>
		<pubDate>Sun, 24 Aug 2008 21:38:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-48875</guid>
		<description>That&#039;s definitely an area to improve. Luckily, I haven&#039;t really come across a name that easy to misspell.</description>
		<content:encoded><![CDATA[<p>That&#8217;s definitely an area to improve. Luckily, I haven&#8217;t really come across a name that easy to misspell.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Tuchen</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-48463</link>
		<dc:creator>Mike Tuchen</dc:creator>
		<pubDate>Wed, 20 Aug 2008 12:29:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-48463</guid>
		<description>I find LinkedIn incredibly useful in many business contexts, but agree its search is decades behind the state of the art.  Another set of simple things it&#039;s missing include any concept of boolean search (everything is hard &quot;AND&quot;), most fielded searches beyond a couple trivial things, or any kind of metadata exploration.  On the latter point, it&#039;s got one of the best set of fielded metadata around but almost completely ignores it from a search UI perspective even in their paid subscription tiers.  I hope the LinkedIn folks hire a great search technologist sometime soon - they&#039;ve done a terrific job of becoming a must-use business tool but haven&#039;t yet built the system that meets some of their users&#039; basic expectations.</description>
		<content:encoded><![CDATA[<p>I find LinkedIn incredibly useful in many business contexts, but agree its search is decades behind the state of the art.  Another set of simple things it&#8217;s missing include any concept of boolean search (everything is hard &#8220;AND&#8221;), most fielded searches beyond a couple trivial things, or any kind of metadata exploration.  On the latter point, it&#8217;s got one of the best set of fielded metadata around but almost completely ignores it from a search UI perspective even in their paid subscription tiers.  I hope the LinkedIn folks hire a great search technologist sometime soon &#8211; they&#8217;ve done a terrific job of becoming a must-use business tool but haven&#8217;t yet built the system that meets some of their users&#8217; basic expectations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Griffies</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-48377</link>
		<dc:creator>Martin Griffies</dc:creator>
		<pubDate>Tue, 19 Aug 2008 14:55:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-48377</guid>
		<description>Using Lucene dies not exclude the use of taxonomies, data dictionaries or whatever for semantic or extended search. I guess it&#039;s pure laziness or other distractions on LinkedIn&#039;s behalf.
Having said that, they seem to add useless features at intervals rather than improving the search, which I also find poor.</description>
		<content:encoded><![CDATA[<p>Using Lucene dies not exclude the use of taxonomies, data dictionaries or whatever for semantic or extended search. I guess it&#8217;s pure laziness or other distractions on LinkedIn&#8217;s behalf.<br />
Having said that, they seem to add useless features at intervals rather than improving the search, which I also find poor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Tunkelang</title>
		<link>http://www.texttechnologies.com/2008/08/19/linkedin-name-search-is-ridiculously-bad/comment-page-1/#comment-48374</link>
		<dc:creator>Daniel Tunkelang</dc:creator>
		<pubDate>Tue, 19 Aug 2008 14:34:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.texttechnologies.com/?p=272#comment-48374</guid>
		<description>LinkedIn is a Lucene shop--see http://www.slideshare.net/linkedin/linkedins-communication-architecture for more details about their architecture. I&#039;m not sure what IMDB is using, but I imagine that they can draw on technology, expertise, and resources from Amazon.

I&#039;d love to see LinkedIn improve its search functionality. Beyond the basics, like better spelling suggestions, they could be a poster child for exploratory search.</description>
		<content:encoded><![CDATA[<p>LinkedIn is a Lucene shop&#8211;see <a href="http://www.slideshare.net/linkedin/linkedins-communication-architecture" onclick="javascript:pageTracker._trackPageview('/outbound/comment/www.slideshare.net');" rel="nofollow">http://www.slideshare.net/linkedin/linkedins-communication-architecture</a> for more details about their architecture. I&#8217;m not sure what IMDB is using, but I imagine that they can draw on technology, expertise, and resources from Amazon.</p>
<p>I&#8217;d love to see LinkedIn improve its search functionality. Beyond the basics, like better spelling suggestions, they could be a poster child for exploratory search.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.189 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-01-24 03:56:48 -->
