tag:blogger.com,1999:blog-5512311610334754148.post339954564936190887..comments2023-04-20T12:46:11.858-06:00Comments on The Ancestry Insider: Monday Mailbox: Ancestry.com Indexing InaccuracyThe Ancestry Insiderhttp://www.blogger.com/profile/02490682912125335188noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-5512311610334754148.post-26529257065710698212012-07-30T19:06:37.545-06:002012-07-30T19:06:37.545-06:00Ancestry has always had problems with their indexi...Ancestry has always had problems with their indexing. If I were you, I would look at the 1940 Census on FamilySearch.Susan Marie Hillier Roehttps://www.blogger.com/profile/01010547319445701130noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-29773258340281533932012-07-29T16:58:43.696-06:002012-07-29T16:58:43.696-06:00I concur--I have yet to come across one entire fam...I concur--I have yet to come across one entire family that did not have transcription errors--just a good magnifying glass in most cases was all that was needed to notice the error.Sharonhttps://www.blogger.com/profile/01982115658114622152noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-88076526705743257102012-07-29T13:31:49.690-06:002012-07-29T13:31:49.690-06:00It is really pretty awful. I've come across d...It is really pretty awful. I've come across dozens of entries so far that are wildly indexed with bizarre names when the handwriting is clearly legible and entries that have nothing to do with what is on the form. It pays to be incredibly creative with indexes - on Ancestry as well as others!Michael D Lacopohttps://www.blogger.com/profile/11804658533353361632noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-1418477468742194782012-07-29T10:32:18.974-06:002012-07-29T10:32:18.974-06:00I found that lack of responsiveness as well, when ...I found that lack of responsiveness as well, when I wrote to tell them that Cincinnati, OH is in Hamilton County, not a neighboring county as they list it. This seemed not to be of any concern.MMWmShttps://www.blogger.com/profile/09179005549810213598noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-28973508835559390872012-07-29T06:27:10.449-06:002012-07-29T06:27:10.449-06:00Unfortunately, Ancestry.com has never done a good ...Unfortunately, Ancestry.com has never done a good job of indexing a census. My experience is that there is about a 20 percent error rate. Making it worse is that they don't seem to care as they leave the errors in the database even when notified and given proof of the errors.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-61001811316681888632012-07-29T05:49:48.883-06:002012-07-29T05:49:48.883-06:00I agree that the indexing for the 1940 census at A...I agree that the indexing for the 1940 census at Ancestry.com is very bad. In one case, the indexer continued with the previous family's surname while indexing the next household. In several other cases, the indexer used an entirely different surname than the one written in the census, presumably because the actual surname was not on an "approved" list and the wrong surname was -- or is there some other possible explanation? As a consequence, I am using Family Search exclusvely for obtaining 1940 census data.Buckeye Galhttps://www.blogger.com/profile/10040364756922977023noreply@blogger.com