<?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: Latest on lifespan filtering</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=latest-on-lifespan-filtering</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: Anne Mitchell</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38253</link>
		<dc:creator>Anne Mitchell</dc:creator>
		<pubDate>Fri, 08 May 2009 23:36:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38253</guid>
		<description>Two hundred and eight comments...if nothing else, we can agree that there is interest in search. :-)

A few things:

&lt;ul&gt;
&lt;li&gt; Trees is not my area, but I do know they are working on some merge problem, or some other problem and they are rolling a fix sometime on Monday, so trees should be in better shape on Tuesday.
&lt;li&gt;When you search on historical records from a tree page, you get a long list of trees, which you shouldn&#039;t and there have been issues with names not going in the right places.  That fix is scheduled to go live, last I heard, on May 20th.
&lt;li&gt;As for the ordering of household members in alphabetical order instead of page order, yes, I agree it is annoying.  Results have been reordered to be alphabetical in search results, because it&#039;s more efficient, and because it tends to make more sense to our members.  Down side of that is that it shows up in alphabetical on the record page.  And yes, we need to go spend the time to order it differently, but I&#039;ll go out on a limb here and guess that it&#039;s not in your top 5 of things you really want us to do.
&lt;li&gt;I&#039;m closing this blog post to comments, because I&#039;m to NGS in Raleigh, NC and I won&#039;t be able to pay a lot of attention to this until I get back.  If you are at NGS, stop by the booth and say hi, or come see my search presentation and you can ask me questions all day long! :-)
&lt;/ul&gt;

Happy Searching.</description>
		<content:encoded><![CDATA[<p>Two hundred and eight comments&#8230;if nothing else, we can agree that there is interest in search. <img src='http://blogs.ancestry.com/ancestry/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>A few things:</p>
<ul>
<li> Trees is not my area, but I do know they are working on some merge problem, or some other problem and they are rolling a fix sometime on Monday, so trees should be in better shape on Tuesday.
</li>
<li>When you search on historical records from a tree page, you get a long list of trees, which you shouldn&#8217;t and there have been issues with names not going in the right places.  That fix is scheduled to go live, last I heard, on May 20th.
</li>
<li>As for the ordering of household members in alphabetical order instead of page order, yes, I agree it is annoying.  Results have been reordered to be alphabetical in search results, because it&#8217;s more efficient, and because it tends to make more sense to our members.  Down side of that is that it shows up in alphabetical on the record page.  And yes, we need to go spend the time to order it differently, but I&#8217;ll go out on a limb here and guess that it&#8217;s not in your top 5 of things you really want us to do.
</li>
<li>I&#8217;m closing this blog post to comments, because I&#8217;m to NGS in Raleigh, NC and I won&#8217;t be able to pay a lot of attention to this until I get back.  If you are at NGS, stop by the booth and say hi, or come see my search presentation and you can ask me questions all day long! <img src='http://blogs.ancestry.com/ancestry/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />
</li>
</ul>
<p>Happy Searching.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Forrest</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38252</link>
		<dc:creator>Kent Forrest</dc:creator>
		<pubDate>Fri, 08 May 2009 23:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38252</guid>
		<description>In general I see the New search as a work in progress. It is still a BETA as far as I am concerned. 

What truly disappoints me is the a host of other issues that seem to be entirely ignored: (e.g. lack of ability to organize photos into folders, no tags for group photos, can&#039;t easily control relative link merges with mispelled names, etc.)

I would rather have Ancestry work on perfecting the organization of what I have than wholesale rooting though questionable data.)

I could go on but no one is going to respond so .....</description>
		<content:encoded><![CDATA[<p>In general I see the New search as a work in progress. It is still a BETA as far as I am concerned. </p>
<p>What truly disappoints me is the a host of other issues that seem to be entirely ignored: (e.g. lack of ability to organize photos into folders, no tags for group photos, can&#8217;t easily control relative link merges with mispelled names, etc.)</p>
<p>I would rather have Ancestry work on perfecting the organization of what I have than wholesale rooting though questionable data.)</p>
<p>I could go on but no one is going to respond so &#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38251</link>
		<dc:creator>Ann</dc:creator>
		<pubDate>Fri, 08 May 2009 22:52:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38251</guid>
		<description>To Jim #203

Hi Jim,

Yes, I also have the same person in 2 trees - my original tree, that just got too messy and will eventually be deleted, and my &quot;good tree&quot; that is and will be a work in progress for years to come.

I also sometimes get the issue that ancestry decides to save the info to my &quot;bad&quot; tree, so I have learned to watch very carefully when I get to the point of attaching the info. There is (in small print) the option to change the tree to which you are saving.

Good luck!</description>
		<content:encoded><![CDATA[<p>To Jim #203</p>
<p>Hi Jim,</p>
<p>Yes, I also have the same person in 2 trees &#8211; my original tree, that just got too messy and will eventually be deleted, and my &#8220;good tree&#8221; that is and will be a work in progress for years to come.</p>
<p>I also sometimes get the issue that ancestry decides to save the info to my &#8220;bad&#8221; tree, so I have learned to watch very carefully when I get to the point of attaching the info. There is (in small print) the option to change the tree to which you are saving.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linda Clark</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38250</link>
		<dc:creator>Linda Clark</dc:creator>
		<pubDate>Fri, 08 May 2009 22:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38250</guid>
		<description>I also find it takes entirely to long to look up any records since the new and improved changes were made. It is so tedious, I often just give up and turn off the computer. I know progress is important, but the parameters are often way to liberal. I want to have the option to do the way that works best for me whether it is the old or new version. 
When I look for someone I know is in KY, why give me information from someone in California. I know you have a difficult job trying to make us all happy, but I am a very unhappy camper right now.</description>
		<content:encoded><![CDATA[<p>I also find it takes entirely to long to look up any records since the new and improved changes were made. It is so tedious, I often just give up and turn off the computer. I know progress is important, but the parameters are often way to liberal. I want to have the option to do the way that works best for me whether it is the old or new version.<br />
When I look for someone I know is in KY, why give me information from someone in California. I know you have a difficult job trying to make us all happy, but I am a very unhappy camper right now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Nygard</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38249</link>
		<dc:creator>Jim Nygard</dc:creator>
		<pubDate>Fri, 08 May 2009 22:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38249</guid>
		<description>Is anyone else having this problem??

There is a bug in the Merge function...
When I find data that I want to merge in to the record of my open Tree and I select the save function it changes from the OPEN tree I am working in to another tree in my list of trees and saves the data there... and Yes I have the same indivdual in two different trees...  

The &quot;REAL&quot; concern is that there is no indicator of this happening until AFTER the merge has completed and you are back to the Person Page. 

VERY FRUSTRATING....</description>
		<content:encoded><![CDATA[<p>Is anyone else having this problem??</p>
<p>There is a bug in the Merge function&#8230;<br />
When I find data that I want to merge in to the record of my open Tree and I select the save function it changes from the OPEN tree I am working in to another tree in my list of trees and saves the data there&#8230; and Yes I have the same indivdual in two different trees&#8230;  </p>
<p>The &#8220;REAL&#8221; concern is that there is no indicator of this happening until AFTER the merge has completed and you are back to the Person Page. </p>
<p>VERY FRUSTRATING&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barb</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38248</link>
		<dc:creator>Barb</dc:creator>
		<pubDate>Fri, 08 May 2009 22:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38248</guid>
		<description>I have not found the new search useful at all and see no improvement.  If I search for a person named Joseph Code, the results I received are zip code, morse code. William Code, Joseph Daly.  None of these are relevant. Scrolling through all of the irrelevant searches, of which there are many, is a waste of time.  If someone else is having success in my examples, please comment, and if you are not please comment.  I cannot believe that I am the only person who is running into this problem.</description>
		<content:encoded><![CDATA[<p>I have not found the new search useful at all and see no improvement.  If I search for a person named Joseph Code, the results I received are zip code, morse code. William Code, Joseph Daly.  None of these are relevant. Scrolling through all of the irrelevant searches, of which there are many, is a waste of time.  If someone else is having success in my examples, please comment, and if you are not please comment.  I cannot believe that I am the only person who is running into this problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janis Jones</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38247</link>
		<dc:creator>Janis Jones</dc:creator>
		<pubDate>Fri, 08 May 2009 22:22:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38247</guid>
		<description>I &quot;feel the pain&quot; of others who have posted about problems that occur with the changes to new search.  In my own research, I&#039;ve used a lot of &quot;tricks&quot; to get the results I want fairly consistently, regardless of the ongoing glitches.  However, the decision to have public and private trees returned at the top level of search is one of the worst ideas anyone has had since I subscribed.  Other people&#039;s trees are, literally, the very last thing I want to see when I&#039;m using the search tool for individual information.  I want original source material:  Census, vitals, military records, not trees.  They are useful enough for suggesting new leads or contacting others researching the same persons, but they should not be the first information presented on a search.</description>
		<content:encoded><![CDATA[<p>I &#8220;feel the pain&#8221; of others who have posted about problems that occur with the changes to new search.  In my own research, I&#8217;ve used a lot of &#8220;tricks&#8221; to get the results I want fairly consistently, regardless of the ongoing glitches.  However, the decision to have public and private trees returned at the top level of search is one of the worst ideas anyone has had since I subscribed.  Other people&#8217;s trees are, literally, the very last thing I want to see when I&#8217;m using the search tool for individual information.  I want original source material:  Census, vitals, military records, not trees.  They are useful enough for suggesting new leads or contacting others researching the same persons, but they should not be the first information presented on a search.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Western</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38244</link>
		<dc:creator>Ed Western</dc:creator>
		<pubDate>Fri, 08 May 2009 19:28:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38244</guid>
		<description>The new search doesn&#039;t always group blacks together.  A lot of times a search for blacks is different than a search for coloreds or negro.  When will Ancestry work on this?</description>
		<content:encoded><![CDATA[<p>The new search doesn&#8217;t always group blacks together.  A lot of times a search for blacks is different than a search for coloreds or negro.  When will Ancestry work on this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Cousins</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38243</link>
		<dc:creator>Tony Cousins</dc:creator>
		<pubDate>Fri, 08 May 2009 19:25:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38243</guid>
		<description>Michelle #198

In some ways I agree, the information that has been amassed on Ancestry really is mind boggling, but that only takes money to buy the collections and scan them. It&#039;s the transcription, indexing, presentation and searching that is paramount. Ancestry is not doing a very good job on that, especially the relevancy of the search results.

Ancestry Anne:

I do believe that someone at Ancestry has been listening - I don’t have to hit the back button multiple times just to go back one page. If that is the case then please pass on my thanks – if it isn’t the case please don’t switch it back on again ;)

TonyC</description>
		<content:encoded><![CDATA[<p>Michelle #198</p>
<p>In some ways I agree, the information that has been amassed on Ancestry really is mind boggling, but that only takes money to buy the collections and scan them. It&#8217;s the transcription, indexing, presentation and searching that is paramount. Ancestry is not doing a very good job on that, especially the relevancy of the search results.</p>
<p>Ancestry Anne:</p>
<p>I do believe that someone at Ancestry has been listening &#8211; I don’t have to hit the back button multiple times just to go back one page. If that is the case then please pass on my thanks – if it isn’t the case please don’t switch it back on again <img src='http://blogs.ancestry.com/ancestry/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>TonyC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michele k.</title>
		<link>http://blogs.ancestry.com/ancestry/2009/05/05/latest-on-lifespan-filtering/#comment-38242</link>
		<dc:creator>michele k.</dc:creator>
		<pubDate>Fri, 08 May 2009 18:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1198#comment-38242</guid>
		<description>All of your efforts, whether they work perfectly or not, are greatly appreciated. I have spent months (when you add up all the hours) combing thru records, and sometimes it is the looking thru all of them that one relevant shows up.
I&#039;m excited that you are still streamlining the process. It&#039;s that instant gratification ideal that allows people to never be satisfied not matter what.
In graditude and sincerity,
michele</description>
		<content:encoded><![CDATA[<p>All of your efforts, whether they work perfectly or not, are greatly appreciated. I have spent months (when you add up all the hours) combing thru records, and sometimes it is the looking thru all of them that one relevant shows up.<br />
I&#8217;m excited that you are still streamlining the process. It&#8217;s that instant gratification ideal that allows people to never be satisfied not matter what.<br />
In graditude and sincerity,<br />
michele</p>
]]></content:encoded>
	</item>
</channel>
</rss>
