Search Result Filter By Year Problem
There have been several discussion here about how the auto-standardization routine converted originally indexed place names into completely wrong place names and how that has made place names as shown in search results very suspect and difficult to use.
I ran across today a problem with dates that makes filtering by a date range problematic. Since I have not seen a discussion or report of this before, I thought I would bring it up here. I do hope the engineers are aware of this an working on a way to repair it.
I was just poking around in the Search routine and tried filtering a results list by marriage date and was very surprised to see this:
Filtering for the sixteen people married in the year 6000 AD and going to the first one that has an image, I find a "marriage date" of 6073 (https://www.familysearch.org/ark:/61903/1:1:6D3V-3C3Q ). Looking at the image for this marriage that took place in 1916, I can't see anything on the page to account for the 6073 number. Scrolling through a few more images on the film I see that all of them have goofy marriage dates in the index.
Are all these strange dates indexing errors? If so, how did they ever make it past a review and through to the final database? Are these another post-processing problem? Looking at the numbers of events in each century, this is admittedly a small percentage of records in this list of over 69 million results, but it still throws into doubt all the results. Is there any hope of these ever getting cleaned up?
Or do we just use such things to continually hammer home to everyone that while indexes are good finding aids, they can never be fully trusted and you always, always, always need to check original images?