<?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: Ancestry Search: Controlling your results with filters</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=ancestry-search-controlling-your-results-with-filters</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Wed, 19 Jun 2013 12:17:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: John Atkins</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43593</link>
		<dc:creator>John Atkins</dc:creator>
		<pubDate>Tue, 26 Jan 2010 20:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43593</guid>
		<description>Update to #74 -

The search pages referred to have reverted back to the previous version.  Thank you.</description>
		<content:encoded><![CDATA[<p>Update to #74 -</p>
<p>The search pages referred to have reverted back to the previous version.  Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diann Cosgrove</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43583</link>
		<dc:creator>Diann Cosgrove</dc:creator>
		<pubDate>Tue, 26 Jan 2010 10:35:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43583</guid>
		<description>I have not been able to figure out how to work this site.  For instance I need to know how to get rid of the pop-up that comes up for every new page re: Internet Explorer 6 which says &quot;it is time to upgrade your browswer&quot;.  This is a work computer and we are not allowed to download programs etc.

More on the subjects you all have been discussing, I too would like to be able to exclude records.  I have a last name of &quot;Baptist&quot; to research. Imagine the thousands of records I get for every Baptist church or minister in the world.  I hate getting thousands of telephone listings for people living before the telephone was invented.  I dislike having to start over again when I find a record and save it to my family tree and then start searching again  I might have found the record way down the line at 10,001 or something like that and have to page through all the records again to get to it.  I find that the less info given the more likely I am to get hits for my tree but it is a paining searching through so many.  In most cases, I too would like to be able to restrict the search to just Canada (or even Ontario, Canada) or just Ohio or just Washington State (this gives me a whole bunch of Washington cities usually on the east coast).</description>
		<content:encoded><![CDATA[<p>I have not been able to figure out how to work this site.  For instance I need to know how to get rid of the pop-up that comes up for every new page re: Internet Explorer 6 which says &#8220;it is time to upgrade your browswer&#8221;.  This is a work computer and we are not allowed to download programs etc.</p>
<p>More on the subjects you all have been discussing, I too would like to be able to exclude records.  I have a last name of &#8220;Baptist&#8221; to research. Imagine the thousands of records I get for every Baptist church or minister in the world.  I hate getting thousands of telephone listings for people living before the telephone was invented.  I dislike having to start over again when I find a record and save it to my family tree and then start searching again  I might have found the record way down the line at 10,001 or something like that and have to page through all the records again to get to it.  I find that the less info given the more likely I am to get hits for my tree but it is a paining searching through so many.  In most cases, I too would like to be able to restrict the search to just Canada (or even Ontario, Canada) or just Ohio or just Washington State (this gives me a whole bunch of Washington cities usually on the east coast).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hazel Clack</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43571</link>
		<dc:creator>Hazel Clack</dc:creator>
		<pubDate>Mon, 25 Jan 2010 22:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43571</guid>
		<description>I have been frustration for years with the information and issues within Ancesty.com. For instance: I upgraded to FTM2009 from the 2006 and rather than upload my data from 2006 into the 2009 I decided to do it manually and that way I could spot any incorrections I might have had, thinking that since the 2009 program added &quot;Hints&quot; that it would be a piece of cake adding the prior documents that had been pulled from Ancestry. Well, I found out that documents, of all types, that I had pulled into my 2006 program were no longer available to me in the 2009 program. Most of my research was in the state of GA and 99% of it was in one county...my family went to GA To this particular county in the mid 1700&#039;s and never left. Ancestry has 3 different catagories, by years, of marriage records for GA and either none showed up or only one showed up and not with the surname I searched for. This still happens on occassions. Now I am having an issue with the ERROR!!! message, or the search goes into loop mode and never brings up a record.  The GA Death Records will not allow it to be merged if the image is opened.  I search for a specific surname and I get everything but the surname I searched for or none show up for GA and I know the record was there when I added it to the 2006 FTM. I agree with all the issues regarding the census records. I never merge a census record until I view the image.  The translations of some of these censuses is just awful. I would like to see a search feature that allows one to search records from a specific state and for a specific county for any given record.  I don&#039;t need nor do I care to scroll through thousands of irrelavent records for other states. If I am searching in GA, born and died there, I don&#039;t need all the extras.  Granted, some are better at using filters than other, I&#039;m an &#039;other&#039;, however Ancestry does have lots of issues at the present that need to be handled First and once that&#039;s done then add your bells and whistles to the program. Ancestry should be adding more of the GA records to their database. Every addition of records they have added do not pertain to a few of the original southern colonies.  Georgia is a state that drew many immigrants from Maryland, VA, NC, SC etc and then some of them spread into other areas as land became available and states were formed. The rescanned censuses using the &#039;new light&#039; method. Good idea and it does make some of the censuses mor readable but then there are the ones that were hit with so much light that the image is barely readable. Happened last night and I couldn&#039;t report an image problem. There was no Report Image Problem listed...and if there was, there would have been no place to explain the light situation. If there had been, and if there was a correction to make it readable then I&#039;d have to remember to go back and recheck the census.

Ancestry has issues and I trust they are doing their best to please everyone, however bottom line is fix what is wrong; stop putting bandids on the problem; stop adding bells and whistles at the expense of time that could and should be devoted to records, enhancing records, adding records for the small counties in the southern states..some are being tossed..The record search is a hit or miss and I haven&#039;t found any of the upgrades to be any better.

As for putting any information in an online tree, no way. Not even to make it private. To me private is private and in no way should anyone be able to access it or see any Living information, but glitches do and have happened. Otherwise, my Living family would never have shown up on someone else&#039;s tree. Ancestry can not control everything with a 100% certainty.</description>
		<content:encoded><![CDATA[<p>I have been frustration for years with the information and issues within Ancesty.com. For instance: I upgraded to FTM2009 from the 2006 and rather than upload my data from 2006 into the 2009 I decided to do it manually and that way I could spot any incorrections I might have had, thinking that since the 2009 program added &#8220;Hints&#8221; that it would be a piece of cake adding the prior documents that had been pulled from Ancestry. Well, I found out that documents, of all types, that I had pulled into my 2006 program were no longer available to me in the 2009 program. Most of my research was in the state of GA and 99% of it was in one county&#8230;my family went to GA To this particular county in the mid 1700&#8242;s and never left. Ancestry has 3 different catagories, by years, of marriage records for GA and either none showed up or only one showed up and not with the surname I searched for. This still happens on occassions. Now I am having an issue with the ERROR!!! message, or the search goes into loop mode and never brings up a record.  The GA Death Records will not allow it to be merged if the image is opened.  I search for a specific surname and I get everything but the surname I searched for or none show up for GA and I know the record was there when I added it to the 2006 FTM. I agree with all the issues regarding the census records. I never merge a census record until I view the image.  The translations of some of these censuses is just awful. I would like to see a search feature that allows one to search records from a specific state and for a specific county for any given record.  I don&#8217;t need nor do I care to scroll through thousands of irrelavent records for other states. If I am searching in GA, born and died there, I don&#8217;t need all the extras.  Granted, some are better at using filters than other, I&#8217;m an &#8216;other&#8217;, however Ancestry does have lots of issues at the present that need to be handled First and once that&#8217;s done then add your bells and whistles to the program. Ancestry should be adding more of the GA records to their database. Every addition of records they have added do not pertain to a few of the original southern colonies.  Georgia is a state that drew many immigrants from Maryland, VA, NC, SC etc and then some of them spread into other areas as land became available and states were formed. The rescanned censuses using the &#8216;new light&#8217; method. Good idea and it does make some of the censuses mor readable but then there are the ones that were hit with so much light that the image is barely readable. Happened last night and I couldn&#8217;t report an image problem. There was no Report Image Problem listed&#8230;and if there was, there would have been no place to explain the light situation. If there had been, and if there was a correction to make it readable then I&#8217;d have to remember to go back and recheck the census.</p>
<p>Ancestry has issues and I trust they are doing their best to please everyone, however bottom line is fix what is wrong; stop putting bandids on the problem; stop adding bells and whistles at the expense of time that could and should be devoted to records, enhancing records, adding records for the small counties in the southern states..some are being tossed..The record search is a hit or miss and I haven&#8217;t found any of the upgrades to be any better.</p>
<p>As for putting any information in an online tree, no way. Not even to make it private. To me private is private and in no way should anyone be able to access it or see any Living information, but glitches do and have happened. Otherwise, my Living family would never have shown up on someone else&#8217;s tree. Ancestry can not control everything with a 100% certainty.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: B. Lawson</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43563</link>
		<dc:creator>B. Lawson</dc:creator>
		<pubDate>Mon, 25 Jan 2010 11:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43563</guid>
		<description>Jan 25, 2010.

    Yes, a filter that could focus on only one state, when that particular state has been entered, i.e  New York.</description>
		<content:encoded><![CDATA[<p>Jan 25, 2010.</p>
<p>    Yes, a filter that could focus on only one state, when that particular state has been entered, i.e  New York.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43558</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Mon, 25 Jan 2010 04:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43558</guid>
		<description>Teresa Re: #72

The yearbooks are, in my personal opinion, the second greatest waste of Ancestry&#039;s resources ever seen (the first being the creation and maintaining of that ungodly OneWorldTree).</description>
		<content:encoded><![CDATA[<p>Teresa Re: #72</p>
<p>The yearbooks are, in my personal opinion, the second greatest waste of Ancestry&#8217;s resources ever seen (the first being the creation and maintaining of that ungodly OneWorldTree).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Hatchett</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43557</link>
		<dc:creator>Andy Hatchett</dc:creator>
		<pubDate>Mon, 25 Jan 2010 04:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43557</guid>
		<description>Terry Re: #73

Aren&#039;t Parish Records usually Church of England records? The CoE is, and always has been a government entity; at least that is what I&#039;ve been told.</description>
		<content:encoded><![CDATA[<p>Terry Re: #73</p>
<p>Aren&#8217;t Parish Records usually Church of England records? The CoE is, and always has been a government entity; at least that is what I&#8217;ve been told.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Atkins</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43555</link>
		<dc:creator>John Atkins</dc:creator>
		<pubDate>Mon, 25 Jan 2010 02:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43555</guid>
		<description>Since your Jan 22 maintenance, the search for historical records page has changed.  Beginning from a PROFILE page it no longer appears possible to easily modify (on the search results page) the data for a person.  This layout had enabled me to tweak the search input data and Search Again in just a few key strokes.  In addition, it no longer appears possible to specify race/nationality and gender. 
 
These were filters that were useful.  

Finally, in order to make a change, the edit input box (now at the bottom of that screen instead of on the left side of the results) now has a very limited selection of inputs. 

Apparently you&#039;ve simplified the historical records search inputs from the PROFILE page to the same inputs as on the HOME page. It contains only the basic data choices on the HOME page. Selecting the Advanced search choice requires you to input even the names again (from a new web page). This is just like the Advanced click from the HOME page.  So - this was easier for your programmers, but bad for the CUSTOMERS.

THIS IS A GIANT STEP BACKWARD. WHAT WILL YOU DO?

Since last week I&#039;ve become EXTREMELY dissatisfied.

Fellow customers:  This was written in haste and irritation. I hope I wrote reasonably clearly.</description>
		<content:encoded><![CDATA[<p>Since your Jan 22 maintenance, the search for historical records page has changed.  Beginning from a PROFILE page it no longer appears possible to easily modify (on the search results page) the data for a person.  This layout had enabled me to tweak the search input data and Search Again in just a few key strokes.  In addition, it no longer appears possible to specify race/nationality and gender. </p>
<p>These were filters that were useful.  </p>
<p>Finally, in order to make a change, the edit input box (now at the bottom of that screen instead of on the left side of the results) now has a very limited selection of inputs. </p>
<p>Apparently you&#8217;ve simplified the historical records search inputs from the PROFILE page to the same inputs as on the HOME page. It contains only the basic data choices on the HOME page. Selecting the Advanced search choice requires you to input even the names again (from a new web page). This is just like the Advanced click from the HOME page.  So &#8211; this was easier for your programmers, but bad for the CUSTOMERS.</p>
<p>THIS IS A GIANT STEP BACKWARD. WHAT WILL YOU DO?</p>
<p>Since last week I&#8217;ve become EXTREMELY dissatisfied.</p>
<p>Fellow customers:  This was written in haste and irritation. I hope I wrote reasonably clearly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry Wells</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43551</link>
		<dc:creator>Terry Wells</dc:creator>
		<pubDate>Mon, 25 Jan 2010 00:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43551</guid>
		<description>Andy says:

&quot;The category “Historical Records” should only contain those items which are the official records of, and produced/published by, a government entity.&quot;

So where would you put Parish Records then? (Baptisms, Marriages, Burials) They are not Stories and Publications, Family Trees or Photos and Maps.</description>
		<content:encoded><![CDATA[<p>Andy says:</p>
<p>&#8220;The category “Historical Records” should only contain those items which are the official records of, and produced/published by, a government entity.&#8221;</p>
<p>So where would you put Parish Records then? (Baptisms, Marriages, Burials) They are not Stories and Publications, Family Trees or Photos and Maps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Teresa Floyd</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43536</link>
		<dc:creator>Teresa Floyd</dc:creator>
		<pubDate>Sun, 24 Jan 2010 01:01:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43536</guid>
		<description>I really hope this gets improved.  It is frustrating searching for someone who died say in 1860 and I get all kinds of records for someone living in the 1900s.  Especailly frustrating is the Yearbooks that come up.</description>
		<content:encoded><![CDATA[<p>I really hope this gets improved.  It is frustrating searching for someone who died say in 1860 and I get all kinds of records for someone living in the 1900s.  Especailly frustrating is the Yearbooks that come up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry Bryan</title>
		<link>http://blogs.ancestry.com/ancestry/2010/01/12/ancestry-search-controlling-your-results-with-filters/#comment-43514</link>
		<dc:creator>Jerry Bryan</dc:creator>
		<pubDate>Sat, 23 Jan 2010 15:53:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=2711#comment-43514</guid>
		<description>Re #70, your search for Samuel Oliver in 1870, Washington County, Ohio worked just fine for me just now, both in Old Search and in New Search.  I was using exact search in both cases.

The only issue that comes to mind is the specification of Washington County, Ohio in New Search.  Sometimes when I type a place name into New Search, it fails to match even though it seems that I have typed the place name correctly.  New Search seems to work better if instead of typing the whole place name myself, I choose the place name from the drop down list.  In this case, type enough of the name so that you can see Washington County, Ohio, USA in the drop down list and select it.  If that doesn&#039;t work, then I&#039;m not sure what else to try.

The drop down lists for place names are one of the least endearing features of New Search, by the way.  They seem to work a lot better now than when New Search was first released.  But they still sometimes seem to cause problems.</description>
		<content:encoded><![CDATA[<p>Re #70, your search for Samuel Oliver in 1870, Washington County, Ohio worked just fine for me just now, both in Old Search and in New Search.  I was using exact search in both cases.</p>
<p>The only issue that comes to mind is the specification of Washington County, Ohio in New Search.  Sometimes when I type a place name into New Search, it fails to match even though it seems that I have typed the place name correctly.  New Search seems to work better if instead of typing the whole place name myself, I choose the place name from the drop down list.  In this case, type enough of the name so that you can see Washington County, Ohio, USA in the drop down list and select it.  If that doesn&#8217;t work, then I&#8217;m not sure what else to try.</p>
<p>The drop down lists for place names are one of the least endearing features of New Search, by the way.  They seem to work a lot better now than when New Search was first released.  But they still sometimes seem to cause problems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
