Record placename does not match actual document
I would like to reopen
Record placename does not match actual document — FamilySearch Community
that was posted 15 months ago but is still not resolved. @Maile L sent it to be reviewed, but that seemed to be the end of it. I further commented on it 9 months ago, but there were still crickets from engineering. Has this been turned into a bug report?
Answers
-
@SerraNola Appears to be one for the place auto standardizing correction team.
Thanks.
1 -
@EarlMarshall if it isnt documented it didnt happen For that collection I have documented the entire film of 23,000 records all show as Essex, New York. Since this one stands out from the pack as a metadata error I can ask if it could be taken on now. For most of the place name issue collections, I've been told to NOT create work orders at this time.
1 -
So what is the appropriate thing to do?
I had this problem in a census record a few days ago. The place indexed was totally different than what was written at the top of the census form. (I might not have caught it, but the place was different than all the other census records for that person so I investigated further.)
Anyway, I was able to edit my person's record, but that doesn't help all the other people on that page or maybe pages. It would be nice to be able to correct such problems when we find them.
1 -
@CherylMillerBlack For most of the place name errors in census records, the wrong place shows in search results but is already correct on the index. Those cannot be edited. Do you remember what census that was with wrong indexing? I'd be interested to know if we have it reported.
0 -
I can try to figure it out, but I've worked on a lot of people recently. Let me see what I can find. (Does a source Edit show in the person's Change Log?)
0 -
I have seen this SO frequently! Just yesterday I saw one census where the place was "Allegany, Cattaraugus, New York" … and was listed as "Broome, New York."
It would be nice if there were a place to report the entire page.
1
