On 8/6/2011 2:28 AM, Ron Savage wrote:
Hi Steve
On Sat, 2011-08-06 at 00:39 -0400, Stephen Woodbridge wrote:
On 8/5/2011 9:04 PM, Darren Duncan wrote:
Ron Savage wrote:
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.
Noted.
Is there some specific action with programs we've mentioned which does
renumber them?
Well the obvious one is a renumber command ;), but merging files and
merge individuals some times creates a new individual and then copies
the data from the two merged ones into the new which causes the new one
to be a new number.
But from a more general point of view and talking about versioning of
data, if 100 people create an INDI record for the same person in
separate research projects and later some of them merge their research
at various points in time it would be nice to know if my INDI includes
one or more of those other INDIs and it might be nice to know at what
version of those INDI(s) got merged into my work.
I suppose one way of thinking about this would be like SVN or GIT source
code respository, where files were INDIs or FACTs and there exists a
link like item the connects facts to INDIs or "LINK"s and INDIs to other
INDIs. I'm not suggesting this as a technical design but as a way of
thinking about the problem of revisioning and history.
-Steve
