Legacy seminar in Fresno, California - November 21, 2009
What Happens When Cousins Marry?

How to best prepare for Legacy 7.5 and the FamilySearch interface - Post #1

We have previously announced that we are getting ready to release Legacy 7.5 - a free update which will add features to interface with the new FamilySearch Family Tree system. You can read all about it here. I'm most excited about the ability to be notified when anything new is found about an ancestor - without me even visiting the website.

This article is the first in a series of articles which will help you prepare your family file for better use with the upcoming Legacy 7.5 and its interface with FamilySearch. Even if you do not plan on synchronizing your data with FamilySearch, these articles will provide valuable insights on cleaning up and standardizing your data.

Important Principle. Researchers should be careful when publishing/sharing information from their family file with FamilySearch, or with any online database. If the information in your family file has errors, duplicate information, or inconsistent data, when that information is published/shared online, the online version will contain those same errors, duplicate information, and inconsistent data. A casual commitment to your personal data entry standards often results in negative unforeseen consequences, especially when publishing your data online.

For this reason, before interfacing with FamilySearch's new Family Tree system, we should all take a closer look at our data.

Tip #1 - Consistency in your locations

Take a look at your Master Location List in Legacy (View > Master Lists > Location). Does it contain more than one variation of the spelling of a place name? For example, in Legacy's sample family file, we intentionally spelled Minneapolis with five different variations to help you see a potential problem:

  • Minn., Henn., MN, USA
  • Minneapolis, Henn., MN, USA
  • Minneapolis, Hennepin County, MN, USA
  • Minneapolis, Hennepin, Minnesota
  • Minneapolis, Hennepin, Minnesota, USA

Publishing the inconsistent locations may eventually result in you/others not successfully finding what you are looking for because what you are searching for, and what is in the database are two different variations of the same place.

FamilySearch's new Standard Finder, which Legacy 7.5 will utilize, helps you achieve standardization in the way you spell your locations. Its goal is to help achieve consistency in how everyone records their locations. It is not a perfect system yet. For example, we know that correct data entry standards suggest to record the place as it existed at the time of the event. Standard Finder does not yet do a great job with correctly interpreting historical locations. But it has a great start.

Assignment #1 - standardize your locations

Clean up the duplicates and variations of your place names in your Master Location List. Legacy Family Tree makes this simple to do. We've created a video for you to see the step-by-step instructions on how to do this. Watch the video by clicking here.

Assignment #2 - clean up your country/county names

If these locations are not immediately obvious to you:

  • Victoria, BC
  • Carrick, LDY
  • Aberdeen, SCT
  • Paris, Bear Lake, ID

then the researcher has not followed the golden rule of data entry:

Enter your locations so that there will be no misunderstanding by other researchers as to the location you are trying to express.

Legacy Family Tree's Expand/Contract Location Parts tool makes it easy to correct common abbreviations, and for the United States, to add the country name to the end of its locations where it is missing. This tool is found by navigating to:

View > Master Lists > Location > Options > Expand/Contract Location Parts.


In the Parts to Work On section, place checkmarks next to the desired countries to "unabbreviate" the various country and county names.

For United States researchers, use the options in the USA Country Name section. To prepare for full compatibility with FamilySearch, select the Add ", United States" option. This will add this country name to the end of all U.S. locations. To clarify, it will not add "United States" to the end of Bristol, Gloucester, England. If you previously typed "USA" instead of "United States" this option will change "USA" to "United States". Now click the Continue button, and Legacy will update your list.

You're now closer to being ready to successfully work with Legacy 7.5. When working with the FamilySearch interface tools, you will no longer have to spend time "resolving" your place names to match the Standard Finder's version. Cleaning up your locations is just the first suggestion in your preparation. Stay tuned....


Feed You can follow this conversation by subscribing to the comment feed for this post.

How should a family-named or historic location be entered? Many people are born and die at historic houses and/or family farms with names such as "Pleasant Rest." For example - "Mount Vernon," Fairfax County, VA, USA. Should quotation marks not be used? Thank you.

Anne Leyden - although I don't have an authoritative answer to your question, I've not seen quotations in locations in any standards. I would likely go without them.

While correcting Master Locations which I sorted by 4th, 3rd, 2nd and 1st fields, I found a number of placeholders without leading commas which indexed out of sequence. I tried to shortcut data entry by using the Geo Location button when correcting and found for NEW ZEALAND it tended to want to put my City/Town , , New Zealand, rather than , , City/Town, New Zealand.
As we don't commonly use counties particularly in historical data, what is the recommendation?

You have answered my question about USA not being added to locations with "of" or "prob". However, the USA was added when these were attached to a city or county, but not a state. If the Family History Department has discouraged the use of these, it will cause a lot of inaccurate information.

You also answered my question about cemetery names. How do I put church names in front of the location, if I can't put cemetery names in front of the location?

And, what happens with locations in Germany where I have five or six parts of a location?

I must be newer at this than I thought....what is the guideline about the comma useage in locations. Sometimes there are spaces between the commas and I don't know if I accidentally put them there or if I was missing something. To refresh: each comma stands for a part of the location I don't know but in order to have it done correctly, I need to use one if for instance I don't have a county or if the location is a province instead of a state. How many are actually available? Is the number different if I am in Europe, Japan, etc?

The country now (and since 1922) is the "United Kingdom of Great Britain and Northern Ireland."
England, Scotland, Wales and so on are NOT countries in their own right any more - they are semi-autonomous regions - similar to how states are in the US.

However, saying that it seems the standard *is* to use England, Scotland etc as the top level identifiers, even for places identified since 1922. I'll be waiting for my English passport to arrive then.


Please pardon my ignorance but I'm assuming we have a choice as to whether we allow family search/IGI to access our information? I do NOT want my information uploaded to the net.

Disey - yes, it is entirely optional.

New Family Search uses the standardized term United Kingdom following the countries of England, Northern Ireland, Scotland and Wales. So, it would be written as Pointon, Lincolnshire, England, United Kingdom.

The comments to this entry are closed.