From roots-in@roots-l.rootsweb.com Sat Jul 22 18:13:41 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 k6N0Dfjb024891; Sat, 22 Jul 2006 18:13:41 -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 k6N0Ddn3016722 for ; Sat, 22 Jul 2006 18:13:39 -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 k6MLZNFI024858 for ; Sat, 22 Jul 2006 17:35:23 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6MLZN88024857 for roots-approved@rootsweb.com; Sat, 22 Jul 2006 17:35:23 -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 k6MKeCFI024702 for ; Sat, 22 Jul 2006 16:40:12 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k6MNIGA9025611 for roots-in@roots-l.rootsweb.com; Sat, 22 Jul 2006 17:18:16 -0600 X-Envelope-From: Kith-n-Kin@cox.net Sat Jul 22 17:18:16 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 k6MNIGjb025600 for ; Sat, 22 Jul 2006 17:18:16 -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 k6MNIDqv019160 for ; Sat, 22 Jul 2006 17:18:14 -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 <20060722231809.PORP6303.fed1rmmtao09.cox.net@TOWER>; Sat, 22 Jul 2006 19:18:09 -0400 From: "Kith-n-Kin" To: "'Kirsten Bowman'" , Date: Sat, 22 Jul 2006 16:17:44 -0700 Message-ID: <01c001c6ade5$0cf337e0$6601a8c0@TOWER> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-reply-to: 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 Subject: [ROOTS-L] RE: AWT, OWT, and Ancestry.com Sender: roots-in@roots-l.rootsweb.com Kirsten I agree that it would be a good thing if people wouldn't double post their trees -- anywhere. On this project, I found 5 identical trees, none of which had a contributor name. And that's another thing. If *someone* put up a tree several years ago, and has since gone golfing or to that big genealogy convention in the sky, perhaps the trees should be removed. A tree without a "sponsor" and without sources, is just so much jumble to me. Are the folks at Ancestry listening? Huh? Huh? Pat (in Tucson) (oh, for those who noticed, I don't know how it got through, but I did not change my e-ddress to DunfordGuthrie -- I just slipped when I chose the return address. Surprised it got through. Back to Kith-n-Kin.) |-----Original Message----- |From: Kirsten Bowman [mailto:viking@rvi.net] |Sent: Saturday, July 22, 2006 15:45 |To: Dunford Guthrie; ROOTS-M@rootsweb.com |Subject: AWT, OWT, and Ancestry.com | | |Pat: | |Thanks for that excellent explanation but, my goodness!, |aren't many of the gedcoms online scrambled enough already |without Ancestry.com devoting a computer to mix them together |even more?? (Rhetorical question.) Personally I prefer the |SmartMatching feature at GenCircles which only suggests |matches and doesn't go off building new confused trees. | |And one point that should be clarified: I believe that |Ancestry.com (probably both OWT and |AWT) and RootsWeb's WorldConnect share databases, so a gedcom |uploaded to WorldConnect appears at AWT although I'm not sure |if the reverse applies. It seems that many people post gedcoms |at both RootsWeb and Ancestry, which creates a lot of |unnecessary duplication. |