Create a Corrections Group for Each County.
My research consists mainly of South Africa due to the teachings of how to index a document you input what you see and add no more has created a big problem regarding locations and Country. There’s far to many documents indexed with the incorrect location ie Death place Ireland it’s a Cape Town South African document and Should have the Location (George, Cape Province, South Africa) . I believe there’s no department that can make this type of correction. I know there’s a lot of South Africans that are willing to become apart of a Corrections group if they given the tools. We have a fantastic indexing group consists of 1.3K members that collaborate each and every day we help one another constantly in many ways not just in indexing documents.
I have noticed over the years that suggestions aren’t taken serious and go completely ignored it’s very frustrating. I can’t help but wonder if ignoring suggestions makes more busy work to keep volunteers busy which to me is completely crazy. I think Successful documented tree building would be rather pleasing to all the volunteers that make Family Search what it is today and encouraging for others to take part.
thanks hope this doesn’t fall on deaf ears.
Roslyn
Comments
-
That's not an indexing error. That's auto-standardization striking (out) again.
What was actually indexed is in the field labeled "(Original)": Hospital, George.
In order to change search mechanisms to a more efficient method for places and dates, FamilySearch needed to associate all of the location fields in its indexed records database with entries in its places database. They used an automated process to do that, but for some reason, they set up that process without any reference whatsoever to collection metadata, such as the location that a particular set of records came from. So, in your example, instead of looking for places matching "Hospital, George" in South Africa (or at least Africa), the computer looked through the entire global database of places and picked the first one that vaguely matched, which happened in this case to be in Ireland.
FamilySearch continues to deny the vast scope of the problem caused by this bot, and expects to fix these errors piecemeal, based on user reports like yours.
1 -
Seeing the (Original) place is great - that way a researcher can know what was indexed originally and come to a conclusion about place! FamilySearch isn't hiding the mistake. As has been said so many times before - the index is not the record - it hopefully helps the researcher find the record (as long as they don't input a place criteria I guess or if the search searches both listed and original place) ...
@Roz14 Maybe show the willing indexers how to attach the record into Tree? Once it's attached where it belongs - the mistaken index becomes less important.
0
