Is it a bug if index data doesn't line up with the image it is beside?
Here is an example: https://www.familysearch.org/ark:/61903/3:1:S3HT-DRS9-TYD?view=index&cc=1416598&lang=en&groupId=M9S3-MZZ
Image 4 of 56, the Names Index has no data and says it hasn't been indexed. First name on image is Mary Oxborough buried 1 Apr 1813, followed by Mary Meal, buried 24 Jun 1813, etc. Images 5 and 6 also have no indexed data.
Skip forward to Image 7 of 56, and the indexed data matches Image 4. This continues through the whole group where the data is 3 pages off from the image to which it is indexed.
I've certainly seen the case when clicking an image in a record that a note pops up to say the correct image might be nearby, but I haven't seen this situation where the actual indexed data is for a different image than what is showing.
Best Answer
-
@T2Montgomery I don't know if it should be called a bug, but I've seen enough of these to say they need to be reported, especially when the index is off by more than two pages. In this case, the last page has no index and the names are not searchable. That's a problem that I will bring to the attention of engineering.
2
