Entire Electoral Census for Zaragoza, Aragon, Spain Incorrectly Indexed as Being for the Year 1910.
There are currently two separate electoral census collections listed as being for the Zaragoza, Aragon, Spain region for the year 1910. One census appears to be correct, the other, to have been incorrectly indexed as being for the year 1910, but was actually for the year 1923. This has been confirmed many times over while tracing my ancestors and their suspected relatives throughout the collections of electoral census records for this region. In all instances the listings for individuals on one of the "1910" Censuses indicated birth years consistent with or close to those listed on other records; while the other collection listed calcutlated birth years approximately 13 years prior to those indicated elsewhere. This appears to have occurred for the entire collection, or at least a considerable section of it.
Please look into this very obvious dating error, and update all or as much of the collection as necessary to correct for that error, before it confuses other users of these collections. To clarlify if necessary, It is the collection containing 405 images to which the following link belongs: https://www.familysearch.org/ark:/61903/3:1:3QSQ-G9S5-299P-8?cc=2304578&personaUrl=%2Fark%3A%2F61903%2F1%3A1%3AWSP7-PMN2
@A Christian We are going to move your report of the error to the Q and A section for Search. This way, a moderator who watches for errors in our Historical Records can get this to someone who can fix it. You will see "moved" on the post here. But you can click the title and monitor progress in the Q and A area.0
@A Christian, we can send this information to a team of specialists to review the problem. Thank you for clearly stating the problem and providing us with a URL so we can see if for ourselves. That is very helpful.
We notice that the event date is editable. So, while you wait for correction, we suggest that you use the Edit option to correct the Event Date for your own relatives. If you've never done that, here is how:
Click Edit at the top of the page showing the indexed information
On the next screen, click the field that you need to update. The edit screen is pretty easy to follow. If you need help with details, you might find this article in the Help Center to be useful.0
Paul W ✭✭✭✭✭
Please update us on the progress (or otherwise) with this issue. Many of us have been reporting metadata problems for years, without anything being corrected. If this is fixed it will encourage others to report these problems (in the way N Tychonievich suggests), knowing FamilySearch does now have a procedure to make such corrections.0
Familysearch has provided me with the following reply on this and a similar issue:
"We wanted to update you on this issue in which 2 electoral census collections are incorrectly indexed as being from the year 1910. Our engineers have informed us that they are working on several projects to make it easier to fix these kinds of issues. In the meantime, they are not accepting our reports of errors. We apologize for this and encourage you to note errors for records that you use as sources. We hope that methods of correction will soon become available."
It sounds like there may be technical difficulties in the design of the Familysearch website that make seemingly easy and obviously needed corrections less than easily correctable. We will just have to trust that efforts are being made to correct these errors; and that it will become easier to do so in the future. Perhaps praying for them to receive guidance on how to correct these and similar issues might be helpful.
Paul W ✭✭✭✭✭
I have received similar advice to that given to Brigham (@A Christian).
I would be grateful if you could attempt to get the current FamilySearch position notified to users reporting similar, metadata issues. It is clear that there is no current provision for these reports to be addressed, so false hopes should not be provided to users who believe their issues are likely to be addressed, when (as stated above: "Our engineers have informed us that they are working on several projects to make it easier to fix these kinds of issues. In the meantime, they (our engineers) are not accepting our reports of errors."
I don't know how this position can be notified to all moderators likely to respond to such reports from users, but it is obviously important they should be aware of the true, current position.