Family Historian User Group

Hi, I have been building some new templates to configure my sources how I want them when I move data up to TNG. Unfortunately, the GEDCOM isn't including the link to repositories for any of the templated sources. I am only seeing the link to the repositories in sources created by Ancestral Sources. I have also tried some standard template sources and they don't export the REPO tag either.

Sorry that you are having a problem Julie.

Could you please update your Profile shown to the right of your posting to say you are using Family History V7.
Click your username, navigate to Edit Profile, select Family Historian V7, then scroll down to SUBMIT.

Please confirm you are using the Export Gedcom File plugin Version 5.1 and not the Export > GEDCOM File... command.
In the plugin have you set the GEDCOM Destination: to (TNG) The Next Generation ?
On the Extra Options tab, the Source Template 1 _SRCT: Move to Note Record settings should create Generic Repository (SOUR.REPO) data from any {Repository} template field. Remember that the {Repository} field must be of type Repository and not Text or Enum or Place.

Plug in was totally up to date updated it a few days ago. I totally reset the TNG settings as I had changed some. Repository is now back and I have redone the other changes I made.

I do have one query though as I had changed the SOURCE TEMPLATE option to Remove Entirely as it looks messy when uploaded. Not a big issue though as I can bulk delete the notes. However, I now get data like this:-

Name Recorded: George BEVIS
Quarter: June
Year: 1896
Registration District: Andover
Reference: 4V/56

Under the sources which again is a little messy for my liking, is there anyway to change the way it formats these fields on upload.

So I think you are saying the reason for the Generic Repository (SOUR.REPO) field going missing is that you chose the Source Template 1 _SRCT: Remove entirely setting. Now you have restored the Source Template 1 _SRCT: Move to Note Record setting the Repository fields are OK again. Is that correct?

You say that you now bulk delete the notes, so why does it matter what format those notes use?
Anyway, in what way would you want to change the format of those fields?

Respository fields fine now and they've notes that get created are easy to delete.

Now the issue is that the plugin outputs all the fields with field name on separate lines for the citation underneath the source name which looks awful. So what I want to know is can this the edited. These appear as notes attached to citations in TNG but don't appear in the list of notes that I can easily delete. What looks much better is copying Footnote to citation note in FH which then just gives a line of text under the source name.

If I understand correctly, it is only lumper method Citations that have templated fields which get converted to labelled Citation Notes, i.e. only the Civil Registration Index sources.

The one field label & value per line is the standard way that all kinds of fields get converted to labelled Notes, so it would be difficult to make those Citation Notes a special case.

Let me look at the Footnote to Citation Note idea which may be a feasible alternative.

Thanks if footnote to citation note would work it would be perfect and put in control of the creator. I have literally just copied it to the citation note after adding the source. Trying to keep sources as EE compliant as I can.

I had another idea overnight that is not so EE compliant but will be easier to implement in the Export Gedcom File plugin.
What if the Remove entirely option removed the Source Template record and all the Templated Fields as it does now, but created a Generic Repository (SOUR.REPO) entry from any {Repository} template field?
Then you would still have the Repository link you require and the Notes would be omitted.

I know the Footnote will not be included, but it has always been the case that only FH holds your comprehensive data and anything exported to another product will inevitably lose some data.

BTW: I have split the DEA discussion into the Record Civil Registration Data (UK) (21433) thread.

That sounds like a good compromise it's easy to copy the footnote into a citation note which will then display fine in TNG. That should resolve the issue.

Julie, please try the attached Export Gedcom File plugin Version 5.1.3 Date 11 Jan 2023 ZIP file.
It is a ZIP file because the raw Plugin is bigger than the Forum attachments limit.
So you must right-click the downloaded ZIP file and use Extract All...
Then double-click the extracted FH Plugin (Lua) Export Gedcom File.fh_lua file to auto-install it into FH.

This version has modified the Source Template 1 _SRCT: Remove entirely setting such that it creates generic Repository links from templated Repository fields before removing all other traces of the templated Source fields.

Thanks Mike I will try it this afternoon

Absolutely perfect Mike, thanks so much. As it stands without copying the Footnote text to the Citation Text from source you get the purple line. If you add the footnote to the Citation Text from source you get both the purple & red which is great.

1. [S6] England & Wales, Civil Registration Birth Index, 1916-2007.
"England & Wales, Civil Registration Birth Index, 1916-2007," database, Ancestry. Birth entry for Robert J Bevis; mother's maiden name: Golding; June quarter 1924, Kingsclere district, 2C/422. Original data: General Register Office. England and Wales Civil Registration Indexes. London, England

This is going to work really well for me once I have tweaked the footnote style a tad more, won't be perfect EE but close enough. Also it means I can identify which database I used for the birth index (so many these days) plus for the odd record I add to WikiTree I can cut and paste this citation which will satisfy them too.

Once I have finished the templates happy to upload somewhere if you think others may find them helpful. All depends on what they want their output to look like.

Thank you Julie. There are some other Export Gedcom File 'glitches' to investigate but when they are fixed I will update the plugin in the Plugin Store.

No probs, will keep an eye out for later updates but for now I am extremely happy with the fab change you have done.