1950 Header Document signature problem
Noticed right away.
Every signature (by enumerator and checker)
is treated wrong way
Della M Burroughs is treated as Della, M Burroughs (treating given name as surname and surname as given name constantly)
Also I noticed something so bizarre constantly.
Here's the example, name does not match signature at all. Constantly in every header I did.
Comments
-
Read vs actual names
-, Alfred J > Marietta M. Mongar
Laura, Harsley > Laura Horsley
-, Eva Maenson > Eva Mae Benson
Elsie, B Mary > Elsie B Moore
-, D Comine > D Romine
Grace, Myers > Grace Myers
-, Charles A John > Chester A Cramblif
-, Ada May Smith > Ada May Smith
Carles, Denning > Charles G Demin
checker
blank > -, Marietta M.
Edwin Power St > Edwin W Powers Jr
How bad does this have to go on?
0 -
Hope they fix this soon. It is a MASSIVE waste of effort to fix these.
0 -
@W D Samuelsen and @VW_via_England , the automated/computerized indexing did not read these names correctly, but I'm sure the designing engineers of system are constantly working on it to perfect it. When we run across these, we are to correct them. This is our job as reviewers when reviewing this project, is to make sure the information is correct. It is the same in regular indexing when we are reviewing. Many times we correct what the indexer of the record put. Please take the comma out of the name when you see this happening. You are very much appreciated.
1 -
So we remove the comma so that it reads Della R Horst instead of Della, R Horst? Just want to make sure that someone doesn't have to go back and fix these so that it reads Horst, Della R. I tried reading the FAQ's but it doesn't give an example of how the name should appear. Same for the Checked by. It would be very helpful if the FAQ's were updated to include how the information should read. The other area I'm not sure about is the date checked by. If they write 4/5 - should it be spelled out April 5?
0 -
@Penny Schrock, yes, you remove the comma so it reads Della R Horst. We put what the document has and correct to match the document in the indexed fields if the computer didn't read it correctly, such as the computer putting a comma in the name. As far as the date, we are instructed to type it as it is written in the document.
0 -
AndLinda, It's not so much that the computer accidentally puts a comma in some names. Every name that I've seen either has a -, firstname lastname or it has firstname, lastname. Like the field has been set up to accept lastname, firstname. But every name I've seen is a signature, so firstname lastname. If the field could be set up without the comma, it would make things a lot easier.
1 -
I understand that, for some unknown reason, FS is 'required' to do what Ancestry has designed; BUT could someone explain the Genealogical value of the NAME of the enumerator & WHY so much time is used (wasted?) in deciding how to index it (or even to bother with indexing it). Ignore it & leave it to AI; along with many (most) if these indexing requiring.
Streamline & get the task done MUCH faster. In the meantime I'll personally just stick to 'Name Review'
0