Overview
The Sources section includes properties related to TMG sources and citations.
Properties
Include Sources
The Include Sources property determines whether source records are included in the GEDCOM file. The default value is checked.
This value affects both TMG sources and citations.
Include Formatted Source
The Include Formatted Source property determines whether TMG to GEDCOM uses the source's Full Footnote template to create text and includes it in the GEDCOM file. The default value is checked.
By default, the value is written using the GEDCOM tag supplied in the GEDCOM Tag Names.Formatted Source Tag property. Its default is "_FULL
". However, if Use Formatted Source as TITL is checked, the formatted source text replaces the standard GEDCOM "TITL
" tag value.
Example:
0 @S1@ SOUR 1 TITL Bezansons from Nova Scotia 1 ABBR Evans, Bezansons from NS 1 AUTH Evans, Dorothy 1 PUBL Privately Published, Halifax, Nova Scotia, 1986, revised 1991 1 _FULL Evans, Dorothy, Bezansons from Nova Scotia (Halifax, Nova Scotia: Privately Published, 1986, revised 1991). 1 NOTE revised 1991 with assistance from Elaine Hoare and John DeCoste
Use Formatted Source as TITL
The Use Formatted Source as TITL property determines if the formatted text created via the Include Formatted Source property is added to the GEDCOM file via the standard GEDCOM "TITL
" tag. The default value is unchecked.
You might use this property to avoid using the GEDCOM reader's source formatting capabilities. When the GEDCOM reader is a fully-featured program, you should probably leave this option off.
Example:
0 @S1@ SOUR 1 TITL Evans, Dorothy, Bezansons from Nova Scotia (Halifax, Nova Scotia: Privately Published, 1986, revised 1991).
Export Record ID
The Export Record ID property control whether TMG to GEDCOM exports the TMG source ID to a substructure under the SOUR
tag for a source.
TMG to GEDCOM always uses the TMG source ID as the XREF
value on the SOUR
record. This property controls whether the value is also written using an additional GEDCOM record.
The choices are:
- Do not export — The TMG source ID is not exported except as the
XREF
value on theSOUR
record. - Export to RIN — The TMG source ID is exported using the
RIN
tag. - Export to REFN — The TMG source ID is exported using the
REFN
tag. - Export to custom tag — The TMG source ID is exported using the custom tag defined by the Export Record ID Tag property.
The default is "Export to REFN".
Export Record ID Tag
The Export Record ID Tag property defines the GEDCOM tag TMG to GEDCOM uses when it exports the TMG source ID and Export Record ID is set to "Export to custom tag".
Example:
If Export Record ID is set to "REFN", the source number is written as shown in the example below for source number 21:
0 @S21@ SOUR 1 REFN 21
Include Source Parts
The Include Source Parts property determines whether TMG source element values are written to the GEDCOM file using custom records. The default value is unchecked.
When checked, source element values are written as follows, with one set of tags for each source element value:
1 _PART 2 _NAME element-name 2 _VALUE element-value
Example:
1 _PART 2 _NAME Short Title 2 _VALUE 1940 Census
Include Excluded Citations
The Include Excluded Citations property determines whether excluded citations are included. The default is unchecked.
Use Formatted Citation as PAGE
The Use Formatted Citation as PAGE property determines if the formatted version of a citation is added to the GEDCOM file via the standard GEDCOM "PAGE
" tag. The default value is unchecked.
You might use this property to avoid using the GEDCOM reader's citation formatting capabilities. When the GEDCOM reader is a fully-featured program, you should probably leave this option off.
Ancestry APID LocationNote 1
See the Ancestry.com template page for more information about APID values.
The Ancestry APID Location property sets the location TMG to GEDCOM should search for an "APID" identifier used by Ancestry.com. The default value is "None
".
An APID identifier links a citation to an entry in an Ancestry.com database. The APID identifier is only understood by Ancestry.com, so you should leave Ancestry APID Location set to "None" if you are not exporting to an Ancestry.com tree.
If you export a GEDCOM file to an Ancestry.com tree, and you have APID identifiers in some of your citations or sources, set this property to the appropriate value based on where you entered the data. TMG to GEDCOM will search for APID identifiers in the indicated location(s).
APID identifiers have a specific format: two numbers separated by two colons, for example, "1234::123456" where each number may have more or less than the number of digits shown.
TMG to GEDCOM searches the indicated location(s) for text in the expected format and assumes the first match, if any, is an APID identifier. If it finds a match, TMG to GEDCOM adds an _APID
record to the citation. Ancestry.com recognizes that GEDCOM tag and creates a link between the citation and the Ancestry.com database entry indicated by the APID identifier.
The Ancestry APID Location choices are:
- None — Do not search for APID values.
- Citation Detail — Search for an APID value in the Citation Detail field. The value may occur anywhere in the Citation Detail text.
- Citation Memo — Search for an APID value in the Citation Memo field. The value may occur anywhere in the Citation Detail text.
- Citation Reference — Search for an APID value in the Citation Reference field. The entire Citation Reference value must match the APID format.
- Source Element — Search for an APID value in a designated source element field. The entire field must match the APID format. The source element field is identified by the Ancestry APID Source Element property.
- Any location — Search for an APID value in any of the valid locations, Citation Detail, Citation Memo, Citation Reference, and Source Element, in that sequence. TMG to GEDCOM will stop searching as soon as it finds an identifier.
APID Prefix
The usual format for APID values is "1234::123456", two numbers separated by two colons. The identifier may have a prefix, the digit "1
" followed by a comma, i.e., "1,
". It is not clear if that prefix must always be "1,
", or if "2,
", "3,
", etc., are valid.
When TMG to GEDCOM searches for APID identifiers, it will accept a numeric prefix as shown above, and will match both "1234::123456
" and "1,1234::123456
". If your identifiers do not include a prefix, TMG to GEDCOM adds "1,
" to produce the value Ancestry.com expects in the _APID
value. If the value you have entered includes a prefix, TMG to GEDCOM uses your prefix, which may be "1,
", "2,
", etc.
Ancestry APID Source Element
The Ancestry _APID Source Element property indicates the source element that should be inspected to determine if it contains an APID value as explained above for the Ancestry APID Location.
If you elect to store the APID in a source element, you must use the same source element in all sources where you include an APID. A good choice is to use the "Number
" source element for the APID value.
Title Concatenation
When Use Formatted Source as TITL is not checked, TMG to GEDCOM creates the SOUR.TITL
value by concatenating several values. This is not ideal, but ensures that values from the source that don't appear in other subrecords are included somewhere in a standard GEDCOM subrecord.
First, the source title is added to the value without a prefix.
Next, any non-empty source elements are added with a prefix set to the name of the source element. The elements are added in source element group sequence, as shown below.
The table below shows the default source element name for each group, but the actual SOUR.TITL
value will use the source element name from the actual source element used in the source.
Group Number | Name |
---|---|
03 | Subtitle |
05 | Record Type |
07 | Subject |
08 | Compiler |
09 | Editor |
10 | Recipient |
11 | Date |
12 | Second Date |
13 | Location |
14 | Second Location |
17 | Series |
18 | Edition |
19 | Roll |
20 | Volume |
21 | Document |
25 | File Reference |
26 | Number |
27 | Film |
If the actual source element in group 11 is "Publish Date", the value is not concatenated to the TITL value. It is added to the end of the SOUR.PUBL
value after 15 ("Publisher") and 16 ("Publisher Address").
Notes
- Thanks to TMG to GEDCOM beta tester Dave Fuller for inspiring the Ancestry APID feature.