Index Information Not Matched to Image Database

lilagarner1

Researching the village of Flinsbach, Baden, where Jost Manhard (many spellings) lived, I found Jost's burial. Every entry on page 24 has the same index entry, presumably birthplace. This is Image Group 102060908, image 493. It must be a mistake--all these people surely didn't come from Hannover and move to Flinsbach in Baden?

N Tychonievich

@lilagarner1 Thank you for pointing out the error. We looked at the page in question and opened up some of the record details pages and see that a computer standardization tool has mis-identified places in this record collection. We will report the problem to the group that can get it fixed. We are not able to predict how long it might take for a correction to be in place.

Meanwhile, if you'd rather bypass the flawed indexed information, you can use the record image itself as your source, You can use the URL of the page to create a new source. Or, depending on how you are accessing the image, you can add it to your Source Box and attach it to relatives from there. These Help Center articles give the details:

https://www.familysearch.org/en/help/helpcenter/article/how-do-i-create-a-source-in-family-tree

https://www.familysearch.org/en/help/helpcenter/article/from-my-source-box-how-do-i-attach-a-source-to-a-person-in-family-tree

https://www.familysearch.org/en/help/helpcenter/article/how-do-i-attach-source-from-source-box

https://www.familysearch.org/en/help/helpcenter/article/how-to-find-the-add-to-source-box-link

W D Samuelsen contact me please

Old issue, not resolved since Feb 2020

https://community.familysearch.org/en/discussion/comment/496594

N Tychonievich

@W D Samuelsen contact me please Yes, we are aware that, even though we report these problems, they are not corrected in a timely manner. I did not actually see that this particular one had been reported to the group that is working on getting things corrected. While we have no expectation that a fix will be in place quickly, at least we know that it has now been properly reported. That's really all we can do at my level.