From roots-in@roots-l.rootsweb.com Sat Mar 11 08:00:24 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 k2BF0Ojb006363; Sat, 11 Mar 2006 08:00:24 -0700 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 k2BF0L1I007134 for ; Sat, 11 Mar 2006 08:00:21 -0700 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 k2BCU1FI023608 for ; Sat, 11 Mar 2006 07:30:02 -0500 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k2BCU1i6023607 for roots-approved@rootsweb.com; Sat, 11 Mar 2006 07:30:01 -0500 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 k2BBfcFI023400 for ; Sat, 11 Mar 2006 06:41:38 -0500 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k2BEBlUv013495 for roots-in@roots-l.rootsweb.com; Sat, 11 Mar 2006 07:11:47 -0700 X-Envelope-From: mscheffl@twcny.rr.com Sat Mar 11 07:11:47 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 k2BEBljb013486 for ; Sat, 11 Mar 2006 07:11:47 -0700 Received: from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.24.2.56]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k2BEBYup008323 for ; Sat, 11 Mar 2006 07:11:45 -0700 Received: from 1070n (cpe-24-92-248-107.twcny.res.rr.com [24.92.248.107]) by ms-smtp-02.nyroc.rr.com (8.13.4/8.13.4) with SMTP id k2BEBWT6007523; Sat, 11 Mar 2006 09:11:34 -0500 (EST) Message-ID: <00c101c64515$b24a2070$6601a8c0@1070n> From: "MScheffler" To: , References: Subject: Re: [ROOTS-L] WILDER: How to record conflicting research Date: Sat, 11 Mar 2006 09:11:30 -0500 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.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 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 Most genealogy programs allow one to have more than one birth, death, event that differs from the others. For myself, I like only having one of these print out on reports. My solution is pick ONE of the conflicting dates to use as the say birth or death fact and then to discuss conflicts in the notes, and keep those notes even when evidence finally proves a particular date right or wrong. It is amazing how often we come across conflicting information. Sometimes the absolute truth may never be known. I have a situation where my gggg grandfather's tombstone is off by almost 2 years. The correct date came from a grandson's daily diary that surfaced a few years back but the incorrect data has been used for years without anyone realizing it is wrong.. On the issue of gedcom data -- I would NEVER possibly pollute my database for which I have worked on for years with someone else's gedcom. One really should prove the information they take from someone else for themselves. It certainly doesn't hurt to look through others material because it may provide useful clues, just put that material in its own gedcom and if you do eventually choose to use a few names or dates that you cannot verify, source the information carefully as to where that information came from and perhaps add your rezoning for why you are using this material in your notes. Once one has merged "possibly garbage" with their own careful work, essentially ones whole database has become much less useful and reliable. And even if the data in the "guest" file were essentially accurate, the gedcom might cause one's own database to become corrupt. Just because gedcom imports frequently work well, does not mean they always will. Always have backups before any merges. And no matter what criteria one uses for adding data, BACKUP your files off your hard drive regularly, and keep a back away from your home. Those new little thumb/flash drives are very easily used for backups, though by no means the only possibility. Margaret Scheffler ----- Original Message ----- From: To: Sent: Friday, March 10, 2006 9:45 PM Subject: Re: [ROOTS-L] WILDER: How to record conflicting research >I use Reunion for the MAC as well. What I do with conflicting events such > as, birth or death, is to add duplicate event. If you keep the most > reliable on > the top it is the one you see when you go through the index cards. If I > can > verify the date with a gravestone or multiple census records or other > primary > sources, I will then delete the bad info. If whole large sections are in > conflict you could create a new family file with the least reliable > information > then you would have it on file for future reference. You could copy and > paste > the verified information into the master file. If you are downloading a > GEDCOM you could put it in a separate family file until you can verify it. > Love > My MAC. John >