{"id":11605,"date":"2020-09-30T11:08:07","date_gmt":"2020-09-30T11:08:07","guid":{"rendered":"https:\/\/fhug.org.uk\/kb\/?post_type=kb_article&p=11605"},"modified":"2024-02-22T11:21:37","modified_gmt":"2024-02-22T11:21:37","slug":"exporting-templated-sources","status":"publish","type":"kb_article","link":"https:\/\/www.fhug.org.uk\/kb\/kb-article\/exporting-templated-sources\/","title":{"rendered":"Exporting Templated Sources"},"content":{"rendered":"

Introduction<\/h2>\n

Family Historian Version 7 introduced Sources created from Source Templates, which are underpinned by \u0192h<\/span><\/span>-specific GEDCOM extensions which will not export readily to other products (such as website generators<\/a>, GEDCOM tools<\/a>, or other genealogy products and services). This article discusses the options available for exporting your GEDCOM including all the information you’ve entered about your Sources when you have created Sources from Templates.<\/p>\n

Note: There are other considerations when exporting and you should review Exporting a Family Tree with\/without Media<\/a> for full details.<\/p>\n

Family Historian Export Command<\/h2>\nFile > Import\/Export > Export > Gedcom File…<\/a> opens the \u0192h<\/span><\/span> Export Gedcom File<\/em> window:<\/p>\n
\"\"
Export Gedcom file<\/figcaption><\/figure>\n

This dialog is documented at Export Gedcom File Dialog<\/a> but there are some aspects to do with exporting Sources created from Templates that need particular consideration.<\/p>\n

If you’re exporting to Family Tree Maker (which has its own support for templated sources), choose Destination: Family Tree Maker<\/em>, accept the defaults offered relating to sources and review the output within FTM to make sure it meets your expectations. If not, move on to the next steps.<\/p>\n

If you’re exporting to \u0192h<\/span><\/span>6 or earlier, standard or strict Gedcom or using the Default settings, and\/or you intend performing further steps to anonymize your data and export to other destinations, you have two options:<\/p>\n

    \n
  1. Include all the Source-identifying information that you want to include in the export in the Source Title (by customising the Source Template<\/a> if necessary) and select Include<\/em> option. This will export a source record with the Title only, which may be all you need for a website generator or other GEDCOM analysis tool.<\/li>\n
  2. Review your Source definitions to ensures the Titles make sense and are unique. Use the Family Historian Export Command and (for Source Records) select one of the Include and Copy Metafields<\/em> options. If your destination can handle\/display multiple notes per Source, select Include and Copy Metafields to New Note <\/em>otherwise Include and Copy Metafields to First Note.<\/em><\/li>\n<\/ol>\n

    Unless you know that your chosen destination supports \u0192h<\/span><\/span>-style Source Template records, you should Exclude Source Templates<\/em>.<\/p>\n

    Both options 1 and 2 above will include the original source fields in the export, which may be handled differently by different destinations, so you should review the output in your chosen Destination to ensure that you’re happy with it.<\/p>\n

    Export GEDCOM File Plugin<\/h2>\n

    The Export Gedcom File<\/a> plugin handles exporting to more destinations than the \u0192h<\/span><\/span> File > Import\/Export > Export > GEDCOM File…<\/a> command, but relies on some of its features.<\/p>\n

    The plugin cannot Select Individuals or Exclude Private\/Tentative\/Rejected Facts. Users must use the File > Import\/Export > Export > GEDCOM File\u2026 <\/a> command to choose those options, and then open the resultant GEDCOM file in \u0192h<\/span><\/span> to run the Export Gedcom File<\/a> plugin. That process is described in the Exporting a Family Tree with\/without Media<\/a> article.<\/p>\n

    Using the plugin:<\/p>\n