Friday, April 1, 2016

GEDCOM Lives!

GEDCOM 2016 Official LogoFor many years users have hoped for a GEDCOM standard extension that would enable the reliable transfer among genealogy programs of sources, citations, and media. Users and vendors alike have looked to FamilySearch to spearhead a community effort to upgrade GEDCOM to do just those things. Several attempts by just the community, and several attempts by just FamilySearch, have failed. Now, after several missteps, FamilySearch and a team of vendors together have successfully extended the standard and it looks like it will finally succeed. FamilySearch and a small group of vendors will announce today (or may have already done so by the time you read this) the GEDCOM-2016 standard.

GEDCOM was created by The Church of Jesus Christ of Latter-day Saints and released to the genealogical community in 1984. It was actively supported and updated for a number of years. After version 5.5 in January 1996 support waned. GEDCOM.org was abandoned and the GEDCOM specification was removed from FamilySearch.org. FamilySearch discontinued testing and registering compliant products.

Since then, FamilySearch has made several missteps in trying to replace the GEDCOM standard. They attempted to produce GEDCOM 6.0 in 2001 and started pushing GEDCOM X in recent years. I think both were pretty much new standards in GEDCOM clothing. They were much more complicated than the original and were expensive to implement. Neither FamilySearch nor other vendors ever produced products that would import or export GEDCOM 6.0 or GEDCOM X files. Version 5.5 remains the de facto standard 20 years later.

That is, until now. With GEDCOM-2016, FamilySearch has returned to their roots (so to speak). It is totally downwards compatible.

“These extensions were so straight forward, Mike and I implemented them all last Wednesday," said Bruce Bush, developer and owner of Enchanted Roots. “By keeping the data model simple, they finally came up with something anyone can implement.”

GEDCOM has human-readable lines of information beginning with four letter keywords like BIRT, DEAT, CHIL, HUSB, and WIFE for birth, death, child, husband, and wife. The new standard adds to these, as well as bringing back the compatibility testing and vendor registration.

In addition to addressing the lack of standards regarding sources, citations, and media, GEDCOM-2016 adds support for DNA.

The author of the “Dear Aunt Pearl” website has been a driving force in user efforts to establish GEDCOM extensions to address these needs. When I asked her opinion on this newest attempt, she said, "This is great. This is the GEDCOM extension that genealogists have been waiting for for a long, long time. I am so grateful that FamilySearch has stepped up to make this happen. Inclusion of DNA results is icing on the cake. This is wonderful."

Some of the newly added four-character GEDCOM codes are:

  • CITE - citation using specified template compatible with Evidence Explained.
  • DNA – raw DNA data
  • DROP - link to shared multimedia file in Dropbox
  • GOO – link to shared multimedia file on Google
  • EVER - link to shared file in Evernote
  • AWS - link to shared file in the Amazon cloud
  • STRIP - remove source citations
  • FAKE – perform a bad merge
  • DUPL – add duplicate to FamilySearch Family Tree
  • FEES - send to external website where fees may apply
  • RT - register for RootsTech
  • JPEG - remove details from photographs
  • RAND - randomly change the user interface on FamilySearch.org
  • SSN - commit identity theft
  • SALT - change all locations to Salt Lake City
  • FOOL - change all dates to April 1

Are there other codes you’d like to see implemented?

14 comments:

  1. love those final codes, especially DUPL and SALT. very funny!

    ReplyDelete
  2. Replies
    1. PICK -Pick a person with the same name for your ancestor

      SUFF - Sufficient authority. You don't have it.

      NOT - This is not the database you seek

      UNAV - The database you want to use is not available at this time

      TD - Technical difficulties

      Delete
  3. That's nice and all but what would be really great is the inclusion of search engine readable metadata tags.

    ReplyDelete
  4. Is any of that legit? Can't wait for the other shoe to drop tomorrow?

    ReplyDelete
  5. As far as I can tell from my experience, it has been a one-way street pretty much, from Ancestry to the other programs. Maybe things will change for the better, to enable better sharing of information. Maybe.

    ReplyDelete
  6. Always look forward to your April 1 postings. Thanks.

    ReplyDelete
  7. OH, man, you got me good! It's late in the day and I was gullible!! Thanks for the laugh!!

    ReplyDelete
  8. Are there other codes you’d like to see implemented?
    FOOLS - change all dates to April 1.

    ReplyDelete
  9. This comment has been removed by the author.

    ReplyDelete
  10. Damn you! Got me.
    I got so excited and then noticed the date.

    ReplyDelete