From roots-in@roots-l.rootsweb.com Wed Jul 19 16:19:53 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 k6JMJrjb001526; Wed, 19 Jul 2006 16:19:53 -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 k6JMJpAi026158 for ; Wed, 19 Jul 2006 16:19:51 -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 k6JJfmFI012091 for ; Wed, 19 Jul 2006 15:41:48 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6JJfmKe012090 for roots-approved@rootsweb.com; Wed, 19 Jul 2006 15:41:48 -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 k6JJeEFI012022 for ; Wed, 19 Jul 2006 15:40:14 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k6JMI79N000443 for roots-in@roots-l.rootsweb.com; Wed, 19 Jul 2006 16:18:07 -0600 X-Envelope-From: Kith-n-Kin@cox.net Wed Jul 19 16:18:07 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 k6JMI7jb000434 for ; Wed, 19 Jul 2006 16:18:07 -0600 Received: from fed1rmmtao09.cox.net (fed1rmmtao09.cox.net [68.230.241.30]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6JMI4a2024876 for ; Wed, 19 Jul 2006 16:18:04 -0600 Received: from TOWER ([68.0.155.47]) by fed1rmmtao09.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060719221800.LCVM6303.fed1rmmtao09.cox.net@TOWER>; Wed, 19 Jul 2006 18:18:00 -0400 From: "Kith-n-Kin" To: "'Margaret Miller'" , Subject: RE: [ROOTS-L] RE: Ancestry.com Date: Wed, 19 Jul 2006 15:17:50 -0700 Message-ID: <00a501c6ab81$31e8f780$6601a8c0@TOWER> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-reply-to: <44BE9091.40206@sw.rr.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Importance: Normal X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by admin.rootsweb.com id k6JMI7jb000434 Sender: roots-in@roots-l.rootsweb.com Margaret Since these trees are posted by individuals, not by Ancestry, how did Ancestry make this change? Perhaps you are speaking of the "OneWorldTree" where people (again, individuals) can add/subtract from trees? It is very difficult, I think, to distinguish between "WorldFamilyTree" WFT, and "OneWorldTree" or OWT. WFT is individual databases; OWT is a computer driven compilation of "possibilities" of combined trees. Here is a description of OWT: "OneWorldTree takes family trees submitted by Ancestry members and "stitches" them together with family trees and historical records from other sources. OneWorldTree identifies probable name matches between these sources and displays consolidated results in a worldwide family tree that can help you with your family history research." Here is a description of WFT: "The Ancestry World Tree was created to bring family historians together. When you upload your family tree, you are sharing your discoveries with other researchers and helping others to find success in their family history work. You may even find lost relatives who have information on your family. You can change, update or remove your work from the Ancestry World Tree at any time." Personally, I don't care for OWT, and only use it when I want some really general ideas of who is in a particular family. For example. I have a WFT tree of a family beginning with the second son who moved west. Jane Smith has a WFT tree with the 1st, 3rd and 4th children. Sam Jones has all the children, but only a couple of generations. Now, understanding that all of us have errors, non-the-less, the trees will be compiled into one tree, errors and all. On the OWT, you can "correct" errors. I just changed the death date on one Henry Trent, b 1767, from 2003 to bef 1850. There was no "proving" I had to do. If you look on the box on the right, you will see the list of trees that make up the OWT. I should note that the change I made in the OWT did not change the WFT database that had the 2003 information. Sometimes, totally unrelated trees are combined, and you can request to have them separated, I suppose. It is possible that whoever thought Georgia Woman was your cousin did so in good faith, so what you could do is go to the OWT tree and make a correction yourself. This will not change it in her WFT tree, you would have to contact her (which you have an opportunity to do) for that. Of course, if you are talking about your tree, that you uploaded, and somehow some electrons switched in Georgia Woman, you need to replace the tree. Pat (in Tucson) |-----Original Message----- |From: roots-in@roots-l.rootsweb.com |[mailto:roots-in@roots-l.rootsweb.com] On Behalf Of Margaret Miller |Sent: Wednesday, July 19, 2006 13:06 |To: ROOTS-M@rootsweb.com |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 | |