Home› Welcome to the FamilySearch Community!› Ask a Question› Search

Reporting indexing errors

MLV2
MLV2 ✭✭✭
October 21, 2021 edited June 30, 2023 in Search

There needs to be a mechanism or process to correct, or at least report errors. When clicking feedback, one is dumped into the community.

The indexing for the source at https://www.familysearch.org/ark:/61903/3:1:3QS7-99JH-LXZ7?i=4231&cc=2367299&personaUrl=%2Fark%3A%2F61903%2F1%3A1%3AQVS3-4MSZ

erroneously shows the officiator, Rev J. H. Ament, as the mother and one cannot alter the suggested linkage

Tagged:
  • New
1

Answers

  • Melissa S Himes
    Melissa S Himes ✭✭✭✭✭
    October 21, 2021

    That is really weird. On the link to the image, the relationship of Rev. Ament to the deceased is blank on that image and there are no parents listed in the obituary or on the image index. It is a decently indexed batch with the exception of the daughter Mrs. Emma Heib who should have been indexed as a female and daughter instead of unknown and child and the absence of her husband Christ Heib who should have been indexed as a male son-in-law.

    Then when you click on the snapshots of each of the folks, the problem begins. All of them are listed in the obituary of UNKNOWN? and the Reverend is not the Parent. But on his record his husband is Mr. Gackle. On Mr Gackle's he is the spouse and on the children he is the parent.

    I don't who is in charge of reporting these things, but, I wonder if instead of posting this in indexing it should be in Search or FamilyTree? It doesn't appear to be an indexing error as much as a technical problem.

    0
  • MLV2
    MLV2 ✭✭✭
    October 21, 2021

    I agree, however FS has told me me more than once to submit via feedback, which only goes to the community and is useless.

    It is a shame because accuracy should be the hallmark of FS records. But with volunteer and computer indexing, there are many indexing errors, many of which can just be ignored, but some of which are egregious. FS likely cannot correct them, so increasingly "caveat emptor!"

    0
  • Melissa S Himes
    Melissa S Himes ✭✭✭✭✭
    October 22, 2021 edited October 22, 2021

    These were indexed back in 2014. I worked on them. I don't think the problem is with the indexing, there is something else going on here. If you think the community is useless, I suggest clicking on the question mark, then Contact Us and give familysearch a telephone call. I don't think the community is useless, it just depends on where your post ends up and I don't think Indexing is going to be of service.

    0
  • MLV2
    MLV2 ✭✭✭
    October 22, 2021 edited October 22, 2021

    For errors like this, the community cannot help. Community can help with other types of problems, but not with errors. When users see indexed records, there is no way of telling what the problem was. When the original document image is available, but what is presented is flat wrong, then it appears that there was an indexing issue. To only have feedback that takes one to discussion board options for thoughts or ideas, is not helpful.

    0
  • MaureenE123
    MaureenE123 ✭✭✭✭✭
    October 22, 2021

    It seems like FamilySearch needs to decide what sort of error this is, what is the process for reporting errors, and inform people how to report errors. Hopefully the new version of Community will include the latter and also include information generally about what is an Idea.

    @N Tychonievich

    @Mark McLemore

    1
  • Melissa S Himes
    Melissa S Himes ✭✭✭✭✭
    October 22, 2021

    @N Tychonievich looking at the image index in the link, the indexer did not make a mistake. You are not suggesting that this is bad indexing, are you? Notice there is no relationship for the Reverend in the image index, and there are correct relationships listed for the other people in the obituary. Additionally, the Rev does not show up incorrectly on most of the other people listed in this obituary when you click on their "personal" link. I don't believe this is a problem with the indexing and should be further investigated to determine if it is some type of a programming error.

    0
This discussion has been closed.
Clear
No Groups Found

Categories

  • All Categories
  • 43.1K Ask a Question
  • 3.4K General Questions
  • 572 FamilySearch Center
  • 6.8K Get Involved/Indexing
  • 645 FamilySearch Account
  • 6.6K Family Tree
  • 5.2K Search
  • 1K Memories
  • 2 Suggest an Idea
  • 478 Other Languages
  • 62 Community News
  • Groups