Committed to seamless genealogy file sharing

DearREADERS,
RootsTech 2011 provided a great deal of answers, but opened up many more questions. Sharing genealogy data is a top concern for Ol' Myrt, and it looks like FamilySearch is considering updating its generic genealogy file system currently known as GEDCOM.

• Ancestry Insider's Richard G. Scott: Some of the Finest at RootsTech
• James Tanner's New Developments at FamilySearch
• Jordan Jones' RootsTech 2011: Towards a New Genealogical Data Model

BetterGEDCOM (a grassroots effort) and OpenGen (a top-down developer model with a genealogy database website component) are two entities also in the conversation about improving file sharing. For a listing of GEDCOM Alternatives see the comprehensive list by Tamura Jones.

Hopefully, conversations will continue when it comes to the concept of sharing genealogy database files between researchers, much like this model:

End-user to end-user
Where Researcher A exports a GEDCOM file from his genealogy management program and then directly shares that file with Researcher B via flash drive, CD or some other means. Researcher B opens his genealogy management program and then imports the GEDCOM file.

At  RootsTech, FamilySearch mentioned SoRD as a method of file sharing, but if Ol' Myrt's understanding is correct, that will involve a third party, much like this model:

End-User to website to End-User
Where Researcher A uploads his GEDCOM file to a genealogy website, where Researcher B  downloads from website and imports the GEDCOM file.

Call me crazy, but Ol' Myrt here doesn't like the idea of a website being part of the equation unless it is a disinterested third party like Dropbox, where two researchers agree to share a folder (instead of snail mailing a flash drive) with a generic file that can read by either researcher's genealogy management program seamlessly.

Allowing big-guy genealogy websites like Ancestry.com or even FamilySearch.org to broker data file transfers between individual researchers can prove problematic on at least these levels:

• How can the end-user determine his data isn't altered perhaps by masks and filters by the website?
• How can the end user determine his data isn't linked and/or merged by the website to other user-contributed databases?
• How can the end user ensure that his data isn't retained by the website, when he chooses to take down the file? One might want to do this and upload a more up-to-date file, or completely remove the file with no further interaction with the website.

GEDCOM FILES AREN'T PERFECT
Generic genealogy database files are currently called GEDCOM files. In his posting File Sharing? GEDCOM or what? James Tanner explains "It seems like whomever you need to share information with never seems to have the same program you use. There was a time when Personal Ancestral File (PAF) was pervasive. But with the de-emphasis on the program, there are dozens of different options. Your first door of opportunity in sharing files is to see what formats are supported by your own program."

Unfortunately each genealogy program out there has decided to pick and choose which GEDCOM file parameters it will to embrace. The less-than-marvelous results have been described by genealogy bloggers. It's particularly disheartening that of Legacy Family Tree, Family Tree Maker and RootsMagic only the later can seamlessly export and import it's own GEDCOM file without data loss. See:

• Randy Seavers' Do Genealogy Template Sources Survive When Passed Through GEDCOM (They don't in 2 out of 3 tests Randy completed.)
• Randy Seavers' Software Programs, GEDCOM Files and Source Citations - Some Recommendations
• Tamura Jones'  groundbreaking work Three Torture Tests
• Tamura Jones' Some GEDCOM Torture Test Results
• Various postings by Russ and GeneJ at the BetterGEDCOM Blog, including GEDCOM import and export tests. 

While The LDS Church owns the "GEDCOM" name, it hasn't supported the GEDCOM file during the last 14 years. See BetterGEDCOM Wikispaces' History of GEDCOM. According to other RootsTech attendees, FamilySearch says it's GEDCOM revision will begin with the GenTech data model. BetterGEDCOM developers have considered this and a variety of other data models on the BetterGEDCOM Wiki, including:

• GEDCOM Data Model
• GenTech Data Model
• GRAMPS Data Model
• DeadEnds Model
• SFT.xml Model
• GenXML Data Model
• GedML Data Format
• Event Gedcom
• OpenGen Data Model
• FSDN Model

And the trick is?

Convincing genealogy software producers to adhere to a single "new" file sharing format will be problematic, particularly since they don't currently agree by using all existing GEDCOM specifications. IF they would work this out together, there would be no need for reforms such being explored by BetterGEDCOM. IF end users bring pressure to bear once a good GEDCOM alternative has been developed, THEN perhaps software producers will adopt the plan.

COMMITTED TO SEAMLESS FILE SHARING

Some folks are pleased FamilySearch is weighing in on improving file sharing, thinking that high-profile organization will galvanize support from software producers. Others question FamilySearch commitment based on its history of dropping PAF and ignoring GEDCOM for 14 years. (I don't think FS dropped PAF per se, but rather decided to focus on things they do best like digitizing records.) My commitment is to support the development of seamless end-user to end-user file sharing capability, without requiring a genealogy website to be part of the equation.



FOR FURTHER READING

• Adrian Bruce's Better GEDCOM Requirements Catalog
• Doug Blank's Gramps
• Louis Kessler's Build a BetterGEDCOM or learn GEDCOMBetter? and his Behold 
• Tamura Jones' A Gentle Introduction to GEDCOM. "Unlike many other introductions to GEDCOM, this text is not about the technical details of the GEDCOM data format, but about basic facts and real-world issues."
• Tom Wetmore's Goals and Requirements

Happy family tree climbing!
Myrt     :)
DearMYRTLE,
Your friend in genealogy.