During last week's Researching with Geoff – Live! webinar, one viewer (Barbara) noticed that I entered the word "County" as part of Fanny Brown's death location and asked,
"Why write in the word 'county' when that position indicates it is the county?"
In addition to Barbara's good eye for detail, she must have known about some of the techniques I taught in the Mastering Legacy: Names, Dates, and Places training CD about proper data entry, but she overlooked one of the golden rules for data entry of locations:
Enter the location so that there can be no misunderstanding by novices or others as to the location being expressed.
In other words, when there is a chance that your data entry may be interpreted incorrectly, make the effort to make it clear with as much consistency as possible. For example, I entered Fanny Brown's death location as:
, Saint Louis County, Minnesota, United States
Following the "rule of commas" for locations – each part/jurisdiction of the location needs to be separated by a comma. So in this example, I added a comma before Saint Louis County to denote that I am missing the city (the next lower jurisdiction). For United States research, nearly every location can be entered as:
City, County, State, Country
When you are missing a part, such as the city, keep the comma there as its placeholder and enter the rest. Obviously this standard does not fit all countries throughout the world. When it does not, just be consistent. Use FamilySearch's Standard Finder for help.
Researchers with a good eye for detail would recognize this as Saint Louis County:
, Saint Louis, Minnesota, United States
But readers with less experience may interpret this as a city in Minnesota. What makes it more difficult is when they are reading this location as part of a narrative. Below is a snippet from Fanny's descendant book:
Fanny Belle BROWN, daughter of Martin C. BROWN and Mary Elizabeth JEFFREY, was born in Jun 1885 in , , Minnesota, United States and died on 21 Nov 1966 in , Saint Louis, Minnesota, United States at age 81.
Even worse, if before creating her book, you turned on the option in Legacy to "remove leading commas from locations" the snippet would read as:
Fanny Belle BROWN, daughter of Martin C. BROWN and Mary Elizabeth JEFFREY, was born in Jun 1885 in Minnesota, United States and died on 21 Nov 1966 in Saint Louis, Minnesota, United States at age 81.
Hopefully this visually explains why, when I am missing the city of a location, I add the word "County" to the county's name. By doing so, the snippet would read as:
Fanny Belle BROWN, daughter of Martin C. BROWN and Mary Elizabeth JEFFREY, was born in Jun 1885 in Minnesota, United States and died on 21 Nov 1966 in Saint Louis County, Minnesota, United States at age 81.
Barbara – I hope I answered your question. I didn't add the word "county" for me so much, but for the future readers of my research.
It would be very convenient if Legacy found a way for users to input two location names — historical and modern. Legacy recommends inputting the original location names. For example, my ancestor was born in 1886 in Vysoko-Litovsk, Grodnenskaya Guberniya, Russia. However, if I input that location, none of my mapping software programs recognizes it (and neither does Legacy’s Geo Location database). I have to input the name in its modern form (Vysoke-Litevske, , Hrodzyenskaya Voblasts’, Belarus). But by inputting the modern location name, I sacrifice my ancestor’s historical heritage. Can any one recommend a good workarond for this problem?