Errors in record locations
In the record set Minnesota, Birth Index, 1935-2002 (https://www.familysearch.org/en/search/collection/1949334), a problem has recently started occurring. This only started occurring a few weeks ago, and was not an issue for many years before. Records in this set will always include the county of birth within Minnesota. But as of the last few weeks, the "Event Place" is completely wrong because it's trying to find a city or township (or seemingly random places) sharing the county's name. Dropping down the "Event Place" options with the arrow next to the location will show the correct location, but often below several additional incorrect locations. Here are some examples, all from one search for the name "James Anderson":
https://www.familysearch.org/ark:/61903/1:1:VCJH-RXJ?lang=en - Supposed to be Douglas County, is instead Douglas Township, Dakota County (and has some unrelated locations in the event places listed)
https://www.familysearch.org/ark:/61903/1:1:VCJW-CQ9?lang=en - Supposed to be Washington County, is instead Washington Township, Le Sueur County
https://www.familysearch.org/ark:/61903/1:1:VCJ4-GHL?lang=en - Supposed to be Blue Earth County, is instead Blue Earth, Faribault County
https://www.familysearch.org/ark:/61903/1:1:VCNP-6BJ?lang=en - Supposed to be Ramsey County, is instead Ramsey Township, Anoka County
I am concerned with these issues because they have the potential to mess with many profiles on familysearch and other sites, spreading misinformation very quickly. I'd estimate more than half of the counties in Minnesota and therefore half of the over 4 million individual records in this record set are currently incorrect because of this. This has only been an issue for a few weeks, though, so whatever was going on before was working correctly and showing only the county of birth (with no attempt to match it to a city or township). Please look into this issue!
Answers
-
@SerraNola This sounds like our old "friend" place name standardization problems.
1 -
Thank you both for responding, sounds like this isn't an issue exclusive to this record set!
1

