{"id":12480,"date":"2023-01-10T16:51:28","date_gmt":"2023-01-10T16:51:28","guid":{"rendered":"https:\/\/fhug.org.uk\/kb\/?post_type=kb_article&p=12480"},"modified":"2023-01-13T15:16:32","modified_gmt":"2023-01-13T15:16:32","slug":"entering-standard-and-custom-fields-for-facts","status":"publish","type":"kb_article","link":"https:\/\/www.fhug.org.uk\/kb\/kb-article\/entering-standard-and-custom-fields-for-facts\/","title":{"rendered":"Entering Standard and Custom Fields for Facts"},"content":{"rendered":"

When using most Facts, the standard Fields of Age, Date, Place, Address & Note are usually sufficient but sometimes extra fields are desirable. Those standard fields are described in Entering Ages<\/a>, Entering Dates<\/a> & Sort Dates<\/a> and\u00a0Working with Places and Addresses<\/a>.<\/p>\n

However, when using standard Facts or creating custom Facts, there may be a desire to add custom fields to hold particular data.<\/p>\n

Custom fields cannot be added to Facts, and even if they could, when exported in a GEDCOM file they would not be recognised by other genealogy products. This article explains some alternative techniques.<\/p>\n

Basic Techniques<\/h2>\n

When designing a Custom Fact and just one extra field is needed, then instead of an Event try using an Attribute, which offers a value field after its name in the Facts tab, and is referenced by the {value}<\/code> code in its Sentence Template (see standard Attributes such as Occupation and Property). In practice, Events and Attributes are identical apart from the value field. There are no significant known issues when exporting to other products by reclassifying Events as Attributes. See Narrative Report Fact Sentence Templates<\/a> for further details.<\/p>\n

In addition to the Age, Date, Place, Address and Note fields, there are other standard fields available via the All<\/em> tab of the Property Box including:
\nCause (CAUS), Descriptor (TYPE), Email (EMAIL), Fax (FAX), Phone (PHON), Web Site (WWW), Responsible Agency (AGNC) & Religious Affiliation (RELI).
\nThey can be used to hold appropriate information and referenced using {cause}<\/code> or {%FACT.CAUS%}<\/code>, {%FACT.TYPE%}<\/code>, etc.
\nThe Cause field is particularly useful because it automatically appears in Reports as illustrated later.<\/p>\n

The Emigration and Immigration events have additional To and From (_PLAC) fields and users often wonder if those fields can be used in other facts. They cannot, but labelled Note meta-fields can be used instead.<\/p>\n

Labelled Note Meta-fields<\/h2>\n

A popular method of adding custom fields uses labelled meta-fields in the Note box, and is illustrated here using a Baptism Event:<\/p>\n

\"Baptism<\/p>\n

The following Function Codes in the Narrative Report Fact Sentence Templates<\/a> would compose the Sentence text:<\/p>\n

{individual} was baptised {date} {place} {age}< by the {=GetLabelledText(%FACT.NOTE2%,\"Minister: \")}>< for a fee of {=GetLabelledText(%FACT.NOTE2%,\"Charge: \")}><\/code><\/p>\n

Each labelled meta-field can be included or excluded in any combination desired.<\/p>\n

This not only allows the details to be exported satisfactorily in GEDCOM files, but also allows other Note text not required in the Sentence, unlike the {note}<\/code> code that would include it all.<\/p>\n

It is advisable to enclose the meta-fields in Private Notes<\/a> privacy [[<\/strong> brackets ]]<\/strong> so the fields or the brackets can be excluded from or included in Reports by adjusting the Options. Those privacy [[<\/strong> brackets ]]<\/strong> also exclude the fields from Note text produced by the {note}<\/code> code.<\/p>\n

In the Tools > Fact Types<\/a> dialogue, Edit…<\/em> definition, there is a handy feature via the Advanced…<\/em> button that offers an Auto-Create Note<\/em> box that can hold the meta-field Note labels, so they automatically get created whenever that Fact is added. To start each label on a new line use Ctrl+Enter<\/code> to insert a line break.<\/p>\n

Source Note Field<\/h2>\n

Alternatively, the Source Note field %FACT.SOUR2%<\/code> can be used in much the same way but rather less obtrusively. It is a local Note that appears in the yellow Sources For<\/em> pane, but is nothing to do with Source records. The way to add a Source Note is via the All<\/em> tab in an Individual\u2019s Property Box. Right-click the Fact and choose Add Source Note<\/em> in \u0192h<\/span><\/span>7 or Add Source<\/em> and then Add Source Note to this Record<\/em> in earlier \u0192h<\/span><\/span> versions. Add the text to the Source Note and it will appear in the Sources For<\/em> pane. To edit the text use the All<\/em> tab again and expand the Fact to reveal the Source Note<\/em> box.<\/p>\n

When exported to other products there is a small risk that Source Notes may get converted to Source Citation Records.<\/p>\n

Show Fact Fields in the Property Box<\/h2>\n

As explained above, a labelled meta-field is visible in the Note box and in the Sentence box when the Fact is selected.<\/p>\n

Summary Template:<\/em> Flew from {_place}< to {=GetLabelledText(%FACT.NOTE2%,\"To: \")}> {cause}<\/code>
\nOverride Template:<\/em> Flew {date} from {_place}< to {=GetLabelledText(%FACT.NOTE2%,\"To: \")}> {cause}<\/code><\/p>\n

Examples of the Fact Types dialogue, and the Property Box Facts<\/em> tab and All<\/em> tab are illustrated below.<\/p>\n

\"Fact<\/p>\n

\"Facts<\/p>\n

\"All<\/p>\n

Most of the other codes and functions are supported similarly to Sentence Templates. So standard fields such as Cause & Descriptor mentioned above can be displayed using the codes {cause}<\/code> or {%FACT.CAUS%}<\/code>, {%FACT.TYPE%}<\/code>, etc.<\/p>\n

A corollary to this technique is to add a symbol to indicate whether the Fact has a Source Citation or not. To do that start the Summary Template<\/em> with the following expression which tests if a Source link exists:
\n{=TextIf(%FACT.SOUR%,\"\u00a7\",\"\u2013\")}<\/code>
\nwhere \u00a7<\/code> is the Section Sign UTF+00A7 and \u2013<\/code> is the En Dash UTF+2013 which are both the same width so the Fact names are tidily aligned.<\/p>\n

Show Fact Fields in Reports<\/h2>\n

The Sentence Template defines how fields appear in Narrative Reports and others that use Narrative style Sentences. The template can use the codes {note}<\/code> and {%FACT.NOTE2%}<\/code> to include Note text, and the Report Options include Event\/Attr Notes by default, but that option is inhibited fact by fact if the template codes are used to prevent duplicated Note text.<\/p>\n

Most other reports show Notes by default, but if the labelled Note is enclosed in privacy [[<\/strong> brackets ]]<\/strong> it will be excluded unless the Inc. [[private]] Notes<\/em> option is enabled.<\/p>\n

\"Individual<\/p>\n

The labelled Note does not have to be in privacy [[<\/strong> brackets ]]<\/strong> but that may cause other problems when there is further Note text.<\/p>\n

An alternative is to create a 2nd local Note via the All<\/em> tab and adjust the template expressions to support both the 1st and 2nd local Notes.<\/p>\n

Template expression: < to {=GetLabelledText(%FACT.NOTE2%,\"To: \")}>< to {=GetLabelledText(%FACT.NOTE2[2]%,\"To: \")}><\/code><\/p>\n

The only drawback is the 2nd local Note is not shown in the Facts<\/em> tab Note box, although it is shown in the Notes<\/em> tab, and can be shown elsewhere in the Property Box as explained above.<\/p>\n

Summary Conclusions<\/h2>\n

If a Custom Fact needs just one extra field, then instead of an Event try using an Attribute, which offers the value field and {value}<\/code> code.<\/p>\n

Consider using the standard Cause field and {cause}<\/code> code available with every Fact and shown in Reports.<\/p>\n

If other fields are needed then a flexible option is to use labelled Note meta-fields available with every Fact and optionally shown in Reports.<\/p>\n

Finally, there are the standard All<\/em> tab fields Descriptor, Email, Fax, Phone, Web Site, Responsible Agency, Religious Affiliation and Source Note.<\/p>\n","protected":false},"template":"","fh_version":[13,14,15,739],"skill_level":[18,17],"topic":[201],"class_list":["post-12480","kb_article","type-kb_article","status-publish","hentry","fh_version-v4","fh_version-v5","fh_version-v6","fh_version-v7","skill_level-advanced","skill_level-intermediate","topic-facts"],"_links":{"self":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article\/12480","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/kb_article"}],"about":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/types\/kb_article"}],"wp:attachment":[{"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/media?parent=12480"}],"wp:term":[{"taxonomy":"fh_version","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/fh_version?post=12480"},{"taxonomy":"skill_level","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/skill_level?post=12480"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.fhug.org.uk\/kb\/wp-json\/wp\/v2\/topic?post=12480"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Any field can be included in the Facts list at the top of the Facts<\/em> tab so it is visible even when the Fact is not selected.
\nThe custom fact Flew from<\/em> illustrates this feature by adding a labelled Note meta-field To: Glasgow, Scotland<\/em> second Place (see Emigration & Immigration events) and on the All<\/em> tab by adding a Cause: by hot-air balloon<\/em> field.
\nUse Tools > Fact Types<\/a>, select the Fact, click the Edit…<\/em> button, then the Advanced…<\/em> button and enter the required templates.<\/p>\n