![]() ![]() For example, instead of displaying “0,” it displays “Unreliable.” Fig 1 Add Media to Citation – Doesn’t display numerical citation quality ratings, although it displays shortened versions of their their interpretation from the GEDCOM standard. – Stripped a valid “Y” on an event detail that had no date or place, essentially leaving it a blank event. There were two other UDF fields that this tool didn’t find, the EMAIL and WWW tags (see below). I again ran the Find Uncategorised Data tool that I discussed below, and there were still four UDFs found: _PHOTO, FACT, WAC, and FORM tags.FH changed this to an _EMAIL tag, which is a custom GEDCOM tag, even though EMAIL is a valid GEDCOM tag for an address structure in a repository record. I tested this feature and apparently had only one Uncategorised Data Field (UDF) that could be recovered, an EMAIL tag in a REPO record. One of the touted improvements of FH 6.1 is that it can “recover hidden data in existing Family Historian projects that were previously created by imports from Family Tree Maker or Ancestry” ( What’s New in Version 6.1).Consequently, it doesn’t support new tags like EMAIL and While it still imported most unrecognized data, it put them on the All tab of the Property Box, where they’re less visible. – It doesn’t fully comply with the GEDCOM standard 5.5.1, which is the latest standard, even though it supports the UTF-8 character set, which was not added until 5.5.1. It even imports FTM’s illegal ALIA tag by changing it to the custom tag _ALIA. ‘BET MAY AND JUNE 1914’).” This is a nice feature to preserve more of FTM’s data. ⋅ FH “now supports all date formats that Family Tree Maker saves dates in, even if not valid GEDCOM (e.g. ![]() However, note that standard GEDCOM tags EMAIL, PHONE, and WWW are included in this extended list-FH still doesn’t recognize them as the standard tags they are (see the Cons section and the GEDCOM Crosswalk table). The fact definitions for this set are hidden by default (“to avoid cluttering up the fact types list”) but can be accessed and modified if needed. ⋅ As of FH 6.1, all of FTM’s custom fields like Arrival, Circumcision, Degree, etc., are imported using what is called the Extended Set of Fact Types (as opposed to the standard set). ⋅ FTM’s custom tags for adopted relationships (but not natural birth relationships). ⋅ FTM’s non-compliant event descriptions by moving them to the custom tag _UNCAT subordinate to the same event. They are visible on the “All” tab of the Property Box. ⋅ FTM’s non-compliant CONC tags occurring after PAGE tags in source citations. + Preserves almost all data from an FTM GEDCOM, with the failures noted in the Cons section below. ![]() + Checks GEDCOMs not created by FH for errors, produces an import error log, and offers to open it for you be sure you do. One such tool is the “Find Uncategorised Data” list from within FH itself, which is useful for viewing what FH considers Uncategorised Data Fields (UDF), but see Cons below. + Has good tools and tips for importing FTM GEDCOMs in the two articles referenced above. Note: portions of text in all capital letters are GEDCOM tags, with the rest of the plain text field name in lowercase. ![]() Version Tested: Family Historian 6.1.4 trial version on Mac OS X using CrossOver 15. I could not test the plugin, as the trial version of FH does not allow plugins to be used, so use it with caution and keep a back-up copy of your original GEDCOM. These steps are also on the Family Historian User Group website in an article titled, “ Import from Family Tree Maker (FTM).” A step missing from the FH article is to open the sample project first so you can modify the preferences, as suggested. Also be sure to follow the steps in the article, “ Handling Uncategorised Data Fields.” Finally, FH user Barnowl has posted a plugin on their FHUG Form Post, “ Plugin to sort problems with FTM Imports,” which purports to correct many problems with FTM GEDCOM files. Users of and Family Tree Maker would do well to take some additional steps to ensure a larger portion of their data are imported. The first page in the guide on “The Project Window” shows where to import a GEDCOM file. Importing a GEDCOM file from FTM or any other app or website into Family Historian (FH) is fairly straightforward if you stick with the default options, but if you need help, FH has a “Quick Start Guide” on their website. ![]()
0 Comments
Leave a Reply. |