Hi John On Wed, 2011-07-27 at 08:47 +0100, John Dobson wrote: > Hi, > > Let me first admit to not being a webtrees expert, although I am going > to use it. Webtrees is a 'fork' in open source terms from the popular > PhpGedView. It initially populates the custom database from data in one > or more GEDCOM files which remain in the file store but aren't referred > to again in operation after the initial loading use. The idea is that > the database is updated online by those collaborating in the project > and, subject to configuration; any user can export a GEDCOM for their > own use at any time.
OK. > Multi-media is more problematic when it comes to portability, the GEDCOM > FILE statement contains just a file pointer to a multimedia item, not > the item itself. It's unlikely that this location would stay the same > through a migration to webtrees so the program optionally strips off the > leading part of the path and replaces it with a media directory > constant. It's the left to the user to migrate media items manually. Yes, external files add a lot of complexity to processing. Let's pretend our non-existent new spec is called Gedcom+ (to save typing). So, in Gedcom+ I'm thinking it'd have a config file, and 1 item therein would be a media directory name, so all file references in the Gedcom+ file would be relative to the local user's value for that dir name. Then come the problem of file type, codecs, etc. I guess we need to d/l a few open source genealogy program and see what they do. That's why I examined the source of Webtrees. -- Ron Savage http://savage.net.au/ Ph: 0421 920 622
