I try to always put the cemetery name (if known) before the city, county and state ... I’ve attached ss for visual example 😊 hope this helps:)
And then this is how it looks on the “person” screen...
What do you mean Where is the name of the cemetery supposed to go? Where?
Further to what 'X24mom' has already proffered ...
As an aside ...
You can also request that 'FamilySearch' make a Cemetery a "Standardized" 'Place' (if it DOES NOT already exist), in the "Place Names Database", within 'FamilySearch', if you so desire.
There are a couple of ways that that can be done ...
[ 1 ]
Through, the "Research/Places" part of 'FamilySearch"
Place Names Database
The 'link'/'button' of:
+ Suggest a New Place
at the 'top 'left-hand-corner' of that page/screen
[ 2 ]
Through, a 'Group' in this "Community.FamilySearch" Forum
By requesting such.
[ 3 ]
Through, a direct E-mail to the [ "Authorities Team" ] "Standards Team" in 'FamilySearch'.
E-mail: [email protected]
And, finally, last; but, not least ...
[ 4 ]
Through, a 'Support' Case
Raise a 'Support' Case with 'FamilySearch'.
[ 5 ]
Through, the 'FamilySearch' ("GetSatisfaction") 'Feedback' Forum
As a 'Feedback' request.
Just a thought.
ps: Would suggest that  through  being the better options.
What I mean is, in the past I have put the cemetery name first before the city. If that is no longer acceptable, and I am not sure if it is, then what field is the cemetery name supposed to go in? I think the next reply is what I needed to know. That is, that we can request FamilySearch to make the cemetery a standardized place. I like putting the cemetery name in the place filled, but I am concerned that someone else will come along and standardize it and take it out.
Sounds like you might not quite understand what is meant by "standardizing" a place name. Furthermore, people doing as you say, also totally misunderstand what is going on and are trashing totally legitimate location names. Unfortunately we've had many FH consultants who do not understand that what they are advocating regarding "Standardized" place names is totally wrong.
Enter the name of the cemetery on the front of the place name followed by a comma. There are a huge number of cemetery place names that exist in the standards database (i.e., they are "standard" names--NOT "standardized" names--think about the meaning of those two words). If the Cemetery has a "standard" place name in the database, great! You can select that to use as your display name. It will be shown with a map-pin icon next to it since it is a "Standard" name.
However, if that cemetery name is NOT a "standard" place in the database, you can "Standardize" it by assigning another "Standard" place name from the database such as the city name. When you do this, the location name that you are displaying has been "Standardized". NOTE that in this case it will not have a map-pin icon showing next to it, but it STILL is a "Standardized" place name.
A "Standard" place name is one from the standards database which has all kinds of alternate name and various time frame information in it that is all associated with a single physical Geo-coordinate where it has always been over time. Place names that have been defined this way have the little map-pin icon shown with them (indicating that they have a geo-coordinate that can be seen on a map).
A "Standardized" place name is any Non-"Standard" place name that has had a "Standard" name from the database attached to it. The "Standard" name from the database is used to "Standardized" the non-standard place name that you are displaying.
You need to have a "Standardized" place name for temple work to be done. That does NOT mean you must have a map-pin icon showing next to it!
The map-pin icon means something totally different to what has been explained to many people. A map-pin icon simply means that the place name you are looking at is from the standards database and it can be shown on a map (i.e., it has Geo-coordinates as part of its definition).
A non-standard place name will never have a map-pin icon. It will either show no symbol (i.e., it has been "Standardized" by attaching a "Standard" name to it), or it will show you a red "!" meaning that it has no "Standard" name assigned to it (i.e., it has NOT been "Standardized")
In other words, nobody should be going through and "Standardizing" ANYTHING unless it has a data error mark on it (the red "!"). Basically, a "non-standardized" place name doesn't exist anywhere in the world because it can't be put onto a map in a physical place. By "Standardizing it, it "Borrows" the geo-coordinate of the standard place it has standardized with. That means it can be put on a map, but at a location that is only physically near the real location.
E.g., If "Smith Cemetery, Springfield" is not a standard place name but "Springfield" is, you can "Standardize" the non-standard place name of "Springfield Cemetery, Springfield" by attaching the standard place name of "Springfield" to it. Now "Springfield Cemetery, Springfield" will show on a map in the center of the city of Springfield (even if it is really 3 miles out of town).
One Warning here. When looking at the way these terms have been used on the website, FS has NOT been consistent with the dictionary meaning of the terms witch is one of the reasons this thing has confused so many people. You "Standardize" any non-"Standard" item by applying a "Standard" to it.
None of the place names in the Standards database have been "Standardized". They are the standards by which non-standard display names are "Standardized"
By the way, this exact same thing applies to street addresses. The number and street name can precede the city name and be "Standardized" with the city name. If had to stop several people going though and chopping off street address on residence information because FH Consultants told them they needed to have the map-pin icons showing in order to be "Standardized".
Thank you, Jeff. You are correct. I did not understand.
You're most welcome. But don't feel bad about it. I suspect that there are far more people that do not understand this than do. Spread the word.😊
Good points. However, do not ask them to create a "Standardized" place with the Cemetery name. It is more correct to ask for them to add a new "Standard" place in the Standards database. The Standards Database does not contain any "Standardized" places, in spite of the terminology that they use on the web pages.
The cemetery name is available on the findagrave record and should be carried over and automatically plugged into the FS cemetery name field.
No one should have to manually enter the cemetery name; yet that is what is currently happening if the cemetery name gets identified AT ALL.
In the event edit tool the little blue "I" icon is a link to some Help Center articles about the FamilySearch Places gazetteer.
Many but not all cemeteries are in the gazetteer already. Anyone can request that any place be added to the gazetteer, and if there is enough evidence of its location it will be added.
The direct link to the gazetteer is https://www.familysearch.org/research/places; in the top left of that page click on "+ SUGGEST A NEW PLACE". It helps if you do a little research first to locate the cemetery on Google Maps, find their website, etc. and provide those URLs.
Unfortunately, I find Find A Grave cemetery locations to be unreliable.
Related ( LATER / SUBSEQUENT ) 'Comment', in a 'Post' ...
Suggest An Idea
HOME > SUGGEST AN IDEA
I agree with the original suggestion here. The issue is the cemetery name is being effectively lost currently. 90% of FS cemetery names are displayed as city and state (and perhaps county) only.