Difference between revisions of "Addon:GEDCOM Extensions"
(→Usage) |
|||
(One intermediate revision by the same user not shown) | |||
Line 16: | Line 16: | ||
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". | 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. | ||
+ | |||
{{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 33: | Line 36: | ||
* {{bug|7965}} Gedcom Extensions export raises error | * {{bug|7965}} Gedcom Extensions export raises error | ||
+ | * [[Gramps_and_GEDCOM]] | ||
== Collection of GEDCOM extension tags used in different programs == | == Collection of GEDCOM extension tags used in different programs == |
Revision as of 23:29, 27 September 2015
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
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.
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
- (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[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.