From roots-in@roots-l.rootsweb.com Wed Jul 19 17:25:38 2006 Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34]) by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k6JNPcjb013167; Wed, 19 Jul 2006 17:25:38 -0600 Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6JNPbvb006117 for ; Wed, 19 Jul 2006 17:25:37 -0600 Received: from roots-l.rootsweb.com (roots-l [127.0.0.1]) by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k6JKlUFI012270 for ; Wed, 19 Jul 2006 16:47:30 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6JKlUhL012269 for roots-approved@rootsweb.com; Wed, 19 Jul 2006 16:47:30 -0400 Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41]) by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k6JKW5FI012180 for ; Wed, 19 Jul 2006 16:32:05 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k6JNA0LW005197 for roots-in@roots-l.rootsweb.com; Wed, 19 Jul 2006 17:10:00 -0600 X-Envelope-From: mscheffl@twcny.rr.com Wed Jul 19 17:09:59 2006 Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34]) by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k6JN9xjb005188 for ; Wed, 19 Jul 2006 17:09:59 -0600 Received: from ms-smtp-03.nyroc.rr.com (ms-smtp-03.nyroc.rr.com [24.24.2.57]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6JN9sIu026737 for ; Wed, 19 Jul 2006 17:09:55 -0600 Received: from m1070n (cpe-69-201-76-92.twcny.res.rr.com [69.201.76.92]) by ms-smtp-03.nyroc.rr.com (8.13.6/8.13.6) with SMTP id k6JN9qrv014185; Wed, 19 Jul 2006 19:09:53 -0400 (EDT) Message-ID: <23ba01c6ab88$70fe3e10$6501a8c0@m1070n> From: "MScheffler" To: "Margaret Miller" , References: <44BE9091.40206@sw.rr.com> Subject: Re: [ROOTS-L] RE: Ancestry.com Date: Wed, 19 Jul 2006 19:09:52 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 Sender: roots-in@roots-l.rootsweb.com Margaret, I think you are referring to the One World Tree that individuals can manipulate. I don't care for it and generally don't use this feature of Ancestry. Personally I like to navigate through individual trees (Ancestry World Tree or WorldConnect) where I can judge by the sourcing and notes if the person appears to be a careful researcher. I tend to ignore databases with gedcoms as sources or no sources as all, although some good researchers have good quality databases and choose only to give out resources if someone writes and asks for them. If you go back and look at your individual database, I believe you will find that it has not changed. If you are confusing One World Tree and Ancestry World Tree just go to www.rootsweb.com and search for your missing woman from WorldConnect. If she comes up ok, you will now it is fine on Ancestry too since they are the same database. Margaret Scheffler ----- Original Message ----- From: "Margaret Miller" To: Sent: Wednesday, July 19, 2006 4:05 PM Subject: [ROOTS-L] RE: Ancestry.com >I have attempted to contact submitters for family trees and have never had >any success. Either no responses or bounced mail. > > Ancestry.com will not correct errors in family trees but they will create > some on their own. I know by experience. They took my information and > converted it to what they have from other sources. Thus my cousin no > longer exists. She has been replaced by a woman who died in GA. a number > of years before my cousin's marriage. > > It's disgusting to see how inaccurate the family trees are and to know > there can nothing be done to correct them. Before a tree can be posted, > documentation should be a requirement. > > mbm >