This same thing has happened to me in FTM. Sent from my iPhone On Aug 20, 2010, at 2:39 PM, Norm Hellmers <[email protected]> wrote: > Hello List, > > I have recently been putting some of my data on Ancestry.com. In doing so, I realized that Ancestry.com has a serious error in its place name database. When a person starts to enter New Orleans, the “auto-complete” function completes it as "New Orleans, Jefferson, Louisiana, USA." > > Because of this, many people have incorrectly entered New Orleans, Jefferson, Louisiana, USA as a place name in their Ancestry Public Member Trees. > > When I discovered this, I remembered a query to the List about this issue over two years ago. You can see that message here: > http://archiver.rootsweb.ancestry.com/th/read/laorlean/2008-03/1206055120 > This mistake has obviously been going on for some time. > > I have notified Ancestry.com of the error, but to date it has not been corrected. In the meantime, people who enter data on Ancestry should be cautious about this auto-complete error, and should be cautious with the auto-complete function entirely, as I have seen many other mistakes made because of it. Everyone should also be aware that Ancestry family trees will frequently contain the erroneous place name of New Orleans, Jefferson, Louisiana, USA. It should of course be New Orleans, Orleans, Louisiana, USA. > > Norm > > > > > > > > > ------------------------------- > To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message

Norm, I sincerely wish you good luck with getting the place name fixed. And I apologize in advance for using this issue as a place to jump in and vent . . . but the worst thing Ancestry.com ever did, in my opinion, was One World Tree. Their computer stitched together "probables" [their word], and matched my mother-in-law to the brother of her actual husband. I wrote to them, and spoke with tech support and supervisors . . . and they can't/won't fix it, remove it, or give me a place to add a comment. The data was originally submitted correctly by a distant relative. And now the mistake will be perpetuated. . .

I found the same thing concerning One World Tree and Ancestry..  I do not rely on the pop up place names, etc and put  my own information on Ancestry. Lots of the family trees that come up are incorrect. Especially if there are no sources, census etc. I think the problem with One World Tree is when it first started, researchers did not have the information/documents available to them now, and relied on oral histories a lot. One "family name" book that I know of that's been published for years, has me as my mother!  When I questioned it, I was told that an aunt of someone told the writer that is what she thought.  In this Internet age so many documents are available, I just hope people use this source to correct things.  Just my opinion.   ________________________________ From: Kathleen Deao <[email protected]> To: [email protected] Sent: Fri, August 20, 2010 3:05:34 PM Subject: Re: [LAORLEAN] Ancestry Place Name Error Norm, I sincerely wish you good luck with getting the place name fixed. And I apologize in advance for using this issue as a place to jump in and vent . . . but the worst thing Ancestry.com ever did, in my opinion, was One World Tree. Their computer stitched together "probables" [their word], and matched my mother-in-law to the brother of her actual husband. I wrote to them, and spoke with tech support and supervisors .  . .  and they can't/won't fix it, remove it, or give me a place to add a comment. The data was originally submitted correctly by a distant relative.  And now the mistake will be perpetuated. . . ------------------------------- To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message

I also noticed this on ancestry and FTM, all versions. You have to watch very carefully. Has to do with Jefferson Parish coming up before Orleans Parish. I also notified Ancestry.com of this problem, but no response. Lots of towns have same name, but different County, guess that is the problem. I change them when I find them in my files, or on line. Jan S - Orlando, FL -------Original Message------- From: Peggy Date: 8/20/2010 3:47:49 PM To: [email protected] Subject: Re: [LAORLEAN] Ancestry Place Name Error This same thing has happened to me in FTM. Sent from my iPhone On Aug 20, 2010, at 2:39 PM, Norm Hellmers <[email protected]> wrote: > Hello List, > > I have recently been putting some of my data on Ancestry.com. In doing so, I realized that Ancestry.com has a serious error in its place name database. When a person starts to enter New Orleans, the “auto-complete” function completes it as "New Orleans, Jefferson, Louisiana, USA." > > Because of this, many people have incorrectly entered New Orleans, Jefferson, Louisiana, USA as a place name in their Ancestry Public Member Trees. > > When I discovered this, I remembered a query to the List about this issue over two years ago. You can see that message here: > http://archiver.rootsweb.ancestry.com/th/read/laorlean/2008-03/1206055120 > This mistake has obviously been going on for some time. > > I have notified Ancestry.com of the error, but to date it has not been corrected. In the meantime, people who enter data on Ancestry should be cautious about this auto-complete error, and should be cautious with the auto-complete function entirely, as I have seen many other mistakes made because of it. Everyone should also be aware that Ancestry family trees will frequently contain the erroneous place name of New Orleans, Jefferson, Louisiana, USA. It should of course be New Orleans, Orleans, Louisiana, USA. > > Norm > > > > > > > > > ------------------------------- > To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message ------------------------------- To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message