As an alternate to this approach,
I maintain my genealogy in FalimyTree maker and dump a GEDCOM file that
gets loaded into a database. This is then used to serve genealogy pages.
The database is a drop and reload when I have new data. and I maintain
the INDI ids to preserve continuity of bookmarks.
http://swoodbridge.com/family/Woodbridge/
The application hides people that are living unless you have a family
login. There is some risk that someone could hack it, but then they can
dumpster dive also.
-Steve
Jim Seymour wrote:
Mike Hamilton wrote:
I did some preliminary work on exactly this quite some years back. I
think I can claim to know the Paul's (excellent) Gedcom module pretty
well, having used it to generate custom charts, etc.
Well, then... I may start hitting you up for some advice... :-)
But there's a huge problem to which I could find no answer; what
happens when somebody makes a change? These should update the Gedcom
file, which would often have a flow-on effect to the rest of the Wiki,
which would need regenerating.
In my case, this is not a problem. The GEDCOM file is merely a one-time
transport mechanism. Once the pages are up, my Wiki will become the
official repository.
In other words, this conversion is a one-way trip.
I used MediaWiki, but I see that DokuWiki "makes sure the datafiles
remain readable outside the Wiki and eases the creation of structured
texts", so it looks a much better choice.
Yes, this is the main reason I chose DokuWiki. The pages are stored as
plain text files. When I first got the Wiki running, I generated most
of the initial pages by converting them from HTML pages (using a quick
one-shot perl script).
Sorry I couldn't give Jim a more positive and useful response
Not a problem. I'll be spending some time on this project this weekend.
When I'm done, I'll try to include a page on my wiki about the
conversion process (in case others might find it useful in the future).
