Family Historian User Group

I assume that objective only applies to the current Generic only plugin.
Once custom Source Templates are involved that objective is impossible.

The only other option is it might be possible to adjust the wording by using a custom Language Pack to 'translate' some words in the report, but that is an advanced technique.

RM treats those items as facts, so allows all the usual subsidiary fields such as Date, Place, Note, Sort Date, Media, Citation, etc. Some are disabled by default but can be enabled and some are unlikely to be used in practice. When exported to GEDCOM those subsidiary fields are invalid and raise er...

If the field definition is known then a Query can filter on its Data Ref, e.g. %SOUR.~UL-ORIGINAL_SOURCE_FILE%

However, a general purpose search is not possible with a Query.
It would need a custom plugin to compare Source Template field definitions with Source record fields.

Coping with various templates is certainly key.
Seeing some examples will help but if you only cope with those variants the plugin may not cope with the next user customised variant. So I think the trick is to allow your plugin data set to be mapped to the template metafields by the user.

Why not start with the FH Essentials collection Civil Registration Index template?

Welcome to the FHUG. I suspect the FH direct import process is treating the Reference No attribute as a special case. By default, it has no Date or Place details so it is converted to the standard GEDCOM/FH Custom Id field. Even RootsMagic exports it to GEDCOM as a Custom Id REFN field. To refer to ...

I found the behaviour was not entirely consistent. However, the position of the cursor certainly affects its visibility. It may be due to subtle differences in the OS - I'm running a native Windows 10 desktop. I suspect it is an IUP bug rather than an FH bug. It might have to be reported to the IUP ...

The 'Add GRO Index Source Citation' plugin does not use that form of 'template'. It uses Plugin Data 'sticky' settings much like many other plugins have custom 'sticky' settings that are chosen by the user and preserved from run to run. The plugins that Helen refers to were written before FH V7 and ...

The invisible cursor problem seems to depend on where the cursor is located initially. If the cursor is outside the plugin dialogue window then Alt + arrow may cause it to vanish. If the cursor is inside the plugin dialogue window it never vanishes! It seems like a bug, but is probably in the IUP sc...

There may be some slight confusion in using the word template in the context of generic Source Citations. Generic Source Citations have a structure, just like all other FH/GEDCOM data, but no template is involved. Using the word template in this context may confuse readers. The aspect that uses expr...

OK, understood, but do consider using =TextPart(...) as it separates on commas by default.

Do all the fields on a Generic Sources map to standard GEDCOM fields that the majority of Genealogy programs should interpret correctly? See KB GEDCOM Extension List for non-standard GEDCOM fields. For Source records, I think the only one is the Source Type (SOUR._TYPE) field. Are there any good Kn...

I was less concerned about the number of commas than the order of the given/surname. In your latest example: "1939 Register, Bloggs Fred" the surname is before the given name(s). Whereas, the OP had "1939 Register, John William Wardle" with the surname after the given name(s). It...

Yes, the customisation of Tools > Preferences > Sources > Generic Source Formats... applies globally.

I chose a simple trigger string of "GRO " that must appear at the start of the Title in position 1 just as an example.
The trigger could be made more stringent if necessary.

If one turns on "Text from Source" for the Footnotes in the Generic Citation Configuration Menu, then the Mother's Maiden Name or Age at death will appear in the citations. This makes it immediately visible; something we chatted about earlier. I'm not well-enough versed in Generic Sources...

In that SCI Birth example, the child's surname precedes the given names in all the Format expressions. That would allow the =Section(...) function to extract the name with surname first as your OP requested. However, the "1939 Register, John William Wardle" title shown in your OP does not ...

When discussing the use of the Citaion specific local Note... John; I'm not sure that how the concept would work is a function of templated or non-templated sources. It is likely more a function of whether the user-template was written to use splitting or lumping, as templates can be used for both. ...

I've moved this to the Sources, Citations & Repositories forum that is more appropriate. In the Essentials collection, the Directory/List template has the Description: One source record per directory or list, including electoral rolls, phone books, city directories, trade directories, passenger ...

In your OP you mentioned a Source Template, so what is the Record Title Format expression? It may be possible to rearrange the given/surname details using that expression so the surname is first. Then the =Section(...) function or a =TextPart(...) function would be able to extract the surname first ...

To populate the Short Title field from the Title field of existing Source records will require a simple custom plugin.

This gets all the names into the correct order but it does not include spaces between the names i.e. WardleJohnWilliam But that does not cater for a variable number of Given Names as requested in the OP. The 'solution' must cater for each of: 1939 Register, John William Wardle 1939 Register, James ...

You have forgotten to cater for the space characters and specify a space as the section separator. e.g. =Section( Section( %SOUR%, 2, ", " ), 2, " " ) However, I cannot think of an easy way to extract the last section to display just the surname. The =TextPart(...) function allow...

Great option for those who don't use formal citations and just want the information recorded in their FH project. You still get formal Footnote citations which in this case the default would be: GRO Death Index. 1910 Q3 West Ham V:4a P:81. Cit. Date: 8 May 2024. There is also a Short Footnote and B...

The =Relationship(FileRoot(),,TEXT,1) function gives that information along with all the other family relationships for the File Root person. It can also work for other root individuals. See the standard Query > Relatives and Relationships > All Individuals > Relationship to Root column. A similar c...