Gramps and GEDCOM - Revision history

Patsyblefebre: which at the time

2013-02-13T02:45:02Z

which at the time

Patsyblefebre: Gramps XML

2013-02-11T08:37:22Z

Gramps XML

Dsblank at 00:13, 23 August 2012

2012-08-23T00:13:22Z

Kulath: Detail event and event reference attributes (see bug 1956)

2012-03-19T18:23:46Z

Detail event and event reference attributes (see bug 1956)

Kulath: Details of GEDCOM import moved to Gramps 3.4 manual

2012-03-05T19:57:42Z

Details of GEDCOM import moved to Gramps 3.4 manual

Show changes

Lcc: /* Information in GEDCOM 5.5 not in Gramps (lost on import) */

2012-02-10T07:29:36Z

‎Information in GEDCOM 5.5 not in Gramps (lost on import)

Kulath: Provide more details about information lost

2012-02-09T23:45:01Z

Provide more details about information lost

Show changes

Romjerome: /* Information in GEDCOM 5.5 not in Gramps (lost on import) */

2012-01-29T08:59:44Z

‎Information in GEDCOM 5.5 not in Gramps (lost on import)

Romjerome: /* Information in GEDCOM 5.5 not in Gramps (lost on import) */

2012-01-29T08:58:58Z

‎Information in GEDCOM 5.5 not in Gramps (lost on import)

Romjerome: /* Information in GEDCOM 5.5 not in Gramps (lost on import) */

2012-01-29T08:58:03Z

‎Information in GEDCOM 5.5 not in Gramps (lost on import)

← Older revision		Revision as of 02:45, 13 February 2013
Line 1:		Line 1:
−	Gramps uses [[Gramps XML]] which is considered a superior format to [[GEDCOM]] by the Gramps developers. Although Gramps should be able to import most data from GEDCOM through its GEDCOM Import module, many of the Gramps features are not supported by the GEDCOM standard and so GEDCOM Export from a Gramps Family Tree or Gramps XML is a lossy operation. This page shall list all the information that is lost on a GEDCOM export from Gramps, so that users may choose to restrain their Gramps use to those features that GEDCOM can handle. Gramps recognizes the relevance of GEDCOM and attempts to offer the best compatibility possible. The Gramps version used as a reference is Gramps Trunk, ~~currently~~ Gramps 3.3.	+	Gramps uses [[Gramps XML]] which is considered a superior format to [[GEDCOM]] by the Gramps developers. Although Gramps should be able to import most data from GEDCOM through its GEDCOM Import module, many of the Gramps features are not supported by the GEDCOM standard and so GEDCOM Export from a Gramps Family Tree or Gramps XML is a lossy operation. This page shall list all the information that is lost on a GEDCOM export from Gramps, so that users may choose to restrain their Gramps use to those features that GEDCOM can handle. Gramps recognizes the relevance of GEDCOM and attempts to offer the best compatibility possible. The Gramps version used as a reference is Gramps Trunk, which at the time was Gramps 3.3.

	The GEDCOM standard stopped evolving on 10 January 1996. There is a draft for a 5.5.1 version, of which Gramps uses several features as noted below.		The GEDCOM standard stopped evolving on 10 January 1996. There is a draft for a 5.5.1 version, of which Gramps uses several features as noted below.

← Older revision		Revision as of 08:37, 11 February 2013
Line 1:		Line 1:
−	Gramps uses [[~~GRAMPS_XML\|~~Gramps XML]] which is considered a superior format to [[GEDCOM]] by the Gramps developers. Although Gramps should be able to import most data from GEDCOM through its GEDCOM Import module, many of the Gramps features are not supported by the GEDCOM standard and so GEDCOM Export from a Gramps Family Tree or Gramps XML is a lossy operation. This page shall list all the information that is lost on a GEDCOM export from Gramps, so that users may choose to restrain their Gramps use to those features that GEDCOM can handle. Gramps recognizes the relevance of GEDCOM and attempts to offer the best compatibility possible. The Gramps version used as a reference is Gramps Trunk, currently Gramps 3.3.	+	Gramps uses [[Gramps XML]] which is considered a superior format to [[GEDCOM]] by the Gramps developers. Although Gramps should be able to import most data from GEDCOM through its GEDCOM Import module, many of the Gramps features are not supported by the GEDCOM standard and so GEDCOM Export from a Gramps Family Tree or Gramps XML is a lossy operation. This page shall list all the information that is lost on a GEDCOM export from Gramps, so that users may choose to restrain their Gramps use to those features that GEDCOM can handle. Gramps recognizes the relevance of GEDCOM and attempts to offer the best compatibility possible. The Gramps version used as a reference is Gramps Trunk, currently Gramps 3.3.

	The GEDCOM standard stopped evolving on 10 January 1996. There is a draft for a 5.5.1 version, of which Gramps uses several features as noted below.		The GEDCOM standard stopped evolving on 10 January 1996. There is a draft for a 5.5.1 version, of which Gramps uses several features as noted below.

← Older revision		Revision as of 00:13, 23 August 2012
Line 2:		Line 2:

	The GEDCOM standard stopped evolving on 10 January 1996. There is a draft for a 5.5.1 version, of which Gramps uses several features as noted below.		The GEDCOM standard stopped evolving on 10 January 1996. There is a draft for a 5.5.1 version, of which Gramps uses several features as noted below.
		+
		+	The following assumes the standard GEDCOM export utility. However, there is also a set of common extensions that have been bundled together. See [[GEDCOM Extensions]] for more information.

	__TOC__		__TOC__

@@ Line 17: / Line 17: @@
 * '''Source Data''': no equivalent in GEDCOM.
 * '''Source on places''': no equivalent in GEDCOM.
-* '''Event Attributes different from age, father age, mother age, cause, agency'''. These other attributes have no equivalent in GEDCOM.
+* '''Event Attributes different from age, father age, mother age, cause, agency'''. These other attributes have no equivalent in GEDCOM. AGNC and CAUS are exported from Agency and Cause attributes (respectively) of an event. AGE, HUSB:AGE and WIFE:AGE are exported from Age, Father's Age and Mother's Age (respectively) of an event reference. Hence these items of data should be stored in the appropriate place for export.
 * '''Media Description''': set by user, no equivalent in GEDCOM.
 * '''Reference region of a media reference'''.

@@ Line 91: / Line 91: @@
 * individual record, individual attribute structure, some event detail is ignored (as shown above), except for the individual attributes EDUC (Scholastic achievement), NMR (Count of marriages), OCCU (Occupation), PROP (Possessions), RELI (Religious affiliation), RESI and TITL (Nobility title), which are all treated in Gramps as 'events's
 * Individual record, link to submitter ignored
-* Individual record, REFN:TYPE ignored (note: REFN, RFN and AFN '''are'' stored as attributes)
+* Individual record, REFN:TYPE ignored (note: REFN, RFN and AFN '''are''' stored as attributes)
      FAMILY_RECORD:=

@@ Line 44: / Line 44: @@
 * Multimedia object in source citation (maybe [[GEPS_023:_Storing_data_from_large_sources|available]] on 3.4?)
 * EVENT_TYPE_CITED_FROM and ROLE_IN_EVENT in source citation. ''Available on 3.4, see {{bug|2918}}''
-* Citations on Notes
+* Citations on Notes (maybe [[GEPS_023:_Storing_data_from_large_sources|available]] on 3.4?)
 [[Category:Documentation]]