Can you please make the index match the record?
https://www.familysearch.org/ark:/61903/1:1:QPNR-HD22
The images in this set do not match the index below the record. Can this please be fixed? Also, can someone please send this question to the right place?
Answers
-
0
-
According to the Collection Home Page, "This project was done in partnership with Ancestry.com."
It may not be possible for FamilySearch to alter the index. https://www.familysearch.org/search/collection/3015626
1 -
The image does still not match the index. Not one of the names on the index matches the image, which is connected to image 230.
0 -
Nothing has changed since you posted 3 days ago. IF (and that's a big IF) it can be changed, it will not be instant.
1 -
There are probably hundreds of thousands (or possibly even millions) of index entries on FamilySearch that are matched up to the incorrect image. It happens especially in older indexes, where the index-to-image association was added (much) later based on now-outdated metadata. It's also not uncommon in cases like the one you've discovered, where there is another website or company involved, increasing the likelihood of data mismatches.
Either way, I wouldn't expect a correction any time soon, if ever.
Franz Heinrich Ludwig Peters's baptism is actually found on film 102546371 image 119 of 676 (https://www.familysearch.org/ark:/61903/3:1:3Q9M-CSZ5-5ZKG?i=118&cat=188177). I suggest simply adding that information to the Notes field of the index-based source, and/or using the "Attach to Family Tree" button on the image to attach it directly as a source.
(When Áine wrote "repaired URL", she really meant just that: the Community software "helpfully" mangles URLs, rendering them unusable until/unless someone manually goes through and replaces the URL entities with the correct characters. She was not talking about any correction in FS's index-to-image association; as she wrote, given Ancestry's involvement, no such correction may be possible on FS's end.)
2 -
When Áine wrote "repaired URL", she really meant just that: the Community software "helpfully" mangles URLs, rendering them unusable until/unless someone manually goes through and replaces the URL entities with the correct characters.
And then staff came along and manually edited the original post, editing the URL in the original post, without a comment.
1
