An Ancestry forum has a limited database facility, with 10 fields, no validation facilities, and the possibility of 50 current members adding their data, which extends over about 800 years to a single originating ancestor.
One of these members could be responsible for editing, adding and deletion rights for the rest of the 50 members, with group checking, and each member has perhaps information on 100 or so members of their recent family.
There is also a fairly good outline genealogy tree back to the original family member.
In order to create a consistent genealogy, how would be the best way to use these 10 fields?
I could imagine a template for each possible data source, for instance:
CensusSource: with values of US,UK,AU etc, FieldDate: 1881 etc, CensusPlace:, PersonID:, PersonSurnName:, PersonGivenName:, PersonBirthdate:, BirthPlace:, etc., etc.
or
BirthSource:, BirthDate:, BirthPlace:, PersonID:, PersonSurname:, PersonGivenName:, etc., etc.
etc.
In other words, to create table definitions with each row of the flat file which could be parsed into a relational database format.
Or is there a more elegant approach?
One of these members could be responsible for editing, adding and deletion rights for the rest of the 50 members, with group checking, and each member has perhaps information on 100 or so members of their recent family.
There is also a fairly good outline genealogy tree back to the original family member.
In order to create a consistent genealogy, how would be the best way to use these 10 fields?
I could imagine a template for each possible data source, for instance:
CensusSource: with values of US,UK,AU etc, FieldDate: 1881 etc, CensusPlace:, PersonID:, PersonSurnName:, PersonGivenName:, PersonBirthdate:, BirthPlace:, etc., etc.
or
BirthSource:, BirthDate:, BirthPlace:, PersonID:, PersonSurname:, PersonGivenName:, etc., etc.
etc.
In other words, to create table definitions with each row of the flat file which could be parsed into a relational database format.
Or is there a more elegant approach?