<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Advanced Search Operators for the LinkedIn Pro</title>
	<atom:link href="http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/</link>
	<description>The corporate blog of LinkedIn, the world's largest professional networking site.</description>
	<lastBuildDate>Sat, 12 Dec 2009 02:37:13 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Childs</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-10280</link>
		<dc:creator>John Childs</dc:creator>
		<pubDate>Thu, 16 Jul 2009 23:26:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-10280</guid>
		<description>A nice feature when pulling up resume/profile results would be to have an indicator on that page showing if a person had already been sent an In Mail and the date it happened.</description>
		<content:encoded><![CDATA[<p>A nice feature when pulling up resume/profile results would be to have an indicator on that page showing if a person had already been sent an In Mail and the date it happened.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Childs</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-10279</link>
		<dc:creator>John Childs</dc:creator>
		<pubDate>Thu, 16 Jul 2009 23:20:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-10279</guid>
		<description>For exclusionary terms, are you still using 
AND NOT or switched to the Minus (-) sign?

It seems that when I use AND NOT and then &#039;OR&#039; a bunch of terms together it excludes the terms as long as none of the terms is not a phrase in quotes such as &quot;technical recruiter&quot; or &quot;Research In Motion&quot;.  If a phrase is entered, profiles still show up with terms that were supposed to be excluded. Can this be fixed?

The search field for Boolean equations is said to hold 1000 characters with spaces, but when I entered a 999 character string, it didn&#039;t work / no results.  I kept deleting characters until I got down to 946 and then it worked.  Can you confirm the max number of characters?</description>
		<content:encoded><![CDATA[<p>For exclusionary terms, are you still using<br />
AND NOT or switched to the Minus (-) sign?</p>
<p>It seems that when I use AND NOT and then &#8216;OR&#8217; a bunch of terms together it excludes the terms as long as none of the terms is not a phrase in quotes such as &#8220;technical recruiter&#8221; or &#8220;Research In Motion&#8221;.  If a phrase is entered, profiles still show up with terms that were supposed to be excluded. Can this be fixed?</p>
<p>The search field for Boolean equations is said to hold 1000 characters with spaces, but when I entered a 999 character string, it didn&#8217;t work / no results.  I kept deleting characters until I got down to 946 and then it worked.  Can you confirm the max number of characters?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Wilby</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-8281</link>
		<dc:creator>Simon Wilby</dc:creator>
		<pubDate>Fri, 24 Apr 2009 22:55:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-8281</guid>
		<description>This is really good post. Human resources of any company should learn these search operators so it would be easier for them to look for prospects.</description>
		<content:encoded><![CDATA[<p>This is really good post. Human resources of any company should learn these search operators so it would be easier for them to look for prospects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dirkfrey</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-7803</link>
		<dc:creator>dirkfrey</dc:creator>
		<pubDate>Tue, 31 Mar 2009 22:33:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-7803</guid>
		<description>@Brad- The search engine will return results for most long complex queries but internally we have an upper limit in place to prevent abuse and attacks. 
Regards,
Dirk</description>
		<content:encoded><![CDATA[<p>@Brad- The search engine will return results for most long complex queries but internally we have an upper limit in place to prevent abuse and attacks.<br />
Regards,<br />
Dirk</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-7182</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Thu, 05 Mar 2009 18:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-7182</guid>
		<description>Okay, so I just asked Customer Service, &quot;what is the maximum # of Characters I can use in an advanced search&quot;. The response was the simplest response I&#039;ve ever received, &quot;It is 30&quot;. So, of course, my curiosity was peaked and I tested it. I did this by using the search 1 OR 2 OR .... Or 29 OR 30 and it worked. However I wanted to double check it and added 31, and it also worked, hmmmm. I then added 5 more, it also worked, then went up to 45, 55, 75, 100; THEY ALL WORKED. Well, I wonder where the 30 answer that the linkedin customer service representative came from. I finally broke it when I jumped up to 125, which returns the response &quot;We are currently upgrading the search engine. Search will be back momentarily.&quot; SO I played around with it and it seems that sometime the search result works and sometimes it doesn&#039;t at or above 104-110 but I was never able to hit the 125 mark. This was all done in the Keyword search criteria, just wanted to know what my options where Since I had broken it with some of my complicated searches earlier. I&#039;m not sure if numbers and words have any comparison but thought I&#039;d play around with things and let any super users know what I&#039;ve found.

Cheers,</description>
		<content:encoded><![CDATA[<p>Okay, so I just asked Customer Service, &#8220;what is the maximum # of Characters I can use in an advanced search&#8221;. The response was the simplest response I&#8217;ve ever received, &#8220;It is 30&#8243;. So, of course, my curiosity was peaked and I tested it. I did this by using the search 1 OR 2 OR &#8230;. Or 29 OR 30 and it worked. However I wanted to double check it and added 31, and it also worked, hmmmm. I then added 5 more, it also worked, then went up to 45, 55, 75, 100; THEY ALL WORKED. Well, I wonder where the 30 answer that the linkedin customer service representative came from. I finally broke it when I jumped up to 125, which returns the response &#8220;We are currently upgrading the search engine. Search will be back momentarily.&#8221; SO I played around with it and it seems that sometime the search result works and sometimes it doesn&#8217;t at or above 104-110 but I was never able to hit the 125 mark. This was all done in the Keyword search criteria, just wanted to know what my options where Since I had broken it with some of my complicated searches earlier. I&#8217;m not sure if numbers and words have any comparison but thought I&#8217;d play around with things and let any super users know what I&#8217;ve found.</p>
<p>Cheers,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Szerszen</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-6649</link>
		<dc:creator>Dennis Szerszen</dc:creator>
		<pubDate>Fri, 20 Feb 2009 14:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-6649</guid>
		<description>LinkedIn has the potential to do much more with search than finding a few contacts. At Quintura, we&#039;ve realized that by representing search terms in the form of an interactive tag cloud, {along with graphic associations) creates new opportunities to leverage search for all sorts of interactions, not just navigation. I think LinkedIn&#039;s search progress is great, but also know that there&#039;s bigger opportunities just over the horizon.</description>
		<content:encoded><![CDATA[<p>LinkedIn has the potential to do much more with search than finding a few contacts. At Quintura, we&#8217;ve realized that by representing search terms in the form of an interactive tag cloud, {along with graphic associations) creates new opportunities to leverage search for all sorts of interactions, not just navigation. I think LinkedIn&#8217;s search progress is great, but also know that there&#8217;s bigger opportunities just over the horizon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-6401</link>
		<dc:creator>Alexander</dc:creator>
		<pubDate>Thu, 12 Feb 2009 15:32:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-6401</guid>
		<description>Hi! It would be great if one were able to use a combination of multiple search operators from one filed. Example ccompany:x pcompany:y . Do you plan to introduce such a function?

Alexander</description>
		<content:encoded><![CDATA[<p>Hi! It would be great if one were able to use a combination of multiple search operators from one filed. Example ccompany:x pcompany:y . Do you plan to introduce such a function?</p>
<p>Alexander</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick OMalley</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-5966</link>
		<dc:creator>Patrick OMalley</dc:creator>
		<pubDate>Thu, 15 Jan 2009 04:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-5966</guid>
		<description>It doesn&#039;t really appear to work.  Even the simple example from your Help Center, 

school:harvard ccompany:linkedin

gives the error 

(BIG RED X) There was an unexpected problem that prevented us from completing your request.

Other, like 

“meeting planner” radius:50 zip:30301 country:&quot;United States&quot; 

return 0 results when there should be 152.  The features look like they could be cool, but need

- to work
- to have better documentation and examples

Pat
http://www.patrickomalley.com</description>
		<content:encoded><![CDATA[<p>It doesn&#8217;t really appear to work.  Even the simple example from your Help Center, </p>
<p>school:harvard ccompany:linkedin</p>
<p>gives the error </p>
<p>(BIG RED X) There was an unexpected problem that prevented us from completing your request.</p>
<p>Other, like </p>
<p>“meeting planner” radius:50 zip:30301 country:&#8221;United States&#8221; </p>
<p>return 0 results when there should be 152.  The features look like they could be cool, but need</p>
<p>- to work<br />
- to have better documentation and examples</p>
<p>Pat<br />
<a href="http://www.patrickomalley.com" rel="nofollow">http://www.patrickomalley.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick OMalley</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-5965</link>
		<dc:creator>Patrick OMalley</dc:creator>
		<pubDate>Thu, 15 Jan 2009 03:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-5965</guid>
		<description>I hvae a ton of these, but it would be nice if 

1) my last search defaults were persistent, i.e. if my last search was within 10 miles of Boston, it should assume that the next search would be within 10 miles of Boston, so I shouldn&#039;t have to specify that again

2) the search button should be at the bottom of the results page, not the top, to save scrolling

Pat 
http://www.patrickomalley.com</description>
		<content:encoded><![CDATA[<p>I hvae a ton of these, but it would be nice if </p>
<p>1) my last search defaults were persistent, i.e. if my last search was within 10 miles of Boston, it should assume that the next search would be within 10 miles of Boston, so I shouldn&#8217;t have to specify that again</p>
<p>2) the search button should be at the bottom of the results page, not the top, to save scrolling</p>
<p>Pat<br />
<a href="http://www.patrickomalley.com" rel="nofollow">http://www.patrickomalley.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carolyn</title>
		<link>http://blog.linkedin.com/2009/01/08/advanced-search-operators-for-the-linkedin-pro/#comment-5960</link>
		<dc:creator>Carolyn</dc:creator>
		<pubDate>Wed, 14 Jan 2009 18:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.linkedin.com/?p=1478#comment-5960</guid>
		<description>I have found at times that using the feature to limit to my network only returns zero results, when I had results with 2nd and 3rd connections prior to checking the box.  Additionally, I wish it could sort by the degrees away from me still, since this was incredibly helpful.</description>
		<content:encoded><![CDATA[<p>I have found at times that using the feature to limit to my network only returns zero results, when I had results with 2nd and 3rd connections prior to checking the box.  Additionally, I wish it could sort by the degrees away from me still, since this was incredibly helpful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
