Addon:GEDCOM Extensions

This is a Third-party Addon. The Addon/Plugin system is controlled by the Plugin Manager. Please use carefully on data that is backed up, and help make it better by reporting any issues to the bug tracker. Unless otherwise stated on this page, you can download this addon by following these instructions. Please note that some Addons have prerequisites that need to be installed before they can be used.

This Addon (available for Gramps 4.0 and higher) has a collection of unofficial GEDCOM extensions which extend Gramps GedcomWriter to include common non-compliant GEDCOM additions. If the feature you want is not listed below, then you can either add it yourself, or ask a developer to help you.

Export GEDCOM Extensions

The following GEDCOM Extensions are supported:

• Exports witnesses associated with a family event

Usage

To run the exporter, select Family Trees > Export.., press Next, select "GEDCOM Extensions (GED2)". Select the relevant options, and the data should be exported to a file with the extension ".ged2".

Warning There is no associated .ged2 importer in Gramps, so the export is one-way only (out of Gramps). It should be possible for someone to also write an associated GEDCOM importer to handle the extensions to bring them into Gramps as well.

Import GEDCOM Extensions

There are no import extensions currently supported.

See also

The code is available from addons-source/blob/master/GedcomExtensions/GedcomExtensions.py.

• 8094 GedcomExtension to export family event secondary participant if role in CELEBRANT, INFORMANT, CLERGY, AIDE, CUSTOM
• 8093 Wrong level for witnesses in GedcomExtension, and export
• 6023 Export Family Historian GEDCOM Extensions

Collection of GEDCOM extension tags used in different programs

• (German)Collection of GEDCOM extension tags used in different programs

Others projects

• GEDCOM (WeRelate.org) is a project for parsing objects ignored by a model. It includes classes and attributes for every GEDCOM tag sequence appearing in more than 4% of the 7000 GEDCOMs submitted to WeRelate.org over the past five years, with the exception of four software-specific schema tags: SCHEMA, _EVENT_DEFN, _PLAC_DEFN, and _EVDEF, generated by Family Tree Maker, Personal Ancestral File, Legacy, and RootsMagic respectively.

See the demo[1]. GEDCOM -> model -> json -> model -> GEDCOM round-trip shows the GEDCOM tags that are represented in the model as extensions, and tags that cannot be represented.

• • differences between the object model and the GEDCOM 5.5 Specification.[2]
  • set of UML diagrams illustrating the core GEDCOM class and each of the top-level objects.[3]