<?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: 1940 Census: Add D.C. to That Index List</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=1940-census-add-d-c-to-that-index-list</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Wed, 19 Jun 2013 04:14:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Linda Ruben</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55391</link>
		<dc:creator>Linda Ruben</dc:creator>
		<pubDate>Tue, 15 May 2012 23:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55391</guid>
		<description>I would like to know when you can honestly predict that Pennsylvania and New York will be searchable. Yes, the indexers are probably working feverishly to make all this happen, but let&#039;s not forget the the indexers AREN&#039;T Ancestry.com, who&#039;s really left us twisting in the wind.</description>
		<content:encoded><![CDATA[<p>I would like to know when you can honestly predict that Pennsylvania and New York will be searchable. Yes, the indexers are probably working feverishly to make all this happen, but let&#8217;s not forget the the indexers AREN&#8217;T Ancestry.com, who&#8217;s really left us twisting in the wind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suzan</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55387</link>
		<dc:creator>Suzan</dc:creator>
		<pubDate>Tue, 15 May 2012 18:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55387</guid>
		<description>Geez zoolie (my grandma&#039;s favourite saying) Ancestry, are you related to JP Morgan Chase?  JP Morgan Chase just lost several billion dollars and report that it&#039;s okay because they still have billions more, t&#039;was just a drop in the bucket loss.  You obviously, and I say obviously after watching six weeks of member frustration, believe that those of us you lose through lack of GOOD customer service and communication will be okay because we&#039;ll be that drop in the bucket loss.  As stated by Lynn Williams-Murphy, #12, I missed the &quot;Will you help us transcribe the census,&quot; announcement (tongue in cheek).  I&#039;ve been a member of Ancestry for nearly a decade, spend several hours a day researching genealogy for friends who can&#039;t afford the $1900+ research estimate by your company, have been a genealogist for 35+ years, and find that 7 out of 10 transcriptions on your service are erroneous.  I also believe in offering solutions for problems.  You could have set up a simple volunteer test for folks like me who are willing to share their time to help index.  Many hands make light work.  Additionally, you could focus more on customer communication, we do keep you in business.  Why not create a &quot;Suggestion Box,&quot; to encourage communication with your customers?   Finally, can you give me a good reason why I shouldn&#039;t cancel my subscription and wait until the end of the year when you may have this 1940 index issue resolved?</description>
		<content:encoded><![CDATA[<p>Geez zoolie (my grandma&#8217;s favourite saying) Ancestry, are you related to JP Morgan Chase?  JP Morgan Chase just lost several billion dollars and report that it&#8217;s okay because they still have billions more, t&#8217;was just a drop in the bucket loss.  You obviously, and I say obviously after watching six weeks of member frustration, believe that those of us you lose through lack of GOOD customer service and communication will be okay because we&#8217;ll be that drop in the bucket loss.  As stated by Lynn Williams-Murphy, #12, I missed the &#8220;Will you help us transcribe the census,&#8221; announcement (tongue in cheek).  I&#8217;ve been a member of Ancestry for nearly a decade, spend several hours a day researching genealogy for friends who can&#8217;t afford the $1900+ research estimate by your company, have been a genealogist for 35+ years, and find that 7 out of 10 transcriptions on your service are erroneous.  I also believe in offering solutions for problems.  You could have set up a simple volunteer test for folks like me who are willing to share their time to help index.  Many hands make light work.  Additionally, you could focus more on customer communication, we do keep you in business.  Why not create a &#8220;Suggestion Box,&#8221; to encourage communication with your customers?   Finally, can you give me a good reason why I shouldn&#8217;t cancel my subscription and wait until the end of the year when you may have this 1940 index issue resolved?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Knight</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55351</link>
		<dc:creator>Tony Knight</dc:creator>
		<pubDate>Thu, 10 May 2012 16:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55351</guid>
		<description>Yet more searchable states available on Family Search today.</description>
		<content:encoded><![CDATA[<p>Yet more searchable states available on Family Search today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Shaw</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55302</link>
		<dc:creator>Bob Shaw</dc:creator>
		<pubDate>Fri, 04 May 2012 11:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55302</guid>
		<description>I can&#039;t belive that ancestry.com just ignores our request for info.  We all understand it will take a while, but gives us some some sort of update.  If this is to be done by the end of 2012 they will need to do about 6 states a month. We(your customers) are asking for some help. Can we get a responce? Even if its we don&#039;t care about our customers.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t belive that ancestry.com just ignores our request for info.  We all understand it will take a while, but gives us some some sort of update.  If this is to be done by the end of 2012 they will need to do about 6 states a month. We(your customers) are asking for some help. Can we get a responce? Even if its we don&#8217;t care about our customers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Zupan</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55292</link>
		<dc:creator>Jeff Zupan</dc:creator>
		<pubDate>Thu, 03 May 2012 13:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55292</guid>
		<description>FamilySearch has just posted Kansas with 1.8 million records.</description>
		<content:encoded><![CDATA[<p>FamilySearch has just posted Kansas with 1.8 million records.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55289</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Thu, 03 May 2012 06:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55289</guid>
		<description>FamilySearch now has 13 states @ 100% and 4 states @ 90% or better. All we know about Ancestry is that they have Nevada, Delaware and the District of Columbia.

Come on, Ancestry! Is it all that hard to tell us the status of your indexing project? Your PR staff either is incompetent or hasn&#039;t got a clue on how to keep the customers fully informed.</description>
		<content:encoded><![CDATA[<p>FamilySearch now has 13 states @ 100% and 4 states @ 90% or better. All we know about Ancestry is that they have Nevada, Delaware and the District of Columbia.</p>
<p>Come on, Ancestry! Is it all that hard to tell us the status of your indexing project? Your PR staff either is incompetent or hasn&#8217;t got a clue on how to keep the customers fully informed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KATHLEEN WHITLOW</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55286</link>
		<dc:creator>KATHLEEN WHITLOW</dc:creator>
		<pubDate>Thu, 03 May 2012 01:01:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55286</guid>
		<description>Please ancestry.com, communicate with us. I agree with Scott of April 27th.  Give us information to &quot;help set reasonable expectations&quot;. I know this is a huge undertaking and I don&#039;t expect immediate results but I do expect some sort of non vague communication from you. Lets face it, what you are giving us now is not communication at all. I know it will take time to do this but you will end up with  informed and happier customer versus frustrated ones.</description>
		<content:encoded><![CDATA[<p>Please ancestry.com, communicate with us. I agree with Scott of April 27th.  Give us information to &#8220;help set reasonable expectations&#8221;. I know this is a huge undertaking and I don&#8217;t expect immediate results but I do expect some sort of non vague communication from you. Lets face it, what you are giving us now is not communication at all. I know it will take time to do this but you will end up with  informed and happier customer versus frustrated ones.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandra Summers</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55281</link>
		<dc:creator>Sandra Summers</dc:creator>
		<pubDate>Wed, 02 May 2012 17:52:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55281</guid>
		<description>I agree with Scott at #10.  I think Ancestry have been poor at managing both expectations and Information.  For me, they have learnt nothing from the UK 1911 Census, released in April 2011.  Ancestry spent all of last year promising a searchable census.  
What we got was an &#039;index&#039;(you try and find Mr Doe), and then the searchable bit, a county at a time.  I am not sure whether it is now all searchable, but most people felt that they were being strung along with &#039;interim&#039; information.
Ancestry:  tell people the full picture, please.</description>
		<content:encoded><![CDATA[<p>I agree with Scott at #10.  I think Ancestry have been poor at managing both expectations and Information.  For me, they have learnt nothing from the UK 1911 Census, released in April 2011.  Ancestry spent all of last year promising a searchable census.<br />
What we got was an &#8216;index&#8217;(you try and find Mr Doe), and then the searchable bit, a county at a time.  I am not sure whether it is now all searchable, but most people felt that they were being strung along with &#8216;interim&#8217; information.<br />
Ancestry:  tell people the full picture, please.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lincoln Lowery</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55277</link>
		<dc:creator>Lincoln Lowery</dc:creator>
		<pubDate>Wed, 02 May 2012 01:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55277</guid>
		<description>Re: Lynn &amp; Nancy&#039;s comments: Just to check, I typed in  last name of &quot;Smith,&quot; and looked at n odd name that cam up. Sadly, Rutt Adams was unavailable for comment... Rutt Adams is a minor typo, but that is what it says... Line 68: http://interactive.ancestry.com/2442/M-T0627-00560-00642/602778?backurl=http%3a%2f%2fsearch.ancestry.com%2fcgi-bin%2fsse.dll%3findiv%3d1%26db%3d1940usfedcen%26rank%3d1%26new%3d1%26MSAV%3d1%26msT%3d1%26gss%3dangs-d%26gsln%3dsmith%26dbOnly%3d_83004006%257c_83004006_x%252c_83004005%257c_83004005_x%252c_F0006AB0%257c_F0006AB0_x%26uidh%3d212%26pcat%3d35%26fh%3d1%26h%3d602778&amp;ssrc=

ALSO, I tried grabbing the image in the new viewer, and it flew around n the screen. It is acting very hinky. I never liked it, but it is not acting right.</description>
		<content:encoded><![CDATA[<p>Re: Lynn &amp; Nancy&#8217;s comments: Just to check, I typed in  last name of &#8220;Smith,&#8221; and looked at n odd name that cam up. Sadly, Rutt Adams was unavailable for comment&#8230; Rutt Adams is a minor typo, but that is what it says&#8230; Line 68: <a href="http://interactive.ancestry.com/2442/M-T0627-00560-00642/602778?backurl=http%3a%2f%2fsearch.ancestry.com%2fcgi-bin%2fsse.dll%3findiv%3d1%26db%3d1940usfedcen%26rank%3d1%26new%3d1%26MSAV%3d1%26msT%3d1%26gss%3dangs-d%26gsln%3dsmith%26dbOnly%3d_83004006%257c_83004006_x%252c_83004005%257c_83004005_x%252c_F0006AB0%257c_F0006AB0_x%26uidh%3d212%26pcat%3d35%26fh%3d1%26h%3d602778&#038;ssrc=" rel="nofollow">http://interactive.ancestry.com/2442/M-T0627-00560-00642/602778?backurl=http%3a%2f%2fsearch.ancestry.com%2fcgi-bin%2fsse.dll%3findiv%3d1%26db%3d1940usfedcen%26rank%3d1%26new%3d1%26MSAV%3d1%26msT%3d1%26gss%3dangs-d%26gsln%3dsmith%26dbOnly%3d_83004006%257c_83004006_x%252c_83004005%257c_83004005_x%252c_F0006AB0%257c_F0006AB0_x%26uidh%3d212%26pcat%3d35%26fh%3d1%26h%3d602778&#038;ssrc=</a></p>
<p>ALSO, I tried grabbing the image in the new viewer, and it flew around n the screen. It is acting very hinky. I never liked it, but it is not acting right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nancy</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/26/1940-census-add-d-c-to-that-index-list/#comment-55266</link>
		<dc:creator>Nancy</dc:creator>
		<pubDate>Mon, 30 Apr 2012 21:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7456#comment-55266</guid>
		<description>I agree with #12.  I have already found at least six errors in transcription. It would better to have a well-indexed census rather than a rushed one.</description>
		<content:encoded><![CDATA[<p>I agree with #12.  I have already found at least six errors in transcription. It would better to have a well-indexed census rather than a rushed one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
