From roots-in@roots-l.rootsweb.com Fri May 5 08:42:40 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 k45Egejb007497; Fri, 5 May 2006 08:42:40 -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 k45EgaVC026160 for ; Fri, 5 May 2006 08:42:36 -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 k45C90FI026811 for ; Fri, 5 May 2006 08:09:00 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k45C90Dq026810 for roots-approved@rootsweb.com; Fri, 5 May 2006 08:09:00 -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 k450UHFI024844 for ; Thu, 4 May 2006 20:30:17 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k4533esg028168 for roots-in@roots-l.rootsweb.com; Thu, 4 May 2006 21:03:40 -0600 X-Envelope-From: mscheffl@twcny.rr.com Thu May 4 21:03:40 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 k4533ejb028159 for ; Thu, 4 May 2006 21:03:40 -0600 Received: from ms-smtp-01.nyroc.rr.com (ms-smtp-01.nyroc.rr.com [24.24.2.55]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k4533Lqb020796 for ; Thu, 4 May 2006 21:03:21 -0600 Received: from m1070n (cpe-24-92-248-107.twcny.res.rr.com [24.92.248.107]) by ms-smtp-01.nyroc.rr.com (8.13.6/8.13.6) with SMTP id k4533JdK014324; Thu, 4 May 2006 23:03:21 -0400 (EDT) Message-ID: <015501c66ff0$76375610$6801a8c0@m1070n> From: "MScheffler" To: "Baldwin" , References: <20060505005516.85377.qmail@web30311.mail.mud.yahoo.com> Subject: Re: [ROOTS-L] Major errors on Ancestry's One Great Tree Date: Thu, 4 May 2006 23:03:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original 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 Stephen and others with similar problems, I would first attempt to write to the submitter of the tree with the incorrect information that is listed in the combined large free shared database "Ancestry World Tree" or "WorldConnect". If the email address is good, simply write and tactfully point out the major errors. Offer to send them the correct information with sources and rationale. If the email is not working and the problems are significant, you might talk with Ancestry on the phone re this. Secondly , you could add post-em notes from the World Connect side and generally from the Ancestry side as well. I looked at a few trees where there was not an option from the tree on the Ancestry side for a post-em. I'm not sure why and I did not go back to see if the same database had the means to post the correction from the Rootsweb World Connect side. A caveat with post-ems is that when the individual's database is replaced the notes will be gone and it may be that the owner of the database can remove them should they choose. I wouldn't spend hours putting up post-em notes, but a few could not hurt. It sounds as if in your case at least one person has posted the correct information. This is a recommendation often made -- to counteract the bad with the good. If both right and wrong are posted, at least the individuals looking at the information realize there are differences of opinion. You might even want to reference the incorrect information found elsewhere in some of the notes on the good database. The more clearly the correct information is presented, the better. It might help for you to post yet another database with correct information on the offending part of the line, since you said I believe a relative had posted the correct one. Although it does not mean much, some people may focus on the relative number of times data is presented, so having more than one correct presentation might be helpful. If you were talking about the "OneWorldTree" combination of databases instead of the "Ancestry World Tree" from which the other is created, you can find the submitter of the tree with the errors. by clicking on some of the options on one of the search pages, and do like I suggest above. There is also a way you can add alternatives on the combined tree that appears on screen. I have not done this. Others may have specific instructions. Even if an incorrect tree is part of the "Ancestry World Tree" database, I think it can be removed, but you might want to persist with Ancestry re this possibility. The do have a statement at least when approached through WorldConnect that they are not responsible for incorrect information. Quoted from the WorldConnecct side: RootsWeb.com, Inc. is NOT responsible for the content of the GEDCOMs uploaded through the WorldConnect Program. If you have a problem with a particular entry, please contact the submitter of said entry. You have full control over your GEDCOM. You can change or remove it at any time. And lastly, none of has control over what others post good or bad. Guess I would try to get others to make changes, and if not, just post yourself what is correct hopefully with SOURCES so that the casual searcher can get a feel for what is most likely to be correct. I know its irritating if one cannot get the changes made, but there are times when one must live with wrong information, like it or not. I would refuse to let it limit my enjoyment of this hobby. Then there is also the possibility that if every few months you go back and add a few post-em notes, the person will get tired of them and remove the offending database. Hopefully you get this resolved to your satisfaction. Margaret Scheffler ----- Original Message ----- From: "Baldwin" Subject: [ROOTS-L] Major errors on Ancestry's One Great Tree >I am interested in feedback on how to correct a major amount of errors on >Ancestry's One Great Tree. When they created the tree on one of my lines, >they have listed wrong counties, wrong parents, wrong spouses, wrong dates, >and wrong children throughout several lines including information on people >I know 100% documented fact are not related (I actually lived with the >people in question growing up), they happen to have similar names and dates >but other than that are in noway connected.