Difference between revisions of "Addon:GEDCOM Extensions"

From Gramps
Jump to: navigation, search
(See also)
(Import GEDCOM Extensions)
(23 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{Third-party plugin}}
 
{{Third-party plugin}}
 +
{{man note|Available for Gramps 4.x and higher.}}
 +
[[File:GEDCOMExtensions-GED2-ChooseTheOutputFormat-tab-ExportAssistant-50.png|right|450px|"GEDCOM Extensions (GED2)" option selected in Export_Assistant]]
  
[[File:GEDCOM Extensions GED2 Export Assistant gramps.png|right|400px|"GEDCOM Extensions (GED2)" option selected in Export_Assistant (Gramps 4.1.3, Ubuntu 14.04.2)]]
+
This Addon has a collection of unofficial GEDCOM extensions which extend Gramps GedcomWriter to include common non-compliant GEDCOM additions.  
  
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.
+
If the feature you want is not listed below, then you can either add it yourself, or ask a developer to help you.
  
 
{{-}}
 
{{-}}
Line 12: Line 14:
  
 
* Exports witnesses associated with a family event
 
* Exports witnesses associated with a family event
 +
* Include media
  
 
== Usage ==
 
== Usage ==
  
To run the exporter, select {{man menu|Family Trees > Export..}}, press {{man button|Next}}, select {{man label|"GEDCOM Extensions (GED2)"}}. Select the relevant options, and the data should be exported to a file with the extension ".ged2".
+
[[File:GEDCOMExtensions-GED2-ExportOptions-tab-ExportAssistant-50.png|right|450px|Checkbox enabled for "Include witnesses" associated with a family event.]]
 +
 
 +
To run the exporter, select {{man menu|Family Trees > Export..}}, press {{man button|Next}}, on the {{man label|Choose the output format}} dialog select {{man label|"GEDCOM Extensions (GED2)"}}, press {{man button|Next}}. On the {{man label|Export options}} dialog select the relevant GEDCOM extension option:
 +
* {{checkbox|1}} {{man label|Include witnesses}} - (checked by default) Exports witnesses associated with a family event
 +
* {{checkbox|1}} {{man label|Include media}} - (checked by default)
 +
Then press {{man button|Next}}, and after selecting the save location and applying the export the data should be exported to a file with the extension ".ged2".
 +
 
 +
Afterwards, you can change the extension from ".ged2" to ".ged" and treat as a normal GEDCOM file.
  
 
{{man warn|Warning|There is no associated .ged2 importer in Gramps, so the {{man menu|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.}}
 
{{man warn|Warning|There is no associated .ged2 importer in Gramps, so the {{man menu|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.}}
Line 22: Line 32:
  
 
There are no import extensions currently supported.
 
There are no import extensions currently supported.
 +
 +
See feature request:
 +
* {{bug|10550}} '''Refactor Gramps GEDCOM import so as to support GEDCOM extension addons'''
  
 
= See also =
 
= See also =
 
The code is available from [https://github.com/gramps-project/addons-source/blob/master/GedcomExtensions/GedcomExtensions.py addons-source/blob/master/GedcomExtensions/GedcomExtensions.py].
 
The code is available from [https://github.com/gramps-project/addons-source/blob/master/GedcomExtensions/GedcomExtensions.py addons-source/blob/master/GedcomExtensions/GedcomExtensions.py].
  
* {{bug|8094}} GedcomExtension to export family event secondary participant if role in CELEBRANT, INFORMANT, CLERGY, AIDE, CUSTOM
+
;Current open Feature request for Gramps:
* {{bug|8093}} Wrong level for witnesses in GedcomExtension, and export
 
 
* {{bug|6023}} Export Family Historian GEDCOM Extensions
 
* {{bug|6023}} Export Family Historian GEDCOM Extensions
 +
* {{bug|688}} Support for Gedcom 5.5EL (or Gedcom-L the more recent standard)
 +
* {{bug|9249}} GEDCOM import improvements to support Ancestry.com, FTM 2012/2014 and FTM for MAC 3
 +
 +
* [[Gramps_and_GEDCOM]]
  
 
== Collection of GEDCOM extension tags used in different programs ==
 
== Collection of GEDCOM extension tags used in different programs ==
 +
* [http://genealogytools.com/family-tree-maker-to-gedcom-to-other-apps-crosswalk/ Family Tree Maker to GEDCOM to Other Apps Crosswalk], by Keith Riggle (This spreadsheet shows alot of the custom GEDCOM extension tags for a number of programs.)
 +
* [http://www.fhug.org.uk/wiki/doku.php?id=glossary:gedcom_extension_list GEDCOM Extension List (FHUG Knowledge Base)], GEDCOM custom tags used by Family Historian
 +
* [http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html GEDCOM Files] - Custom tags in Legacy Family Tree
 
* (German)[http://wiki-de.genealogy.net/GEDCOM/_Nutzerdef-Tag#.C3.9Cbersicht_bekannter_Nutzerdefinierter_Kennzeichen Collection of GEDCOM extension tags used in different programs]
 
* (German)[http://wiki-de.genealogy.net/GEDCOM/_Nutzerdef-Tag#.C3.9Cbersicht_bekannter_Nutzerdefinierter_Kennzeichen Collection of GEDCOM extension tags used in different programs]
 
  
 
== Others projects ==
 
== Others projects ==
  
* [https://github.com/DallanQ/Gedcom 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.  
+
* [https://github.com/FamilySearch/Gedcom 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[https://github.com/DallanQ/Gedcom/wiki/Demo]. ''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.
 
See the demo[https://github.com/DallanQ/Gedcom/wiki/Demo]. ''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.

Revision as of 22:06, 16 April 2018

Gramps-notes.png

Please use carefully on data that is backed up, and help make it better by reporting any comments or problems to the author, or 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/Plugin system is controlled by the Plugin Manager.

Gramps-notes.png
Available for Gramps 4.x and higher.

"GEDCOM Extensions (GED2)" option selected in Export_Assistant

This Addon 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
  • Include media

Usage

Checkbox enabled for "Include witnesses" associated with a family event.

To run the exporter, select Family Trees > Export.., press Next, on the Choose the output format dialog select "GEDCOM Extensions (GED2)", press Next. On the Export options dialog select the relevant GEDCOM extension option:

  • Include witnesses - (checked by default) Exports witnesses associated with a family event
  • Include media - (checked by default)

Then press Next, and after selecting the save location and applying the export the data should be exported to a file with the extension ".ged2".

Afterwards, you can change the extension from ".ged2" to ".ged" and treat as a normal GEDCOM file.

Gnome-important.png
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 feature request:

  • 10550 Refactor Gramps GEDCOM import so as to support GEDCOM extension addons

See also

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

Current open Feature request for Gramps
  • 6023 Export Family Historian GEDCOM Extensions
  • 688 Support for Gedcom 5.5EL (or Gedcom-L the more recent standard)
  • 9249 GEDCOM import improvements to support Ancestry.com, FTM 2012/2014 and FTM for MAC 3

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]