From roots-in@roots-l.rootsweb.com Sat Aug 19 17:55:30 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 k7JNtTjb032324; Sat, 19 Aug 2006 17:55:30 -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 k7JNtS6X014203 for ; Sat, 19 Aug 2006 17:55:28 -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 k7JLFXFI020981 for ; Sat, 19 Aug 2006 17:15:33 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k7JLFWqd020980 for roots-approved@rootsweb.com; Sat, 19 Aug 2006 17:15:32 -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 k7JKAgFI020827 for ; Sat, 19 Aug 2006 16:10:42 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k7JMoQoj019467 for roots-in@roots-l.rootsweb.com; Sat, 19 Aug 2006 16:50:26 -0600 X-Envelope-From: Kith-n-Kin@cox.net Sat Aug 19 16:50:26 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 k7JMoQjb019456 for ; Sat, 19 Aug 2006 16:50:26 -0600 Received: from fed1rmmtao07.cox.net (fed1rmmtao07.cox.net [68.230.241.32]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k7JMoORZ000708 for ; Sat, 19 Aug 2006 16:50:25 -0600 Received: from TOWER ([68.0.155.47]) by fed1rmmtao07.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060819225021.TVRR21457.fed1rmmtao07.cox.net@TOWER> for ; Sat, 19 Aug 2006 18:50:21 -0400 From: "Kith-n-Kin" To: Date: Sat, 19 Aug 2006 15:50:07 -0700 Message-ID: <002701c6c3e1$d291db70$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 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 In-Reply-To: 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 k7JMoQjb019456 Subject: [ROOTS-L] Uploading trees to Ancestry (was: Re:Family trees) Sender: roots-in@roots-l.rootsweb.com Update on Ancestry.com and the trees. If you don't have a sub to Ancestry, most of this is moot: I don't think you can any longer upload a tree to Ancestry World Tree (AWT) from the Ancestry site. I think we have "personal member trees" and "public member trees". The public trees are apparently incorporated in to OneWorldTree (OWT) *search engine*. The Personal member trees (private) are not. But, you can still send messages to the uploader. I went to upload a tree a few minutes ago. I was on the page: "My Ancestry" The tree uploaded to "My Trees" -- as a "public" tree. It did not upload to AWT, and I couldn't find any way to do so (except, of course, to use RootsWeb, my next project). There are a couple of problems with this, but the most significant one was related to the reason I did this to start with. "I" have an old AWT tree which is WRONG (I'm so much smarter now than I used to be ) up on AWT. I didn't put it there, and can only assume it was uploaded from the old CDs we contributed to for Family Tree Maker, some ten years ago. It has no "contact" and no number or other identifying flags. I'm asking to have it removed, but haven't heard back yet. Based on the conversation on this list which dealt with "if you can't change what's there, at least make sure you have the correct information out there", I have split my database (to make it easier to handle), and created family group and generation specific GEDCOMs (not including "living" anyone), with the intent of publishing them to Ancestry/Rootsweb. I am not sure the tree I've put up is really "public" as I am me and can access it anyway. It is supposed to show up on One World Tree. If someone could look up Harriet Winfrey Gray, I'd appreciate it. If you find her with a death date of 1994, that's the "old" gedcom. If you find 18 OCT 1994, that is what I uploaded as "public" this morning. This is all, frankly, confusing to me. Second problem is that all my carefully crafted notes on "why I think blah, blah" are not appearing. The sources are, not the conclusions. I've sent a query to Ancestry on this. Point is, gang, I think it's a whole new world out there on these trees. We have recently had a couple of comments on this list that I, for one, didn't understand. They had to do with such things as "why did someone put their tree up if they didn't want to share it. PERSONAL TREES -- If you want to operate your research base on Ancestry, not to share, but just for convenience (say you're going to Library of Virginia, and don't want to take your own laptop), and put up a tree to do it with, sometimes a query will result in a "hit" that says "personal trees". You can see the specific data on a person "John Smith, b 1812, Virginia", but not his folks, the source for the information, or anything else. YOU CAN, however, send a query to the "owner" to see if s/he is interested in collaborating. Sondra was nice enough to explain to us why sometimes these things take time. Another reason may be that the person is just "playing" with some ideas, and doesn't even intend to do anything further. May never look again. We all know the story of the orphan AWTs, I suspect we will have the same thing here. Or, may just not be at a point of being ready to collaborate. PUBLIC TREES, which can be viewed from OWT, behave much like the AWT trees, and you can send queries (without knowing the uploader's name) about the tree. Not the same as post-ems and such. The Private Trees do not integrate with OWT, but will crop up in a separate category on a search. Obviously doesn't happen often, or we would have already had this discussion . I hope I haven't further confused the issue. Now, I'm going over to WorldConnect, upload the same tree, and see if my notes are there . Pat (in Tucson)