GEDCOM Tag Names Section

Overview

The GEDCOM Tag Names section includes properties that determine custom GEDCOM tag names. Custom GEDCOM tags are used to include information in the GEDCOM file that does not have a standard GEDCOM tag. Support for custom tags varies, and some applications require specific values. This section allows you to specify the GEDCOM tag names expected by the GEDCOM reader you intend to use.

The GEDCOM specification mandates that custom GEDCOM tag names begin with an underscore character, "_". TMG to GEDCOM follows that requirement except as described for the Non-Standard Exhibit Tag.

Properties

Force Valid Tag Names

The Force Valid Tag Names property determines whether or not TMG to GEDCOM will enforce valid GEDCOM tag names for TMG events. The default value is checked, and invalid tag names will be replaced with either:

• A FACT tag and a TYPE subrecord set to the TMG event's label.
• An EVEN tag and a TYPE subrecord set to the TMG event's label.

Compliant GEDCOM applications will accept FACT and FACT.TYPE records and create an attribute, and they will accept EVEN and EVEN.TYPE records and create an event. For many GEDCOM readers, that is all that is needed. Some may require users to further specify what the data represents. In either case, it's better and easier to use a FACT or EVEN record than to use a non-standard GEDCOM tag. For that reason, I recommend that you leave Force Valid Tag Names checked.

If the GEDCOM reader application does not process FACT and EVEN records properly, you may be forced to uncheck this option to use non-standard GEDCOM tags. You will have to edit the TMG Tag Types via TMG's Tools > Master tag Type List command and modify the GEDCOM tag assigned to the event. See the GEDCOM Tags help page for information related to this topic.

Citation Reference Tag

The Citation Reference Tag property determines the GEDCOM tag used to add a Citation Reference value to a citation. The default value is "_CREF".

The GEDCOM specification does not include citation reference values. Some programs accommodate citation references using custom GEDCOM tags. If the GEDCOM reader you intend to use accomodates citation references, but expects a different tag name, change this property.

If the Citation Reference Tag property is set to DATA.TEXT, TMG to GEDCOM will write a parent DATA record followed by a child TEXT record:

n DATA
n+1 TEXT value

GEDCOM intends DATA.TEXT for source transcriptions, and TMG's Citation Reference fields to not contain transcriptions, but using a transcription field may be a convenient location if you cannot use some other GEDCOM record.

Formatted Source Tag

The Formatted Source Tag property determines the GEDCOM tag used to add the text created by formatting the Full Footnote template for a TMG source. The default value is "_FULL".

Master Place Tag

The Master Place Tag property determines the GEDCOM tag used to add master place records. The default value is "_PLAC".

The GEDCOM specification does not include master place records. Place information is provided separately for each event. To accommodate data assigned to master place lists, such as exhibits, some programs accommodate custom master place records. If the GEDCOM reader you intend to use accomodates master place records, but expects a different tag name, change this property.

Non-Standard Exhibit Tag

The Non-Standard Exhibit Tag property is used to add multimedia record references under records where the GEDCOM specification does not allow exhibit references. The default value is "OBJE".

The GEDCOM specification does not support exhibit references for NAME tags or for master place records, which are themselves custom records. TMG allows exhibits for both names and places. To include those exhibit references, TMG to GEDCOM writes an exhibit reference using the standard GEDCOM tag intended for that purpose. However, because the tag is not used in a standards-compliant location, those standard tags will be invalid relative to the GEDCOM specification. The GEDCOM reader you intend to use may or may not support exhibits under names and places. If it does support them, it's likely it will expect to see a standard OBJE record. If it expects a different tag name, change this property.

If you leave this value set to the default, a GEDCOM validator may issue an error or warning message. To avoid the message, use a proper custom tag name such as "_OBJE".

Person Role Tag

GEDCOM 7.0 includes support for the ROLE tag as part of the ASSOCIATION_STRUCTURE and that structure can be used to specify a person's role in a shared event. When writing a GEDCOM 7 file, TMG to GEDCOM ignores the Person Role Tag property and uses the standard ROLE tag.

The Person Role Tag property determines the GEDCOM tag used to describe how an additional person was involved in an event. The default value is "_ROLE".

As described above, the GEDCOM specification does not support witnesses and supports only a single principal for all events except "family" events. Some programs that accommodate sharing events also support specifying a "role" to indicate how an additional person was involved in an event. When writing additional principals and witnesses, TMG to GEDCOM will use the Person Role Tag to specify the role label.

The GEDCOM specification includes a ROLE tag that is not used for the same purpose as described above. However, some applications re-use the standard ROLE tag to describe how an additional person was involved in an event. When used with such programs, you may have to set this property to ROLE rather than _ROLE.

Primary Indicator Tag

GEDCOM 7.0 defines explicit rules for determining which record should take rpecedence when there are two or more records with the same tag, and primary/preferred indicators are not necessary. When writing a GEDCOM 7 file, the Primary Indicator Tag property is disabled.

The Primary Indicator Tag property determines the GEDCOM tag used to indicate that a parent record is primary for the current person. The default value is "_PRIM".

As described above, the GEDCOM specification does not support multiple principals except for "family" events. Some programs that accommodate sharing events also support indicating whether the event is primary for the additional principal. When writing additional principals, TMG to GEDCOM will use the Primary Indicator Tag to specify when an event is primary for the current person.

The Primary Indicator Tag is also used to indicate the primary person image exhibit.

Shared Event Tag

GEDCOM 7.0 includes support for the ASSO tag as part of the ASSOCIATION_STRUCTURE and that structure can be used to share events. When writing a GEDCOM 7 file, the Shared Event Tag property is disabled and TMG to GEDCOM uses the standard ASSO tag.

The Shared Event Tag property determines the GEDCOM tag used to attach additional principals and witnesses to an individual event. The default value is "_SHAR".

The GEDCOM specification does not support witnesses and supports only a single principal for all events except "family" events. Family events are limited to marriage, divorce, census, and residence, and the two principals must be married or must be co-parents.

Some GEDCOM readers accommodate additional principals and witnesses by "sharing" individual events. When writing additional principals and witnesses, TMG to GEDCOM will use the Shared Event Tag.

Sort Date Tag

GEDCOM 7.0 includes support for sort dates via the SDATE tag. When writing a GEDCOM 7 file, TMG to GEDCOM ignores the Sort Date Tag and Dates.Include Sort Dates properties.

The Sort Date Tag property determines the GEDCOM tag used to add a sort date value to an individual event. The default value is "_SDATE".

The GEDCOM specification does not include sort date values. Some programs accommodate sort dates using custom GEDCOM tags. If the GEDCOM reader you intend to use accomodates sort dates, but expects a different sort date tag, change this property.

Custom Attribute Tag

When writing a GEDCOM 7 file, TMG to GEDCOM always uses the FACT tag and the Custom Attribute Tag property is disabled.

The Custom Attribute Tag property determines the GEDCOM tag used to identify a custom attribute. The default value is "FACT".

The default value is usually the best choice. Some GEDCOM readers accept GEDCOM 5.5.1 files but fail to recognize the FACT tag, probably because they accept GEDCOM 5.5.1 but actually only implement GEDCOM 5.5 which did not include the FACT tag. For those GEDCOM readers, setting the property to EVEN will usually work.

Custom Event Tag

When writing a GEDCOM 7 file, TMG to GEDCOM always uses the EVEN tag and the Custom Event Tag property is disabled.

The Custom Event Tag property determines the GEDCOM tag used to identify a custom event. The default value is "EVEN".

It's usually best to use the default value for this property.

Father Relationship Tag

The Father Relationship Tag property determines the GEDCOM tag used to describe the relationship of a child to the father in the family. The default value is "_FREL".

Several applications support _FREL. I am not aware of any other common extension records used in place of _FREL.

Mother Relationship Tag

The Mother Relationship Tag property determines the GEDCOM tag used to describe the relationship of a child to the father in the family. The default value is "_MREL".

Several applications support _MREL. I am not aware of any other common extension records used in place of _MREL.