<?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: Refine your searches in fewer steps in new search</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=refine-your-searches-in-fewer-steps-in-new-search</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Sat, 25 May 2013 04:38:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42381</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Sat, 21 Nov 2009 22:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42381</guid>
		<description>Rhonda Re:#73

The easy way is to just ignore all those little wavy green things and ignore other member trees.

Do all research by searching actual records.

If you hit a brick wall, then- and in my opinion, only then - you might want to check on a few documented trees for hints.

Many won&#039;t agree with me and have their own opinion; and they are entitled to that opinion... even if its wrong. *grin*</description>
		<content:encoded><![CDATA[<p>Rhonda Re:#73</p>
<p>The easy way is to just ignore all those little wavy green things and ignore other member trees.</p>
<p>Do all research by searching actual records.</p>
<p>If you hit a brick wall, then- and in my opinion, only then &#8211; you might want to check on a few documented trees for hints.</p>
<p>Many won&#8217;t agree with me and have their own opinion; and they are entitled to that opinion&#8230; even if its wrong. *grin*</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rhonda Corbett</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42375</link>
		<dc:creator>Rhonda Corbett</dc:creator>
		<pubDate>Sat, 21 Nov 2009 18:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42375</guid>
		<description>It took a bit to get the hang of the new search set, I am a new member and was just getting the hang of the old one, but once I did I liked being able to filter out everything but the 1 census year or what ever I was looking for. 
I love Ancestry but I have 1 area where I am feeling overwhelmed..........the list of people with hints.  Alot of these names aren&#039;t in my direct line and at this point anyway I am not really interested in completing those records.  It seems like it takes forever for me to locate members of my direct lines to clear their hints. Is there some way to just have direct line ancestors or a &quot;hot list tag&quot; (for lack of a better term) to make it easier and faster to get to the hints you want and need NOW. ?</description>
		<content:encoded><![CDATA[<p>It took a bit to get the hang of the new search set, I am a new member and was just getting the hang of the old one, but once I did I liked being able to filter out everything but the 1 census year or what ever I was looking for.<br />
I love Ancestry but I have 1 area where I am feeling overwhelmed&#8230;&#8230;&#8230;.the list of people with hints.  Alot of these names aren&#8217;t in my direct line and at this point anyway I am not really interested in completing those records.  It seems like it takes forever for me to locate members of my direct lines to clear their hints. Is there some way to just have direct line ancestors or a &#8220;hot list tag&#8221; (for lack of a better term) to make it easier and faster to get to the hints you want and need NOW. ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darlene Steffens</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42371</link>
		<dc:creator>Darlene Steffens</dc:creator>
		<pubDate>Sat, 21 Nov 2009 15:55:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42371</guid>
		<description>Addition to #71 - I should have included in my previous comment the databases where I am experiencing the search result &quot;[See User Comments]&quot;.  It will be found on all the US Census databases, the Social Security Death Index and the World War I Registration Draft Cards 1917-1918 to name a few.</description>
		<content:encoded><![CDATA[<p>Addition to #71 &#8211; I should have included in my previous comment the databases where I am experiencing the search result &#8220;[See User Comments]&#8220;.  It will be found on all the US Census databases, the Social Security Death Index and the World War I Registration Draft Cards 1917-1918 to name a few.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darlene Steffens</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42370</link>
		<dc:creator>Darlene Steffens</dc:creator>
		<pubDate>Sat, 21 Nov 2009 15:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42370</guid>
		<description>Over the last few days I have been searching for families whose surname is SEELEY and spelled in a variety of ways.  When I enter a search for last name SEE or SEE* thousands of records are found for &quot;[See User Comment]&quot;.  This seems to be a new search response. Could it be the result of recent site enhancements? Is there a method to eliminate the &quot;[See User Comment]&quot; responses from the search criteria? I am using the Old Search tool.  Thanks!</description>
		<content:encoded><![CDATA[<p>Over the last few days I have been searching for families whose surname is SEELEY and spelled in a variety of ways.  When I enter a search for last name SEE or SEE* thousands of records are found for &#8220;[See User Comment]&#8220;.  This seems to be a new search response. Could it be the result of recent site enhancements? Is there a method to eliminate the &#8220;[See User Comment]&#8221; responses from the search criteria? I am using the Old Search tool.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42365</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Sat, 21 Nov 2009 05:23:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42365</guid>
		<description>Emily Re:#69 &amp; 69

I just went to thge California Death Index 1940-1997 and entered:

Last name: Hammond
Mother&#039;s Maiden Name: Dean

and I got the over 50 hits-  Charles Edwain Hammond was the first one.

I then repeated it with &quot;Exact Matches Only&quot; checked and got only two hits- Charles Edwain was first and a Marjorie Colvin Dean was second.

The above was all done in old search.

I went to new search and tried the same ting- in the first case I also got 50 hits- but Charles Edwain was not among them.

When I marked &quot;match all terms exactly&quot; I got 0 results

If I marked only last name :Hammond and Mother&#039;s Maiden Name: dean
as exact I still got no results.

I will say this- until NewSearch can at least duplicate the same results as OldSearch it is not fit for prime time operation.

Once NewSearch can duplicate OldSearch results then we can- maybe- start talking about improving NewSearch&#039;s results - but certainly not until then.</description>
		<content:encoded><![CDATA[<p>Emily Re:#69 &amp; 69</p>
<p>I just went to thge California Death Index 1940-1997 and entered:</p>
<p>Last name: Hammond<br />
Mother&#8217;s Maiden Name: Dean</p>
<p>and I got the over 50 hits-  Charles Edwain Hammond was the first one.</p>
<p>I then repeated it with &#8220;Exact Matches Only&#8221; checked and got only two hits- Charles Edwain was first and a Marjorie Colvin Dean was second.</p>
<p>The above was all done in old search.</p>
<p>I went to new search and tried the same ting- in the first case I also got 50 hits- but Charles Edwain was not among them.</p>
<p>When I marked &#8220;match all terms exactly&#8221; I got 0 results</p>
<p>If I marked only last name :Hammond and Mother&#8217;s Maiden Name: dean<br />
as exact I still got no results.</p>
<p>I will say this- until NewSearch can at least duplicate the same results as OldSearch it is not fit for prime time operation.</p>
<p>Once NewSearch can duplicate OldSearch results then we can- maybe- start talking about improving NewSearch&#8217;s results &#8211; but certainly not until then.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42361</link>
		<dc:creator>Emily</dc:creator>
		<pubDate>Sat, 21 Nov 2009 02:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42361</guid>
		<description>P.S. On a positive note, it was very nice to return to this blog and find my comment (#39) had been addressed. Usually if I bother to send a message to a company I never know if it was even read. Anne, I did notice when the census problem I mentioned was fixed. Thanks.

Emily</description>
		<content:encoded><![CDATA[<p>P.S. On a positive note, it was very nice to return to this blog and find my comment (#39) had been addressed. Usually if I bother to send a message to a company I never know if it was even read. Anne, I did notice when the census problem I mentioned was fixed. Thanks.</p>
<p>Emily</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42359</link>
		<dc:creator>Emily</dc:creator>
		<pubDate>Sat, 21 Nov 2009 02:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42359</guid>
		<description>Referring to messages #39, 41, 45, and 46. (Jerry and Anne, thank you for the follow up messages!)

Today I found yet another problem of the same type (see #39) in searching the California Death Index. 

If I search with these criteria:

First &amp; Middle Name(s): Charles Edwin
Last Name: Hammond

this fellow is returned:

Name: Charles Edwin Hammond
Mother’s maiden name: Dean

But if I search the same database with these criteria:

Last Name: Hammond
Mother: Dean

zero results are returned.

So I continue to find this sort of problem ever since the “refine” update (and I’m not talking about obscure little databases). I have associated this with the “refine” update because of the timing I experienced, but perhaps that’s just coincidental. And frankly, I don’t care what the cause is. I just can’t help wondering how such seemingly obvious bugs go un-fixed, if not undetected. (Is it policy to rely on customers to do this sort of Q&amp;A? I wouldn’t mind doing it if I were being paid, rather than paying!)

Emily</description>
		<content:encoded><![CDATA[<p>Referring to messages #39, 41, 45, and 46. (Jerry and Anne, thank you for the follow up messages!)</p>
<p>Today I found yet another problem of the same type (see #39) in searching the California Death Index. </p>
<p>If I search with these criteria:</p>
<p>First &amp; Middle Name(s): Charles Edwin<br />
Last Name: Hammond</p>
<p>this fellow is returned:</p>
<p>Name: Charles Edwin Hammond<br />
Mother’s maiden name: Dean</p>
<p>But if I search the same database with these criteria:</p>
<p>Last Name: Hammond<br />
Mother: Dean</p>
<p>zero results are returned.</p>
<p>So I continue to find this sort of problem ever since the “refine” update (and I’m not talking about obscure little databases). I have associated this with the “refine” update because of the timing I experienced, but perhaps that’s just coincidental. And frankly, I don’t care what the cause is. I just can’t help wondering how such seemingly obvious bugs go un-fixed, if not undetected. (Is it policy to rely on customers to do this sort of Q&amp;A? I wouldn’t mind doing it if I were being paid, rather than paying!)</p>
<p>Emily</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick H O'Brien</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42324</link>
		<dc:creator>Patrick H O'Brien</dc:creator>
		<pubDate>Fri, 20 Nov 2009 02:53:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42324</guid>
		<description>Specifying EXACT seems to have un-expected results. Merely  specifying the last name   to be exact will often exclude all previous results when the the previous result contained correctly spelled last names.   Why is so restrictive?

Pat O&#039;Brien</description>
		<content:encoded><![CDATA[<p>Specifying EXACT seems to have un-expected results. Merely  specifying the last name   to be exact will often exclude all previous results when the the previous result contained correctly spelled last names.   Why is so restrictive?</p>
<p>Pat O&#8217;Brien</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick H O'Brien</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42323</link>
		<dc:creator>Patrick H O'Brien</dc:creator>
		<pubDate>Fri, 20 Nov 2009 02:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42323</guid>
		<description>It would be very useful if you could specify categories to exclude when refining a search.  Currently, I can only speciy a category to include (thereby excluding all other categories).

For instance, after I have found all relevent census records, I would like to exclude census records and include all other catregories. 

This seems to be a very reasonable request and consistent with how one would normally look for things. After I have found my g-father&#039;s WW-I draft registration. I DON&#039;T NEED to plow through hundreds of other people&#039;s draft cards before getting to the mext possible military entry.

Just change the scheme to specify exclusion rather than inclusion in the list of databases listed when editing the search.

Pat O&#039;Brien</description>
		<content:encoded><![CDATA[<p>It would be very useful if you could specify categories to exclude when refining a search.  Currently, I can only speciy a category to include (thereby excluding all other categories).</p>
<p>For instance, after I have found all relevent census records, I would like to exclude census records and include all other catregories. </p>
<p>This seems to be a very reasonable request and consistent with how one would normally look for things. After I have found my g-father&#8217;s WW-I draft registration. I DON&#8217;T NEED to plow through hundreds of other people&#8217;s draft cards before getting to the mext possible military entry.</p>
<p>Just change the scheme to specify exclusion rather than inclusion in the list of databases listed when editing the search.</p>
<p>Pat O&#8217;Brien</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Willford</title>
		<link>http://blogs.ancestry.com/ancestry/2009/11/07/refine-your-searches-in-fewer-steps-in-new-search/#comment-42307</link>
		<dc:creator>Charles Willford</dc:creator>
		<pubDate>Thu, 19 Nov 2009 21:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2397#comment-42307</guid>
		<description>64 Jade,

I understand the Census data. That was not the issue. 

Any way, the last update fixed the problem and now I can select an individual from the family and add it&#039;s data without having to go back and change the search request.

It&#039;s fixed.

Chuck</description>
		<content:encoded><![CDATA[<p>64 Jade,</p>
<p>I understand the Census data. That was not the issue. </p>
<p>Any way, the last update fixed the problem and now I can select an individual from the family and add it&#8217;s data without having to go back and change the search request.</p>
<p>It&#8217;s fixed.</p>
<p>Chuck</p>
]]></content:encoded>
	</item>
</channel>
</rss>
