Burial Locations Don't Match Cemetery Locations
I believe we have a very large problem. Over the last few weeks, I have noticed numerous instances of the location of the grave, not matching the actual location of the cemetery. I've had the problem twice just within the last ten minutes. Example: Edith Richard Vice-Person Record L1NV-JQ9 https://familysearch.org/ark:/61903/1:1:X34X-9K5P
The "Event Place" list Indiana
The "Event Place (Original)" is correct.
Abbeville, Vermilion Parish, Louisiana, United States of America
Miss Edith's daughter (Helen - Person Record L1NV-R9N) is buried just forward of this headstone. Helen's "Event Place" is listed as
Event Place | Saint Paul Cemetery, Hurtsboro, Russell, Alabama, United States |
|---|
My father is buried in this same cemetery. Travis Callahan-Person record GH1D-WNM. Dad's "Event Place" is listed as
Event Place | Saint Paul Cemetery, Starkville, Oktibbeha, Mississippi, United States |
|---|
Event Place (Original) | Abbeville, Vermilion Parish, Louisiana, United States of America |
|---|
The problem is not only with St. Paul's Cemetery in Abbeville, Vermilion, Louisiana.
My paternal Grandfather- Ivey Joseph Callahan-Person record LBSC-M21 has an original event place of
Event Place | Graceland Cemetery, Rowan, Wright, Iowa, United States |
|---|---|
Grandpa is located on the north side of Abbeville in Graceland Cemetery
Event Place (Original) | Abbeville, Vermilion Parish, Louisiana, United States of America |
|---|
My grandmother Winnie Bodin Callahan - Person Record GH1D-7FW rests right next to her husband, yet her Event Place lists
Event Place | Graceland Cemetery, Knoxville Township, Marion, Iowa, United States |
|---|
My MATERNAL grandparents have the same issue in another town. Pamela Norris Vincent Person record KCPM-JBB. Is buried about 12 miles away in another Vermilion Parish town. Her Event Place lists
Event Place | Our Lady Of Lourdes Cemetery, Gaylord, Stark, North Dakota, United States |
|---|---|
Event Place (Original) | Erath, Vermilion Parish, Louisiana, United States of America |
In some instances, The Detail Record for each person lists no information for Burial, yet, when you open the Sources record you can find the issue on the Source. Grandma Vincent doesn't have a burial record listed on her Details record, yet her husband (my grandfather) has a Burial listed in the Details record. Freddie Vincent, Sr - Person Record K8FR-H55. Grandpa's Burial Data lists a source of "Find a Grave Index" Again, he rests right next to his wife.
Event Place | Our Lady Of Lourdes Cemetery, Trenton, Mercer, New Jersey, United States |
|---|---|
Event Place (Original) | Erath, Vermilion Parish, Louisiana, United States of America |
This isn't a problem for Vermilion Parish, Louisiana. My maternal Aunt Delsey Vincent Perrin- Person Record GDLV-LH4, has the same Source as her father, "Find a Grave Index" her Details record lists the proper burial location but the source record is wrong.
Event Place | Saint John Cemetery, Sauk Centre, Stearns, Minnesota, United States |
|---|---|
Event Place (Original) | Lafayette, Lafayette Parish, Louisiana, United States of America |
Yes, this is probably a Find a Grave issue but this problem is corrupting the Family Search database. If the Event Place (Original) value ever gets deleted, the burial locations for many people will be lost to time.
My maternal uncle is buried in Texas. Roland Patrick Vincent - person record GDLV-J8T has corrupt data as well.
Event Place | Green Lawn Cemetery, Wingate, Coal Creek Township, Montgomery, Indiana, United States |
|---|---|
Event Place (Original) | Groves, Jefferson, Texas, United States of America |
The problem gets even worse, when the Event place isn't converted to a Standard Place.
Event Place | World |
|---|---|
Event Place (Original) | , Contra Costa, California, United States of America |
Cemetery | Lafayette-Orinda Presbyterian Church Garden |
Please let me know how I can help to resolve these problems. I'm happy to volunteer to correct data, but I don't want that data overwritten AGAIN.
Answers
-
Record Issues:Use a reporting form to flag errors, problems, restrictions or bugs, with specific records/collections. To report an issue, please click on the following link, Records Issue. Complete the form with as detailed information as possible and submit.This approach will allow us to keep development-related issues within the proper feedback channels, while allowing the Community to be used as a space for discussion, collaboration and support- where users can learn from one another and receive help with research; helping the Community to remain focused, effective, and helpful for everyone.
0 -
@AlainaCallahan
Several posts have been created in the past couple of weeks reporting this new bug. Here is one of them:2 -
@sc woz The form has required fields without details explanations. EX:
Collection URL *Required
If this pertains to a full collection of records please provide the Link/URL to that collection
=============
How do I link the entire Find a Grave Index? Each individual source is particular for that Person Record. How do I find the URL for the entire Find a Grave collection?
EX: #2
Image URL
*Required
Please provide the link/URL for the image you are reviewing
==========
I'm not viewing an image but that is a required field to submit the support request.
I spent 27 years in IT Design and Support. If I'm having trouble with this form, many more people will just not report the problem.
4 -
@Nyx773 The issue is being reported frequently, but what action is being taken to address the issue?
3 -
@sc woz @AlainaCallahan My experience with the Records Issue Form is that FS is handling so many differing Records Issue requests, they're having trouble prioritizing because of the AI indexing/transcribing errors in various collections — as well as printing the form itself
1 -
Please complete the Records Request Form to the best of your ability. The more detail you provide, the more effectively we can investigate and resolve your issue.
When submitting your request, include specific instances of the problem you are experiencing—dates, URLs, record collections, error messages, and any steps you took before the issue occurred. Detailed examples allow our team to accurately identify the root cause and provide a meaningful response.
All issues submitted through the Records Request Form will receive an answer. While we are unable to provide a timeline for how quickly you will receive that response, we will strive to deliver an explanation or solution that directly addresses your concern.
Thank you for taking the time to provide complete information. It significantly improves our ability to assist you.
1 -
@AlainaCallahan
The URL for the full Find a Grave Index collection is: https://www.familysearch.org/en/search/collection/22218012 -
I put n/a for one of the fields on the Find a Grave one I did, and the Find a Grave URL for the Image URL. The wording is a bit too much focused on standard FS 'local' Historical Records, but no doubt it'll get tuned.
2 -
Lately I am noticing error in last few days - hint says WORLD, but when I attached the hint, it change to actual burial place so I double checked to be sure.
Clearly there is a bug somewhere between Findagrave and FamilySearch rendering the burial places as World.
1 -
This insanity need to stop now!
Literally ever new Find A Grave hint has the problem. It is always "Event Place" problem literally wrong, wrong, wrong. (wrong city, wrong state, even wrong country) while "Event Place (Original)" is always correct.
One of my friends told me she intend to REJECT EVERY ONE OF THOSE HINTS because you haven't got this fixed quickly. She plan to tell others to do the same.
Personally I am very irked that I have to correct them before finalizing the source-linking.
-1 -
@W D Samuelsen contact me please
I am assuming you are discussing the Find a Grave issues in this area? If not, please identify the collection you are having problems with.
I am sorry, but I do think your friend needs to be dissuaded from, effectively, subverting the Hints system (for everyone) to prove what is effectively an unrelated point (assuming reject=dismiss).
We can't influence FS' engineering and records management priorities except by completing the relevant forms (Suggest an Idea, Records Issues, Feedback) in as much clear detail as possible. My understanding is that these forms now drive well-defined processes within FS.
Fixes to problems like the Find a Grave cemetery placename one are going to be twofold: fix the logic, so it stops happening to new stuff, and fix the data it's already happened to. Judging by other high volume problems we've encountered here, and with the best will in the world, the data fixing may take a while.
In my view, given that the user has easy access to the /correct/ data, identified as such both on FS (Event Place Original) and on Find a Grave, this is not the worst FS data problem I have seen, though it did feel irritatingly avoidable when I researched and reported it: see
3 -
Thank you for raising this; the concern is absolutely valid, and you’re not the only one seeing it.
The current Find A Grave hint import is populating the “Event Place” field with incorrect standardized locations, even when “Event Place (Original)” is accurate. We understand how disruptive this is, especially when it affects every new hint and forces users to manually correct the place before the source can be finalized.
I want to emphasize two things for everyone following this thread:
- Rejecting all Find A Grave hints is not necessary and not recommended. The underlying data is still correct; it’s the standardized place resolution that is misfiring.
- The issue has already been escalated. Engineers are aware, and this is not an intentional change. It’s a system-level place standardization bug affecting multiple hint types, with Find A Grave being the most visible.
In the meantime, the best approach is exactly what you’re doing: Review the hint, correct the standardized place if needed, and then attach the source. It’s extra work, and yes, it’s frustrating, but it keeps the tree accurate while the fix is in progress.
Please encourage your friend (and anyone else feeling the same irritation) not to reject hints wholesale, as that can lead to missed sources and lost information.
We’ll continue to update the community as soon as we have confirmation that the correction has been deployed. Unfortunately, this is a large-scale problem being worked on by many people and we do not have a time frame for the fix.
Please remember that FamilySearch Community is a place where everyone should feel welcome to raise concerns without feeling stressed or discouraged. We absolutely want people to speak up about issues like this, and to do so in a way that helps all of us work toward solutions together.
The Find A Grave “Event Place” problem is real, it’s known, and it’s already escalated. While it’s frustrating, especially when it affects every new hint, we ask everyone to keep discussions constructive and supportive.
Thank you for sharing your experience, and thank you to everyone who continues to report issues respectfully so we can keep this a collaborative, safe space for all.
To avoid confusion and duplicate reports, this discussion will now be closed while the investigation is underway. If additional information is needed, the team may reach out for further details. Thank you for your patience, for helping improve FamilySearch records, and for being a valued member of the FamilySearch Community.
2
