Is this probem specific to this record does it indicate a wider issue?
I was reviewing an indexed record which seemed to indicate the death of a 2 year old with a spouse and with a different last name from her father which didn't seem right for a family in sicily. When I looked at the image of the record the information in the index isn't correct but it is a "partial overlap" with the record information. Here's the link to the indexed information:
https://www.familysearch.org/ark:/61903/1:1:XRRX-H8D?cid=fs_copy
And here is the link to the image of the record:
https://antenati.cultura.gov.it/ark:/12657/an_ua15390561/wREzVv4
Which shows the death of 2 year old Angela Russa with father Alfonso and mother Gaetana Lentini while the indexed information suggested Angela Russo was married to Alfonso and had different mother & father names: Paolo Gucciardino & Rosa Lumia.
Those parents appear on the next record, #310, for the death of their son Salvatore Gucciardino who is 55 years old. This makes me wonder if it's a programming issue with how the indexed info is being displayed.
If the problem is specific to this record, I know how to handle it but I wanted to run it by the community in case it should be elevated to the programming team for broader correction. If I can help to provide additional info to help, please let me know. Thank you for your help.
Best Answer
-
The legacy status of that record set means the programmers won't look at it, won't add to it, won't change it.
2
Answers
-
Repaired URL for the benefit of those who may try to assist: https://www.familysearch.org/ark:/61903/1:1:XRRX-H8D?cid=fs%5Fcopy
[The community software will often corrupt the URL if the poster enters a return or space immediately after the URL.]According to the Wiki description, the record set is a Legacy Collection. That means no changes will be made. https://www.familysearch.org/en/wiki/Italy_Deaths_and_Burials_-_FamilySearch_Historical_Records
1 -
Yes, that makes sense but I guess I was thinking this type of problem might be an indication of a problem between the databases (like they're offset from each other or something) so it might be worth a look by the programmers. Maybe I misunderstood your response and the legacy status is going to impact if they'll take a look or that you know it isn't that sort of problem if so sorry to ask again but it just seems like a shame to lose all the value from a record set if it is a database issue.
0