Michael J. Hannah
, Los Ranchos, NM.
Modified February 24, 2018 9:50 am
Michael J. Hannah , Los Ranchos, NM.
Ancestral File, Baptismal Certificate, Baptismal Register, Birth Certificate, Birth Church Register, Birth Register, Burial Cemetery Register, Burial Certificate, Burial Church Register, Census, City (or County) Directory, Correspondence, Death Certificate, Death Church Register, Death Register, Electronic Database, Employment Record, Family Group Sheet, Government Certificate, Government Register, International Genealogical Index, Interview, LDS Patron Sheets, LDS Pedigree Resource, Manuscript, Marriage Certificate, Marriage Church Register, Marriage Register, Miscellaneous, Obituary/Newspaper Article, Obituary/Newspaper Lumped, Passenger List, Photograph, Published work, Published work-combined, Records (MultiVolume), School Record, SSDI
• Other miscellaneous ideas about possible source templates.
A Source Type defines master Source Templates which are used as the basis for defining individual Sources which can have multiple Source Citations. Source Types, Source Elements, and Sources are unique to a given data set within a TMG project. The Source Templates of a specific Source define output Patterns (FullFootnote, ShortFootnote, Bibliography) for TMG reports to use to arrange the information you provide in the Source Element data entry fields for that Source to construct these three output forms. The final output structure of source citations for publication can be dictated by the editor of a publication, and there are numerous commonly accepted structures, often differing greatly, that are considered standard in specific topic areas and professional fields. Commonly referenced guides to citation output structure for genealogy publications are by Elizabeth Shown Mills 1 , and the default customizable source templates within TMG were based and interpreted by Wholly Genes somewhat 2 on her publications. While influenced by their comments and examples, my templates do not attempt to match her publications. My main goals are to construct citations that make it clear what I saw and make it clear how someone else might find that same information again. I choose to follow the general guidelines for the Humanities Style in the Chicago Manual of Style 3 which Ms. Mills states is also the “root” for her examples 4 . A recognized guide for citing government documents, such as census records, is often referred to as the Garner citation style 5 . And the U.S. National Archives and Records Administration (NARA) has developed its own citation style, which both I and Ms. Mills 6 choose to simplify for U.S. census citations. 7
You may customize source templates in TMG only if you have chosen to use Custom source categories in
Preferences > Current Project Options > Other
. You may create a new custom Source Type or change an existing Source Type’s output Templates (which affects all Sources using that Source Type) by the
Tools>SourceTypes
menu. When you create a new Source Type you may specify which Standard Source Type this new type “is most similar to”. Once a Source Type is created the “is most similar to” cannot be changed. Copying an existing Source Type will create an identical new type with a number appended to the name. Although I usually don’t recommend it, an output Pattern for a
single
source may also be modified from the Source Type default in the Output Forms tab of that one source’s Source Definition. To recover the default template, simply delete all of the custom template Pattern.
The uniqueness (“lumping” or “splitting”) of a source in the Master Source List is dependent upon the source template and its defined source elements. Different values for a defined element require separate source entries in the MSL. Many of these source templates are my own (with acknowledgments to the original TMG templates based on Mills’ publications and to TMG user Lee Hoffman 8 ) custom templates, with more to come as I encounter more source types in my research. Their designs are primarily based on which TMG fields I prefer to store/enter data, and especially to balance the number of separate documented sources versus separate dataset sources and their need for different template structures.
The style of these source templates also reflect my personal preference to range from the least to the most detail, from Short Footnote through Full Footnote to Bibliography. My principle is for the Short Footnote to be just barely enough to refer back to the Full Footnote (or maybe find the Bibliographic entry), and the Full Footnote to be just enough to clearly identify the source and find its more complete Bibliographic (Source List) annotated entry. My personal style intentionally differs from the principal cited by Ms. Mills
9
, but since I almost always include a Bibliography with any TMG report this focus on the bibliograpy entry is recognized by the Chicago Manual of Style
10
. This structure also works for me in Second Site, as I use the Short Footnote for the citation on the person’s web page and the Bibliographic format for the entry on the hyperlinked master source page. As examples of this heirarchy of detail, I usually put the
[PUBLISHER]
information and the
[REPOSITORY]
in the Bibliographic entry and not in the Full Footnote, and always reserve the
[REPOSITORY ADDRESS]
for the Bibliography, as well as generally include annotations in
[COMMENTS]
to the Bibliographic entry.
The source template marked “primary” is used by TMG as the default template when one is not otherwise specified, such as GEDCOM Import. By default this is “Book (Authored)”. See also the discussion about merging sources in the Import/Export chapter.
To identify the custom source element names I have added to various source element groups, see my list of Source Elements. As for
which
elements I use, most of my templates take into consideration that there are some source elements
always
present for input in TMG whether or not the element appears in a default citation template, so I choose to
always
include such elements in my templates. For example, I always make use of the
[TITLE]
element in the templates as it is always provided for input for every source whether specified in the templates or not, and I often optionally define a
[SHORT TITLE]
for use in the SF. In addition to
[CD]
, I always include
[CM]
as a separate sentence as the last optional element in both FF and SS as it is also always available for input as part of the citation. However, I don’t include
[CREF]
in the templates as I (sometimes) use that for identifying where in
my
filing system I stored my personal notes, or photocopy, or original source document that produced this citation. As this is of little use to others and I can always look it up myself directly in TMG, I do not print it. In the same vein I always include
[REPOSITORY REFERENCE]
as optional elements in the bibliography template as again these are always available for input. Unlike
[CREF]
, I use the
[REPOSITORY REFERENCE]
for the data for where the source is found in
that
repository and this
would
help others find the reference in that repository, so if I know it I include it. When appropriate I try to provide some annotations to my bibliography entries
11
to describe my impression of the work, its condition and/or usefulness to my research. Thus I always have
[ANNOTATION]
as an optional element since its field is always available for input on the Supplemental tab. I always enter
[ANNOTATION]
(my custom alias for
[COMMENTS]
) as complete separate sentences but with no ending period and put this element at the end of only the bibliography template. If you choose to include
[COMMENTS]
in FF as has been done in some template examples I have seen, remember it will only print once per report (the first time it is cited or as the unique footnote). Finally, if I use it at all I prefer
Cited as
to describe the
[SHORT TITLE]
in the Full Footnote rather than
Hereinafter cited as
simply as less stilted English (to my ear).
Remember that all names in “people” source element groups should be entered “surname, given”, with multiple names in the same field each entered in that structure separated by semicolons, so that TMG can automatically select and order the parts of the names. Because of this automated behavior with these elements, I try never to use a source element from a “people” group (Author, Compiler, Editor, Second Person, Subject) as a field that might otherwise contain a comma or semicolon. For usage, and ways to avoid the automatic selection/ordering, see my separate discussion of “people” source element groups.
My source templates often leave out some detail fields others choose to include in a template, such as page or item number, etc. I tend to put this kind of information in the Citation Detail field. Using the terms attributed to Jim Byram 12 , although I start with the source categories based on the Mills publications I tend to be a “lumper” 13 and minimize categories and individual sources. In this way, different citations can reuse the same Source again without either having to re-enter (or copy) an entire Source or have it listed as a separate Source in the Master Source List just because a page number or other detail has changed. However, lumping can produce reports with a significant string of “ibid”s that would have been lessened by splitting the source into multiple source records. Split source definition field names remind you what details to put where, and automates the rearrangement of names, where lumped sources with differing Citation Details need discipline to remember what should be in the (various split fields of the) CD. Note that Full and Short Footnotes can be made to look identical in reports (possibly using split citation details) whether you “lump” or “split”. Further TMG will combine entries 14 from different sources in to a single bibliographic entry if the different Bibliography templates are made to output the identical text in TMG reports by leaving out their differing “split” information. This combining of Bibliography entries will not occur in Second Site Source page entries. 15 Thus the difference between the two approaches in TMG reports, if the templates are constructed carefully, will only be reflected in the quantity and uniqueness of the sources in the Master Source List (which normally only you will see).
If you are a “splitter”, especially if you include detail fields such as page or item number in your Bibliography templates, there may be a limit to how far TMG will sort among Bibliographic entries. 16
Listed below are the custom Source Templates currently used by me, and roughly arranged according to an approximation of TMG’s Mills citation category names. Each category shows the template for Full Footnote (
FF
), Short Footnote (
SF
), and Bibliography (
B
) with the appropriate Source Elements. The source element groups in use are noted by their abbreviations. My initials (
MH
) in front of the
category name
indicates that this category of source is sufficiently in use in one or more of my projects that I feel comfortable with it, though any of my custom templates are subject to change. Others that are modified but are not prefixed with my initials are ideas for my expected future use and are likely to change as I actually use them. Two asterisks (
**
) in front of the category name indicates that this is a custom category
17
not included in the sample categories provided by Wholly Genes. The
AB=
CODE
18
following the
template name
lists my source type abbreviation code(s) (which link to that abbreviation’s details) for such sources that might use this category. An asterisk (
*
) in front of the
template type
(
FF
,
SF
or
B
) in a category indicates that this template differs from the default provided by Wholly Genes. However, the
global change
of
Cited as
instead of the default
Hereinafter cited as
in nearly every Full Footnote
did not warrant an asterisk. Following some of the templates, there are examples of how that template might appear when printed in a report. These are marked as
EX
to denote examples. If there are examples for more than one template type, the example data matches. In a few cases where I considered that the data to be entered was not obvious to me from the name of the variable, I have specified my expected variable values.
GENL
The LDS Ancestral File™ (now FamilySearch™) is a searchable database of genealogical information submitted by individuals. Rather than considering this a source, I generally consider it a Repository of sources provided by individuals. However, as an exercise I customized a template for this source my way. This template “splits” source records since it names the compiler and thus has “split” sources for each FGS. The [CD] should contain the actual record data, such as the person’s Ancestral File Number. However this Bibliography template will “lump” to simply the LDS Ancestral File itself. An alternative to this template is the LDS Patron Sheets that focuses on the nature of the submission of the data to the Ancestral File. In that template the Ancestral File on-line database can be cited as the Repository. I prefer that template more than this one, and thus do not currently use these templates. Source groups in use: C, Cp, D, RA, Rp, ShT, T, Vr.
I don’t use this or any other specialized “article” template as my more general purpose Published Work templates fulfill this need.
|
[AUTHOR], "[TITLE]," [ITAL:][SERIES][:ITAL]<, [DATE]><, [COMMENTS]><, [CD]><. Cited as "[SHORT TITLE]">. |
|
|
[AUTHOR], "[SHORT TITLE]," [ITAL:][SERIES][:ITAL]<, [DATE]><, [CD]>. |
|
BAPM
This source is for an individual certificate or document of registration of entry into a religious organization. It can be used for either a child or adult baptism or enrollment.
[LOCATION]
is usually the name of the parish or place where the event took place, which is typically broader than the name of the site or church which is entered in
[LOCATION DETAIL]
.
[LOCATION]
is unconditional to produce “unknown” if not identified.
[PUBLISHER]
is usually a specific religious entity authorized to issue certificates or grant enrollment, which likely has a different name than the
[LOCATION]
.
[TITLE]
is the kind of document, e.g. Certificate of Registration of Baptism.
[RECORD TYPE]
gives specifics about the document, e.g. Certified Copy or Original.
[ORIGINAL DATE]
is the date of the event.
[FILE DATE]
is the issue date of the document. Often the date of birth also is included in such documents, but that information would be entered in the
[CD]
. As two date types are already included, the date obtained should be entered in the [ANNOTATION]. Custom source elements:
[LOCATION DETAIL]
in Second Location which permits having the detail before
[LOCATION]
in FF and SF, but after in B. Source groups in use: C, D, D2, FN, L, L2, RA, Rp, RR, RT, Sj, T.
|
[VOLUME], [TITLE]<: [CD]><, ([DATE])><, [COMMENTS]>, [REPOSITORY], [REPOSITORY ADDRESS]<. Cited as [SHORT TITLE]>. |
|
BAPM
Although I have defined them as different Source Types, I use this same structure for multiple types that deal with church registers.
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a source of multiple registers (e.g. Bishop’s transcripts with combined Baptism, Marriage, and Burial registers). Even though these are church records they may have been compiled by an individual, then the optional
[COMPILER]
element is used. If the register interleaves different types of entries in a single register, e.g. a church register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[JURISDICTION]
is usually the name of the parish or area covered by this register, which is typically different from the name of the
[CHURCH]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger ecclesiastical jurisdiction other than the actual church parish published the register, e.g. the Archdeaconry. Custom source elements:
[CHURCH]
in Second Location. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
A “bibliography only” source with the FullFootnote and ShortFootnote templates excluded was proposed to be used if you simply wanted to have a bibliographic entry, but no footnote/endnote. One example was to generate a bibliographic entry to a “source of source” that might otherwise be only mentioned in a memo, citation, or source comment. However, a source will not be included in the bibliography unless it occurs as a non-excluded citation to a tag that prints (i.e. the tag is included in the report options, its surety meets the threshold, and exclusion settings will include the citation). The only way to have such otherwise non-cited entries is to copy them into the Bibliography as part of post processing in a word processor.
This test template for Bibliography is based on my most general custom Miscellaneous source type. In previous versions, these excluded templates did not work at all satisfactorily. 19 As of Version 8 leading exclusion markers in templates do somewhat control the output, but a Bibliography entry will not be produced without at least one full footnote/endnote citation of the source. 20 An alternative could be to use a second citation to an appropriate source type on the same tag but have some text like “Source of the above source” preceding a normal footnote template, or possibly as the citation memo. However, one would need to ensure the appropriate citation order and not use unique endnotes.
BIRT
This source is for an individual certificate or document of registration.
[TITLE]
is the kind of document, e.g. Certificate of Registration of Birth.
[RECORD TYPE]
gives specifics about the document, e.g. Certified Copy.
[LOCATION DETAIL]
is the entity or specific office within the jurisdiction that issued the certificate. The
[JURISDICTION]
is the area covered by the issuing entity. For the U.S. it will typically be a state and I will not include USA, in other countries it will typically be something equivalent, such as county in England, but I then follow with the country name.
[FILE DATE]
is issue date of the document. The actual date (and if identified the location) of the birth is in the
[CD]
. Custom source elements:
[DATE OBTAINED]
in the Second Date group,
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF and SF, but after in B. Source groups in use: C, D, D2, FN, L, L2, RA, Rp, RR, RT, Sj, T.
BIRT
Churches seldom have separate registers just for births, but this source type is defined for completeness. Although I have defined them as different Source Types, I use this same structure for multiple types that deal with church registers.
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a register with multiple types of entries (e.g. Bishop’s transcripts with combined Baptism, Marriage, and Burial registers). Even though these are church records this may be a compiled copy by an individual, then the optional
[COMPILER]
element is used. If the register interleaves different types of entries in a single register, e.g. a church register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[JURISDICTION]
is usually the name of the parish or area covered by the register, which is typically different from the name of the
[CHURCH]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger ecclesiastical jurisdiction other than the actual church parish published (a copy of) the register, e.g. the Archdeaconry. Custom source elements:
[CHURCH]
in Second Location. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
BIRT
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a source of multiple registers (e.g. town record with separate sections for births and deaths).
[LOCATION DETAIL]
is used (instead of church) if the register only covers a smaller area than the recording governmental
[JURISDICTION]
or it identifies the entity or specific office within the jurisdiction that maintained the register. The
[JURISDICTION]
in the U.S. is typically the state and I do not include USA, in other countries it will typically be something equivalent, such as county in England, but I then follow with the country name. Even though these are usually government records this may be a compiled copy by an individual, then the optional
[COMPILER]
element is used. If the register interleaves different types of entries in a single register, e.g. a town register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger governmental entity other than the actual location published the register, e.g. County copy of a town’s transcripts. Custom source elements:
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF and SF, but after in B. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
|
[SUBJECT] entry, [RECORD TYPE]< [NUMBER]><, [CD]>< ([DATE])>, [REPOSITORY], [REPOSITORY ADDRESS]. |
|
|
[SUBJECT] entry, [RECORD TYPE]< [NUMBER]><, [CD]>< ([DATE])>. |
|
Use “Book (Authored)”: Enter the names of the author(s) in square brackets, e.g., [Meredith B. Colket Jr. and Frank E. Bridgers].
Use “Book (Authored)”: Enter “[Anonymous]” (with square brackets) for the name of the author(s).
This template is the default “primary” source, and is thus used for GEDCOM Import sources. I have notes that it includes: Citation Memo (from TEXT), Short Title, Author (from AUTH), Publish Date, Publisher (from PUBL), Publication Address, Abbreviation?? from (ABBR). [Someday I need to do more testing here with various GEDCOM source input to determine what gets put where as part of this automated GEDCOM import, and then update my Source Element variable names discussion. In general a source will be of this source type only upon import until changed to one of my custom types, such as Published Work.]
This is the same template structure as “Book, Authored” but assumes that multiple names will be entered in the single Author field separated by semicolons with each using the “surname, given” structure.
The only change was to remove the unbalanced closing parenthesis in the standard Bibliography entry.
Use “Book (Authored)”: Enter, e.g., “unpaginated, 10th page” in the citation detail or as a [PAGE] element added to the source template.
Use “Book (Authored)”: Enter “privately printed” in the publisher field. [See “Book (Multi-Authored)” above.]
Use “Book (Authored)”: The output will include “no date” if the publication date is left empty.
Use “Book (Authored)”: The output will include “no place” if the publication place field is left empty.
Use “Book (Authored)”: The output will include “no publisher” if the publisher field is left empty.
BURI
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a source of multiple registers (e.g. town record with separate sections for different cemeteries).
[LOCATION DETAIL]
is used (instead of church) if the register only covers a smaller area than the recording governmental
[JURISDICTION]
or it identifies the entity such as the cemetery company or specific office within the jurisdiction that maintained the register. The
[JURISDICTION]
in the U.S. is typically the state and I do not include USA, in other countries it will typically be something equivalent, such as county in England, but I then follow with the country name. Even though these are usually government or company records this may be a compiled copy by an individual, then the optional
[COMPILER]
element is used. The
[PSEUDO PERSON]
element is not needed to be included even when there is a Cemetery Location Pseudo Person since that person is not the source but should be linked to the burial tag as a Witness with the appropriate role. If the register interleaves different types of entries in a single register, e.g. a collection of burials and/or cremations, or for different cemeteries, arranged chronologically or by name, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger governmental or company entity other than the actual location published the register, e.g. County or headquarters copy of a specific cemetery’s transcripts. Custom source elements:
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF and SF, but after in B. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
BURI
This source is for an individual certificate, document, or other record of interment. Since
[TITLE]
identifies the kind of record (e.g. “Certificate of Burial”, or “Gravestone”) I also use this for recording the information for a single gravestone marker.
[RECORD TYPE]
gives specifics about the record, e.g. Certified Copy, Joint marker.
[LOCATION]
is usually the name of the county or parish where the burial took place, while the name of the cemetery and/or specific site is entered in
[LOCATION DETAIL]
.
[PUBLISHER]
is optionally used for the governmental or religious entity authorized to issue the certificate or document, which may have a different name than the
[LOCATION]
or
[LOCATION DETAIL]
.
[FILE DATE]
is issue date of the document. The
[PSEUDO PERSON]
element is not needed to be included even when there is a Cemetery Location Pseudo Person since that person is not the source but should be linked to the burial tag as a Witness with the appropriate role. If identified, the actual date/time and specific plot location of the burial is in the
[CD]
. Custom source elements:
[DATE OBTAINED]
in the Second Date group which can be used for the “viewed” date of a marker,
[LOCATION DETAIL]
in Second Location which permits having the detail before
[LOCATION]
in FF and SF, but after in B. Source groups in use: C, D, D2, FN, L, L2, RA, Rp, RR, RT, Sj, T.
BURI
Although I have defined them as different Source Types, I use this same structure for multiple types that deal with church registers.
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a register with multiple types of entries (e.g. Bishop’s transcripts with combined Baptism, Marriage, and Burial registers). Even though these are church records they may have been compiled by an individual, then the optional
[COMPILER]
element is used. The
[PSEUDO PERSON]
element is not needed to be included even when there is a Cemetery Location Pseudo Person since that person is not the source but should be linked to the burial tag as a Witness with the appropriate role. If the register interleaves different types of entries in a single register, e.g. a church register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[JURISDICTION]
is usually the name of the parish or area covered by the register, which is typically different from the name of the
[CHURCH]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger ecclesiastical jurisdiction other than the actual church parish published the register, e.g. the Archdeaconry. Custom source elements:
[CHURCH]
in Second Location. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
In the
[COMMENTS]
include something like
“This is a re-publication on CD of Author, [ITAL:]title[:ITAL], (publication date)”
If the original source is in the system, use embedded citation.
I do not use this, as I “lump” such source information using the Burial Certificate template, but identify the
[TITLE]
as a “Gravestone” or “Memorial Marker”.
I also do not use this as I use the source type appropriate for the publication itself, such as a Published Work or an Electronic Database.
This source type is a subject of major discussion among TMG users. See my separate chapter describing my entire system for dealing with census data. Showing my “lumper” preference, I currently use the single source type “Census (MJH)” described below for all my census data regardless of type of census source. However I store these other examples here for completeness.
I modified this template in this manner in an earlier effort prior to settling on my single template structure.
|
< [DATE]> [RECORD TYPE], [LOCATION]<, [CD]>, [REPOSITORY]< [FILM]>. |
|
|
1860 U. S. Census, Montgomery County, Kentucky, [CD], National Archives micropublication M653, roll 388. |
|
|
[HOUSEHOLD],< [DATE]> [RECORD TYPE], [LOCATION], [RECORD INFO], [REPOSITORY] [REPOSITORY ADDRESS]<, [CD]>. |
|
|
[LOCATION].< [DATE]> [RECORD TYPE]. [REPOSITORY] [REPOSITORY ADDRESS]. |
CENS
This single source template has so far sufficed for “lumping” all my census sources. For USA I have one source per county/microfilm. A county spanning multiple films is multiple sources. Multiple counties on the same film are multiple sources.
Field meanings in order on the General tab:
•
[TITLE]
defines the overall location/type census of which this source is a part, e.g. “U. S. Census”.
•
[RECORD TYPE]
describes the kind of census data. As examples, for 1790-1840 in the U.S. I usually leave this empty as the population schedule is typically the only thing available and is assumed, but it would not hurt to specify “population schedule” and you might find a “mortality schedule”. In 1820 both the U.S. “population schedule” and “manufactures schedule” existed and both are useful genealogy resources. In 1850 and 1860 the U.S. had both a “population schedule” and a “slave schedule”. In 1900 for the separate U.S. “Indian population” if it is wholly contained in and part of a county record then I do not cite it as a separate record type but in the
[CD]
as a section of the county schedule similar to an Enumeration District. But if it is enumerated as a separate location, often straddling multiple county boundaries, then I enter it in
[LOCATION DETAIL]
as a separate location like a separate county. I cite state or local copies of the U.S. Census (such as duplicate originals or exhibition copies) as an added note to the
[RECORD TYPE]
, e.g. “population schedule, county-level copy”, with additional appropriate text in the bibliography in the
[REPOSITORY]
and
[ANNOTATION]
. If you are not citing a full enumeration then an appropriate
[RECORD TYPE]
of something like “soundex”, or “index” should be used.
• The element
[PSEUDO PERSON]
in the Pages group is used to link to a Census Source Pseudo Person as I almost always create one for census sources.
The template includes most of the Second Site specific codes, but the entire Second Site
PageLink
structure must be entered as text in this element.
21
The template and codes will produce the link to the pseudo census person immediately following the text of any and all elements which constitute the full title of the source.
This code produces a superscript number in the Second Site source output corresponding to the PersonID of the pseudo census person. Even if source entries are more split than pseudo people, multiple entries in the Master Source List can link to the same pseudo census person, so this works well. This link will be present on the Second Site pages for each citation as well as in the Bibliography entry in the List of Sources. For more formal output I use Second Site Tag Groups to only output the Census tags themselves on the pseudo census people pages. The absence of Census tags on a person page potentially removes the link in those source citations to the census person’s page which now is the only page with the full census narrative. However I (try to) always have a person’s census records cited to at least one of their narrative tags, usually the Birth tag, so those citations preserve the link to the census person page and thus to the full census transcription.
•
[PUBLISH DATE]
is the as-of date of the publication of the census (in the U.S. as of 1952 usually 72 years after the enumeration).
•
[CENSUS DATE]
is only the year the census was taken.
•
[LOCATION]
is the largest geographical subdivision of the census (e.g. state) with
[LOCATION DETAIL]
identifying the locale of this whole source, e.g. county.
•
[PUBLISHER]
is usually “National Archives and Records Administration” with address “Washington, D.C.” and following my style (which does not exactly follow either NARA or EE or Garner style) is only listed in the Bibliography. However, if it is a state or local copy, then the publisher address and publisher will the local governmental office that complied them, e.g. “Tuscaloosa, Alabama: Probate Judge’s Office”.
•
[VOLUME]
has the details covered by this single source (e.g. the soundex range, the EDs covered, the index volume).
•
[FILM]
is the published film, e.g. “micropublication M653, roll 372”, and the
[REPOSITORY REFERENCE]
is the call number in this specific repository.
•
[CD]
contains the detailed location and SD/ED followed by the complete identification of the household, e.g. “Marietta Township, SD 4, ED 229, page 7(227A), lines 37-44, dwelling 61, family 67”. While some of this may be redundant (lines and dwelling and family), I have found them useful, especially if I make a data entry typo in one. Though not strictly required for the citation, I also include the street address, if given, as useful genealogical data. This Source Element is made conditional, as I will cite this source without a CD to the Census Pseudo Person’s Created tag.
The memos of the various Census Tags contain all the details of the entry. As I encounter census records for other countries I may choose to construct separate templates for them, but currently believe this single template will work.
Custom source elements:
[CENSUS DATE]
in Second Date group for the year,
[LOCATION DETAIL]
in Second Location for the county/locale which permits having the county/locale before the state in FF and SF, but after in B,
[PSEUDO PERSON]
in the Pages group. Source groups in use: C, D, D2, FN, L, L2, Pb, PL, Pg, RA, Rp, RR, RT, T, Vm.
BAPM
BIRT
BURI
CHUR
DEAT
MARR
Not sure I need this type. Needs to be updated to my latest structure for my generic church register type.
[TITLE]
would be type of record, e.g.
Banns Register, General Register
, etc. The fact that it is filmed would show from the Repository information. Custom source elements:
[CHURCH]
in Second Location.
BAPM
BIRT
BURI
CHUR
DEAT
MARR
Not sure I need this type. Needs to be updated to my latest structure for my generic church register type.
[TITLE]
is type of record, e.g.
Banns Register, General Register
, etc. The fact that I viewed the original would show from the Repository information. Custom source elements:
[CHURCH]
in Second Location.
|
[ITAL:][TITLE][:ITAL] ([PUBLISHER ADDRESS]: [PUBLISHER]<, [DATE]>)<, [CD]><. Cited as [ITAL:][SHORT TITLE][:ITAL]>. |
|
|
[ITAL:][TITLE][:ITAL]. [PUBLISHER ADDRESS]: [PUBLISHER]<, [DATE]>. |
PLAC
Custom source elements:
[LOCATION DETAIL]
in Second Location which permits having the detail before
[LOCATION]
in FF and SF, but after in B. Source groups in use: C, D, L, L2, Pb, PL, RA, Rp, RR, ShT, T, Vm.
CORR
[AUTHOR]
and
[RECIPIENT]
should be entered “surname, given” as with all names. Because it occurs first in the footnotes, be sure to capitalize
[RECORD TYPE]
. The element
[PSEUDO PERSON]
in the Pages group is used to link to a Correspondance Source Pseudo Person if one is created for this author’s correspondence.
22
In my “lumper” spirit, by entering “E-mail” as the
[RECORD TYPE]
and the e-mail addresses in
[AUTHOR ADDRESS]
and
[RECIPIENT ADDRESS]
(usually in
‘<>’
brackets), this correspondence template can eliminate the need for a separate e-mail template. If the e-message is to a ListServ or bulletin board, use an appropriate entry for the
[RECORD TYPE]
and put the name of the ListServ as the
[RECIPIENT]
with the URL as the
[RECIPIENT ADDRESS]
. I consider e-messages (and phone calls) as simply another form of correspondence. However, if the purpose of the phone call is an interview, then I use the Interview source template. Custom source elements:
[PSEUDO PERSON]
in the Pages group. Source groups in use: A, C, D, L, L2, P2, RA, Rp, RR, RT, ShT, T.
|
[ITAL:][TITLE][:ITAL], [SERIES]< ([COMMENTS])><, [CD]><. Cited as [ITAL:][SHORT TITLE][:ITAL]>. |
|
DEAT
This source is for an individual certificate or document of registration.
[TITLE]
is the kind of document, e.g. Certificate of Death.
[RECORD TYPE]
gives specifics about the document, e.g. Certified Copy.
[LOCATION DETAIL]
is the entity or specific office within the jurisdiction that issued the certificate. The
[JURISDICTION]
is the area covered by the issuing entity. For the U.S. it will typically be a state and I will not include USA, in other countries it will typically be something equivalent, such as county in England, but I then follow with the country name.
[FILE DATE]
is issue date of the document. The actual date and (if identified) location of the death is in the
[CD]
. Custom source elements:
[DATE OBTAINED]
in the Second Date group,
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF and SF, but after in B. Source groups in use: C, D, D2, FN, L, L2, RA, Rp, RR, RT, Sj, T.
DEAT
Churches seldom have separate registers just for deaths, but this source type is defined for completeness. Although I have defined them as different Source Types, I use this same structure for multiple types that deal with church registers.
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a register with multiple types of entries (e.g. Bishop’s transcripts with combined Baptism, Marriage, and Burial registers). Even though these are church records they may have been transcribed or compiled by an individual, then the optional
[COMPILER]
element is used. If the register interleaves different types of entries in a single register, e.g. a church register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[JURISDICTION]
is usually the name of the parish or area covered by the register, which is typically different from the name of the
[CHURCH]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger ecclesiastical jurisdiction other than the actual church parish published the register, e.g. the Archdeaconry. Custom source elements:
[CHURCH]
in Second Location. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
DEAT
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a source of multiple registers (e.g. town record with separate sections for births and deaths).
[LOCATION DETAIL]
is used (instead of church) if the register only covers a smaller area than the recording governmental
[JURISDICTION]
. The
[JURISDICTION]
for the U.S. is typically the state entered as “State of Michigan” and I do not include USA. In other countries it will typically be something equivalent, such as county in England, but I then follow with the country name. Even though these are usually government records they may have been transcribed or compiled by an individual, then the optional
[COMPILER]
element is used. If the register interleaves different types of entries in a single register, e.g. a town register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger governmental entity other than the actual location published the register, e.g. County publication of a town’s transcripts. Custom source elements:
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF and SF, but after in B. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
|
[NAME OF PERSON] entry, [TITLE]<, [VOLUME]><, [CD]>, [REPOSITORY], [REPOSITORY ADDRESS]<. Cited as [SHORT TITLE]>. |
|
|
[REPOSITORY ADDRESS]. [REPOSITORY]. [RECORD TYPE]. [NAME OF PERSON] entry. |
|
[TITLE]< [VOLUME]><: [CD]>, [REPOSITORY], [REPOSITORY ADDRESS]<. Cited as [SHORT TITLE]>. |
|
|
[AUTHOR], "[TITLE]" ([RECORD TYPE], [LOCATION]<, [DATE]>)<, [CD]><. Cited as "[SHORT TITLE]">. |
|
Instead of this separate template I use my general Correspondence template above.
|
[COMPILER], online [URL], [AUTHOR] ([LOCATION])<, downloaded [DATE]><, [CD]>. |
|
|
[COMPILER]. Online [URL], [AUTHOR]. [LOCATION]<. Text downloaded [DATE]>. |
The TMGL ListServ discussed this generic custom source type
23
for all on-line databases. While I liked the idea, I was not comfortable with that template, and adapted it to my own style of source templates as shown below, especially since I usually have the database be the Repository rather than the source itself.
[TITLE]
= the name of the database.
[COMPILER]
= the host site.
[URL]
= the main address of the site.
[COMMENTS]
= a short description of the source of the data, taken from the site. In the
[CD]
is the information needed to find the specific record, such as name, and serial numbers or dates, depending on what the specific data shows. Note that this source type is for complied databases - that doesn't include images of original records, like census and draft cards. For them it was suggested to cite the original, and note in the
[COMMENTS]
that you saw an image, and where. The example below from the ListServ is for a Passerger List, but for that source type I have my own
Passenger List
template.
The TMGL ListServ discussed an alternative generic custom source type
24
for information retrieved from the USGenWeb site. Again I expect to adapt it to my own style of source templates, possibly “lumping” with the above, and especially making the Bibliographic entry the most complete. The split CD has
[CD1]
= location, e.g. County, State.
[CD2]
= has the format of what you are looking at, usually based on Mills.
WWWD
This is my version of a generic “lumped” source for an on-line electronic database constructed somewhat from the TMG-L electronic database examples above but tailored to my source style. Its name includes “database” but I also use it for web pages. It is only used when the on-line database or page is actually the source of the information. More often I enter on-line archives as the Repository of the source, such as an on-line copy of a book. The
[URL]
source element contains the main address for the database and is intentionally only used in the Bibliography. Either the specific search terms, or the complete specific URL of the results using sentence formatting codes, for a citation will be in the
[CD]
. Thus the
[URL]
element is not needed in either footnote template. I expect to modify/enhance this template as I encounter more on-line sources. Source groups in use: C, L2, Pb, RA, RM, Rp, RR, SbT, ShT, T.
|
[AUTHOR], [RECORD TYPE]<, [DATE]>, [LOCATION].< [COMMENTS],>< [CD]>. |
|
|
[AUTHOR], [RECORD TYPE]<, [DATE]>, [LOCATION]<. [COMMENTS]>. |
This is similar to the separate e-mail message template. I choose to use my general Correspondence template or my Electronic Database template above. The standard full footnote sentence omits quotes around the
[SHORT TITLE]
which I have added.
There is considerable discussion and many alternatives to citation structures for electronic resources. 25 For example see my Electronic Database template above.
|
Compressed Pedigree of Lee Hoffman, online http://www.users.mis.net/~lhoffman/Pedig001.htm, downloaded 30 Nov 1998, [CD]. Cited as Lee Hoffman Pedigree. |
|
EMPL
This source is for a document or record concerning employment about an individual.
[TITLE]
is the kind of document, e.g. Job Offer.
[RECORD INFO]
gives identifying details about the document, e.g. a serial number or job title.
[RECORD TYPE]
gives specifics about the document, e.g. Certified Copy or department assigned.
[DATE]
is issue date of the document. The details of the event associated with this employment record is in the
[CD]
. Custom source elements:
[EMPLOYER]
in the Author group,
[LOCATION DETAIL]
in Second Location which permits having the detail before
[LOCATION]
in FF and SF, but after in B. Source groups in use: A, C, D, D2, L, L2, RA, RN, Rp, RR, RT, Sj, T.
GENL
This is for a separately obtained FGS. I often use my source type LDS Pedigree Resource, LDS Patron Sheet or Electronic Database templates for what might otherwise be considered a Family Group Sheet. Source groups in use: C, Cp, D, D2, L, RA, Rp, RR, ShT, T.
Cite published source fully, according to type, then add (for example): micro film/fiche no. 123,456, frame 123, Family History Library (FHL), Salt Lake City, Utah.
Cite unpublished source fully, according to type, then add (for example): micro film/fiche no. 123,456, frame 123, Family History Library (FHL), Salt Lake City, Utah.
This “dummy” source type can be used if you simply want to have a textual comment that will appear as a footnote or endnote wherever citations appear, but do not desire a Bibliographic entry. You would need to create and cite a dummy source entry of this type. It somewhat produces a Bibliographic entry 26 , but the entry is simply empty lines containing only a carriage return which appear at the beginning of the Bibliograpy. Post processing in a word processor could remove those empty lines. It is probably more appropriate to use an embedded citation without a source number in the tag memo or sentence field, since embedded citations do not produce Bibliography entries.
GOVT
MILR
This source is for a government certificate or document for a single individual.
[TITLE]
is the kind of document, e.g. Passport.
[RECORD TYPE]
gives specifics about the document, e.g. Certified Copy. For the
[JURISDICTION]
for parts of the U.S. I will typically enter the state and not include USA, in other countries it will typically be something equivalent, such as county in England, but I then follow with the country name.
[FILE DATE]
is issue date of the document. The actual date and location of the some event being recorded by the document is in the
[CD]
. Custom source elements:
[DATE OBTAINED]
in the Second Date group,
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF, omitted in SF, but after in B. Source groups in use: C, D, D2, FN, L, L2, RA, Rp, RR, RT, Sj, T.
MARR
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a source of multiple registers (e.g. town record with separate sections for births and deaths).
[LOCATION DETAIL]
is used (instead of church) if the register only covers a smaller area than the recording governmental
[JURISDICTION]
. The
[JURISDICTION]
for the U.S. is typically the state and I do not include USA, in other countries it will typically be something equivalent, such as county in England, but I then follow with the country name. Even though these are usually government records they may have been compiled by an individual, then the optional
[COMPILER]
element is used. If the register interleaves different types of entries in a single register, e.g. a town register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger governmental entity other than the actual location published the register, e.g. County publication of a town’s transcripts. Custom source elements:
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF and SF, but after in B. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
GENL
GOVT
Most of my sources using this type are citations created before much of this information was moved to on-line databases. Source groups in use: C, D, En, FN, Pb, PL, RA, Rp, RR, ShT, Sr, T.
I have chosen to modify this standard template, see below.
INTV
With my “lumper” philosophy, I could use the structure of my Correspondence template above, but have chosen to modify the standard Interview template for this purpose.
[RECORD TYPE]
describes the type of interview, e.g. “in person” or “by phone”.
[INFORMANT]
,
[INTERVIEWER]
, and
[TRANSCRIBER]
should be entered “surname, given” as with all names. Custom source elements:
[TRANSCRIBER]
in Compiler,
[INTERVIEW LOCATION]
in Second Location. Source groups in use: A, C, Cp, D, L, L2, P2, RA, Rp, RR, RT, ShT, T.
GENL
My
LDS Patron Sheets
and
LDS Pedigree Resource
are similar structures and probably should be combined (lumped) to a generalized genealogical resource source type. The LDS Church archives all forms of genealogical information including such things as LDS enrollments and data in the form of Family Group records, Individual records, and Pedigree charts. The LDS Ancestral File™ (now LDS FamilySearch™) is a searchable database of such genealogical information submitted by individuals, and can be used as the source itself. See also my Ancestral File or Electronic Database templates as alternatives. In some cases that database will point to a FHL microfilm with an image of the original submission. When possible I prefer to view such originals and will access the film through the FHL. The
[SERIES]
element allows “lumping” or “splitting” sources as desired. For example, I usually lump all of an enrollment batch as a single source with the
[CD]
containing the specific sheet and data, and the
[CM]
containing the submitter information and/or Stake. If an entire “split” source, e.g. a batch number, was submitted from a single Stake, I use that Stake as the
[PUBLISHER ADDRESS]
. Since my style is to put the FHL film number as the
[REPOSITORY REFERENCE]
when I actually view the film, there is no need for the
[FILM]
element in the templates. However, when the Patron Sheet data is viewed on-line, the only provided reference grouping is often the FHL film number. When I am using this template instead of my Ancestral File template the film number would then go in the
[SERIES]
element. In the on-line situation the Repository would be the Ancestral File™ (now LDS FamilySearch™) on-line database. Source groups in use: C, D, Pb, PL, RA, Rp, RR, SbT, ShT, Sr, T
GENL
My
LDS Patron Sheets
and
LDS Pedigree Resource
are similar structures and probably should be combined (lumped) to a generalized genealogical resource source type. The Pedigree Resource File is a lineage-linked database of records submitted by individuals, and usually involves either the on-line index or the set of published CD-ROMs. The
[SERIES]
element allows “lumping” or “splitting” sources as desired, and I usually “lump” at a CD-ROM, with all other details in the
[CD]
Source groups in use: C, D, Pb, PL, RA, Rp, RR, SbT, ShT, Sr, T.
I prefer to use my more general Correspondence source type for letters. However, if I were to use this separate source type, I would likely change it as follows, which makes more of the fields optional, and follows my convention of reserving
[COMMENTS]
, etc. for the bibliography.
|
[LOCATION], [TITLE]<: [CD]>; [FILM], [REPOSITORY], [REPOSITORY ADDRESS]<. Cited as [SHORT TITLE]>. |
|
|
[LOCATION], [TITLE]. [FILM], [REPOSITORY], [REPOSITORY ADDRESS]. |
MANU
Source groups in use: A, C, D, Pb, PL, RA, RM, Rp, RR, T.
|
[SPOUSES’ NAMES] marriage<, [DATE]>, [REPOSITORY], [REPOSITORY ADDRESS]. [MANUSCRIPT INFO]<, [CD]>. |
|
|
[SPOUSES’ NAMES]. [RECORD TYPE]. [REPOSITORY], [REPOSITORY ADDRESS]. [MANUSCRIPT INFO]. |
MARR
This source is for an individual certificate or document of registration.
[SPOUSES’ NAMES]
should be entered “groom-surname, given; bride-surname, given” as with all names.
[LOCATION]
is usually the name of the parish or place where the marriage took place, which is typically broader than the name of the site or church which is entered in
[LOCATION DETAIL]
.
[PUBLISHER]
is usually a specific governmental or religious entity authorized to issue certificates, which likely has a different name than the
[LOCATION]
.
[TITLE]
is the kind of document, e.g. Certificate of Marriage.
[RECORD TYPE]
gives specifics about the document, e.g. Certified Copy.
[DATE]
is issue date of the document. If the actual date of the marriage is different, the date of the ceremony would be identified in the
[CD]
. Custom source elements:
[LOCATION DETAIL]
in Second Location,
[DATE OBTAINED]
in the Second Date group. Source groups in use: C, D, D2, L, L2, Pb, PL, RA, RN, Rp, RR, RT, Sj, T.
MARR
Although I have defined them as different Source Types, I use this same structure for multiple types that deal with church registers.
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a register with multiple types of entries (e.g. Bishop’s transcripts with combined Baptism, Marriage, and Burial registers). Even though these are church records they may have been compiled by an individual, then the optional
[COMPILER]
element is used. If the register interleaves different types of entries in a single register, e.g. a church register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[JURISDICTION]
is usually the name of the parish or area covered by the register, which is typically different from the name of the
[CHURCH]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger ecclesiastical jurisdiction other than the actual church parish published the register, e.g. the Archdeaconry. Custom source elements:
[CHURCH]
in Second Location. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
GOVT
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a source of multiple registers (e.g. town record with separate sections for different purposes).
[LOCATION DETAIL]
is used if the register only covers a smaller area than the recording governmental
[JURISDICTION]
. The
[JURISDICTION]
for the U.S. is typically a state, county, or municipality and I do not include USA, in other countries it will typically be something equivalent, such as county in England, but I then follow with the country name. Even though these are usually government records they may have been compiled by an individual, then the optional
[COMPILER]
element is used. If the register interleaves different types of entries in a single register, e.g. a town register of events chronologically, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
.
[VOLUME]
identifies the date and/or name range.
[PUBLISHER ADDRESS]
is used if a larger governmental entity other than the actual location published the register, e.g. County publication of a town’s records. Custom source elements:
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF and SF, but after in B. Source groups in use: C, D, L, L2, PL, RA, Rp, RR, SbT, T, Vm.
|
[SUBJECT], [ITAL:][TITLE][:ITAL]<, [FILM]><, [CD]> [REPOSITORY], [REPOSITORY ADDRESS]<. Cited as [ITAL:][SHORT TITLE][:ITAL]>. |
|
|
[ITAL:][TITLE][:ITAL]<. [FILM]>. [REPOSITORY ADDRESS], [REPOSITORY]. |
ZZZZ
This general purpose source template has the maximum possible source element groups that TMG will accommodate on its various input screens, and should suffice for any source type that does not have its own template. All names should be entered “surname, given”. Since using this type implies the source type doesn’t fit anything predefined, I always enter a
[RECORD TYPE]
, which is unconditional. That also permits the punctuation to work for the preceding three optional elements in the templates. Use
[SUBTITLE]
and/or
[TITLE]
depending upon whether you want quotes or italics.
[ORIGINAL DATE]
is used for the item’s date since
[PUBLISH DATE]
is already in the
DATE
group. If any of
[PUBLISHER ADDRESS]
,
[PUBLISHER]
or
[PUBLISH DATE]
is entered, you must enter something in all three to make the punctuation work.
[REPOSITORY]
is unconditional to ensure “unknown repository” if I do not enter it, and to make its surrounding punctuation work. Source groups in use: A, C, D, D2, En, L, L2, P2, Pb, PL, RA, RM, Rp, RR, RT, SbT, Sj, Sr, T, Vm.
|
[DOCUMENT], [FILE NAME]<; [SERIES]>; [ITAL:][FILM][:ITAL]<; [NUMBER]> ([REPOSITORY ADDRESS]: [REPOSITORY])<, [ROLL]><, [CD]>. |
|
|
[FILM]<, [NUMBER]>. [REPOSITORY ADDRESS]: [REPOSITORY]<. [ROLL]>. |
Could “lump” multiple articles from the same newspaper into a single source for just the newspaper on that date by using split citations and putting the article title in
[CD1]
. However, I use my modified version of this template below.
NEWS
Whenever an article is reproduced, republished, or transcribed separately, it will invariably have a separate repository from the actual newspaper. In this case I do not use the “lumped” source type style described above, since I will want the article details, such as the title, in the Bibliography template. While this may result in multiple bibliography entries for the same newspaper edition, this is desired since each article may be in a different repository with separate
[ANNOTATION]
and
[REPOSITORY REFERENCE]
elements. The source type is similar to my custom “lumped” style below, except for which templates include the elements for the article details.
[NEWSPAPER]
is a mandatory element but could be empty and will then print as “unknown newspaper” in the Full Footnote and Bibliography.
[ARTICLE TITLE]
is optional in the Full Footnote, but mandatory in the Bibliography and will then print as “unknown article title”. If the
[ARTICLE TITLE]
is left blank, include some description of the article in the
[ANNOTATION]
. If
both
[NEWSPAPER]
and
[ARTICLE TITLE]
are empty/unknown, include at least include a
[REPOSITORY REFERENCE]
or more usually have some guess or comment in the
[ANNOTATION]
so that all untitled articles from unknown newspapers do
not
lump under one entry in the Bibliography.
[SHORT ARTICLE TITLE]
is mandatory for use in the Short Footnote and may include Subject or other data.
[DATE]
is mandatory so that when not identified will print out “n.d.”. Currently I do not use the
[PUBLISHER]
element, but may revisit this. I considered including a
[SUBJECT]
element for the people that are the subject of the article, but choose to include that information in either the
[CD]
or
[CM]
or article title as appropriate.
[EDITION]
should be used either for the edition number in a publication series (e.g. Volume 18, No. 5) that is equivalent to this date, or for a specific edition (e.g. city edition) among many on that date if the article does not exist or is not on the same page in every edition.
[SECTION]
is a named (e.g. Business section) or numbered (e.g. sec. 3) section of the newspaper.
[PAGES]
is only included in the Bibliography template and identifies the page(s), and perhaps column(s), spanned by the
entire
article, not just the bit being cited.
[CD]
includes the page and column (e.g. p. 3, col. 4), and maybe a subheading, of the
specific
data within the overall article being referenced by that citation.
While the
Chicago Manual of Style
recommends sorting the Bibliography by name of newspaper, I prefer the guidelines in
Evidence Explained
which sorts them by location. Thus I include both
[LOCATION]
and
[LOCATION DETAIL]
elements to have the location data in different orders in the Full Footnote and Bibliography.
[LOCATION]
is a mandatory element but could be empty and will then print as “unknown location” in the Bibliography. If part of the location can be presumed, enter as much of the location as appropriate, but including/ending with “unknown location” which avoids having only “unknown location” with an initial lowercase,
27
e.g enter “Michigan, unknown location”. But
[LOCATION DETAIL]
is not mandatory and may simply be missing in the Full Footnote.
NOTE:
These two location elements are used slightly differently in these templates than in most of my other custom templates. Here
[LOCATION DETAIL]
contains the “complete” location, details first.
[LOCATION]
also contains the “complete” location, but details last.
Custom source elements:
[DATE OBTAINED]
in the Second Date group,
[SECTION]
in Record Type,
[NEWSPAPER]
in Title, and
[LOCATION DETAIL]
in Second Location which permits having the detail first in FF and SF, but last in B. Source groups in use: A, C, D, D2, En, L, L2, Pg, RA, Rp, RR, RT, SbT, ShSb, ShT, T.
NEWS
One could “lump” multiple articles from the same newspaper into a single source record which only contained source element data about that newspaper on that date. Anything specific to the article could be included in the
[CD]
or
[CM]
, possibly using split citations and (for example) putting the article title in
[CD1]
.
Even when I wish to “lump” all articles from a single edition into a single bibliographic reference, I still prefer a separate source record per article or column in the Master Source List. TMG’s automatic Bibliographic “lumping” feature facilitates this. This custom source type excludes the details of each separate article, such as the title, from the
Bibliography
template so TMG will automatically “lump” or merge all these identical bibliography entries to the same newspaper on that date into one entry. However, the
Footnote
templates may include details specific to the article being cited, including the page/column numbers. This source type should only be used if all the citations to this editition used the identical source, such as a copy of the actual newspaper, or an archive image or facsimile or collection of transcriptions of the newspaper. Using this source type still allows separate articles to have separate TMG source records, but any source elements or data specific to the article may only be included in the Full or Short Footnote templates, or the
[CD]
and
[CM]
.
WARNING:
this lumping requires for each of these separate TMG source records the data in those elements which
are
used in the Bibliographic template be
identical
for that same newspaper to generate identical bibliography entries which can be merged. Thus such Bibliographic elements such as
[ANNOTATION]
and
[REPOSITORY]
and
[REPOSITORY REFERENCE]
must be identical for all of these separate source records. The safest way to ensure this is to copy an existing source record to that newspaper edition to create a source record for another article from that same edition.
[NEWSPAPER]
is a mandatory element but could be empty and will then print as “unknown newspaper” in the Full Footnote and Bibliography. If empty/unknown, include a
[REPOSITORY REFERENCE]
or use the
[ANNOTATION]
to make a guess or comment so that all unknown newspapers do
not
lump under one entry in the Bibliography.
[ARTICLE TITLE]
is optional.
[SHORT ARTICLE TITLE]
is mandatory for use in the Short Footnote and may include Subject or other data.
[DATE]
is mandatory so that when not identified will print out “n.d.”. Since the Bibliography entry will be “lumped” from several articles which may be obtained at different times, the optional custom source element
[DATE OBTAINED]
is specific to the article and thus only in the Full Footnote template. Currently I do not use the
[PUBLISHER]
element, but may revisit this. I considered including a
[SUBJECT]
element for the people that are the subject of the article, but choose to include that information in either the
[CD]
or
[CM]
or article title as appropriate.
[EDITION]
should be used either for the edition number in a publication series (e.g. Volume 18, No. 5) that is equivalent to this date, or for a specific edition (e.g. city edition) among many on that date if the article does not exist or is not on the same page in every edition.
[SECTION]
is a named (e.g. Business section) or numbered (e.g. sec. 3) section of the newspaper.
[PAGES]
is only included in the Full Footnote template and identifies the page(s), and perhaps column(s), spanned by this specific article, not just the bit being cited.
[CD]
includes page and column (e.g. p. 3, col. 4), and maybe a subheading, of the
specific
data within the overall article being referenced by that citation.
While the
Chicago Manual of Style
recommends sorting the Bibliography by name of newspaper, I prefer the guidelines in
Evidence Explained
which sorts them by location. Thus I include both
[LOCATION DETAIL]
and
[LOCATION]
elements to have the location data in different orders in the Full Footnote and Bibliography.
[LOCATION]
is a mandatory element but could be empty and will then print as “unknown location” in the Bibliography. If part of the location can be presumed, enter as much of the location as appropriate, but including/ending with “unknown location” which avoids the initial lowercase,
28
e.g “Michigan, unknown location”. But
[LOCATION DETAIL]
is not mandatory and may simply be missing in the Full Footnote.
NOTE:
These two location elements are used slightly differently in these templates than in most of my other custom templates.
[LOCATION DETAIL]
contains the “complete” location, details first.
[LOCATION]
also contains the “complete” location, but details last.
Custom source elements:
[DATE OBTAINED]
in the Second Date group,
[SECTION]
in Record Type,
[NEWSPAPER]
in Title, and
[LOCATION DETAIL]
in Second Location which permits having the detail first in FF and SF, but last in B. Source groups in use: A, C, D, D2, En, L, L2, Pg, RA, Rp, RR, RT, SbT, ShSb, ShT, T.
An alternative method for obituaries once proposed by Elizabeth Churchett on the ListServ creates two different source templates, one for when you know at least the newspaper it’s from, and one for when you only have an obit clipping from an unknown newspaper.
[BIBLIOGRAPHY ADDRESS]
is her custom Source Element (in what group, Second Location?) to have the location print out state first, then city/county.
PASS
[REGISTER TITLE]
is used for the sub-part if
[TITLE]
is for a source of multiple registers (e.g. separate crew, passenger and steerage lists).
[VOLUME]
is used if the
[TITLE]
includes more than one passenger list.
[SHIP NAME]
should be the full, official name of the vessel, but should not include any commas since this is a People element.
[SHORT TITLE]
should abbreviate the full register and volume name and will be preceded by the
[SHIP NAME]
in the SF. (Normally I would put a “Cited as” phrase in the FF, but since you cannot use the
[SHIP NAME]
element twice in the FF template, I simply don’t include that phrase.)
[ENTRY PORT]
is optionally used for the name of the port if different than the
[LOCATION]
which is usually the city name. Even though these are usually government records they may have been compiled from one or more sources by an individual, then the optional
[COMPILER]
and
[COMPILE DATE]
elements are used. If the lists are a publication, the source type Records (Multi-Volume) may be more appropriate. The details of the specific entry or entries is in the
[CD]
. The
[CD]
is optional to permit this template type to be used when the register was searched, but no information found, which would be explained in the
[CM]
. I usually do not add the image or transcription of the text as an exhibit. If it is short enough I include it in the
[CM]
. Otherwise I add a following Transcript tag which I can selectively choose whether to include in reports. Custom source elements:
[ENTRY PORT]
in Second Location which permits having the port name before
[LOCATION]
in FF, but after in B; and
[ARRIVAL DATE]
as an element name in the Second Date group as a memory jog. Source groups in use: Cp, D, D2, L, L2, P2, RA, Rp, RR, SbT, ShT, T, Vm.
PHOT
This general purpose template can be used for any photograph or equivalent visual record of a specific time. The
[SUBJECT]
should either include the names of the people identified in the image, or the subject matter if there are no people.
[TITLE]
identifies the type of image, such as “Family snap shot”, “Home movie”, “Commercial studio photo”, etc. The text for
[DATE]
and
[LOCATION]
can either be specific or approximate.
[MEMO1]
is the first part of the split Source Memo and includes any annotations or identification that is physically with or on the image. General source annotation can be put in
[MEMO2]
. Source groups in use: C, D, L, RA, Rp, RM, RR, Sj, T.
|
[SUBJECT] [RECORD TYPE]; [REPOSITORY], [REPOSITORY ADDRESS]<. [COMMENTS]><, [CD]>. |
|
|
[SUBJECT]. [RECORD TYPE]. [REPOSITORY]. [REPOSITORY ADDRESS]. |
|
[SUBJECT] [RECORD TYPE]<, [COMMENTS]>, [REPOSITORY] ([REPOSITORY ADDRESS])<, [CD]>. |
|
|
[SUBJECT]. [RECORD TYPE]. [DATE], [REPOSITORY], [REPOSITORY ADDRESS]. |
various to match type of work)
This general purpose source template should suffice for most any published work, including articles from journals, etc. All names should be entered “surname, given”. Use either
[SUBTITLE]
or
[TITLE]
of the publication depending upon whether you want quotes or italics. Normally I use only one or the other, but for a published collection of articles, the article title is entered in the
[SUBTITLE]
field and the name of the publication in the
[TITLE]
. NOTE: A true subtitle should be entered in the same Source Element with the title, following the title and separated by a colon. Use
[SUBJECT]
and/or its correspoding
[LOCATION]
, or
[SECOND PERSON]
and/or its corresponding
[SECOND LOCATION]
, depending upon whether you want quotes and this MSL entry is specific to a person or topic. If this specific source record is for only part of a publication, these fields can be used to indicate the portion of the work, e.g. pp. 287-291. They are not included in the Short Footnote template as the
[CD]
is likely to indicate the specific portion. If you cite multiple subjects/locations from the same publication and wish to have a single Bibliographic entry in TMG reports for the publication but separate source records in the Master Source List for each subject/location, use the “Published work - combined” template below.
[ORIGINAL DATE]
is used for the item’s date since
[PUBLISH DATE]
is already in the
[DATE]
group. If any of
[PUBLISHER ADDRESS]
,
[PUBLISHER]
or
[PUBLISH DATE]
is entered, you must enter something in all three to make the punctuation work.
[REPOSITORY]
is unconditional to ensure “unknown repository” if I do not enter it. The custom element
[PSEUDO PERSON]
in the Pages group is used to link to a Source Pseudo Person if one is created for this source.
29
If I am linking to a Pseudo Person I should have a
[TITLE]
. Source groups in use: A, C, D, D2, En, L, L2, P2, Pb, PL, Pg, RA, Rp, RR, SbT, Sj, Sr, T, Vm.
various to match type of work)
This source template is the same as “Published work” above, but will combine
30
multiple separate source records for each subject/location in the Master Source List for this same published work into a single Bibliographic entry in TMG reports. Indentical Source entries in Source pages will
not
be combined by Second Site, so this template should be used with care if your output is to Second Site and thus I no longer use it.31 It removes the subjects and locations from the TMG Bibliographic entry but leaves them in the footnotes. All names should be entered “surname, given”. Use
[SUBTITLE]
and/or
[TITLE]
of the publication depending upon whether you want quotes or italics. Normally I use only one or the other, but for a published collection of articles, the article title is entered in the
[SUBTITLE]
field and the name of the publication in the
[TITLE]
. NOTE: A true subtitle should be entered in the same Source Element with the title, following the title and separated by a colon. Use
[SUBJECT]
and its correspoding
[LOCATION]
, or
[SECOND PERSON]
and its corresponding
[SECOND LOCATION]
, depending upon whether you want quotes, but these are output only in the footnotes.
[ORIGINAL DATE]
is used for the item’s date since
[PUBLISH DATE]
is already in the
[DATE]
group. If any of
[PUBLISHER ADDRESS]
,
[PUBLISHER]
or
[PUBLISH DATE]
is entered, you must enter something in all three to make the punctuation work.
[REPOSITORY]
is unconditional to ensure “unknown repository” if I do not enter it. The custom element
[PSEUDO PERSON]
in the Pages group is used to link to a Source Pseudo Person if one is created for this source.
32
If I am linking to a Pseudo Person I should have a
[TITLE]
. Source groups in use: A, C, D, D2, En, L, L2, P2, Pb, PL, Pg, RA, Rp, RR, SbT, Sj, Sr, T, Vm.
various to match type of record)
This template is for types of records for which I have not defined a specific template and are published in multiple volumes.
[COMPILER]
defines either the compiler or editor of the series and is entered “surname, given” as are all name fields. Since this is a multi-volume source,
[TITLE]
and
[VOLUME]
are unconditional fields and specify the title of the series and how each volume is sequentially identified.
[SUBTITLE]
is optionally used for the name of the specific volume if it differs from
[TITLE]
. If the record interleaves different types of entries in a single volume, e.g. a register of events chronologically or multiple types of records in a volume, put the type of entry at the beginning of the
[CD]
. The
[CD]
is optional to permit this template type to be used when these records were searched, but no information found, which would be explained in the
[CM]
. If the title is short and there is no sub-title, duplicate it in
[SHORT TITLE]
which avoids the “Cited as” phrase. Otherwise shorten the title and/or combine it with any subtitle in
[SHORT SUBTITLE]
for use in the SF which will produce a “Cited by” phrase. Only enter one or the other of the
SHORT
variables. Since this is a published series,
[PUBLISHER]
is an unconditional field. Source groups in use: C, Cp, D, SbT, ShSb, ShT, Pb, PL, RA, Rp, RR, T, Vm.
SCHL
This source is for an individual certificate or document of associated with schooling.
[TITLE]
is the kind of document, e.g. School Registration.
[RECORD TYPE]
gives specifics about the document, e.g. Certified Copy.
[LOCATION DETAIL]
is the entity or specific office within the jurisdiction that issued the certificate or document, usually the name of the school. The
[JURISDICTION]
is the area covered by the issuing entity. For the U.S. it will typically be a local school district or the state where the college is located and I will not include USA, in other countries it will typically be something equivalent, such as parish in England, but I then follow with the more full location and country name.
[FILE DATE]
is issue date of the document. The actual date(s) (and if identified the location) as well as the personal details of the schooling event is in the
[CD]
. Custom source elements:
[DATE OBTAINED]
in the Second Date group,
[LOCATION DETAIL]
in Second Location which permits having the detail before
[JURISDICTION]
in FF and SF, but after in B. Source groups in use: C, D, D2, FN, L, L2, RA, Rp, RR, RT, Sj, T.
For this type of source, see my own Passenger List template.
SSAN
I made the
[SUBJECT]
,
[FILE NUMBER]
and
[CD]
optional so I could cite the SSDI without them but with a
[CM]
indicating that the index was searched but an entry was not found. Source groups in use: C, D, En, FN, Pb, PL, RA, Rp, RR, ShT, Sj, Sr, T.
|
[NAME OF PERSON] entry, [TITLE], [LOCATION]<, [CD]>; [REPOSITORY], [REPOSITORY ADDRESS]<. Cited as [SHORT TITLE]>. |
|
|
[COMPILER ADDRESS], [TITLE]<, [VOLUME]>, [REPOSITORY], [REPOSITORY ADDRESS]<, [CD]><. Cited as [SHORT TITLE]>. |
|
|
[COMPILER ADDRESS]. [TITLE]. [REPOSITORY REFERENCE]. [REPOSITORY], [REPOSITORY ADDRESS]. |
|
[TESTATOR] will< ([DATE])>, [TITLE] [FILE NUMBER], [REPOSITORY], [REPOSITORY ADDRESS]<, [CD]><. Cited as [SHORT TITLE]>. |
|
|
[REPOSITORY ADDRESS]. [TITLE]<, [DATE]>. [TESTATOR]. [REPOSITORY]. |
There was lots of discussion about what is the repository and what is the source, and whether to “lump” or “split”, this type of recorded data, with lots of suggestions
33
on the TMG-L ListServ. Instead I choose to use my Burial Certificate source type, but identify the
[TITLE]
as a “Gravestone” for those gravestones which I have seen, and my Electronic Database source type for tombstone data which I cannot verify and that may exist solely on a site like
FindAGrave
.
I considered this example, and then constructed my more general purpose Published Work template to fulfill this need..
[TITLE]
would be the type of personal record concerning this individual, e.g.
Delayed Birth Certificate.
[NAME OF PERSON]
should be entered “last name, given” like all names. Instead of this general type, I decided to use the type of record as the template, e.g. Birth Certificate. This kind of source could also be entered associated with the issuing agency of the document.
• Phone Call - Rather than a separate type, I have included this as either part of my Correspondance type or my Interview type depending upon the nature of the call with the
[RECORD TYPE]
specified as “by phone”.
•
MINE [knowledge/conclusion/assumption/wild guess]
if I have a separate document that records my comments. While I haven’t created this as a separate source type, nor entered such a source yet, I am more likely to use either the Interview type with myself as the Informant, or an unpublished Manuscript type for my own document. However, I plan to use the Abbreviation as shown.
• Record-Index (e.g. SSDI) - I have defined a separate type for the SSDI, and this type could be a model if I needed a general type for indices.
1. Elizabeth Shown Mills, Evidence! Citation and Analysis for the Family Historian (Baltimore: Genealogical Publishing Co, 1997). Elizabeth Shown Mills, Evidence Explained: Citing History Sources from Artifacts to Cyberspace (Baltimore: Genealogical Publishing Company, 2007).
2. As stated in TMG Help: “Source templates are constructed by Wholly Genes, Inc., according to our particular interpretation of the style guides mentioned above and are not intended to suggest endorsement on the part of their authors, nor do we warrant that they accurately reflect the intentions of those authors. Users are encouraged to consult the style guides in question to ensure proper usage.”
3. My personal copy is: The Chicago Manual of Style , 13 th edition, Revised and Expanded. Chicago: University of Chicago Press, 1982.
4. Elizabeth Shown Mills, Evidence Explained: Citing History Sources from Artifacts to Cyberspace (Baltimore: Genealogical Publishing Company, 2007) section 2.2 page 42, “Among these options, The Chicago Manual’s Humanities Style has been the most effective for history researchers. Evidence Explained is rooted in that style.”
5. Diane L. Garner; Diane H. Smith. The Complete Guide to Citing Government Information Resources: A Manual for Social Science and Business Research , 3rd ed., revised edition, by Debora Cheney for the Government Documents Round Table, American Library Association. Bethesda, MD: Congressional Information Service, 2002. Garner citation style based on ANSI bibliographic standards.
6. Mills, Evidence , section 6.14 page 263, “While Evidence adheres to NARA Style for manuscripts , Evidence Style citations follow most presses in using a simpler format for microfilmed censuses.”
7. I need to also explore the Scottish Old Parish Records citation “models” in March 1999, NGS Quarterly, Volume 87, described within an article by Dr. Helen Hinchliff “A Right to Bear Arms? …”
8. I started with TMG’s “Custom” templates that are based on Mills. While this template list, its format, and many of the examples, were originally based on a web page published on-line by Lee H. Hoffman, which I shamelessly copied and to whom I am indebted, many of the templates and the examples have been altered, sometimes greatly, to reflect my taste.
9. Elizabeth Shown Mills, Evidence Explained: Citing History Sources from Artifacts to Cyberspace (Baltimore: Genealogical Publishing Company, 2007) section 3.4, page 119, “Your First Reference Note ... almost always will be a fuller citation than the entry in your Source List.”
10. The Chicago Manual of Style , 13 th edition, section 17.2, “A source should be given a full reference the first time it is cited in a book or article, unless it appears in an alphabetical bibliography at the end of the work.”
11. Ibid., section 15.84, “When a bibliography is intended to direct the reader to other works for further reading and study, an annotated bibliography is useful.”
12. Chapter 7, Getting the Most Out of The Master Genealogist , compiled and edited by Lee H. Hoffman
13. See the archives of the TMG-L listserv for repeated discussions of the pros and cons of “lumping” versus “splitting” sources and other TMG entities.
14. My notes clearly show this combining of entries with identical text “used to” occur in Bibliographies, but recent testing in the final TMG V9.05 does not seem to perform this combining. Further testing is required.
15. Even if Second Site source options for Data / Sources are set to Show Sources and use the Bibliography template for the Source Sentence, Second Site will not automatically combine Source entries with identical text. Each TMG Source Record will be separately numbered and output, and only the citations to that Source Record will link to this Source page entry.
16. Based on testing against Version 6.12 reported by Linda Kuhn on the TMG-L ListServ, the limit was the first six elements within the Bibliography template. I have not exhaustively tested this, but now can observe sorting at least through eight template elements. If there is a limit, it may now be a total number of characters rather than a number of Bibliographic elements. Need to test in the final Version.
17. I also adopted the custom of including the characters “(MJH)” at the end of the name of my template types to distinguish in the list of Source Types my very different types from those that were still quite similar to the original. While many TMG lists provide the capability to disable or deactivate entries instead of delete, it is not possible to deactivate a specific Source Type only delete. Need to test and verify in the final Version.
18. Need to test and decide whether to add to these headings the abbreviation code to be used for every source type, not just for my modified source templates. Since currently my modified templates are the only ones I use, as of 5 March 2013 I have so far chosen not to do so.
19. In previous versions beginning with Version 6.12 and including Version 7, citing this source type, whether normally or as an embedded citation, still produced a numbered footnote or endnote citation. The citation text did strip the exclusion markers but now the text output consisted of only a period. Need to test in the final Version.
20. As of Version 8, full footnote output is affected by leading exclusion markers in combination with the Miscellaneous/”Show excluded data” report option. If the FullFootnote template begins with a double exclusion marker, or begins with a single exclusion marker and “Show excluded data is not checked, this source is simply never output at all, neither for any full nor short footnote/endnote nor the Bibliography. In this case the presence or absence of a leading exclusion marker in the ShortFootnote template has no affect on producing that output. Since the first full footnote form is never produced, neither a short footnote nor an Ibid is ever attempted.
If the FullFootnote template and report options cause a full footnote or endnote to be output, but the ShortFootnote template has leading exclusion markers, those exclusion markers and options will affect the short footnote output. If the full footnote is output, but the ShortFootnote template begins with a double exclusion marker, or begins with a single exclusion marker and “Show excluded data” is not checked, the short footnote data is not output but a numbered footnote or endnote citation with only a period as data is output. It is not clear that such an empty short footnote is useful.
While exclusion marker behavior with the footnote templates now seems predictable, I still wish there was a way to include a Bibliography only source. Maybe an option on the Source Definition? Need to be creative when testing for this capability in the final Version.
21.
If the
PageLink
structure is placed as text in the template, Second Site will not recognize the code. Second Site HELP only mentions using this code in memos, but it will work in this Source Element as an undocumented feature. The interaction between TMG codes and Second Site codes is complex. I tried nearly all combinations of structure and order to find both what would work in Second Site and what would look good both when there was
PSEUDO PERSON
text and when there was not.
22.
The Second Site
PageLink
structure must be entered as text in the element and not in the template, otherwise Second Site will not recognize the code. Second Site HELP only mentions using this code in memos, but it will work in this Source Element as an undocumented feature. The interaction between TMG codes and Second Site codes is complex. I tried nearly all combinations of structure and order to find both what would work in Second Site and what would look good both when there was
PSEUDO PERSON
text and when there was not.
25.
Besides Mills’
Evidence Explained
, two on-line references I find useful for citing electronic resources are:
The Columbia Guide to Online Style
https://cup.columbia.edu/book/the-columbia-guide-to-online-style/9780231132107
and the
Internet Citation Guide for Genealogists
originally posted on the ProgGenealogists web site but now only available from the
Internet Archive WayBackMachine
http://web.archive.org/web/20140718005750/http://www.progenealogists.com/citationguide.htm
26. This proposed source type is similar to the Bibliography Only source type.
27.
Unfortunately if the entire
[LOCATION]
is left blank the “unknown location” prints first, and TMG leaves it with lowercase. In previous versions the text code FCAP did not work in a source template. As of Version 8.05 the code works in the output, but the codes display in the Output form Previews. I could force capitalization for
[LOCATION]
with this code, but it would produce “Unknown Location” and would also prevent initial lowercase of interior words in an actual location. Need to consider and try more options and test in the final Version.
28.
Unfortunately if the entire
[LOCATION]
is left blank the “unknown location” prints first, and TMG leaves it with lowercase. In previous versions the text code FCAP did not work in a source template. As of Version 8.05 the code works in the output, but the codes display in the Output form Previews. I could force capitalization for
[LOCATION]
with this code, but it would produce “Unknown Location” and would also prevent initial lowercase of interior words in an actual location. Need to test in the final Version.
29.
The Second Site
PageLink
structure must be entered as text in the element and not in the template, otherwise Second Site will not recognize the code. Second Site HELP only mentions using this code in memos, but it will work in this Source Element as an undocumented feature. The interaction between TMG codes and Second Site codes is complex. I tried nearly all combinations of structure and order to find both what would work in Second Site and what would look good both when there was
PSEUDO PERSON
text and when there was not.
30. My notes clearly show this combining of entries with identical text “used to” occur in Bibliographies, but recent testing in the final TMG V9.05 does not seem to perform this combining. Further testing is required.
31.
Even if the elements which would output differentiating text are surrounded with
[HID:][SS:]
text
[:SS][:HID]
, TMG sees these Bibliography entries as different and separately outputs them, even though the output is identical.
32.
The Second Site
PageLink
structure must be entered as text in the element and not in the template, otherwise Second Site will not recognize the code. Second Site HELP only mentions using this code in memos, but it will work in this Source Element as an undocumented feature. The interaction between TMG codes and Second Site codes is complex. I tried nearly all combinations of structure and order to find both what would work in Second Site and what would look good both when there was
PSEUDO PERSON
text and when there was not.
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-2018. All rights reserved.