Burial date corruption?

LegacyUser

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:

LegacyUser

Lundgren said: Thank you for the feedback.

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

Thanks!

LegacyUser

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:

LegacyUser

Paul said: Thanks, Lundgren.

LegacyUser

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.