Why is it wrong to enter { or } instead of question marks?
Answers
-
Hi, James. I'll give you my opinion - and that's all it is.
As you know - as Indexers, we're supposed to capture the information on the batch image that the data custodian has specified. FS incorporates the custodian's requirements into the choice of entry fields and the project instructions. If a name is unambiguously clear - in the Indexer's best judgment - then the Indexer's job is done for that field. If the Indexer is unsure of a character or string of characters in a name, then by using wildcards ("?" and "*") to indicate what parts are unclear, the Indexer provides Researchers with the result of his best judgment yet allows them to use their judgment. Maybe, if given the opportunity, the Researchers might see some options the Indexer didn't consider. Wildcards give the Researchers complete freedom to explore the unclear parts and decide. They can also do a Google search to narrow the choices. Using wildcards broadens yet guides the possibilities for the Researchers rather than substituting the Indexer's judgment for theirs in unclear situations or perhaps limiting it prematurely.
1 -
I will do the best I can. I only put ( or ) if there is one letter in question and only 2 possible letters. I will try to stop myself but I did not see any instructions stating to only use ( or's ) in certain circumstances. I mostly review and I see a lot of other indexers doing the same thing. That is why, when I first started, thought it was alright to do the ( or ) option.
0 -
Hi, James. That's all that's expected of us. But for your consideration -
Here, from the General Indexing Guidelines (GIG) section - usually, the last section - of your project instructions is the complete guide on what to do when you can’t read part or all of a field on a record. Using Or in the way you wish is not one of the options.
https://prod.familysearch.psdops.com/cmsa/idx/unreadable-information
Here, from the Indexing Help Center is a Knowledge Article on when and where to use Or.
1