Go through 5000+ photos and change the file name to the name I wanted in “Captions” and go through all the “Facts” that were in error which all of the above would have caused sufficient hair loss to require a hair transplant and/or four lens in my glasses instead of the three that now exist. Most programs would import my photos, after entering the location on my HD, but would not show the Photo Caption, as it appears in FTM Mac and on Ancestry, but only the photo file name. I have tried multiple programs with a combination of results: Most tried would import the GEDCOM but could not interpret the custom fields that I had entered into FTM Mac and some had problems with what I thought were standard fields. What I do know is a program that works in interpreting the GEDCOM and the Photo descriptions in Ancestry. What I know about about GEDCOMs is probably in a thimble. The Perils of Following the GEDCOM Standard About Keith Riggle Part 14: Should You Stick with Family Tree Maker?įamily Tree Maker to GEDCOM to Other Apps Crosswalk
The Family Tree Maker Alternatives Series Part 1: How to Scrub Your Data : Updated the web address in source citation from NOTE to _LINK for Family Tree Maker and updated source fields for RootsMagic. Updated version numbers of apps I have rechecked. : Updated the fields for Family Tree Maker 2019 and MacFamilyTree 8. : Updated the Also Known As and Submitter fields for Family Tree Maker based on versions 2014.1 and 3.1. Also added fields for Association, Event, and Fax Number for all apps.ġ4 Apr 2016: Added GEDitCOM II fields and GEDCOM tags (not shown in the image above).ġ9 Apr 2016: Added Brother’s Keeper 7 fields and GEDCOM tags (not shown in the image above). : Added Heredis 2015 fields and GEDCOM tags (not shown in the image above).ĩ Apr 2016: Added iFamily for Mac fields and GEDCOM tags (not shown in the image above). : Added Family Tree Builder 7 fields and GEDCOM tags (not shown in the image above). : Added MacFamilyTree 7 fields and GEDCOM tags (not shown in the image above). Added borders between apps for readability. : Added a column for “Generic Field Name.” : Added information about a FTM 2014 GEDCOM tag (not shown in the image above). : Added fields and GEDCOM tags (not shown in the image above). : Updated Reunion 11 fields and GEDCOM tags.Ģ1 Jan 2016: Added Family Historian 6 fields and GEDCOM tags (not shown in the image above). : Added Ancestral Quest 14 fields and GEDCOM tags (not shown in the image above). : Added Legacy Family Tree 8 fields and GEDCOM tags (not shown in the image above). : Added RootsMagic 7.0.10 fields and GEDCOM tags (not shown in the image above). : Added Reunion 11 fields and GEDCOM tags
We called the document that mapped the old manpower posts to the new ones a “crosswalk.” Now I see that its full name is a “ schema crosswalk.” Updates Every few years it seemed like we had to rejigger the manpower documents. I learned the term when I was a NATO personnel officer. Click the image above to open the crosswalk in DropboxĪ note on the term “crosswalk:” no, I’m not referring to a North American or Australian pedestrian crossing. Please let us know in the Comments if you find any errors. Items in yellow are custom fields, which may be problematic for some applications. Items highlighted in red are missing or handled incorrectly if the field name is highlighted, then it’s imported incorrectly into the app, while if the GEDCOM tag is highlighted, then it’s exported incorrectly to GEDCOM.
If you click on the image, it will open in Dropbox, where you can download it to your device. You can use it as a quick reference and as a checklist of fields that might require corrective action before or after you export your family tree to a GEDCOM.
As I complete my testing of each app, I’ll update the table. The table below maps most of the fields in Family Tree Maker to their GEDCOM 5.5.1 tag (at least how FTM exports them).