Changes

Jump to: navigation, search

Addon:GEDCOM Extensions

1,826 bytes added, 23:12, 20 April 2016
→‎See also
= Export Gedcom Extensions ={{Third-party plugin}}
There is an Addon [[File:GEDCOM Extensions GED2 Export Assistant gramps.png|right|400px|"GEDCOM Extensions (GED2)" option selected in Export_Assistant (currently available for Gramps 4.0) which has a collection of unofficial GEDCOM extensions1. If the feature you want is not listed below3, then you can either add it yourself, or ask a developer to help youUbuntu 14.04.2)]]
The code is in the This Addon [http://svn.code.sf(available for Gramps 4.net/p/gramps0 and higher) has a collection of unofficial GEDCOM extensions which extend Gramps GedcomWriter to include common non-addons/code/trunk/contrib/GedcomExtensions/GedcomExtensionscompliant GEDCOM additions.py gramps-addons/trunk/contrib/GedcomExtensions/GedcomExtensions.py]If the feature you want is not listed below, then you can either add it yourself, or ask a developer to help you.
== Extensions =={{-}}
= Export GEDCOM Extensions = The code currently supports the following extensionsGEDCOM Extensions are supported:
* Exports witnesses associated with a family event
* Include media
 
== Usage ==
 
[[File:Export-GEDCOM-Extensions-export-options-dialog-gramps42.png|right|400px|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.}}
 
= Import GEDCOM Extensions =
== Running the Exporter ==There are no import extensions currently supported.[http://gramps.1791082.n4.nabble.com/Geneanet-Gramps-importing-woes-tp4673883p4673965.html]
To run the exporter, select "Gedcom Extensions"= See also =The code is available from [https://github. Select the relevant options, and the data should be exported to a file with the extension "com/gramps-project/addons-source/blob/master/GedcomExtensions/GedcomExtensions.ged2"py addons-source/blob/master/GedcomExtensions/GedcomExtensions.py].
Currently, there is not an associated ;Current open Feature request for Gramps:* {{bug|6023}} Export Family Historian GEDCOM Extensions* {{bug|688}} Support for Gedcom 5.ged2 importer in Gramps, so 5EL (or Gedcom-L the current export is one-way only (out of Grampsmore recent standard)* {{bug|9249}} GEDCOM import improvements to support Ancestry. It would be easy com, FTM 2012/2014 and FTM for someone to also write an associated importer to handle the extensions to bring them into Gramps as well.MAC 3
= Import Gedcom Extensions =* [[Gramps_and_GEDCOM]]
There are no import extensions currently supported== 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 ==
* [https://github.com/DallanQFamilySearch/Gedcom 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.
** 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 GEDCOM class and each of the top-level objects.[https://github.com/DallanQ/Gedcom/wiki/UML-Diagrams]
[[Category:Developers/General]]
[[Category:Documentation]]
[[Category:Plugins]]
Retrieved from "https://gramps-project.org/wiki/index.php/Special:MobileDiff/43461...61411"

Navigation menu