Re: Validation of genealogy data

On 8/5/2011 9:04 PM, Darren Duncan wrote:
> Ron Savage wrote:
>> OK. So we're saying we should be able to store multiple versions of any
>> assertion, since - at least at first - it's all 'just data'.
>>
>> Then, we should be able to report on various matters regarding this
>> data, such as the error/warning (of type 'inconsistent') when someone
>> says today (Aug 6th) is a Sunday, when in fact it's a Saturday, since
>> they may have meant Aug 7th.
>>
>> To me this suggests that all the data be preserved indefinitely, even
>> after the user (or the program as the user's behest) has somehow chosen
>> one version to be promoted as the definitive version (not necessarily
>> making it correct), even though future research could change the status
>> of that version. This in turn suggests the need for a multi-valued flag
>> attachable to each version indicating the researchers degree of faith in
>> the veracity of that version.
>
> Yes, much as you say, though details can vary.
>
>> Do any current programs support such labelling of assertions?
>
> None that I know of, but I am aware that some savvy genealogists retain
> all of their sources even if contradictory.

Well not a good solution, but I current store this info in NOTE tag and 
in multiple SOURCE tags. But yes it is all just data and needs to 
support multiple versioned facts that can have goodness quality assigned 
to them or some way to indicate good|bad|questionable|not_verified|etc

By the way this is my web app:

http://swoodbridge.com/family/Woodbridge/index.php?indi=I2921

I keep all the data in Family Tree Maker, export that to a GEDCOM, then 
load it use a Gedcom.pm script into Postgresql database and serve the 
pages via php. The photos are integrated by a separate web app that 
allows loading, editing and linking them to the genealogy tables in the 
database.

I really big requirement is persistent IDs for individuals. I have to be 
very careful to not do anything that might renumber them.

-Steve