Relationships

Overview

The Relationships item in the Person Entry list controls the inclusion of relationship information in the person entry. Add a Relationships item to have GedSite calculate the relationship between the subject and the people included in the People list.

Example

The following example shows a Relationships item where George Bezanson has been added as a "relationship target".

The Relationships item above would produce output as follows. Each person who is related to George Bezanson would have an entry that describes the relationship.

Properties

Title

Enter the text that you want to appear as the label for the person references.

If your Title text includes the characters ||, the text before the || will be the title if there is only one entry in the list, and the text after the || will be the title if there is more than one entry in the list.

Enabled

See Enabled in the Common Properties section of the User Items help page.

People

Add one or more people to the People list. Each person in the list is a "relationship target". GedSite will calculate relationships for each person in the site to each of the people in the list.

For example, if you add three people to the list, GedSite will add up to three relationship sentences to each person entry. If someone is related to all three people, that person will have three relationship entries in their person entry.

Include Partner Relationships

If Include Partner Relationships is checked, GedSite will attempt to find a relationship to a target person through a partner or spouse if no relationship is found to the subject.

Not Related Template

If the subject is not related to a target, and the Not Related Template is not empty, GedSite will create the output text from the Not Related Template and include that in the output.

For example, if you set the Not Related Template to "Not related to [P1]", and the subject is not related to relationship target "John Doe", the subject's person entry will include "Not related to John Doe".

The Not Related Template is empty by default. When the Not Related Template is empty, no text is included for subjects who are not related to a target.

Distant Relation Template

GedSite includes relationship templates for people related within 75 generations. If a subject is related to a target via more than 75 generations, GedSite will attempt to use the Distant Relation Template to create the output text.

For example, if you set the Distant Relation Template to "Distant relation of [P1]", and the subject is a 10th cousin, 70 times removed of "John Doe", the subject's person entry will include "Distant relation of John Doe".

The Distant Relation Template is empty by default. When the Distant Relation Template is empty, no text is included for subjects who are not related within 75 generations.

Circular Relationship Error

A circular relationship is when someone is an ancestor of himself or herself. This often happens when ancestors have a common name, and the wrong "John Doe" is specified as the parent of someone and that "John Doe" appears later in the descendency.

When using the Relationship item, a circular relationship error in your data will sometimes cause a failure making the site. GedSite will issue the message, "Maximum stack exceeded (circular relationship)".

To determine the cause of the circular relationship, look in GedSite's application log. Search for the text, "ID stack entries". That message will include several ID numbers that represent the most recent people processed by the relationship calculator. You will usually see a repeating pattern of ID numbers, such as "4, 5, 6, 4, 5, 6, 4, 5, 6", and so on. In that example, the error occurs where the pattern starts to repeat, so either between person #6 and person #4, or between person #4 and person #5. That example uses only three generations, but there may be many more, which makes it harder to see where the pattern begins and ends.

If GedSite can determine the repeating sequence, the log will also include a message that begins, "Circular relationship starting at ID #n", where "n" is the first repeating ID number in the sequence, and the following "ID stack entries" message will show that ID number and the ID numbers that follow it until it repeats.

After reviewing the GedSite application log, open your genealogy project and review the parent-child relationships for the people of interest. Correct the invalid parent-child relationship, and after re-exporting your GEDCOM file, the Relationship error in GedSite should not recur.

Relationship Templates

Note The information in this section is intended for users who want to make advanced customizations. It is not necessary to read or understand this section to use the Relationships feature.

GedSite uses relationship templates to construct text that appears in person entries when the current person is related to one of the people included in the People list. Relationship templates are defined by files in the Languages subfolder. GedSite includes relationship templates in several languages. As of version 1.5.1, those languages are:

You may customize the relationship templates, or provide values for a different language. Take note, however, that the task may require significant editing effort. There are more than six thousand templates in the English relationships file.

Relationship templates are like event sentences. The templates provided with GedSite are of the form:

father of [P1]
mother of [P1]
son of [P1]
daughter of [P1]
 ...

When the template is processed, the P1 variable is set to one of the people from the People list: the person to whom the current person is related. [P1] returns the full name of that person. P2 is set to the current person for whom GedSite is creating a person entry. As a result, you can include the current person's name as follows.

[P2] is the father of [P1]
[P2] is the mother of [P1]
[P2] is the son of [P1]
[P2] is the daughter of [P1]
 ...

You can also use other person variable parameters.

Relationship Templates File Format

Note The information in this section is intended for users who want to make advanced customizations. It is not necessary to read or understand this section to use the Relationships feature.

The format for the entries in the \Languages\culture-code-relations.xml file is as follows:

<r g1="00" g2="01">
   <m>son of [P1]</m>
   <f>daughter of [P1]</f>
   <a>child of [P1]</a>
</r>

g1 is the number of generations to the common ancestor. g2 is the number of generations to the subject. That means the relationship above describes a child of the target. Because g1 is zero, the target is the common ancestor. The m and f elements are for gender-specific descriptions of the relationship. The a element is for unknown gender and can be used as the default when the template does not require gender-specific variations, as in this entry:

<r g1="02" g2="03">
   <a>1st cousin 1 time removed of [P1]</a>
</r>

g1 is 2, which means the target is two generations from the common ancestor. g2 is 3, so the subject is three generations from the common ancestor. If both were two generations from the common ancestor, they'd be first cousins. In English, generation mismatches are called "removes", so the template is "1st cousin 1 time removed of [P1]". As described above, GedSite substitutes the name of the target in place of [P1].