My Way ©MJH 1996-2017; Index

Modified February 13, 2017 1:22 pm

Customizing TMG™
Source Elements My Way ©MJH

Chapter Contents

• Multiple variable names for source elements are synonyms within source element Groups

• Specially handled “people” group variables

• My group name abbreviations

• See also my Source Element Table.

• Source element Variables based on where entered:

Citation Screen, Repository Screen, Source Definition Attachments Tab, Source Definition Supplemental Tab, Title on Source Definition General Tab, User Selected Elements on Source Definition General Tab

and Variable Names indexed alphabetically:

Address, Agency, Annotation, Applied To, Arrival Date, Article Title, Author, Author Address, Author E-Mail, Bible Title, Book Title, Call Number, CD, Census Date, Chapter Title, Church, Citation Detail, Citation Memo, Citation Reference, CM, Comments, Compilation Title, Compile Date, Compiler, Compiler Address, CREF, Date, Date Obtained, Document, Edition, Editor, Employer, Entry Port, Essay Title, Family Info, File Date, File Name, File Number, File Reference, Film, Film Number, First Party, Household, Informant, Informant Address, Interview Date, Interviewer, Journal Title, Jurisdiction, Listserve, Location, Location Detail, M, Manuscript Info, Memo, Name Of Person, Newspaper, Newspaper Title, Number, Original Date, Page, Pages, Period, Photographer, Present Owner, Printout Date, Pseudo Person, Publish Date, Publisher, Publisher Address, Publisher Location, Reader, Recipient, Recipient Address, Record Group, Record Info, Record Number, Record Title, Record Type, Register, Register Title, Repository, Repository Address, Repository Info, Repository Memo, Repository Reference, Roll, RM, Second Date, Second Location, Second Party, Second Person, Section, Series, Ship Name, Short Article Title, Short Bible Title, Short Book Title, Short Chapter Title, Short Compilation Title, Short Essay Title, Short Journal Title, Short Newspaper Title, Short Record Title, Short Register Title, Short Subtitle, Short Title, Speaker, Spouses’ Names, Subject, Subset, Subset Volumes, Subtitle, Testator, Text, Title, Transcriber, Translator, URL, Version, Volume, Volumes

Source Element Groups

Source Elements are names for data entry fields whose contents can be output as part of source documentation. All the Source Element names which are in the same Source Element Group can be considered aliases for that group. For details on which source elements I use and how I use them, see my separate chapter on Source Templates. Only when you are defining a default output Pattern (FullFootnote, ShortFootnote, Bibliography) for a Source Type, or custom modifying one specific source’s Patterns for these output forms, may you add or delete variable names from a list of pre-defined Source Elements for that source. A source Pattern may not use more than one name from a given Source Element Group. The names of Source Elements in each dataset within a Project are supposed to be independent, and TMG will let you create a same-named Source element in one dataset which is in a different group than that same-named element in another dataset. However due to a remaining bug, TMG will be confused in the datasets as to which source group that same-named element belongs. It is safer to ensure that any custom Source Element with a given name is always created in the same Source Element group in any project or dataset. Source element names cannot be used until they are predefined ( Tools>Source Elements menu) as a member of one of the 31 fixed Source Element Groups. Once it is in use by any source Pattern, the variable name cannot be deleted or changed to different group.

Source Element names initially could be created to be as long as 30 characters but, although some standard names are longer than 20, these names longer than 20 now can cause problems. 1 Longer names will be truncated in display, but the truncated value will not work in the source definition window. You must use the full, actual name to its total number of characters. Although the list of Source Elements presents the variable names with only an initial capital, any variable name entered in a Template Pattern will be converted to all capitals by TMG. Thus most documentation uses all capitals in the Templates for Source Element variable names.

Each Source element used in a Full Footnote, Short Footnote, or Bibliography (FF, SF, B) for a Template or Pattern automatically becomes a data entry field on the Source Definition Screen for any Source using that Template or for that one specific Pattern. Though I don’t recommend it, you may add source elements for a single source or for an entire source type by clicking a blank element button on the General tab of the Source Definition. Doing this does have the advantage of limiting your choices to only those Source Element Groups not currently in use in that source or source type. However, if it is never used in any Template or Pattern, any information entered for that unused element will never print. Instead, I choose to use the automatic method of causing an element to appear on the Source Definition, even when it is for a single source, by first using the element variable name in the Template or Pattern and then returning to the General tab where the element name will now appear. That helps me remember to define it for output before I ever enter any data into an element field.

Note that choosing to use a particular source element as part of the output for a source type (e.g. PAGES , or FILM NUMBER ) has the consequence that differing values for the contents of that source element can only be entered by defining separate sources in the Master Source List (e.g. a separate source for each different value of PAGES or FILM NUMBER ). I prefer to “lump” into physical entities rather than “split” my TMG sources to parts of an entity. Therefore I tend to use fewer unique source definitions, and put the identification of the part of a source, such as the pages, in the individual Citation Detail and Citation Memo. However, this might produce a report with a significant number of “ibid” citations which could be reduced by subdivided sources.

These Source Element variable names are uniquely assigned to one of the 31 fixed Source Element Groups. In any one Template or Pattern, you may not use more than one variable name from the same Source Group. Variable names defined in the Source Element Groups are listed below according to the five categories of where their data entry field appears.

1) Those elements whose data entry fields appear on the citation screen which cites this source — citation detail and citation memo (either of which can be split into 9 segments like most memos), and citation reference. None of these elements may be included in a Bibliography pattern.

2) Those elements associated with (only) the primary repository that is linked to this source on the Source Definition Attachments Tab. The Repository Reference is also entered on that screen. The remaining repository data fields are entered on the definition of that repository — Repository Name-Other, Info which is the combination of address fields, and a Memo (which can be split into 9 segments like most memos).

3) The source Comments (also called the source Memo) group, whose data entry field appears on the Supplemental tab of the Source Definition (and can be split into 9 segments like most memos).

4) The source Title group, which is a data entry field that always appears on the General tab of the Source Definition screen.

5) The other 22 source element groups, whose data entry field appears in the lower part of the General tab of the Source Definition screen only if a variable name from that group is defined in an output Pattern for that source.

You can use one variable name from any number of all these groups in a source Pattern, with just one limitation — there is only display/entry room for 14 2 data entry fields for the 22 possible element groups in category 5 — as can be seen on the Source Definition General tab.

“People” Source Element Groups

Five of the Source Element Groups (Author, Compiler, Editor, Subject, Second Person 3 ) are designed for entering names of people. Entering an integer as the value in any one of these elements implies a person ID number from this dataset and will be expanded to that person’s Primary name. 4 You can only enter one such ID number in a people element. 5 If a people source element begins with an integer, anything following that integer (e.g. a colon to try to refer to a different dataset or semicolon to designate multiple people) is stripped and ignored, and the link is set to the one person whose ID number is the initial integer. (If you wish to enter data that begins with an integer in one of these Elements, precede it with an empty sensitive data field, e.g "{}101st Infantry" ). If you do not enter an ID integer 6 , then enter the full name of the person or names of multiple persons as described below separated by semicolons.

These five “people” element groups “should” be entered with multiple names separated by semicolons with the two parts of each person’s name separated by a comma (e.g. “surname, given; surname2, given2; …”). Any comma in a people source element will trigger automatic selection/ordering of what parts of each name will print in what order for the three output types. The absence of any comma will prevent selection/ordering. As examples, TMG will select and order the parts of the names as: “Given Surname and Given2 Surname2” or “Given Surname, Given2 Surname2 and Given3 Surname3” for full footnotes, “Surname and Surname2” or “Surname, Surname2 and Surname3” for short footnotes, “Surname, Given and Given2 Surname2” or “Surname, Given, Given2 Surname2 and Given3 Surname3” for the bibliography.

Warning: Entering a person with a middle initial which has a trailing period in a “people” element may cause duplicate punctuation in the Bibliography. Whether entered in the element as “Surname, Given M.” or referenced by ID number, the middle initial trailing period will always print as text in the Bibliography. If the Bibliography output template includes punctuation (e.g. a period) following the “people” element, both the middle initial trailing period and the template punctuation will output. Cleanup in the word processor may be needed. For this reason I choose not to enter trailing periods for middle initials.

Use of the ID number will cause automatic name part selection/ordering of the referenced primary name. If the name needs to be entered as sensitive data you must use a double set of braces for each name, with the break immediately before the comma, and a space after the comma, so the automated name part selection/ordering will work whenever you print sensitive data. 7 For example, {Hannah}{, Michael Jon} will give “unknown” when sensitive data is not printed, and select the appropriate parts in the appropriate order when such data is printed. 8 If you wish to avoid this automated selection/ordering to get exactly what you want, you could enter the name as text in the unique (not global) output Pattern of that single source. Alternatively you could double enter the name in two different source elements. Although Subject is a “people” group, some have suggested using the expected comma structure for name entries in one of the other “people” group elements, e.g. Author, but also enter the name again in Subject without commas. You can then adjust the templates for that Source Type to use whichever of these two elements will produce a closer match to a specific desired output style for names.

Group Name Abbreviations

In my list of source templates I identify the source groups that are in use by the source elements within that template using the following abbreviations. The abbreviation is also noted in parentheses at the head of the description of each source group below.

A

Author

L2

Second Location

RT

Record Type

C

Comments

Pb

Publisher

Sj

Subject

Cp

Compiler

P2

Second Person

SbT

Subtitle

Ed

Editor

Pg

Pages

ShSb

Short Subtitle

En

Edition

PL

Publisher Location

ShT

Short Title

FN

Film Number

RA

Repository Address

Sr

Series

FR

File Reference

RM

Repository Memo

T

Title

D

Date

RN

Record Number

Vm

Volumes

D2

Second Date

Rp

Repository

Vr

Version

L

Location

RR

Repository Reference

 

 

My Source Element Variable Names by Group

In the lists below, ‘*’ indicates my personal custom variable name additions. An ‘#’ indicates this is a people source element, as described above. My notes show that if you import a GEDCOM file that has source records, the GEDCOM defined subfields of [TITL] , [PUBL] , [PAGE] , and [TEXT] are automatically imported from these source records and prefill the four source element groups Title, Publisher, Citation Detail, and Citation Memo described below. For a one-page list of my elements by group, see my Source Element Table. See also my discussion on the Book (Authored) source template.

How a Source Element variable name is displayed on the source definition data entry screen indicates its usage in the output Pattern sentences. A name enclosed in <conditional brackets> means its only uses are <conditional> . 9 An Initial uppercase letter means the element is Required in at least one Pattern sentence and therefore “something” will print for this element. If no value is supplied for a required element, the Pattern will output the word “unknown” followed by the all lowercase name of the variable (e.g. “unknown bible title”). Beyond aiding in data entry by having a meaningful data field label, this automatic output for an empty required field is another reason to define a custom variable name. If the element name is all lowercase letters, this element is not defined or used in any Pattern or output sentence for this defined source or source type so anything you enter is not defined to be output anywhere.

Citation Screen

Creating new custom names in these groups will not change the label of the text entry fields, but it will change the text for “unknown”. A custom name does not provide access to either the split citation detail or split memo features. While Citation Details and Citation Memos both can be split, I do not commonly use this feature in my Source Templates. Note that for both there should always be an appropriate 10 place holder character for any empty split part, otherwise the wrong split text will be output for a later split variable. The wrong split text being output seems especially to affect CD and CM. There is further discussion concerning the specific place holder characters as part of the discussion of empty split memo parts. If those empty split parts lack their place holder character they can demonstrate various different errors.

Citation Detail

[PAGE] 11 , CD, CD1, CD2, CD3, CD4, CD5, CD6, CD7, CD8, CD9

Any empty split Citation Detail part prior to the last entered should contain the appropriate placeholder character. If this element or split part is unconditional but no text is entered, TMG will output “unknown detail” regardless of the name of the element. However the Citation Preview from the Citation screen will simply show the element name in brackets, e.g. [CD] which indicates it is unconditional.

Citation Memo

[TEXT] 12 , CM, CM1, CM2, CM3, CM4, CM5, CM6, CM7, CM8, CM9

Any empty split Citation Memo part prior to the last entered should contain the placeholder character. If this element or split part is unconditional but no text is entered, TMG will output “unknown comment” regardless of the name of the element. However the Citation Preview from the Citation screen will simply show the element name in brackets, e.g. [CM] which indicates it is unconditional.

Citation Reference

CREF 13

If this element is unconditional but no text is entered, TMG will output “unknown referrence” regardless of the name of the element. However the Citation Preview from the Citation screen will simply show the element name in brackets, e.g. [CREF] which indicates it is unconditional.

Repository Screen (Linked Primary Repository)

Creating new custom names in these groups will not change the label of the text entry fields, but it will change the text for “unknown”. A custom name does not provide access to the split memo feature.

Repository (Rp) [entered in Name-Other]

REPOSITORY

Repository Info (RA) [entered using the multiple Place fields]

Although it has multiple Place fields and can be assigned a Place Style, this style affects only the field labels. The Place Style output template for that Place entry is ignored and the entire location is always output as a single value in the order: [L1], [L2], [L3], [L4], , [L10]. Separate Source Element variables do not exist for the separate Repository Address Place fields, nor is there a way to define them.

REPOSITORY ADDRESS, REPOSITORY INFO

Repository Memo (RM)

REPOSITORY MEMO, REPOSITORY MEMO1, REPOSITORY MEMO2, REPOSITORY MEMO3, REPOSITORY MEMO4, REPOSITORY MEMO5, REPOSITORY MEMO6, REPOSITORY MEMO7, REPOSITORY MEMO8, REPOSITORY MEMO9, RM, RM1, RM2, RM3, RM4, RM5, RM5, RM7, RM8, RM9

Any empty split Repository Memo part prior to the last entered should contain the appropriate placeholder character. If a split memo part is unconditional but no text is entered, the appropriate “unknown” text will output using the name of the element.

Source Definition Attachments Tab

Creating new custom names in this group will not change the label of the text entry field, but it will change the text for “unknown”. Because this field is restricted to 25 characters I typically must abbreviate this entry. For example, I do not put commas in FHL film numbers, and since I include the [REPOSITORY] I do not put “FHL” in front of the Repository Reference film number. I created [REPO CALL NUMBER] for the purposes of its “unknown” text, but don’t currently use it.

Repository Reference (RR)

REPOSITORY REFERENCE, *REPO CALL NUMBER

Source Definition Supplemental Tab

Some special characters entered in this field can cause problems when output by Second Site. See the discussion of HTML Code Characters. Creating new custom names in this group both changes the label of the text entry field and the text for “unknown”. A custom name does not provide access to the split memo feature. For example, my defining [ANNOTATION] in this group does not automatically define [ANNOTATION1] , etc. Manually defining custom names [ANNOTATION1] , etc. in addition to [ANNOTATION] also does not work, as these all simply become new unique aliases for [COMMENTS] , which if the data is split will only output the first part. 14 Although [M1] etc. are legitimate, I prefer to use [MEMO1] etc. in my templates to avoid my confusion with the identically named Tag memo variables.

Comments (C)

COMMENTS, MEMO, MEMO1, MEMO2, MEMO3, MEMO4, MEMO5, MEMO6, MEMO7, MEMO8, MEMO9, M, M1, M2, M3, M4, M5, M6, M7, M8, M9, *ANNOTATION

Any empty split Memo part prior to the last entered should contain the appropriate placeholder character. If this element is unconditional but no text is entered, TMG will output “unknown memo” regardless of the name of the element or split part.

Title on Source Definition General Tab

Creating new custom names in this group both changes the label of the text entry field and the text for “unknown”. I created [NEWSPAPER] so that it can be non-optional and produce “unknown newspaper”.

Title (T)

[TITL] 15 , BIBLE TITLE, BOOK TITLE, COMPILATION TITLE, JOURNAL TITLE, *NEWSPAPER, NEWSPAPER TITLE, TITLE

User Selected Elements on Source Definition General Tab

While there are 23 Source Element Groups in this category, only 14 fields are available for data entry on the General tab of the Source Definition screen for input for any source template so all 23 cannot be used. The order that the Source Element Groups will appear on the General tab of the Source Definition screen (regardless of whether an alternative variable name is used from within that group) is the order that follows, e.g. the first group in this list that is used will appear first, the second one used second, etc. Creating new custom names in these groups both changes the label of the text entry field and the text for “unknown”.

Short Title (ShT)

SHORT BIBLE TITLE, SHORT BOOK TITLE, SHORT COMPILATION TITLE 16 , SHORT JOURNAL TITLE, SHORT NEWSPAPER TITLE 17 , SHORT TITLE

If this element is unconditional but no text is entered, you may not get the “unknown” text. If there is text entered in a Title element, TMG will automatically construct a Short Title by possibly shortening/truncating the text of the Title and deleting short words like “a” and “the”. If there is also no text in the Title, then both the Title and Short Title will output their appropriate “unknown” text.

Subtitle (SbT)

ARTICLE TITLE, CHAPTER TITLE, ESSAY TITLE, RECORD TITLE, REGISTER TITLE, SUBTITLE

Short Subtitle (ShSb)

SHORT ARTICLE TITLE, SHORT CHAPTER TITLE, SHORT ESSAY TITLE, SHORT RECORD TITLE, SHORT REGISTER TITLE, SHORT SUBTITLE

If this element is unconditional but no text is entered, you may not get the “unknown” text. If there is text entered in a Subtitle element nothing will be output, which may cause strange output. A shortened Subtitle will not be constructed. If there is also no text in the Subtitle, then both the Subtitle and Short Subtitle will output their appropriate “unknown” text.

Record Type (RT)

I created [SECTION] for use in the Newspaper source type.

RECORD TYPE, *SECTION

Author (A) [people]

I created [EMPLOYER] for use in the Employment source type.

#, AGENCY, AUTHOR, *EMPLOYER, FIRST PARTY, INFORMANT, SPEAKER

Subject (Sj) [people]

#, FAMILY INFO, HOUSEHOLD, NAME OF PERSON, SPOUSES’ NAMES, SUBJECT, TESTATOR

Compiler (Cp) [people]

I created [TRANSCRIBER] for use in the Interview source type since [INTERVIEWER] was already in the Second Person element group.

#, COMPILER, *TRANSCRIBER

Editor (Ed) [people]

#, EDITOR

Second Person (P2) [people]

#, APPLIED TO, INTERVIEWER, PHOTOGRAPHER, PRESENT OWNER, READER, RECIPIENT, SECOND PARTY, SECOND PERSON, SHIP NAME, TRANSLATOR

Date (D)

COMPILE DATE, DATE, FILE DATE, INTERVIEW DATE, PRINTOUT DATE, PUBLISH DATE

If this element is unconditional but no text is entered, TMG will output “n.d.” with no spaces regardless of the name of the element.

Second Date (D2)

[ARRIVAL DATE] I use in the Passenger List source type. I created [CENSUS DATE] for use in my generic Census source type. [DATE OBTAINED] I use in various certificate source types to document obtaining the data, whether getting the actual certificate, or viewing the data in the source.

*ARRIVAL DATE, *CENSUS DATE, *DATE OBTAINED, ORIGINAL DATE, PERIOD, SECOND DATE

If this element is unconditional but no text is entered, contrary to the Date element the appropriate “unknown” text will output using the name of the element.

Location (L)

ADDRESS, AUTHOR ADDRESS, COMPILER ADDRESS, INFORMANT ADDRESS, JURISDICTION, LISTSERVE, LOCATION

Second Location (L2)

I created [CHURCH] for various church record source types. [LOCATION DETAIL] is used when I want the detail to come before [LOCATION] in the FF and possibly not in the SS, but want it after in the B. [ENTRY PORT] was created for a similar reason to [LOCATION DETAIL] for use in my Passenger List source type. I created the [INTERVIEW LOCATION] element name as a memory aid for use in my Interview source type. I only use the standard element [URL] in Bibliography templates. If it is a “split” source, then it is the specific URL for that source and that URL is not duplicated in either the footnotes or Citation Detail. For “lumped” sources, it is the URL of the main page of the site, and will not be duplicated in the footnotes, but the complete specific URL will be in the Citation Detail using sentence formatting codes.

AUTHOR E-MAIL, *CHURCH, *ENTRY PORT, *INTERVIEW LOCATION, *LOCATION DETAIL, RECIPIENT ADDRESS, SECOND LOCATION, URL

Publisher (Pb) [not people, no #]

[PUBL] 18 , PUBLISHER

If this element is unconditional but no text is entered, TMG will output “n.pub.” with no spaces regardless of the name of the element.

Publisher Location (PL)

PUBLISHER ADDRESS, PUBLISHER LOCATION

If this element is unconditional but no text is entered, TMG will output “n.p.” with no spaces regardless of the name of the element.

Series (Sr)

SERIES, SUBSET

Edition (En)

EDITION, RECORD GROUP, SUBSET VOLUMES

Version (Vr)

ROLL, VERSION

Volumes (Vm)

VOLUME, VOLUMES

Pages (Pg)

Since I am a “lumper” and seldom use this element group, I created the element [PSEUDO PERSON] to aid in linking Source Pseudo People to a Source Definition.

DOCUMENT, PAGE, PAGES, *PSEUDO PERSON

File Reference (FR)

FILE NAME, FILE REFERENCE

Record Number (RN)

CALL NUMBER, FILE NUMBER, MANUSCRIPT INFO, NUMBER, RECORD INFO, RECORD NUMBER, REGISTER

Film Number (FN)

FILM NUMBER, FILM

 


1. When you try to edit an existing Source Element, the entry for the new changed name now may not be more than 20 characters. If an element was created with more than 20 characters in an earlier version and you wish to change its name, its name in the Edit Source Element screen will be blank, and no name change of any length will be recognized. You must first remove this old longer-named element from any source templates so that you can delete it and then add it again with a new name of not more than 20 characters. I think a better method is to leave it alone and create a new element in the same group with the shorter name. Now change all source templates to reference that new element. Then if you desire, the old longer name will no longer be being used so it can be deleted.

2. Even if you define every possible source element in an output pattern, the General tab will only show Title plus the first 14 from category 5: Short Title, Subtitle, Short Subtitle, Record Type, Author, Subject, Compiler, Editor, Second Person, Date, Second Date, Location, Second Location, Publisher. Even if the elements are entered last to first but you use all possible element groups, you will get these first 14. However, I believe this maximum 14 element groups to be defined on the General tab (in order) that are meaningful (to me) and give the greatest flexibility for templates (and are all defined by my Miscellaneous custom source type) are Title plus: Subtitle, Record Type, Author, Subject, Second Person, Date, Second Date, Location, Second Location, Publisher, Publisher Address, Series, Edition, Volumes.

3. Previous versions of TMG Help did not list all five of these “people” groups, but as of Version 8 all five are now identified in “Source Definition: General”. Note that “Publisher” is not a “people” group and thus does not allow an ID number although it is often a person’s name.

4. If you enter an ID number, the Primary name (Title Given Surname Suffix), is output in both Full and Short Footnotes. While only the Surname “should” output in Short Footnotes to match what would occur if the name was entered as text, a remaining bug will cause the full Primary name to output. The Bibliography will output Surname first followed by the rest of the name after a comma (Surname, Title Given Suffix). The name will be displayed using all four of the fields described, regardless of the Name Style assigned to the Name tag, or any Preferences setting I have tried.

Using an ID number allows the filter conditions in a List of Sources report to search either based on the number (e.g. using the filter field “Author ID#”) or on a specific part of the Primary name (e.g. using the filter “Author-ID... // Given Name”). In other words, even if only the ID# is entered the Given Name filter will work.

5. For display purposes, the ID number will be replaced in the Source Definition screen with the Primary name of the individual followed by their ID number in parentheses, but name parts will both display and output as described in the previous footnote.

6. If you do not enter an ID number, for filter conditions in a List of Sources report on any of these five “people” groups you must use the appropriate “-Other” filter field (e.g. Author-Other).

7. Need to test this sensitive construct with the latest version of SecondSite as it works in TMG but not in an earlier version of SecondSite.

8. If a name is sensitive within a set of names, then be sure to include the appropriate semi-colon and comma in the separate sensitive parts for the surname and given names, e.g. “Surone, Giveone{; Sursens}{, Givesens}; Surname3, Given3”. With sensitive off it will output as only two names in the three forms appropriate for the three output templates, but with “Show sensitive data” on in the Miscellaneous Report Options, it will output as three names in the three forms appropriate for the three output templates.

9. The TMG HELP explicitly states that “Conditional brackets and variables cannot be nested” and implies that only one variable may be included within a single set of conditional brackets. However, just like sentence variables, it can be shown as an undocumented feature in the final Version that if multiple source element variables are included within a single set of conditional brackets, the text within the brackets is only output if all variables within those brackets have value. And multiple instantiations of the same variable cause that entered text to be output multiple times.

10. TMG HELP specifies that a space as a placeholder for an empty split part should always be used. But this character is stripped if entered in the first split part.

11. This portion of a GEDCOM Source record is preloaded by automated import into this group.

12. This portion of a GEDCOM Source record is preloaded by automated import into this group.

13. An alternate spelling of this element “ CITREF ” existed historically in a very early version of TMG and exists as a custom element in some sample datasets, but that spelling is now obsolete, is not referenced in TMG Help nor in the default list of elements. If you wish to use this spelling you must create it as a custom element name.

14. However, using both [ANNOTATION1] and [ANNOTATION2] in the same output Pattern does not give an error for using two elements from the same group, but it just duplicates the first split part on output.

15. This portion of a GEDCOM Source record is preloaded by automated import into this group.

16. This standard element name is longer than the maximum 20 characters mentioned above. In most lists it will show truncated as simply “Short Compilation” or “Short Compilation Ti” but the entire element name must be entered as the variable name.

17. This standard element name is longer than the maximum 20 characters mentioned above. In most lists it will show truncated as simply “Short Newspaper” or “Short Newspaper Titl” but the entire element name must be entered as the variable name.

18. This portion of a GEDCOM Source record is preloaded by automated import into this group.


Disclaimer

I am not affiliated in any way with TMG™, its company Wholly Genes, Inc., or its primary author Bob Velke. I am simply a satisfied user of this software package and have constructed these documents to aid me in its use.

If others find these documents useful, so much the better. I do not warrant in any way that they are accurate or useful, and any use of them is at the user’s own risk.

These documents were composed with Adobe® Framemaker® using its hyperlink and HTML conversion features.

©MJH Consulting, 1996-2017. All rights reserved.