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:
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:
0
Comments
-
Lundgren said: Thank you for the feedback.
There are lots of bad burial dates in there. We will look into this.
Thanks!0 -
-
Paul said: Thanks, Lundgren.0
-
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
This discussion has been closed.