Recording a Marriage/Civil Partnership

Introduction

It is recommended that you use Ancestral Sources to capture Marriage Records and similar ceremonies such as Civil Partnerships. This program makes entering Certificate details much easier and quicker, and helps to organise your Family Historian data in a logical fashion. It is recommended that you have a good understanding of Source Records before using the program.

Capturing Certificate Details

Certificate details for the couple should be captured in a Family Marriage Event with a Source Citation.

Usually a Method 1 or 'source splitters' Source record will be created with a meaningful Title, a transcript in the Text From Source, and an image linked to the Media tab. Alternatively, a Method 2 or 'source lumpers' Source Citation will have one Source record for all Marriage Records, and each Citation will provide specific details.

Automatic Source Citations could be enabled, and associated Individuals such as parents & witnesses, created &/or updated with Residence and Occupation facts, but Ancestral Sources is far more convenient.

Sometimes the Age is given as Full that is not allowed in a GEDCOM Age field, so enter > 21 yrs, which is what it means. Sometimes Minor or Under age is given, and < 21 yrs can be entered.

Recording Ceremony Witnesses

In this context, Witnesses are not just the Certificate Witnesses, but may also be the minister, bridesmaids, best man, etc.

Ancestral Sources has options for recording such roles, including fh V6 Fact Witnesses. Users migrating from products like TMG and Legacy may have used Witnesses for those roles, but the Role names might need adjusting.

From the perspective of the Witness Individual, those roles are not currently included in the Individual Records Window, nor Query or Diagram or Report, except for Narrative Reports.

Witnesses employ a non-standard GEDCOM structure not recognised by most other products, although this is partly mitigated by the Export Gedcom File plugin that creates synthetic facts for the Witness roles.

To list any roles in a marriage, right-click the Marriage Event and choose Witnesses, then use the Go To button and Locate Event for Witness to show their Property Box.

Recording Civil Partnerships

Civil ceremonies such as Civil Partnerships or Civil Unions, often for same sex couples, can be recorded using a number of methods each with pros and cons. Bear in mind that key events such as Marriage have a significant impact in Diagrams, Reports, Queries, and Plugins. They can govern Icons in Diagrams, the structure of Reports, the results in BMD Queries, and the behaviour of BMD Plugins.

A global customisation is to adjust the heading of Marriage in Individual Summary Reports. This can be set in the Report > Options > Format tab under Heading by using Marriage > Edit > Heading Text: Civil Union / {default}. This has the advantage of retaining the suffix such as (2) when there are multiple Family partnerships.

Standard Marriage Event

See Index for related topics

The big advantage of the Marriage Event is its existing support in Diagrams, Reports, Queries, and Plugins not just in fh but all other products. The drawback is it does not differentiate Marriage from Civil Union, but the customisations below will help.

Fact Label

A simple change is to set Tools > Fact Types > Marriage > Edit > Label to Marriage / Civil Union which then appears instead of Marriage in the Property Box Facts tab and non-narrative Reports. You may wish to reduce the Report > Options > Format > Section Label > Edit > Font to Arial Narrow so that long Label fits on one line.

Fact Note or Cause

A basic customisation of the Marriage Event is to add a local Note such as Ceremony: Civil Partnership, which will appear in Diagrams and Reports often by default. It can also be used to customise the Narrative Report Sentence and Property Box Facts tab Templates.
e.g.

  • In Tools > Fact Types > Marriage > Edit > Sentence Template replace the word married with:
    {=CombineText( "entered a ", GetLabelledText( %FACT.NOTE2%, "Ceremony: " ), " with", "married" )}
    so the sentence says for example He entered a Civil Partnership with John SMITH in 1900.
  • In Tools > Fact Types > Marriage > Edit > Advanced > Use Override Template for Facts tab Listings use:
    {=CombineText( "", GetLabelledText( %FACT.NOTE2%, "Ceremony: " ), "", "Marriage" )}
    so the Facts tab says Civil Partnership to John in both the upper and lower pane.

A similar customisation uses the Cause field, with GetLabelledText( %FACT.NOTE2%, "Ceremony: " ) replaced by %FACT.CAUS% in both Templates above. The Cause field is in the All tab under Spouse family > Marriage, and can be customised into the Main tab Shared Details with a Data Reference of FAM.MARR.CAUS.

Fact Type Descriptor

A rarely used feature is the standard fact Descriptor field, which can be applied the same as the Cause field above by replacing CAUS with TYPE in the data references. It is in the All tab under Spouse family > Marriage.
e.g.

  • In Tools > Fact Types > Marriage > Edit > Sentence Template replace the word married with:
    {=CombineText( "entered a ", %FACT.TYPE%, " with", "married" )}
    so the sentence says for example He entered a Civil Partnership with John SMITH in 1900.
  • In Tools > Fact Types > Marriage > Edit > Advanced > Use Override Template for Facts tab Listings use:
    {=CombineText( "", %FACT.TYPE%, "", "Marriage" )}
    so the Facts tab says Civil Partnership to John in both the upper and lower pane.
  • It can be customised into the Main tab Shared Details with a Data Reference of FAM.MARR.TYPE.

The GEDCOM Standard says: "The MARR tag could be subordinated with a TYPE tag and EVENT_DESCRIPTOR value of Common Law. Other possible descriptor values might include Childbirth–unmarried or Tribal Custom for example. The event descriptor should use the same word or phrase and in the same language, when possible, as was used by the recorder of the event. Systems that display data from the GEDCOM form should be able to display the descriptor value in their screen or printed output."

fh does not honour that last requirement to display the Descriptor value of facts in Reports, and it has no {descriptor} sentence Template Code. Those and associated ideas are the subject of Wish List request Ref 559 Fact Descriptor for Civil Union, two Place Travel, Preferred Occupation, etc.

An advantage of the local Note or Cause or Descriptor field is they can take any value to qualify the 'Marriage' such as Civil Union, Civil Partnership, Common Law Marriage, Bigamous Marriage, etc. They are all standard Gedcom fields that should be supported by all products.

Custom Civil Union Event

It is easy to create a custom Family Event named Civil Union, based on the Marriage Event, and used in its place.

This overcomes the need for most customisations above, but Diagrams, Reports, Queries, and Plugins that are customised for the Marriage Event will need similar customisations to accommodate the Civil Union Event. Unless everyone employs the same custom Event Name, those customisations will differ for each user, so shareable versions will be a challenge.

Wish List Ref 558 Civil Partnership family status and associated Civil Partnership event requests a Civil Union Event to be added to the existing Extended Set fact set, to encourage everyone to use the same Event Name. However, that one Event Name must be applicable to all such civil ceremonies.

Family Record Status

The Family Record has a Status field that currently has values such as Divorced and Never Married that primarily govern features in Diagrams and Reports. The fh Help says: "The Status field should normally be left blank. It is used to record non-default status information. … it represents the final or last-known status of the marriage or relationship."

It is a non-standard Gedcom field, so not recognised by other products, although this is partly mitigated by the Export Gedcom File plugin that converts it to a Family Record local labelled Note.

This field could have the extra value of say Civil Union, which will appear in Diagrams and Reports often by default, even without a Marriage Event, but may also be employed in customisations as discussed above with %FACT.TYPE% replaced by Field(GetRecord(%FACT%),'FAM._STAT').

If there is a series of partnership states, such as Civil Union, Separation, and Divorce, only one can be recorded.

Source Citations cannot be applied directly to the Status field, so must be applied to the Family Record instead.

Wish List Ref 558 Civil Partnership family status and associated Civil Partnership event requests a Civil Union value to be added to the Status field. However, that one value must be applicable to all such civil ceremonies.