Difference between revisions of "Addon:GEDCOM Extensions"

From Gramps
Jump to: navigation, search
m (Others projects)
(Usage)
(24 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Export Gedcom Extensions =
+
{{Third-party plugin}}
  
There is an Addon (currently available for Gramps 3.5) which has a collection of unofficial GEDCOM extensions. If the feature you want is not listed below, then you can either add it yourself, or ask a developer to help you.
+
[[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)]]
  
The code is in the Addon [http://gramps-addons.svn.sourceforge.net/viewvc/gramps-addons/trunk/contrib/GedcomExtensions/ gramps-addons/trunk/contrib/GedcomExtensions/GedcomExtensions.py].
+
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.
  
== Extensions ==
+
{{-}}
  
The code currently supports the following extensions:
+
= Export GEDCOM Extensions =
 +
 
 +
The following GEDCOM Extensions are supported:
  
 
* Exports witnesses associated with a family event
 
* Exports witnesses associated with a family event
  
== Running the Exporter ==
+
== 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".
 +
 
 +
Afterwards, you can change the extension from ".ged2" to ".ged" and treat as a normal GEDCOM file.
  
To run the exporter, select "Gedcom Extensions". Select the relevant options, and the data should be exported to a file with the extension ".ged2".
 
  
Currently, there is not an associated .ged2 importer in Gramps, so the current export is one-way only (out of Gramps). It would be easy for someone to also write an associated 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.}}
  
= Import Gedcom Extensions =
+
= Import GEDCOM Extensions =
  
 
There are no import extensions currently supported.
 
There are no import extensions currently supported.
 +
 +
= 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].
 +
 +
;Current open Feature request for Gramps:
 +
* {{bug|8094}} GedcomExtension to export family event secondary participant if role in CELEBRANT, INFORMANT, CLERGY, AIDE, CUSTOM
 +
* {{bug|8093}} Wrong level for witnesses in GedcomExtension, and export
 +
* {{bug|6023}} Export Family Historian GEDCOM Extensions
 +
* {{bug|688}} Support for Gedcom 5.5EL (or Gedcom-L the more recent standard)
 +
* {{bug|7965}} Gedcom Extensions export raises error
 +
 +
* [[Gramps_and_GEDCOM]]
 +
 +
== Collection of GEDCOM extension tags used in different programs ==
 +
* (English)[http://www.fhug.org.uk/wiki/doku.php?id=glossary:gedcom_extension_list GEDCOM Extension List (FHUG Knowledge Base)]
 +
* (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/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.  
  
See the demo[https://github.com/DallanQ/Gedcom/wiki/Demo]. ''GEDCOM -> model -> json -> model -> GEDCOM'' round-tripp 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.
  
 
** differences between the object model and the GEDCOM 5.5 Specification.[https://github.com/DallanQ/Gedcom/wiki/Specification-differences]
 
** differences between the object model and the GEDCOM 5.5 Specification.[https://github.com/DallanQ/Gedcom/wiki/Specification-differences]
** set of UML diagrams illustrating the core Gedcom class and each of the top-level objects.[https://github.com/DallanQ/Gedcom/wiki/UML-Diagrams]
+
** set of UML diagrams illustrating the core GEDCOM class and each of the top-level objects.[https://github.com/DallanQ/Gedcom/wiki/UML-Diagrams]
  
 
[[Category:Developers/General]]
 
[[Category:Developers/General]]
 
[[Category:Documentation]]
 
[[Category:Documentation]]
 
[[Category:Plugins]]
 
[[Category:Plugins]]

Revision as of 23:29, 27 September 2015

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.


"GEDCOM Extensions (GED2)" option selected in Export_Assistant (Gramps 4.1.3, Ubuntu 14.04.2)

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".

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 also

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

Current open Feature request for Gramps
  • 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
  • 688 Support for Gedcom 5.5EL (or Gedcom-L the more recent standard)
  • 7965 Gedcom Extensions export raises error

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]