Major Post-Processing Error in Historical Index for Norway Baptisms
LegacyUser
✭✭✭✭
Gordon Collett said: In the database "Norway Baptisms, 1634-1927" for at least batch C42920-1 there has been a major error introduced in the displayed database.
Here is the batch:
https://www.familysearch.org/search/r...
In the result list, the event place is shown as "Åkre Gravplass, Fusa, Hordaland, Norway." The Åkre Gravplass, as can be seen in the Places database, is the cemetery that lies next door to Strandvik church in Fusa.
When looking at the full index record, they all have an "Event Place (Original)" entry of Aakre, Hordaland, Norway, which is the correct event place:
This correct Aakre is Åkre parish in what was formerly Skånevik community.
Åkre cemetery in Fusa (where they certainly did not do any baptisms) is 220 miles away from Åkre church in Skånevik (where all these actually took place.).
The problem probably arose because Åkra church in the Places database did not have the older spelling of Aakre included as an alternate name. But that does not explain why the cemetery was picked for the event place. That was just not paying attention. Please fix these entries.
Here is the batch:
https://www.familysearch.org/search/r...
In the result list, the event place is shown as "Åkre Gravplass, Fusa, Hordaland, Norway." The Åkre Gravplass, as can be seen in the Places database, is the cemetery that lies next door to Strandvik church in Fusa.
When looking at the full index record, they all have an "Event Place (Original)" entry of Aakre, Hordaland, Norway, which is the correct event place:
This correct Aakre is Åkre parish in what was formerly Skånevik community.
Åkre cemetery in Fusa (where they certainly did not do any baptisms) is 220 miles away from Åkre church in Skånevik (where all these actually took place.).
The problem probably arose because Åkra church in the Places database did not have the older spelling of Aakre included as an alternate name. But that does not explain why the cemetery was picked for the event place. That was just not paying attention. Please fix these entries.
Tagged:
0
Comments
-
Paul said: If this is fixed, I believe many of us will be given hope as to there actually being a method of finally addressing such problems. I have reported similar instances over the years and don't recall any of these metadata issues being addressed.
As I have commented in the past, if there are links to report problems in the Catalog (incorrect titles, etc.) and to add "new" place names to the Standards database, shouldn't there be a direct link for reporting errors that affect the accuracy in detail of possibly thousands of sources in a particular collection?0 -
FamilySearch Moderator said: This has been passed on to the correct engineering team. Please give us some time and if it is not fixed please ask us for a status.0
-
Juli said: Is there a mechanism for reporting such metadata errors? If yes, what is it, and how are users expected to find it? If not, why not?0
This discussion has been closed.