Bug/Issue: Editing Event Place not available

Concetta Phillipps

I am doing a lot with the adding of records to the family tree for a couple particular branches and in most cases, there's a link to click that says something like "this event was indexed by computer" so that you can report the incorrect place being used for an event. (like this one https://www.familysearch.org/ark:/61903/1:1:XMJ5-FYNL?lang=en where it was indexed as Jackson, Arkansas, but its actually Jackson, Florida).

However, I am noticing in particular with the Native American Census Rolls that there is a rampant event place problem where the event is being listed as Tonalea, Coconino, Arizona, United States, when its actually in Red Lake, Beltrami, Minnesota, United States. But there is no where to be able to edit or change it. (For example https://www.familysearch.org/ark:/61903/1:1:W9J6-CY2M?lang=en ) so people are posting on profiles that the source is from Arizona, when it very much is not.

There is no way to report the error or fix it, so it just keeps on happening. Is there any way to get this to someone to get it fixed?

Thanks!

MandyShaw1

@SerraNola one of yours, I think, please.

SerraNola

@Concetta Phillipps You've run into a classic example of auto-standardization errors. Red Lake, Minnesota was standardized as townships all over the U.S. named Red Lake. (Tonalea Coconino, Arizona is also known as Red Lake.)

Since the records were indexed with the correct place name there is no user editing that can be done. The incorrect place name showing up in search results has to be fixed by engineering. Because Minnesota is in the indexed data, a persona can be retrieved in a search with Minnesota in the residence field. Also, Source Linker should correctly attach the residence as Minnesota. Hopefully, most users will recognize what's on the image when they source these records but I do share your concerns.

Thank you for the alert to the issue in this collection. It was not on my list.

Concetta Phillipps

@SerraNola thank you! I know to look for it, so I just correct it on profiles every time i see it, but I will start letting others know who are working on the same records to keep an eye out for the oddball Arizona entry.

South Dakota's 1925 state census also has some weirdness but at least the place comes up as South Dakota so profiles have that place instead of a different state.

SerraNola

@Concetta Phillipps Thanks, I'll take a look at SD 1925 Census.