Difference between revisions of "Addon:GEDCOM Extensions"
(→Usage) |
(→See also) |
||
(6 intermediate revisions by the same user not shown) | |||
Line 12: | Line 12: | ||
* 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)"}}. | + | [[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. | 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 24: | Line 29: | ||
= Import GEDCOM Extensions = | = Import GEDCOM Extensions = | ||
− | There are no import extensions currently supported. | + | There are no import extensions currently supported.[http://gramps.1791082.n4.nabble.com/Geneanet-Gramps-importing-woes-tp4673883p4673965.html] |
= See also = | = See also = | ||
Line 30: | Line 35: | ||
;Current open Feature request for Gramps: | ;Current open Feature request for Gramps: | ||
− | |||
− | |||
* {{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|688}} Support for Gedcom 5.5EL (or Gedcom-L the more recent standard) | ||
− | * {{bug| | + | * {{bug|9249}} GEDCOM import improvements to support Ancestry.com, FTM 2012/2014 and FTM for MAC 3 |
* [[Gramps_and_GEDCOM]] | * [[Gramps_and_GEDCOM]] | ||
Line 44: | Line 47: | ||
== Others projects == | == Others projects == | ||
− | * [https://github.com/ | + | * [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 23:12, 20 April 2016
This is a Third-party Addon. 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 |
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.
Contents
Export GEDCOM Extensions
The following GEDCOM Extensions are supported:
- Exports witnesses associated with a family event
- Include media
Usage
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.
Import GEDCOM Extensions
There are no import extensions currently supported.[1]
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
- (English)GEDCOM Extension List (FHUG Knowledge Base)
- (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[2]. 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.