<?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: U.S. Content Update: Is Ancestry.com Slowing Down on U.S. Content?  Nope!</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=us-content-update-is-ancestrycom-slowing-down-on-us-content-nope</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Mon, 20 May 2013 04:33:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Jeanette Stokes Ferguson</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36826</link>
		<dc:creator>Jeanette Stokes Ferguson</dc:creator>
		<pubDate>Mon, 16 Mar 2009 13:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36826</guid>
		<description>I was on a few weeks ago.A tag came up with, A Book of Stokes . I had already clickes on something else
and couldn&#039;t find it again.</description>
		<content:encoded><![CDATA[<p>I was on a few weeks ago.A tag came up with, A Book of Stokes . I had already clickes on something else<br />
and couldn&#8217;t find it again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JP</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36623</link>
		<dc:creator>JP</dc:creator>
		<pubDate>Fri, 13 Mar 2009 16:43:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36623</guid>
		<description>Chris,

There are many databases that are &quot;broken&quot;. I only use a small percentage of all that is available so I can only imagine how many there are out there are a &quot;broken&quot;.

1. From the day they are added

and

2. After someone does something as with the 1925 IA census.

There are also search forms that are &quot;broken&quot; for the same reasons as stated above for the databases. I&#039;m not talking about the complaints you all are getting on the &quot;new improved&quot; searches. There are ways around that problem. I don&#039;t have that problems since I use a VERY old search form.

There are databses that just disappear never to be seen again.

There is information with the results that was once there but part of that information has now disappeared. An example is the IN marriages. The only time you find these is when you are going back to check something out and what you know was there is not longer there. Who knows how many databases are not showing all the information that is availabe in the records but doesn&#039;t show up in the results.

Quality control and testing the products doesn&#039;t seem part of ancestry&#039;s normal operating procedure.

Reporting  broken databases and forms just seems to fall on deaf ears. Some have never been fixed after years of reporting. An example are the Tioga Co., PA WWI card images that we have been reporting over 
and over and over again.

End users are paying for a service and expect quality.

Since it seems to be left us to the end user to do the testing and reporting - although reports fall on deaf ears - I would like to see a message board just for reporting REAL problems which I outlined above.

This message board should have the ability for us to upload images which sometimes better show what the problem is.

I would like it to exclude transcription errors, trees and problems with the &quot;new improved&quot; search engines, shoeboxes, hints and all the other window dressings which don&#039;t really have anything to do with real research.

This message board would need to be monitored by the person responsible for the above. And we would like a response from that person regarding the problem and the schedule for fixing it and then an announcement when the problem is fixed.

If ancestry really cares and wants to have a quality product - quality control, testing the product and listening to the end user and correcting problems would be their top priority.</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>There are many databases that are &#8220;broken&#8221;. I only use a small percentage of all that is available so I can only imagine how many there are out there are a &#8220;broken&#8221;.</p>
<p>1. From the day they are added</p>
<p>and</p>
<p>2. After someone does something as with the 1925 IA census.</p>
<p>There are also search forms that are &#8220;broken&#8221; for the same reasons as stated above for the databases. I&#8217;m not talking about the complaints you all are getting on the &#8220;new improved&#8221; searches. There are ways around that problem. I don&#8217;t have that problems since I use a VERY old search form.</p>
<p>There are databses that just disappear never to be seen again.</p>
<p>There is information with the results that was once there but part of that information has now disappeared. An example is the IN marriages. The only time you find these is when you are going back to check something out and what you know was there is not longer there. Who knows how many databases are not showing all the information that is availabe in the records but doesn&#8217;t show up in the results.</p>
<p>Quality control and testing the products doesn&#8217;t seem part of ancestry&#8217;s normal operating procedure.</p>
<p>Reporting  broken databases and forms just seems to fall on deaf ears. Some have never been fixed after years of reporting. An example are the Tioga Co., PA WWI card images that we have been reporting over<br />
and over and over again.</p>
<p>End users are paying for a service and expect quality.</p>
<p>Since it seems to be left us to the end user to do the testing and reporting &#8211; although reports fall on deaf ears &#8211; I would like to see a message board just for reporting REAL problems which I outlined above.</p>
<p>This message board should have the ability for us to upload images which sometimes better show what the problem is.</p>
<p>I would like it to exclude transcription errors, trees and problems with the &#8220;new improved&#8221; search engines, shoeboxes, hints and all the other window dressings which don&#8217;t really have anything to do with real research.</p>
<p>This message board would need to be monitored by the person responsible for the above. And we would like a response from that person regarding the problem and the schedule for fixing it and then an announcement when the problem is fixed.</p>
<p>If ancestry really cares and wants to have a quality product &#8211; quality control, testing the product and listening to the end user and correcting problems would be their top priority.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ida French</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36232</link>
		<dc:creator>Ida French</dc:creator>
		<pubDate>Thu, 12 Mar 2009 03:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36232</guid>
		<description>Chris,  FYI - I reported a problem to customer service months ago about a problem with the Kentucky Death Records 1852-1953.  Mainly Jefferson County.  The first names were transcribed incorrectly.  They said they would look into it but nothing has been done.  They said I should send in corrections as I found them but this is something that Ancestry should correct.

I can give you some examples:  Sarah A Fisher Died 8 Jan 1875  the index gives the name of A.P. Fisher - If you look at the record the first name is clearly Sarah A.

Julia A Kell Died 10 Jan 1887 the index gives the name of William Kell - If you look at the record the first name is clearly Julia A.

I could site many more but you probably get what  I am saying.  Now this does not occur in later years and I am not sure if it occurs in other counties but it needs to be fixed.</description>
		<content:encoded><![CDATA[<p>Chris,  FYI &#8211; I reported a problem to customer service months ago about a problem with the Kentucky Death Records 1852-1953.  Mainly Jefferson County.  The first names were transcribed incorrectly.  They said they would look into it but nothing has been done.  They said I should send in corrections as I found them but this is something that Ancestry should correct.</p>
<p>I can give you some examples:  Sarah A Fisher Died 8 Jan 1875  the index gives the name of A.P. Fisher &#8211; If you look at the record the first name is clearly Sarah A.</p>
<p>Julia A Kell Died 10 Jan 1887 the index gives the name of William Kell &#8211; If you look at the record the first name is clearly Julia A.</p>
<p>I could site many more but you probably get what  I am saying.  Now this does not occur in later years and I am not sure if it occurs in other counties but it needs to be fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jade</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36220</link>
		<dc:creator>Jade</dc:creator>
		<pubDate>Thu, 12 Mar 2009 01:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36220</guid>
		<description>Chris,

This evening 11 Mar in the USA the missing 1925 Iowa State Census images were restored.

This is a remarkable example of how responsive to database trouble TGN can be when it is determined to do so.  The process of taking care of this in the past few days is also a model of how TGN *can* honestly admit to and address a problem when someone decides to do so.

So - it is possible!  Good things can happen!  Stuff can be done right!

The nagging little question remains - it was reported to Customer Support two weeks ago.

Thanks to everyone who made this fix possible.</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>This evening 11 Mar in the USA the missing 1925 Iowa State Census images were restored.</p>
<p>This is a remarkable example of how responsive to database trouble TGN can be when it is determined to do so.  The process of taking care of this in the past few days is also a model of how TGN *can* honestly admit to and address a problem when someone decides to do so.</p>
<p>So &#8211; it is possible!  Good things can happen!  Stuff can be done right!</p>
<p>The nagging little question remains &#8211; it was reported to Customer Support two weeks ago.</p>
<p>Thanks to everyone who made this fix possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Hennings</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36183</link>
		<dc:creator>Ann Hennings</dc:creator>
		<pubDate>Wed, 11 Mar 2009 22:56:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36183</guid>
		<description>Am I the only one who would like to see a translation of new database titles when they are not in English?  Isn&#039;t there room for both?  I might use them (along with Bable Fish translator) if I had some idea of what the content was.  It would sure save time.</description>
		<content:encoded><![CDATA[<p>Am I the only one who would like to see a translation of new database titles when they are not in English?  Isn&#8217;t there room for both?  I might use them (along with Bable Fish translator) if I had some idea of what the content was.  It would sure save time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36162</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Wed, 11 Mar 2009 21:26:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36162</guid>
		<description>In terms of what happened with the Iowa State Census missing images, a bit of human error and a bit of process complexity.  We&#039;ve documented the learnings to help avoid this happening in the future.</description>
		<content:encoded><![CDATA[<p>In terms of what happened with the Iowa State Census missing images, a bit of human error and a bit of process complexity.  We&#8217;ve documented the learnings to help avoid this happening in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jade</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36121</link>
		<dc:creator>Jade</dc:creator>
		<pubDate>Wed, 11 Mar 2009 18:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36121</guid>
		<description>Chris,

Thank you very much for the info on the 1925 Iowa State Census!  Can you tell us how deleting half of the images occurred?

Now, if we can only get the images for the last 2/3 of the alphabet for World War I Draft Registration Cards for Tioga Co, PA; the images are somewhere, they are indexed, but the images cannot be found by the index links or by browsing.  This issue was brought to Ancestry&#039;s attention more than 2-1/2 years ago.  No explanation was offered.

Thank you so much,
Jade</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Thank you very much for the info on the 1925 Iowa State Census!  Can you tell us how deleting half of the images occurred?</p>
<p>Now, if we can only get the images for the last 2/3 of the alphabet for World War I Draft Registration Cards for Tioga Co, PA; the images are somewhere, they are indexed, but the images cannot be found by the index links or by browsing.  This issue was brought to Ancestry&#8217;s attention more than 2-1/2 years ago.  No explanation was offered.</p>
<p>Thank you so much,<br />
Jade</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kathy Duncan Cawley</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36113</link>
		<dc:creator>Kathy Duncan Cawley</dc:creator>
		<pubDate>Wed, 11 Mar 2009 17:03:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36113</guid>
		<description>I too have noticed the dramatic decrease of U.S. posting......a mere trickle.
I am thinking of canceling my subscription as we could certainly use the money.

I think it&#039;s very sad that not only have the records dwindled, but even with my DSL connection, AOL is painfully slow at peak hours. 
I think it got to big and forgot to grow, shame shame</description>
		<content:encoded><![CDATA[<p>I too have noticed the dramatic decrease of U.S. posting&#8230;&#8230;a mere trickle.<br />
I am thinking of canceling my subscription as we could certainly use the money.</p>
<p>I think it&#8217;s very sad that not only have the records dwindled, but even with my DSL connection, AOL is painfully slow at peak hours.<br />
I think it got to big and forgot to grow, shame shame</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36107</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Wed, 11 Mar 2009 16:52:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-36107</guid>
		<description>FYI: The Iowa State Census missing image problem has been found and will be fixed on the site shortly.  Thanks for pointing this out to us.</description>
		<content:encoded><![CDATA[<p>FYI: The Iowa State Census missing image problem has been found and will be fixed on the site shortly.  Thanks for pointing this out to us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JP</title>
		<link>http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-35925</link>
		<dc:creator>JP</dc:creator>
		<pubDate>Tue, 10 Mar 2009 19:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/02/26/us-content-update-is-ancestrycom-slowing-down-on-us-content-nope/#comment-35925</guid>
		<description>Mike,

If I had cancelled my subscription at some point and then started again I agree that whatever their policy is at the time would trump previous policies or if they had personally notified me of a change in their policy that would take place at the time of renewal I would be stuck with whatever they chose to do.

With my  US Records Colleciton subscription they just starting locking me out of new US records. This was in the middle of my subscription.

As you know, ancestry just bills your account unless you tell them to cancel your subscription. With any other contract, rent, leasing etc. you are notified of changes and you are usually required to be notified a certain number of days before the renewal period.

I have received very few renewal notices and none of them have stated that I would no longer receive the same services as what I originally signed up for and I have never been notified that they are removing one database or another.

IMO, Ancestry is the provider and it is their resposibility to notifiy subscribers in policy changes and that those changes need to be in writing to the individual subscriber.

Since I don&#039;t know the ins and outs of the legalities of any of this - some of this is fact and some is opinion - I could be way out in left field on the opinion part.

This discussion is probably all mute. Ancestry will do what it wants to do - like NEVER doesn&#039;t really mean NEVER.

Since I have cancelled my paid yearly subscription I may take it once in a while for a month if anything interesting shows up but I was without any subscription for about 9 months and I can say that I didn&#039;t miss out on much during that time period.</description>
		<content:encoded><![CDATA[<p>Mike,</p>
<p>If I had cancelled my subscription at some point and then started again I agree that whatever their policy is at the time would trump previous policies or if they had personally notified me of a change in their policy that would take place at the time of renewal I would be stuck with whatever they chose to do.</p>
<p>With my  US Records Colleciton subscription they just starting locking me out of new US records. This was in the middle of my subscription.</p>
<p>As you know, ancestry just bills your account unless you tell them to cancel your subscription. With any other contract, rent, leasing etc. you are notified of changes and you are usually required to be notified a certain number of days before the renewal period.</p>
<p>I have received very few renewal notices and none of them have stated that I would no longer receive the same services as what I originally signed up for and I have never been notified that they are removing one database or another.</p>
<p>IMO, Ancestry is the provider and it is their resposibility to notifiy subscribers in policy changes and that those changes need to be in writing to the individual subscriber.</p>
<p>Since I don&#8217;t know the ins and outs of the legalities of any of this &#8211; some of this is fact and some is opinion &#8211; I could be way out in left field on the opinion part.</p>
<p>This discussion is probably all mute. Ancestry will do what it wants to do &#8211; like NEVER doesn&#8217;t really mean NEVER.</p>
<p>Since I have cancelled my paid yearly subscription I may take it once in a while for a month if anything interesting shows up but I was without any subscription for about 9 months and I can say that I didn&#8217;t miss out on much during that time period.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
