GEDCOM 7 support
Gramps does not currently (Sunday, 3 November 2024) import GEDCOM 7 Revision 7.0.14 published on 8 February 2024 (7.0.14 pdf). |
Contents
- 1 GEDCOM 7 features Unsupported by Gramps Due to data model issues
- 1.1 Header
- 1.2 PersonRef
- 1.3 SUBM
- 1.4 NON EVENT STRUCTURE
- 1.5 Events
- 1.6 Attributes
- 1.7 Family
- 1.8 Persons
- 1.9 Identifier structure
- 1.10 Creation date
- 1.11 Change
- 1.12 Mutimedia link
- 1.13 Dates
- 1.14 Notes
- 1.15 Citations
- 1.16 Sources
- 1.17 RepoRef
- 1.18 Address related
- 1.19 Privacy
- 1.20 Media
- 1.21 LDS
- 1.22 Names
- 1.23 Places
- 2 Gramps features Unsupported by GEDCOM 7 Due to data model issues
- 3 Outdated GEDCOM Wikipages
- 4 See Also
GEDCOM 7 features Unsupported by Gramps Due to data model issues
(Note: some of these are also issues with GEDCOM 5.5.1)
Header
HEAD.NOTE {0:1}
HEAD.SOUR.DATA (info about source) HEAD.SOUR.DATA.DATE HEAD.SOUR.DATA.COPR
HEAD.SOUR.CORP (Corporate info about source program) HEAD.SOUR.CORP.ADDR
HEAD.COPR (Copyright)
HEAD.LANG (not sure what to do with this)
PersonRef
x.ASSO.PHRASE (PHRASE is text added in a lot of places)
x.ASSO.ROLE.PHRASE
SUBM
and all its sub data), could be multiple and referenced in several places
NON EVENT STRUCTURE
We need a way to say events didn't happen (still has date, notes, sources)
Events
ADDR (address and place are both allowed and are independent This makes trying to combine the two into one place problematical).
AGNC/RELI/CAUS (can probably be attributes)
SDATE (sort date, not historical information but to be used for sorting)
AGE AGE.PHRASE (some events have this)
TYPE (some events have types) Could be attribute
EVEN.TEXT (generic EVEN.TYPE also has this for description)
Attributes
FAM/INDI.ATTR FAM/INDI.ATTR.TYPE (really these are more like events with dates, ages etc., Gramps often treats them as Attributes without date support)
Family
FAM.ASSO
FAM.HUSB/WIFE/CHIL.PHRASE
FAM.NCHI number of children (attribute?)
FAM.SUBM (submitter of this particular record)
Persons
INDI.FAMC.STAT (status of relationship type)
INDI.FAMC.PEDI.PHRASE (could be a note...)
INDI.ALIA An alias, not of name, but of the INDI record itself???
INDI.ANCI INDI.DESI Ancestor or descendant interest by a SUBM
INDI.SUBM (submitter of this particular record)
Identifier structure
(x.REFN.TYPE / x.UID /x.EXID.TYPE) We have been using notes for subtype and attribute for the type for REFN. We have a PR for UID (on only persons and families) at the moment, but it works differently than specification, which requires a string type without modification.
Creation date
x.CREA.DATE and optional TIME (everywhere CHAN was used)
Change
x.CHAN.DATE.NOTE optional TIME (Why a note on the change???)
Mutimedia link
x.OBJE.TITL (we could put in MediRef attribute or note...)
Dates
DATE.PHRASE (can be present even when fully supplied with detailed date)
DATE.TIME
Notes
NOTE.MIME (Support for HTML in notes, with unsupported sub/superscript).
NOTE.LANG
NOTE.TRAN NOTE.TRAN.MIME NOTE.TRAN.LANG
NOTE.SOUR (big one! requires core data model to have citations on notes, spec says be careful about circular references)
SNOTE (currently all Gramps notes are shared, we don't have a way to make a note local)
Citations
SOUR.DATA.TEXT {0:M} SOUR.DATA.TEXT.MIME SOUR.DATA.TEXT.MIME.LANG (citation text field)
SOUR.EVEN SOUR.EVEN.PHRASE SOUR.EVEN.ROLE SOUR.EVEN.ROLE.PHRASE (about event the citation references)
Sources
SOUR.DATA.EVEN {0:M} (list of events described) SOUR.DATA.EVEN.DATE SOUR.DATA.PLAC
SOUR.DATA.AGNC
SOUR.DATA.NOTEs
SOUR.TEXT (text of source)
RepoRef
REPO.CALN.MEDI.PHRASE
PHON/FAX/EMAIL/WWW These can be anyplace an address can be, but are independent of the address
Privacy
x.RESN (Three values, Confidential, Locked, Privacy) as opposed to our single Private setting.
Media
The OBJE record allows a single OBJE to refer to multiple files.
OBJE.FILE.FORM.MEDI.PHRASE FILE.TITLE FILE.TITLE.TRAN
OBJE.FILE may want to support all URLs (load on import? or for all operations?)
LDS
STAT.DATE (supposed to be a separate date for the status)
Names
NAME.TYPE.PHRASE (A lot of types also have phrases)
NAME.TRAN {0:M} NAME.TRAN.LANG (I think we can deal with this as multiple names)
Places
PLAC.LANG PLAC.TRAN (I think we actually have this covered with place name editor)
Gramps features Unsupported by GEDCOM 7 Due to data model issues
- There are elements currently documented as lost in a symmetrical export/import via GEDCOM : Lost information on a GEDCOM (5.5.1) export from Gramps
- There are elements currently documented as transformed in a symmetrical export/import via GEDCOM : Information written in other form on GEDCOM (5.5.1) export
Outdated GEDCOM Wikipages
- Feature 12226 : [GEDCOM 7] Support Import & Export of New (June 2021) version
- Gramps 5.2 Wiki Manual - FAQ : What standards does Gramps support? (refers to 5.5.1)
See Also
GEDCOM official resources
- FamilySearch list of products reporting or announcing future GEDCOM 7 support
- GEDCOM - basic description and resources for GEDCOM
- GEDCOM specification documents on the gedcom.io official site. Includes the officially recommended specifications (7.0.2, 5.5.1 and 5.5), previous (superseded) variants and orphaned (but authorized) proposed variants. Unauthorized variants are NOT listed.
- FamilySearch (GEDCOM X BASED) data model (diagram) (superseded)
- Example FamilySearch GEDCOM 7.0 Files files provided for testing.
- Migrating v5.5.1 to v7.0
Gramps implementations of GEDCOM
- Gramps Data Model (diagram)
- Gramps and GEDCOM - list of data lost/transformed during export to GEDCOM 5.5
- Addon:GEDCOM Extensions - exporter.
- GEPS 045: Place Model Enhancements
- GEPS 037: Support GEDCOM X - a proposal to support the GEDCOM X file format (superseded)
- Feature Request 12226 [GEDCOM 7] Support Import & Export of New version
- Feature Request 9925 Support import and export of Custom [_APID] records to and from Ancestry.com generated GEDCOM files