| ID |
Software - FTM |
| Name |
Family Tree Maker |
| Version |
?2011 |
| Vendor/Website |
http://store.ancestry.com/index.aspx?p=4825 |
| Platform |
Win |
| Default Template / GEDCOM friendly |
|
| Source System functionality (description) |
|
| Evidence Explained Support (Yes/No/comment) |
Yes |
| Other Named Styles Supported (list and comment) |
|
| Describe export mechanics |
|
| Other Source Data Challenges |
|
| QUAY (Yes/No/Comment) |
|
| Reported GEDCOM compatibility |
|
| Vendor Forum / User Group Archives |
Ancestry.com, "Family Tree Maker software" GenForum, "Using Family Tree Maker" |
| BetterGEDCOM Wiki Page(s) |
Family Tree Maker |
| Change (Date, by) |
2 April 2011, GeneJ; |
| ID |
Software - FTMM |
| Name |
Family Tree Maker for Mac |
| Version |
2010 |
| Vendor/Website |
http://store.ancestry.com/ProductDetail.aspx?P=P-4845 |
| Platform |
Mac |
| Default Template / GEDCOM friendly |
Default template exists and Citation Element are GEDCOM friendly; Customized Citation, however, reported in a custom tag "_Foot" |
| Source System functionality (description) |
Program includes a default template and also implements Evidence Explained (2007). FTMM's EE templates and elements can not be edited, but the user can make freestyle customizations (including applying formatting) to the template output. |
| Evidence Explained Support (Yes/No/comment) |
Yes |
| Other Named Styles Supported (list and comment) |
None observed |
| Describe export mechanics |
Test for EE - Book: Multivolume Set (Print Publication): fields for citation details and citation text exported to the corresponding field in GEDCOM; the balance of the Citation Elements exported to in TITL field with commas separating the various elements. Test for Default Template with Customized citation: Citation Elements exported correctly, but exclusive of any customization. The customized citation was reported in a custom tag, _FOOT. The only way I could find to format the book title was by customizing, so that formatting was lost on export. |
| Other Source Data Challenges |
|
| QUAY (Yes/No/Comment) |
Yes - appears based on a 5 point system of 0-4, with 0 being "no rating" FTMM allows users to choose from two "Rate Source Citation" approaches. (1) Based on "blue stars"--User can place up to 4 stars (so the rating is 0-4 stars, with zero being no rating; it includes space for the user to type a "justification." (2) "Use standardized ratings" includes the choices below--FTMM converts these by some mechanism to "Gold Stars" (0 to four stars). The Gold Star rating is output to GEDCOM. Source: Original or Derivative Clarity: Clear or Marginal Information: Primary or Secondary Evidence: Direct or Indirect. There is also a space for the user to type a justification. |
| Reported GEDCOM compatibility |
GEDCOM 5.5 |
| Vendor Forum / User Group Archives |
Ancestry.com, "Family Tree Maker for Mac Forums" |
| BetterGEDCOM Wiki Page(s) |
|
| Change (Date, by) |
2 April 2011, GeneJ; 2 April 2011, GeneJ (updated some proposed terminology) |
| ID |
Software - GB |
| Name |
Genbox Family History |
| Version |
3.7.1 |
| Vendor/Website |
Thoughtful Creations http://www.genbox.com/ |
| Platform |
Win |
| Default Template / GEDCOM friendly |
|
| Source System functionality (description) |
Citation templates are predefined for almost 100 source types. Users can define new ones. For each source type there are about 14 fields (Title, Author, Place, Dates etc.) and for 6 of these the field label can be defined by the user. The 14 fields can be considered as a built in master citation element list, where some (6?) have a grouping function because the label can be changed. Additional fields that apply to all source types can be used as citation elements. Dates and places are treated specially. There are additional predefined fields at the citation level. Default values can be defined for some fields. Source types can be defined to be within a higher level source type (cf. Gentech), and lower level sources can be linked to a higher level source. A lower level source could be an article and the higher level source the journal, similarly a book in a series of books, or a chapter in a book, or one of several documents on a CD. Some fields are not available for lower level sources, they are given by the higher level. For each source type the user can define templates for a Primary citation, Secondary citation and Bibliography. All built in source types and templates can be changed by the user. |
| Evidence Explained Support (Yes/No/comment) |
No |
| Other Named Styles Supported (list and comment) |
None documented. |
| Describe export mechanics |
Gedcom tags are used when appropriate, and proprietary _tags are used for other fields. |
| Other Source Data Challenges |
|
| QUAY (Yes/No/Comment) |
|
| Reported GEDCOM compatibility |
5.5 |
| Vendor Forum / User Group Archives |
Thoughtful Creations, GenBox Forum RootsWeb, "GenBox-L Archives" |
| BetterGEDCOM Wiki Page(s) |
|
| Change (Date, by) |
8 April 2011, GeneJ (added user links) |
| ID |
Software - RM |
| Name |
RootsMagic |
| Version |
4.1 |
| Vendor/Website |
http://www.rootsmagic.com/win |
| Platform |
Win |
| Default Template? / GEDCOM friendly? |
Default template, as such, not observed. User may create a basic generic template (author, title, date) as a custom source; but it is not GEDCOM friendly. Upon export, the template and source element data will export as that user created template will export exported to GEDCOM with custom tags |
| Source System functionali (description) |
Citation templates (called Source Templates) are predefined for almost 400 Source types, and users can define new ones. Templates have fields (of type text, name, date or place) which are elements in Footnote templates, Short footnote templates and Bibliography templates. A field is at the source level or source detail (citation) level. Field types (which are data types) are used to validate input, control output format or extract bits of the field (eg. only surname from a field of type name). There is no master list of common fields used in several templates - in the user interface, but field names in predefined built in templates are harmonized. Built in templates can not be changed. Templates may be categorized and can have descriptions. User defined (only) templates can be imported and exported from/to files. |
| Evidence Explained Support (Yes/No/comment) |
Yes |
| Other Named Styles Supported (list and comment) |
The following scemes are referred to in the definition of built-in templates: E!, AQS, QS, QC, CYS, sec???, in addition to EE. From the help file: EE = Evidence Explained, QC = QuickCheck model in EE (QC-3 indicates a QuickCheck model in chapter 3), E! = Evidence!, QS = QuickSheet, CYS = Cite Your Sources. The extent of support for each style guide has not been checked. |
| Describe export mechanics |
RM exports some Citation Elements in standard GEDCOM tags, not in a very standard way. The source name goes in ABBR, and a few other elements are placed in standard tags. The text of a full footnote reference goes into the TITL. A short footnote and an bibliographical note are placed in proprietary fields. Two proprietary _TMPLT structures, one at the source and one at the citation level (where in source), contain source-value pairs for each element (field) for the source type, with the full name of the element as the type. An ID for the source type is stored in the _TMPLT structure in the SOUR record. |
| Other Source Data Challenges |
|
| QUAY (Yes/No/Comment) |
|
| Reported GEDCOM compatibility |
5.5.1 |
| Vendor Forum / User Group Archives |
RootsMagic, "RootsMagic Forums" |
| BetterGEDCOM Wiki Page(s) |
|
| Change (Date, by) |
2 April 2011, gthorud; 2 April 2011, GeneJ (mistakenly deleted, :(, re-added and expanded); 2 April 2011, GeneJ (updated some proposed terminology) |
| ID |
Software - TMG |
| Name |
The Master Genealogist |
| Version |
v7 (incl. v8 Public Beta) |
| Vendor/Website |
Wholly Genes |
| Platform |
PC |
| Default Template / GEDCOM friendly |
Testing now. |
| Source System functionality (description) |
Type: Applications that enable essentially full customization of both Citation Elements and Templates. TMG is packaged with 160 Citation Elements (called "Source Elements") users may create custom Citation Elements. TMG's templates are called "Source Types"; program comes packaged with Lackey and Mills template interpretations; users may create custom templates. In an "initialize process" Users can overwrite Source Types universally to select between Lackey or Mills. |
| Evidence Explained Support (Yes/No/comment) |
Not directly, but users are able to develop custom templates and custom Citation Elements, as needed, for that purpose. |
| Other Named Styles Supported (list and comment) |
Lackey, Mills, Evidence! (1997). [File>Preferences>Current Project Options>Other>Source Categories (for selections: Custom > Evidence > Lackey)] |
| Describe export mechanics |
TMG's Citation Elements (there are more than 150) are each associated with one of about 30 "Source Groups." When a GEDCOM is created, those Source Groups are further consolidated and merged into the available standard GEDCOM fields, without identification of each element. See message/view/EE+%26+GPS+Support/35991094 |
| Other Source Data Challenges |
|
| QUAY (Yes/No/Comment) |
Yes. A four point scale (0-3). TMG refers to this as "Surety" (or Max Surety); defined as, "judgments as to the reliability of that source with respect to the information derived from it" In Advance mode, the scale can be assigned to up to five citation related information parts (the two principals, date, place and/or memo field, from which the "Max[imum] Surety is determined by the Application. Users apply rating based on scale of 0 to 3 (a four point scale). |
| Reported GEDCOM compatibility |
GEDCOM v4 or GEDCOM 5.5; WhollyGene's is the creator of GenBridge (TM), which reportedly imports directly from FTM, Personal Ancestral File (PAF), and other programs. |
| Vendor Forum / User Group Archives |
Wholly Genes Community TMG-L (listserve) |
| BetterGEDCOM Wiki Page(s) |
Application Details - TMG |
| Change (Date, by) |
30 Mar 2011, GeneJ; 2 April 2011, GeneJ (updated some proposed terminology) 18 May 2011, updates per note from Geir |
| ID |
|
| Name |
|
| Version |
|
| Vendor/Website |
|
| Platform |
|
| Default Template / GEDCOM friendly |
|
| Source System functionality (description) |
|
| Evidence Explained Support (Yes/No/comment) |
|
| Other Named Styles Supported (list and comment) |
|
| Describe export mechanics |
|
| Other Source Data Challenges |
|
| QUAY (Yes/No/Comment) |
|
| Reported GEDCOM compatibility |
|
| Vendor Forum / User Group Archives |
|
| BetterGEDCOM Wiki Page(s) |
|
| Change (Date, by) |
ID
Name
Version
Vendor/Website
Platform
Default Template / GEDCOM friendly
Source System functionality (description)
Evidence Explained Support
(Yes/No/comment)
Other Named Styles Supported
(list and comment)
Describe export mechanics
Other Source Data Challenges
Reported GEDCOM compatibility
Vendor Forum / User Group Archives
BetterGEDCOM Wiki Page(s)
Change (Date, by)