And if you are mixing generic and templated sources, in addition to the points noted above, the different handling of repositories can create complications when viewing the source record window, or querying sources, because there are two fields that could be relevant.<\/p>\n
We don’t recommend mixing the two types of source, because of the potential inconsistencies of presentation, but if you choose to do so, it is possible to configure templated sources to use the generic repository field.<\/p>\n
Actually, it’s already present for all templated sources, just not visible by default (as are all generic source fields).<\/p>\n
There are also advantages in using the generic repository field for templated sources, even if you are not also using generic sources: it simplifies export to other programs and website (although it does not eliminate all the compatibility issues associated with templated sources); and it retains compatibility with older queries.<\/p>\n
Warning<\/strong>: it will be a hard work to arrive at a consistent way of working with templated sources and the generic repository field if you have already created a lot of templated sources without it. It is best embarked upon as part of the process of deciding how to use templated sources, before you start creating any sources. It will also be much easier if you create your own source template definitions, either from scratch or by cloning definitions provided with FH (because the standard template definitions cannot be edited).<\/p>\n Note:\u00a0<\/strong>Some source templates (e.g. in the Advanced collection) may have multiple Repository metafields. GEDCOM 5.5.1 supports multiple instances of the generic repository field, but that scenario isn’t addressed in detail here.<\/p>\n Please read the whole article before making any changes!<\/p>\n To swap from using template repository metafields to generic repository fields, you need to:<\/p>\n In the Property Box for a Source record:<\/p>\n Your property box for a templated source will now show the generic repository field (highlighted in green ) and probably also a template repository metafield (highlighted in orange). You can tell the difference between the two because the template metafield is prefixed by a bullet and the generic field is not.<\/p>\n And if you now go to Prepare a Citation<\/em> via the scroll item on the main toolbar, you will see that this change has been made in the Citation window as well.<\/p>\n<\/div>\n Now go to the Source Record Window. <\/em>Right-click anywhere on the column headers and choose Configure Columns<\/em>.<\/p>\n Check if there is already a Repository column present. if it exists, use Edit<\/em> to check that it refers to If it doesn’t exist and you want to display the Repository, choose <Other> <\/em>in the left hand pane, enter a name for the column (usually Repository) and click Insert Data Ref..<\/em>. In the dialog that appears, choose Repository<\/em> ( This only applies if you have already created some templated sources.<\/p>\n To transfer the repository data from templated repository metafields to the corresponding generic repository field, you need to open each Templated Source in turn and cut-and-paste the data between the two fields (from<\/strong> the template metafield prefixed with a bullet to\u00a0<\/strong>the generic field which does not have a bullet.). It should be possible to automate it with a simple plugin, but there isn’t one publicly available.<\/p>\n Make sure you complete the data transfer before adjusting any templates, so that you don’t inadvertently lose data.<\/p>\n<\/div><\/details><\/div>\n The standard Source Template Definitions cannot be edited, so you must first clone all the standard templates you use or intend to use via Tools > Source Template Definitions<\/em>, then Clone<\/em>. Chose a meaningful name for the custom collection that will help you remember where they came from — e.g Custom Essentials For each template you create, use Add to Project<\/em> to make it available for use.<\/p>\n Next, you must edit any sources you’ve already created using the standard templates to use their custom equivalents.<\/p>\nSteps In Outline<\/h2>\n
\n
\n
Make Generic Repository Field Visible<\/h3><\/summary>
\n
![\"\"](\"https:\/\/www.fhug.org.uk\/kb\/wp-content\/uploads\/2024\/09\/Screenshot-2024-09-03-125532-1024x737.png\")
<\/p>\n<\/div>\n![\"\"](\"https:\/\/www.fhug.org.uk\/kb\/wp-content\/uploads\/2024\/09\/Screenshot-2024-09-03-130837-1024x883.png\")
<\/p>\n<\/div>\n%SOUR.REPO[1]>%<\/code> and change it it if doesn’t (for the template metafield it will be something like %SOUR.~RP-REPOSITORY>% <\/code>where the element after ~ may vary if the Repository metafield has a different name.<\/p>\n%SOUR.REPO[1]>%<\/code>) and click OK<\/em>. Then click Add<\/em>, and position the column using the up and down arrows before finally clicking OK<\/em>.<\/p>\n<\/div>\n![\"\"](\"https:\/\/www.fhug.org.uk\/kb\/wp-content\/uploads\/2024\/09\/Screenshot-2024-09-03-133332-758x1024.png\")
<\/p>\n<\/div>\n<\/div><\/details><\/div>\nTransfer Repository Data<\/h3><\/summary>
Convert Standard Templates to Custom Templates<\/h3><\/summary>
![\"\"](\"https:\/\/www.fhug.org.uk\/kb\/wp-content\/uploads\/2024\/09\/Screenshot-2024-09-05-191340.png\")
<\/p>\n<\/div>\n![\"\"](\"https:\/\/www.fhug.org.uk\/kb\/wp-content\/uploads\/2024\/09\/Screenshot-2024-09-05-191552.png\")
<\/p>\n<\/div>\n