Overview
TMG to GEDCOM supports _FREL and _MREL. They are extension records used to describe relationships between parents and children such as "adopted", "foster", etc. The Parent Labels section contains properties that configure these records.
This page uses _FREL and _MREL to describe the extension records, _FREL for the father relationship and _MREL for the mother relationship. You may modify the actual tags used via the GEDCOM Tag Names.Father Relationship Tag property and the GEDCOM Tag Names.Mother Relationship Tag property.
Properties
Method
- When Method is set to "None", TMG to GEDCOM will not include relationship label records.
- When Method is set to "Custom FAM.CHIL", TMG to GEDCOM will use custom relationship label extension records under the FAM.CHIL record that links a child to one or more parents.
For example, TMG to GEDCOM will write the following records to indicate that person
I3was adopted by parentsI1andI2:0 @F1@ FAM 1 HUSB @I1@ 1 WIFE @I2@ 1 CHIL @I3@ 2 _FREL adopted 2 _MREL adopted
TMG to GEDCOM will write the following records to indicate that person
I3was the step-child of fatherI1and the biological child of motherI2:0 @F1@ FAM 1 HUSB @I1@ 1 WIFE @I2@ 1 CHIL @I3@ 2 _FREL step
In the example above, no
_MRELrecord is required because the default relationship type is biological.
Labels
The Labels list controls the values used in the _FREL and _MREL records. TMG to GEDCOM uses a two-step process to determine the output value. Each entry in the list associates a term with a GEDCOM Label.
- When TMG to GEDCOM reads a TMG project, it converts TMG's relationship tag types to one of several terms to describe common parental relationships.
TMG Relationship Tag Suffix Term -ado adopted -adopted adopted -bio birth -biological birth -nat birth -can candidate -candidate candidate -fst foster -foster foster -god godparent -godparent godparent -oth other -other other -ste step -step step -unk unknown -unknown unknown For any Relationship Tag suffixes NOT in the table above, TMG to GEDCOM uses the lowercase value of the suffix as the term. So, for example,
Father-CustomandMother-Customare assigned the term "custom". - While writing the GEDCOM file, TMG to GEDCOM uses the terms in the Labels list to determine the GEDCOM Labels written to the
_FRELand_MRELrecords.If a term appears in the Labels list, the output value is determined by the term's GEDCOM Label value:
- If the GEDCOM Label value is not empty, TMG to GEDCOM will write an
_FRELor_MRELrecord with the GEDCOM Label value. - If the GEDCOM Label value is empty, TMG to GEDCOM will not write an
_FRELor_MRELrecord.
- If the GEDCOM Label value is not empty, TMG to GEDCOM will write an
The standard Label entries used by TMG to GEDCOM are shown below. You may edit the list, and templates may provide their own values.
| Term | GEDCOM Label | Notes |
|---|---|---|
| adopted | adopted | |
| birth | The default GEDCOM Label value is empty so that TMG to GEDCOM does not write _FREL or _MREL records for birth relationships. The birth relationship is the default relationship for children included in GEDCOM FAM subrecords so no _FREL or _MREL record is necessary. | |
| candidate | The default GEDCOM Label value is empty so that TMG to GEDCOM does not write _FREL or _MREL records for candidate relationships. I suggest you use non-primary relationship tags in TMG for candidate (possible but unproved) parents. | |
| foster | foster | |
| godparent | The default GEDCOM Label value is empty so that TMG to GEDCOM does not write _FREL or _MREL records for godparent relationships. If the target application supports godparent relationships, change the GEDCOM Label to the term it expects. | |
| other | other | |
| step | step | |
| unknown | unknown |