* Source Title Preference

[Chrisv]

I would like to get the Opinion of folks that have a lot more experience in general and specifically with FH about the best way to structure your Source Title that shows in the Source Records list.
I used to be a typical RootsMagic lumper (since that is the way RM is pretty much set up) and have recently been convinced to become a FH splitter, depending on the situation. This is definitely NOT a lump vs. split discussion - Rather, I would like different opinions on how to phrase the Source Records Title using the Record Title Format in the Source Template Definition Editor.
At this point not opined in any direction, but just for instance, In the past, I structured all my source titles with the following structure:

US - Birth Records - MI, Ottawa County, Grand Haven
US - Marriage Records - WI, Racine County, Sturtevant
US - 1910 Census - MI, Kent County, Moline
Neth - 1880-1890 Pop. Record - Friesland, Achkterspelen, Surhuisterveen
Neth - Death Record - Groningen, Oldhove

With FH, I have experimented with a few of the automated Record Title structures (I definitely want it to be automated) but I'm not happy with any of the outcomes, and since I am leaning more toward a splitter mentality, I think I need to include the Principal Person(s) in the title and some form of the Location - but in what order for sorting purposes and what shortcuts or tricks are there to structure the Title in the best manner?

I tried sorting with the Event Type, Location, Person - but the Location was too long and placed the Person too far to the right in the Source Records list - and is sorting by Location better than sorting by Person when using predominantly split sources?
What works best for seasoned researcher using FH?
Thanks for your input!

[ADC65]

For Certificates, I use [Certificate Type] - [Person], e.g.:

Birth Certificate - JONES, David Evans
Marriage Certificate - JONES, David Evans & SMITH, Mary Jane
Death Certificate - JONES, David Evans

In some cases I add a date of birth to distinguish between two people with the same name

Birth Certificate - JONES, David Evans (b1868)
Birth Certificate - JONES, David Evans (b1902)

For census records, I use the location rather than person name:

UK Census 1861 - England, Hannington, Hannington Bridge
UK Census 1901 - Wales, Caerphilly, 3 Mardy Cottage
US Census 1940 - Massachusetts, Bristol, Berkley Town, Hill Street

Where there is more than one schedule for a page or an address, I include that:

UK Census 1921 - Wales, New Tredegar, 11 Farm Terrace (Schd 62)
UK Census 1921 - Wales, New Tredegar, 11 Farm Terrace (Schd 63)

UK Census 1911 - England, Bristol, Crews Hole Road [Page 150]
UK Census 1911 - England, Bristol, Crews Hole Road [Page 153]

For other records I normally use the form [Record Type] - [Person] - [Date] [Source]

Newspaper Report - DARKE, Joseph WH - 1926-11-12 Timaru Herald
Travel Record - HARRIS, Elizabeth Thirza & Family (1947-04-16)
Directory - BRADFORD, Blanche - Kellys Trade Directory 1902 Somerset
Marriage Announcement - PHIPPS, Winston Arthur & DAVIES, Phoebe (1930-04-23)

I name the media attached to the record in exactly the same way - it makes it a lot easier to find things.

[tatewise]

To give you something to consider, most Templated Source Records have common fields such as Type, Region, Principal, Date, Location, etc, that can be shown in Columns in the Records Window and will appear in other Source Record lists.
Such lists can be sorted by clicking any Column heading, so the order of fields in the Title Format is not so important.

[Chrisv]

Mike, that's interesting about using the different fields columns in the Records Window, but I don't understand how that is accomplished? I use Templated Records that use the Type, Principal, Event and Location fields, but in the Source Records view, the autogenerated Record Title shows only in the first column.
Can you point me in the right direction of what Help article will show me how to accomplish your suggestion?

You gave me some good idea's Adrian.
I like how your use different rules for different record types - as long as there is consistency within each type. I assume you do not use the autogenerated Record Title?? If you do use it, how do you get the customisation and the capitalised surname? (I do have the upper case surname option selected in the Preferences box).

[tatewise]

See FHUG KB How to Customise or Print Records Window or Named List Columns for background concepts.
It focuses on the Individuals tab but the same general rules apply to the Sources tab.
Use the Lists > Configure Record Window Columns... command or right-click a heading and choose Configure Columns....

In the Configure Columns for the Source Records List dialogue select <Other...> and add > to Columns.
The Heading will be the name of the metafield and the Expression is such as %SOUR.~PL-LOCATION% where the two letters in the PL position depend on the type of metafield and the rest is the metafield name in uppercase.
See Help page Understanding Data References under Data References And Metafields near the bottom.
You cannot use the << Insert Data Ref... button in this case of template metafields.

[Chrisv]

Wow!
This looks like a LOT of fun!
I will study, and experiment, and get back to you.

I am still interested in other's ideas and techniques for Source Title design configurations...

[fhtess65]

The more I learn about FH, the more I realize I've barely scraped its surface. I swear I need to take a sabbatical from work and just focus on my tree...a lovely dream indeed

See FHUG KB How to Customise or Print Records Window or Named List Columns for background concepts.
It focuses on the Individuals tab but the same general rules apply to the Sources tab.
Use the Lists > Configure Record Window Columns... command or right-click a heading and choose Configure Columns....
<snip>

[ColeValleyGirl]

The more I learn about FH, the more I realize I've barely scraped its surface. I swear I need to take a sabbatical from work and just focus on my tree...a lovely dream indeed

I said exactly that nearly 14 years ago, and retired (early) shortly afterwards. Still haven't managed to focus on my tree though!

[Chrisv]

I have successfully created 4 new columns! This is really nice!
Is there any way to change the order of a name or to abbreviate a location? For instance, a name is listed as Chad VEENSTRA and I would like it to read VEENSTRA, Chad. I guess one option would be to customise my Source template to have two fields for the Name, and then I could have two Columns for the name - or I could simply enter the name in the manner I want it to show up, but then it may look odd on reports?? It would also be nice to be able to abbreviate the place name. For instance, instead of it saying "Muskegon, Muskegon County, Michigan, United States" to say " USA, MI., Muskegon".
I know... I'm always wanting more...

[tatewise]

Several types of field have qualifiers that adjust their display. See Help page Understanding Data References under Qualifiers.
There are many qualifiers that format Names, Dates & Places. See if you can find them in the Help or Data Ref Assistants.

Assuming your person's name is a Name type of metafield then you can use the SURNAME_FIRST qualifier:
%SOUR.~NM-PRINCIPAL:SURNAME_FIRST% displays VEENSTRA, Chad

Assuming your place name is a Place type of metafield you can use the SHORT or MEDIUM qualifiers:
%SOUR.~PL-LOCATION:SHORT% displays Muskegon
%SOUR.~PL-LOCATION:MEDIUM% displays Muskegon, Muskegon County

I presume you realise you can change the width of any of the columns by dragging the dividers.
If you change the order of the Place name parts then they won't sort in the same order as say Place records.
Have you thought about using abbreviations in all your Place names, i.e. United States => USA, and every Sate uses its standard abbreviation.

[fhtess65]

Lol! I'm sure I'd find other things to amuse me as well, but, alas, short of a lottery win, no chance of early retirement...will soldier on for the nonce, working on my tree evenings and weekends

I said exactly that nearly 14 years ago, and retired (early) shortly afterwards. Still haven't managed to focus on my tree though!

[Chrisv]

Thanks Mike!
This is great! I appreciate you showing me these. It's exactly what I was looking for. I will also use them as learning templates along with the Help pages to continue experimenting.
Abbreviating the Place names sounds good. In RM, they "suggested" you stick with what Google Maps considered to be a correct Place and if you strayed from their standard, RM would give a warning screen where you could stick with the proper Place, or override the standard. I always assumed, by overriding it, the maps portion would not work properly - but I never found a need to test it. Long story, short (or not), it sounds like it's OK to change the Place for an abbreviation in FH. Good news!

Thanks!

[davidf]

It would also be nice to be able to abbreviate the place name. For instance, instead of it saying "Muskegon, Muskegon County, Michigan, United States" to say " USA, MI., Muskegon".
I know... I'm always wanting more...

>

Have you thought about using abbreviations in all your Place names, i.e. United States => USA, and every State uses its standard abbreviation.

There has been debate before about what to enter in Place Name fields - one view being that you enter what was on the document, thereby "preserving" what the writer intended - particularly in areas where the place "moved" (e.g. Alsace, (London)derry, etc.)

For this reason place standardisation was introduced as a feature. In V6 Tools, Work with Data, Places - then select a name and choose edit. I think most people put the current "gazetteer" name in the standardised box (I tried to use pre-1974 English counties here but got in a horrible muddle with "London Places").

There is no reason why the standardised name should not be abbreviated; "NYC, USA" - although I am unsure about the implications of leaving out "obvious" name elements ("NYC, USA" rather than "NYC, NY, USA" or "Oxford, UK" rather than "Oxford, Oxfordshire, UK" etc.)

In diagrams and queries etc. you access standardised placenames with the %INDI.BIRT[1].PLAC>STAN% syntax - which you can "pick from the list" when working with text schemes.

[ADC65]

I assume you do not use the autogenerated Record Title?? If you do use it, how do you get the customisation and the capitalised surname? (I do have the upper case surname option selected in the Preferences box).

I don't use Templated Sources, Chrisv, I only use Generic Sources. I find them simpler and less tiresome to enter rather than messing about trying to find the right Template. It does mean you have to type the Title yourself, but after a few thousand you get the hang of it

It looks like you have some very good advice from Mike and others on how to proceed with automation, if you need anything else from me on the subject please ask.

[Chrisv]

Thanks Adrian!
I do have a quick question. There is a place where you can delete any templates that you have brought into your project. I remember thinking at the time that it was in what I considered to be an odd place, and now I can't find it for the life of me. Any idea's?

[tatewise]

Source Templates are records and so listed in the Records Window on the Source Templates tab, where they can be deleted.

[ADC65]

Oh, I didn't know you could do that ... I use Tools > Source Template Definitions and delete them from the pop-up windows that appears.

The Tab on the Record Window didn't appear for me, although I did have one Custom Template defined. In Preferences > Records Window, I did have it set to Hide If None - but I would have thought it would have shown the Custom one.

[Chrisv]

Hi Mike,
I want to delete the actual templates (that I have been testing), not the record itself (see below). There was an area where this was possible by selecting delete on your keyboard. I'm getting too much junk in the selection box.

[ADC65]

Try Tools > Source Template Definitions (in case you missed my post)

[Chrisv]

I just found it.
It is View > Other Record Lists > Source Templates
Instead of deleting the template itself, it deletes (removes) it from the Project.
I can then go into where you are talking about to actually delete it from the Program.

[Chrisv]

So Mike,
You were absolutely correct! I did not have the tab for Source Templates.
Thanks for pointing me there.

[tatewise]

In Tools > Preferences > Records Window ensure all Record Type Display Options are Always Show as advised in FHUG KB Key Features for Newcomers under Records, Fields and Multimedia.