Home› Welcome to the FamilySearch Community!› Suggest an Idea

Burial date corruption?

LegacyUser
LegacyUser ✭✭✭✭
August 24, 2020 edited February 19, 2021 in Suggest an Idea
Paul said: When I have come across a similar issue in the past, I believe it has related to the year not being indexed and the date being derived from the day/month in the source. However, I can't figure out what is happening here.

This example was found in a search for individuals with first name David, buried 1800-12 in Northumberland, England. See https://www.familysearch.org/search/r...

Screenshot is extract from that page:
Tagged:
  • New
0
0
Up Down
0 votes

New · Last Updated February 19, 2021

Comments

  • LegacyUser
    LegacyUser ✭✭✭✭
    August 24, 2020
    Lundgren said: Thank you for the feedback.

    There are lots of bad burial dates in there. We will look into this.

    Thanks!
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    August 24, 2020
    Paul said: I decided to see what the burial detail would look like if I were to attach a source to an ID. This further screenshot is of a random sample I just chose:

    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    August 24, 2020
    Paul said: Thanks, Lundgren.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    August 24, 2020
    Lundgren said: I've tracked this down to a data issue.

    There appears it be an incomplete bit of information in the original index that is not being shown in the record once you click on it, but it is being sent to the search system.

    We will figure out the best solution for this. For now, I would ignore the bad burial date.

    Thank you again for reporting it.
    0
Clear
No Groups Found

Categories

  • 24.6K All Categories
  • 25.7K FamilySearch Help
  • 130 Get Involved
  • 2.8K General Questions
  • 457 FamilySearch Center
  • 482 FamilySearch Account
  • 4.8K Family Tree
  • 3.7K Search
  • 4.8K Indexing
  • 683 Memories
  • 338 Other Languages
  • 34 Community News
  • 6.9K Suggest an Idea
  • Groups