<?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: How Can I Improve the 1940 U.S. Census?</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-can-i-improve-the-1940-u-s-census</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: Jess</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56943</link>
		<dc:creator>Jess</dc:creator>
		<pubDate>Sun, 09 Sep 2012 08:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56943</guid>
		<description>I have been shocked at how poor the indexing has been for the 1940 Census. In Rockingham, Virginia over 60% of the surnames that I am researching have been indexed incorrectly often with multiple spelling variations on the same page for the same surname. First names and relationship to head of household have also been bad. Ancestry.com&#039;s quality control has been atrocious.

Sure I could submit an alternate name but when we are talking thousands of individuals with the incorrect last name AND a service which I pay for why should I waste my time doing YOUR job.

If people are having issues I highly recommend using familysearch.org which has been more accurate for my surnames and localities or using the long method with street addresses.</description>
		<content:encoded><![CDATA[<p>I have been shocked at how poor the indexing has been for the 1940 Census. In Rockingham, Virginia over 60% of the surnames that I am researching have been indexed incorrectly often with multiple spelling variations on the same page for the same surname. First names and relationship to head of household have also been bad. Ancestry.com&#8217;s quality control has been atrocious.</p>
<p>Sure I could submit an alternate name but when we are talking thousands of individuals with the incorrect last name AND a service which I pay for why should I waste my time doing YOUR job.</p>
<p>If people are having issues I highly recommend using familysearch.org which has been more accurate for my surnames and localities or using the long method with street addresses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Helen Dearing</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56918</link>
		<dc:creator>Helen Dearing</dc:creator>
		<pubDate>Wed, 05 Sep 2012 21:42:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56918</guid>
		<description>I, too, have found many, many errors in indexing names that were originally written correctly by the enumerator in 1940.  This is especially frustrating since the majority of these names are commonly used in the USA, leading me to the belief that Ancestry outsourced the 1940 Census transcription to people who are not familiar with USA names.  Disappointed in Ancestry!
Helen Dearing</description>
		<content:encoded><![CDATA[<p>I, too, have found many, many errors in indexing names that were originally written correctly by the enumerator in 1940.  This is especially frustrating since the majority of these names are commonly used in the USA, leading me to the belief that Ancestry outsourced the 1940 Census transcription to people who are not familiar with USA names.  Disappointed in Ancestry!<br />
Helen Dearing</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fchambers</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56818</link>
		<dc:creator>fchambers</dc:creator>
		<pubDate>Thu, 30 Aug 2012 19:05:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56818</guid>
		<description>So far, I have found hundreds of incredibly transcribed misspellings of both given and surnames.  It&#039;s hard to believe that the transcribers were paid to make such obvious an careless errors.  I have corrected each error as I found it whether a family member or not.  Otherwise, it would be impossible for anyone to find someone in the search results.  It would be prudent to make the transcribers review the original census images, look more closely and correct their errors (without additional pay since their carelessness created this problem).  As we all know, haste makes waste.</description>
		<content:encoded><![CDATA[<p>So far, I have found hundreds of incredibly transcribed misspellings of both given and surnames.  It&#8217;s hard to believe that the transcribers were paid to make such obvious an careless errors.  I have corrected each error as I found it whether a family member or not.  Otherwise, it would be impossible for anyone to find someone in the search results.  It would be prudent to make the transcribers review the original census images, look more closely and correct their errors (without additional pay since their carelessness created this problem).  As we all know, haste makes waste.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MsWinston</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56752</link>
		<dc:creator>MsWinston</dc:creator>
		<pubDate>Sat, 25 Aug 2012 17:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56752</guid>
		<description>Some individuals and families are fairly easy to find, while others are impossible to locate using the Index. I have found this to be particularly true for families who lived in the state of Arkansas, where I have many distant maternal cousins. Whole families are just missing, yet the people didn&#039;t die until the 1970&#039;s and beyond. I have researched under married names and maiden names, made deliberate spelling errors on surnames, all to no end. What in the heck is going on?</description>
		<content:encoded><![CDATA[<p>Some individuals and families are fairly easy to find, while others are impossible to locate using the Index. I have found this to be particularly true for families who lived in the state of Arkansas, where I have many distant maternal cousins. Whole families are just missing, yet the people didn&#8217;t die until the 1970&#8242;s and beyond. I have researched under married names and maiden names, made deliberate spelling errors on surnames, all to no end. What in the heck is going on?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ellen</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56708</link>
		<dc:creator>Ellen</dc:creator>
		<pubDate>Thu, 23 Aug 2012 14:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56708</guid>
		<description>It appears that searching on &quot;William&quot; no longer pulls up names indexed as &quot;Wm&quot;; &quot;John&quot; no longer pulls up &quot;Jno&quot;; Samuel no longer pulls up Sam&#039;l; etc. I&#039;ve been making an addition to the names enumerated and indexed by abbreviations when I find them and doing it under &quot;variation&quot;. I would like you see you go back to the former method of searching. I like that you do not remove the earlier (incorrect) transcription as this allows me (if I&#039;ve entered it in my database as originally transcribed [i.e., Sara for Sarah]to find it again easily under the incorrect rendering as well as the corrected one. I would also like to see an alternative in the name correction protocol that says Formal Name (or something similar) so that when John&#039;s name has been entered as &quot;Johnny&quot; by the enumerator there is an accurate place to enter his true name.</description>
		<content:encoded><![CDATA[<p>It appears that searching on &#8220;William&#8221; no longer pulls up names indexed as &#8220;Wm&#8221;; &#8220;John&#8221; no longer pulls up &#8220;Jno&#8221;; Samuel no longer pulls up Sam&#8217;l; etc. I&#8217;ve been making an addition to the names enumerated and indexed by abbreviations when I find them and doing it under &#8220;variation&#8221;. I would like you see you go back to the former method of searching. I like that you do not remove the earlier (incorrect) transcription as this allows me (if I&#8217;ve entered it in my database as originally transcribed [i.e., Sara for Sarah]to find it again easily under the incorrect rendering as well as the corrected one. I would also like to see an alternative in the name correction protocol that says Formal Name (or something similar) so that when John&#8217;s name has been entered as &#8220;Johnny&#8221; by the enumerator there is an accurate place to enter his true name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Rabbeni</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56682</link>
		<dc:creator>Kim Rabbeni</dc:creator>
		<pubDate>Mon, 20 Aug 2012 23:44:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56682</guid>
		<description>What are you supposed to do when you errors in census itself?

I found an instance where at least one street was placed in two different enumeration districts.  So the people on the street were counted twice in the census.

Is there a protocol for reporting errors?  This wasn&#039;t a case of someone transcribing the information incorrectly.  This was a case of two different census takers interviewing the same people.  It&#039;s the exact same address and the exact same information.  I found this because one of the people on the street is in my tree.</description>
		<content:encoded><![CDATA[<p>What are you supposed to do when you errors in census itself?</p>
<p>I found an instance where at least one street was placed in two different enumeration districts.  So the people on the street were counted twice in the census.</p>
<p>Is there a protocol for reporting errors?  This wasn&#8217;t a case of someone transcribing the information incorrectly.  This was a case of two different census takers interviewing the same people.  It&#8217;s the exact same address and the exact same information.  I found this because one of the people on the street is in my tree.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George C. Dixon</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56680</link>
		<dc:creator>George C. Dixon</dc:creator>
		<pubDate>Mon, 20 Aug 2012 19:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56680</guid>
		<description>I will agree that I am very disappointed with the way the 1940 Census has been set up for a couple of reasons.  First,  I have any number of family members whose names I can clearly read on the census form but cannot merge into my family tree program because their names do not appear when I do a web search via the little green leaf or otherwise.  Secondly, all too often in order for me to merge those family members I have found in the 1940 Census, it is necessary for me to close my program in order to merge them into my tree,  Rarely am I able to merge successfully these names into my program.  Please do not tell me that it is my program, for I am able to merge other material such as directory listings or war records, etc.  I will also agree with one of the individuals above who commented upon the misspelling of names.  I do not know who did the transcribing of the 1940 Census, but they certainly cannot read English correctly.</description>
		<content:encoded><![CDATA[<p>I will agree that I am very disappointed with the way the 1940 Census has been set up for a couple of reasons.  First,  I have any number of family members whose names I can clearly read on the census form but cannot merge into my family tree program because their names do not appear when I do a web search via the little green leaf or otherwise.  Secondly, all too often in order for me to merge those family members I have found in the 1940 Census, it is necessary for me to close my program in order to merge them into my tree,  Rarely am I able to merge successfully these names into my program.  Please do not tell me that it is my program, for I am able to merge other material such as directory listings or war records, etc.  I will also agree with one of the individuals above who commented upon the misspelling of names.  I do not know who did the transcribing of the 1940 Census, but they certainly cannot read English correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toni</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56667</link>
		<dc:creator>Toni</dc:creator>
		<pubDate>Sun, 19 Aug 2012 19:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56667</guid>
		<description>Although disappointed at the many indexing errors I have been finding in the 1940 census, there is one bright spot.
I just discovered that highlighting the name in the bottom index allows alternate information to be added for a name I was not researching, right there, without having to do another search.  Louisiana has many French names that show up badly transcribed.  I&#039;m glad if I can help others find their family members by making a few extra submissions.</description>
		<content:encoded><![CDATA[<p>Although disappointed at the many indexing errors I have been finding in the 1940 census, there is one bright spot.<br />
I just discovered that highlighting the name in the bottom index allows alternate information to be added for a name I was not researching, right there, without having to do another search.  Louisiana has many French names that show up badly transcribed.  I&#8217;m glad if I can help others find their family members by making a few extra submissions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurie</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56658</link>
		<dc:creator>Laurie</dc:creator>
		<pubDate>Sun, 19 Aug 2012 00:34:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56658</guid>
		<description>While it is helpful when people correct transcription errors by entering alternate names, one thing I find frustrating is when users submit alternate names that are incorrect. There&#039;s no way to notify Ancestry to remove the invalid alternate.</description>
		<content:encoded><![CDATA[<p>While it is helpful when people correct transcription errors by entering alternate names, one thing I find frustrating is when users submit alternate names that are incorrect. There&#8217;s no way to notify Ancestry to remove the invalid alternate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Concetta Phillipps</title>
		<link>http://blogs.ancestry.com/ancestry/2012/08/15/how-can-i-improve-the-1940-u-s-census/#comment-56638</link>
		<dc:creator>Concetta Phillipps</dc:creator>
		<pubDate>Fri, 17 Aug 2012 16:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7984#comment-56638</guid>
		<description>I&#039;ve been very disappointed with the quality of the indexing so far for Ancestry for the 1940. Very obvious errors have been made, and the Quality Assurance reviews have obviously not caught them. For example, on one page, the gentleman&#039;s name was clearly &quot;Lamar G&quot; and Ancestry ran the whole name through so that the indexed entry was &quot;Lamarg&quot;, making it impossible to find the gentleman by name because of the way Ancestry&#039;s search system works. This was not my own family, I reported it because it was the right thing to do.

The 1940 errors on FamilySearch aren&#039;t fixable, but the overall quality of the indexing is definitely better than on Ancestry. All the fancy technical advancements are great, but bottom line is, we need quality in the indexed entries in order to be able to use them.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been very disappointed with the quality of the indexing so far for Ancestry for the 1940. Very obvious errors have been made, and the Quality Assurance reviews have obviously not caught them. For example, on one page, the gentleman&#8217;s name was clearly &#8220;Lamar G&#8221; and Ancestry ran the whole name through so that the indexed entry was &#8220;Lamarg&#8221;, making it impossible to find the gentleman by name because of the way Ancestry&#8217;s search system works. This was not my own family, I reported it because it was the right thing to do.</p>
<p>The 1940 errors on FamilySearch aren&#8217;t fixable, but the overall quality of the indexing is definitely better than on Ancestry. All the fancy technical advancements are great, but bottom line is, we need quality in the indexed entries in order to be able to use them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
