For now there is a photo management system included if you turn it on
#FAMILY TREE BUILDER EXPORT GEDCOM CODE#
This code currently does not support GEDCOM 5.5 support for media links. Integrating Photos with your Genealogy Data Have both the new genealogy data and you existing photo tables and moves the new graph database The last two command moves the updated test.db back into place and you should Then the next commandĭrops the genealogy tables only leaving the photos in place and reloads the genealogy tablesįrom the GEDCOM. The first command copies your existing database with the photo tables in it. To load a GEDCOM file, run these commands and then edit mygedcom.cfg (see below for details) and mygedcom.about as appropriate for your GEDCOM: about - html about this database that gets displayed as part of the home page for this database cfg - database specific configuration information The system supports multiple databases and each can be configured independently ofĭatabases are stored in. Requests are served in under 200 ms, but this is obviously based on system performance The development and testing has been based on using Sqlite databases that are quick andĮasy to work with and minimize the configuration dependencies and setup.
#FAMILY TREE BUILDER EXPORT GEDCOM HOW TO#
The section describes how to load a GEDCOM file and configure the server to use it. Follow theĬonfiguration instructions below and put your database and configuration in This will create a db folder that is mounted into the container. See the package.json file for up to date list and versions. I use Family Tree Maker as my master repository then export that to GEDCOM files to load into this application.Ĭollaboration and/or pull requests are welcome. This was built to work with my GEDCOM files and it might need changes and/or additions to work with other GEDCOM files. For example in my database, six generations and about 150 individuals in the list took about 3 seconds using a sqlite database. Performance is generally very good, 100-200 ms on most requests with the exception of the descendants listing that can take several minutes for a large number of descendants due to the fact that the query is recursive and needs to collect all the children of all families down through all generations from the selected individual. It can be configured to serve multiple separate databases and each database can its own configuration. This application is a Node.js webserver that serves family tree information from a GEDCOM loaded into a Sqlite database.
0 kommentar(er)
