5,414
edits
Changes
m
no edit summary
{{man warn|Gramps currently ({{CURRENTDAYNAME}}, {{CURRENTDAY}} {{CURRENTMONTHNAMEGEN}} {{CURRENTYEAR}}) experimenting with import of [[GEDCOM_7_support|GEDCOM 7 features Unsupported by Gramps Due to data model issues ]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.14 published on 8 February 2024] [https://gedcom.io/specifications/FamilySearchGEDCOMv7.pdf (Note7.0.14 pdf)] in the experimental stage. <br />Although first announced May 2021, the [https: some of these are also issues with //www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 57 implementation progress] list is still very thinly populated.5Due to the lack of broad support, the new version cannot be recommended as a transfer tool.1)}}
* Discourse Gramps community support forum: [https://gramps.discourse.group/t/gedcom-7-library-future-basis-of-a-new-gedcom-7-import-addon/7781 announcement of GEDCOM7 experimental import] ==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.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).
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.SUBM (submitter of this particular record)
===Persons===
INDI.FAMC.STAT (status of relationship type)
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).
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.TEXT (text of source)
===RepoRef===
REPO.CALN.MEDI.PHRASE
===Address related===
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 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 : [[Gramps_and_GEDCOM#Lost_information_on_a_GEDCOM_export_from_Gramps|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 : [[Gramps_and_GEDCOM#Information_written_in_other_form_on_GEDCOM_export|Information written in other form on GEDCOM (5.5.1) export]]
==Outdated GEDCOM Wikipages==
* Feature {{bug|12226}} : [GEDCOM 7] Support Import & Export of New (June 2021) version
* Gramps {{man version}} Wiki Manual - FAQ : [[Gramps_{{man version}}_Wiki_Manual_-_FAQ#What_standards_does_Gramps_support.3F|What standards does Gramps support?]] (refers to 5.5.1)
==See Also==
====GEDCOM official resources====* FamilySearch [https://www.familysearch.org/en/GEDCOM/implementation-progress list of products reporting or announcing future GEDCOM 7 support]* [[GEDCOM]] - basic description and resources for GEDCOM* [https://gedcom.io/specs/ 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. * [https://www.familysearch.org/developers/docs/guides/FamilyTree-data-objects FamilySearch (GEDCOM X BASED) data model] (diagram) ''(superseded)''* [https://gedcom.io/tools/ Example FamilySearch GEDCOM 7.0 Files] files provided for testing.* [https://gedcom.io/migrate/ Migrating v5.5.1 to v7.0]** [https://gedcom.io/migrate/#how-do-i-replace-gedcom-551-tags-that-were-removed-in-familysearch-gedcom-70 Replacing deprecated 5.5.1 tags] ====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[GEPS 045:_Place_Model_EnhancementsPlace Model Enhancements]]* [[GEPS 037: Support GEDCOM X]] - a proposal to support the GEDCOM X file format ''(superseded)''* Feature Request {{bug|12226}} [GEDCOM 7] Support Import & Export of New version* Feature Request {{bug|9925}} Support import and export of Custom [_APID]records to and from Ancestry.com generated GEDCOM files
[[Category:Developers/General]]
[[Category:GEPS|W]]