Wrong cemetery listed on 'About'

Gale French

Comment: when I click ABOUT for LJWH-5K7 the burial site is wrong; lists Sandy Point instead of Southpark

Tiffany Farnsworth Nash

@Gale French

It is because it isn't Standardized.

The 'Place of Burial' has the entry 'Southpark Cemetery, Pearland, Brazoria, Texas, United States' but it isn't standardized.

First, double-check the cemetery. Click on the FindaGrave Source and scroll down until you can see the Cemetery Name. If needed, you can copy/paste it into the 'Place of Burial'.

Then, If you click anywhere on the entry a drop-down list will appear of Standardized Place Suggestions. Just click the correct one.

Additionally, you will want add a Reason Statement to the 'Reason This Information Is Correct' box. An easy way to do this is the copy/paste the word 'Standardized' into the box.

One last thing. You can add the year '2017' into the 'Date of Burial' field. The year is most likely the same as the year of death.

Nyx773

Since the actual "Place of Burial" field does not contain standardized data, the "Sandy Point" could be from the "Verify Places" opportunity. Mistakes happen.

https://www.familysearch.org/en/getinvolved/opportunities

The fix is easy. Edit the field and pick "Southpark Cemetery…."

For all applicable fields, make sure that they contain standardized dates and places to avoid confusion in the future.

Nyx773

@Gale French
@Tiffany Farnsworth Nash
Please do not list guesses in any field. Leave the burial date blank if unknown.

2017 may not be correct. I’ve seen several instances of a person being cremated and then interred several months later, sometimes the following year. I’ve also seen reinterring just a year or so after the first burial.

Tiffany Farnsworth Nash

@Nyx773

Good point! I am going to revise that to 'about 2017'. That way it is in the ballpark.

Nyx773

@Tiffany Farnsworth Nash For any and all unknown data, please leave those fields blank. Blank is far better than a ballpark. Please do not guess or make assumptions in the data entry fields. Instead, please use the "Reason" field and/or make a Collaborate note for discussions.

Please read the last 3 comments on this post for some catchy phrases:

https://community.familysearch.org/en/discussion/185976/i-stumble-across-a-person-who-is-attaching-and-creating-profiles-with-literally-no-sources

@Gale French However, in the case of LJWH-5K7, the current biography on Find a Grave lists a funeral date of 3 March 2017. That is usually the date the person was interred (but not always). In this case we are fortunate that it also states "Interment will follow at South Park Cemetery."

https://www.findagrave.com/memorial/176890999/hubert-richard-french

P.S. Since biographies on Find a Grave can change at a moments notice (or memorials can be deleted), and since there isn't an obituary attached to his FamilySearch profile, I recommend copy-and-pasting the biography into the "Notes" section for that source on the Sources tab.

Tiffany Farnsworth Nash

@Nyx773

I know this is controverial, however I have had great luck with adding approximate dates in regards to the FS search engine. It seems to be very helpful to add approximate dates (based on existing facts of course) and I get way more hints this way. Many times I would not have found info or duplicates if I had not added an approximate date. For instance. When I only have a spouse surname I extrapolate an approximate date from the spouses date. This provides the system with 3 points for searching: surname, approximate date, and spouse. Three points seem to be key for getting results. Adding an approximate date narrows search parameters so that it is at least searching in the correct century. Yes, reason statements are good. 'About' means just that, it is just an approximate. My goal using approximate dates is merely to feed info into the search engine in order to get more hints/records. If I don't get a hint then I will never know, if I do then I can evaluate it. Note that it sometimes takes the system several days to provide hints. I'm sure many will disagree. This is an intereseting discussion and I am open to constructive feedback. Please do let me know if you have any specific reasons or instances where this does not work. Thank you.

Gordon Collett

I have to correct a few comments above that reflect either a common misunderstanding or a poor choice of words.

Several people above indicated that your problem was that the cemetery name was not standardized. This is incorrect. The cemetery name was standardized. It was just standardized incorrectly.

In FamilySearch terminology, to standardized is to link the name you enter for a place to an appropriate standard name in the Places database. These two entries do not need to be the same and both entries are always present even though only one is displayed if they happen to look the same. This dual entry place name entry system has several great advantages. One is that it allows the user to enter more information to more completely describe a place while still giving the program identifiable information to use in program routines. Another is that it allows for internationalization in some areas.

Most areas in Family Tree show only the user entered place name. Some show both the user entered place name and the linked standard. Some show only the linked standard.

Here is your example:

The user entered name is Southpark Cemetery. The linked standard is Payne Cemetery. There is a standard so it is standardized. If it were not standardized, there would be a notice to that effect in big red letters like this:

(I removed the standard in the FamilySearch's Beta site, not on the actual site to you can correct the entry yourself.)

How to add or correct a standard is explained above. As stated there, just click on the edit link then click on the cemetery name to re-open the drop down menu and choose the name you want to use:

Because the user entered name matches an existing standard, you only have one choice.

To demonstrate the usefulness of the dual entry place name as mentioned in my two examples, here I have added more information to the place name. (Again, only in Beta and totally fictional. Don't add it to his real entry!) Here you can see the user entered place name and the linked standard:

Now I'm going to change the website language to Norwegian:

Notice that the user entered place name did not change but the standard was translated to Norwegian. In this case that was not much of a change because only the country name changed.

The computer generated short biography in the About section is one of the areas of the website that only uses the linked standard instead of showing only the user entered name or both of them. That is why you saw the standard "Payne Cemetery" there.