Compiling historical family data is not easy. Luckily, my wife has taken the job. This summer, she has been attempting to piece together our ancestry from a variety of sources. Ancestry.com has provided valuable census records which have been useful in tracking the migration of both of our families across the Unites States since the late 18th century. Relatives on either side have donated old memorabilia including pictures, letters, and diaries that have been an enormous help in tracing birth and death dates. These dates have been the single most important clue in searching the census records provided by Ancestry.com. Unfortunately, Ancestry’s transcribed data contains numerous misspellings that has made our quest harder than it should be.

Earlier this year I learned of the website, Geni.com, from the net@nite podcast provided by the TWiT network. Geni has proved a useful tool for recording genealogy data. The site itself is very well designed. It uses Flash as its backbone to provide a user-friendly means for adding and updating family records. Without even registering, users can immediately get to work by adding relatives to a dynamic family tree. The tree can easily be navigated with the click and drag of a mouse. Throughout the past six months, Geni has been adding new features at break-neck speed. None of which has caused the website any serious downtime. Not too bad for a Beta release.

The backups kick that I’ve been on lately prompted me to have a long conversation with my wife as to how we’re going to store our data for future generations. Will a SATA hard drive formatted in an arcane file system even be readable in 100 years? Will Geni.com exist? I doubt it. As our forefathers, my wife and I have begun to record our history on a media that has proven timeless, paper. To our benefit, Geni provides a data export service. This service allows data to be exported in two versions of the Genealogical Data Communication (GEDCOM) file format. Version 6.0 happens to use XML as its format. Reading this, my imagination immediately entertained several geek fantasies involving data migrations, SVG, and… JSON? My wife quickly squelched these dreams by reminding me of her pressing deadline.

I did, however, harbor the notion of converting the raw GEDCOM XML into DOT scripts so I could then use Graphviz to render some intricate graphs of my lineage. A quick test proved this possible, but manipulating the graphs would have taken too much time. Searching Google for Linux genealogy software yielded a handy program called GRAMPS. With little effort, I was able to import a GEDCOM file from Geni and begin testing GRAMPS’ reporting tools. Generating text reports was easy, but the graphing functionality in GRAMPS provided less than desirable results. With some time, I’ll master this new program and create a suitable low-tech solution for archiving the family tree.