From roots-in@roots-l.rootsweb.com Sun Jul 23 10:32:42 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 k6NGWgjb012671;
	Sun, 23 Jul 2006 10:32:42 -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 k6NGWdFp000837
	for <roots-approved@rootsweb.com>; Sun, 23 Jul 2006 10:32: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 k6NDsNFI009176
	for <roots-approved@rootsweb.com>; Sun, 23 Jul 2006 09:54:23 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6NDsNSA009175
	for roots-approved@rootsweb.com; Sun, 23 Jul 2006 09:54: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 k6NDd1FI009084
	for <roots-in@roots-l.rootsweb.com>; Sun, 23 Jul 2006 09:39:01 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k6NGH85r007357
	for roots-in@roots-l.rootsweb.com; Sun, 23 Jul 2006 10:17:08 -0600
X-Envelope-From: Kith-n-Kin@cox.net Sun Jul 23 10:17:08 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 k6NGH8jb007348
	for <ROOTS-M@lists5.rootsweb.com>; Sun, 23 Jul 2006 10:17:08 -0600
Received: from fed1rmmtao04.cox.net (fed1rmmtao04.cox.net [68.230.241.35])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6NGH5BO024777
	for <ROOTS-M@rootsweb.com>; Sun, 23 Jul 2006 10:17:06 -0600
Received: from TOWER ([68.0.155.47]) by fed1rmmtao04.cox.net
          (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP
          id <20060723161701.IXCB6711.fed1rmmtao04.cox.net@TOWER>;
          Sun, 23 Jul 2006 12:17:01 -0400
From: "Kith-n-Kin" <Kith-n-Kin@cox.net>
To: <JYoung6180@aol.com>, <ROOTS-M@rootsweb.com>
Subject: RE: [ROOTS-L] Re: AWT, OWT, and Ancestry.com
Date: Sun, 23 Jul 2006 09:16:48 -0700
Message-ID: <01ed01c6ae73$69808420$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: <4f8.37de38c.31f46450@aol.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 k6NGH8jb007348
Sender: roots-in@roots-l.rootsweb.com

Joan

Thank you for that very good explanation of the orphan trees. And, I agree with you!  I didn't mean to
advocate a summary removal, but the trees I don't like, and am referring to are those with no notes, no
sources -- or worse, five identical trees with the same source "gedcom # blah blah" -- something they got
from the FTM CDs, or copied from another AWT/WC tree. 

Problem is, of course, "how do you know what is a true orphan, and what is a legacy tree" -- perhaps it
would be a possibility, when people like you, me, and Margaret, and others, find these repetitious trees
in the process of searching, that there be an "alert" sent to Ancestry/RootsWeb, and consideration for
removal take place.  Even in the electronic age, I suspect there is a "paper trail" as to the origin of
these trees. If four people downloaded a legacy tree, in fact, and then uploaded it again, under a
different identity, and then dropped out (so to speak) that is four trees more than we need.

Matter of fact, how about labeling the legacy trees as what they are!  How many times on this list has
someone become very upset because s/he had tried everything humanly possible to find the "owner" of a tree
that has "unknown" as the source. Just replace "unknown" with "Legacy Tree" and we are part way there! We
can honor those who have gone before, and at the same time, quit spinning our wheels!

Again, I've never worked for either of these (Ancestry or RootsWeb) but I bet it could be done.

Pat (in Tucson)



|-----Original Message-----
|From: roots-in@roots-l.rootsweb.com 
|[mailto:roots-in@roots-l.rootsweb.com] On Behalf Of JYoung6180@aol.com
|Sent: Saturday, July 22, 2006 22:34
|To: ROOTS-M@rootsweb.com
|Subject: [ROOTS-L] Re: AWT, OWT, and Ancestry.com
|
|

|I would not want to see anyone arbitrarily decide to remove a 
|file of a  
|deceased or incapacitated submitter against the wishes of the 
|individual or his  
|heirs.
| 
|Joan
|
|



