I haven't been using Gramps for very long, so I don't know how workable the
following is, but it's how I've been dealing with false events. I've been
giving them an alternate event type, such as "Claimed Birth". Because any
reports that deal with birth dates don't use these event types, they don't
get picked up. Some of them I've also marked private so they won't get
displayed in reports I generate for other people.
What I do wish is that there was a good way to mark confidence on an event
itself, rather than on a citation. Each citation I use usually covers a
couple pieces of information, with different levels of confidence for each.
E.g., a citation to a death certificate often includes the birth
information or the parents names. I have high confidence in the death
date, but low confidence in the parents names. That requires two different
citation to differentiate. But then I have two citations in my selection
lists that look almost exactly the same which takes extra time to determine
which one I need to use.
On Wed, Oct 3, 2012 at 8:44 AM, Brian Hamilton-Vise <bdhamilton@...:
> On Wed, Oct 3, 2012 at 15:23, Jesse Meyer <dasunt@...…> wrote:
> > But one thing to add to this - sooner or later you may discover which
> > is factual. Then you may have the urge to automatically delete the wrong
> > event. If I were you, I'd reconsider. Because that "wrong" data may
> > be needed for research. If someone had a habit of lying about their age
> > (perhaps to enter into military service, or just to seem younger), you'll
> > want to know both the actual birthdate and the wrong birthdate because
> > records may use either birthdate. If a children were mistaken about
> > parent's country of birth, you'd want to keep both the right and wrong
> > country to search for records involving ethnicity - such as US census
> > records. If someone lied about their parentage, their "wrong" parent(s)
> > may end up on such documents as marriage certificates.
> > So figure out a way how you will deal with information that you know is
> > wrong, but may be useful.
> > Just my $.02
> That's a helpful point, Jesse. Any ideas about how to keep that data
> around without cluttering up your tree? I wouldn't want to keep multiple
> birth events after I was sure which one was factual. Maybe at that point
> it's more appropriate to relegate the secondary data to a note attached to
> the right birth date?
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> Gramps-users mailing list