Tired of Indexers not following simple rules.
Have been mostly Reviewing Naturalization forms. Now doing Illinois [Part D]. Almost 100 percent of the time they keep on entering (Male) when they shouldn't be. Before anyone indexes Naturalization or other projects for the first time, they should be put to the test to confirm they are ready. There are many more issues, but I don't have time to put down every single one.
Answers
-
This has been going on for basically, ever. I've made a handful of posts about this, and how to index them correctly. I've also posted about reading the PI, GIG and Field Helps. Either indexers don't read them, partially read them or just don't care. I haven't seen a beginner batch in quite a while. I think the last one was Tennessee Death Records and some of those were screwed up or even so badly indexed that it was better to send the batch back for reindexing, so new indexers have to go for, at least, Intermediate batches without knowing how to index them. Beginner batches hone an indexer's skills so they came move up to Intermediate. Something like 1,000 Beginner batches should be the mark to where new indexers can access Intermediate batches.
I think they should bring back feedback on batches. That helped me a ton when I first started out, but that was jettisoned when they switched to web indexing full-time. How else are new indexers going to learn?2 -
I am more than just a little aggravated when I see batches returned for indexing when I know they were done properly to begin with. I just ran into a few of them just now.
0 -
Dunno about the naturalizations and such, but in the Hungarian project, people generally ignore the instructions because they disagree with them. I'm of two minds on this: on the one hand, I sympathize with wanting to stick the surname in for the child even if it's only recorded for the parents, because I've come up against Search - Record's literal-mindedness — but on the other hand, does it really ever hurt anyone not to put in the sex, if it's not recorded? (You may think Toni must be male and Béla must be female, but you'd be wrong, if you were indexing Hungarian records.)
In the Slovakian project, I return any non-tabular Latin batches, even though I'd be perfectly able to do them, because I can't abide the thought of indexing all of those genitives for the parents' names. I know that if I follow the instructions and index Johannes filius Georgii Szabo with father's given name = Georgii, there will be a clueless researcher somewhere down the line who will see this as proof that his ancestor was called Georgie.
1 -
I do that sometimes too. For example: (1) When it is written Poland Russia, I eliminate Russia because it took over Poland. (2) I do not enter Polish for a color or race when their birthplace was Poland.
I also wish the instructions about Certificates of arrival were clearer. Example: Should we just completely ignore them? Sometimes the state puts the names on the main form. I have to index those.
0 -
Why are you omitting Poland? We index what it was at the time of the document. If it was Poland Russia on the document, you index Poland Russia. It may be Russia in 2024, but at the time of the document, it was Poland Russia. If Polish was the race, and the color is not there, Polish is indexed. Same with German, Hebrew, Scandinavian, etc.
With the exceptions of Alaska and Ohio Part A, Certificates of Arrivals are not indexed. It literally says that in the PI:
Do not index affidavits of witnesses, certificates of arrival, certificates of loyalty, examination records, or naturalization cards in this project.Unless you are working An all-records project, nothing from the COA is indexed.
1 -
I'm not inserting things that don't make any sense. Why enter in something that is not in the drop-down list? If Polish or Italian were in the list, of course I will enter them. I will enter what I see from now on in regard to Russia Lithuania etc. For your information, I have been just entering Poland only when it was written Poland Russia.
0 -
It doesn't matter if it doesn't make sense to you. You have to follow the Field Help instruction.
If the color or race has been abbreviated and you can tell what the abbreviation stands for, choose the race from the drop-down list. If the color or race is not found in the drop-down list, type what you see.
And again, you type what you see with the birthplace. You type what it was at the time of the document, not what it is in 2024. Austria Hungary no longer exists, but when it says Austria Hungary, Bohemia, Poland Russia, you index. It literally says this under the Birthplace Field Help:
Do not change the place-name to its modern name.
You don't get to play fast and loose because you don't think it makes sense. You have to follow the PI, GIG and Field Helps. Doing what you're doing only creates headaches.2 -
Please Define Nationality. Field help - Do not index nationality in this Field.
0 -
Nationality is the state of belonging to a nation or country. American, German, Russian. In the Nats project, 98% of applicants Nationality is the country they were born in.
This batch shows that the applicant's race is English and the nationality as British because she was born in England.
[MQ2V-KP4]0 -
I see what James is getting at, with that bit about nationality. (This is the Illinois naturalizations, but I'm pretty sure it's not new or unique to this project.)
Field Help: Color or Race. "Do not index the nationality in this field."
OK, fine — but the form says:
My race is Dutch.
"Dutch" is a nationality or ethnicity, not a race. So, does that bit of instructions mean that I shouldn't index it? Or is it just saying that if there were a spot on the form labeled "nationality", I shouldn't index its contents as the color or race? That latter should go without saying -- I mean, if it says "occupation", I'm not going to index it as the birthplace, despite there not being any instructions against it, right?What is the actual purpose of that line in the field help? What information is it trying to convey?
(Leaving aside that at least four of the choices in the drop-down are nationalities.)
(The fact is, the whole question of color, race, nationality, ethnicity, etc. is Complicated and Fraught, and people in past decades and centuries got it right just about as infrequently as we do. Which just underlines the need to have sensible instructions — and then to follow them, even if the contents of a field do not fit the modern definitions.)
0 -
If the race is Dutch, German, etc, it was the race at the time of the document. We now associate Dutch with nationality, however, in the indexing world, it was a race. Nationality is something like British, Russian, Poland, especially when Jewish people applied. The race is Hebrew, the Nationality is Russia, Poland.
We do not apply modern definitions, places, etc. in indexing.2 -
I really wish they would add a feedback feature!
1 -
Is there anywhere we can find information on anything we personally are indexing incorrectly? I'm a beginner…I now have 1000 under my belt. But, if I've incorrectly indexed something the same way for the past 1000 times, how am I to know? I have read the instructions over and over to make sure but if we are not corrected, who's to know?
4 -
There is no place you can check your work, but what you can do is come here and post your issue; preferably with the batch code, and we'll take a look.
0 -
Thanks!
0 -
I thought we had a feedback feature at one time.
Some of the errors are indeed committed because of unfamiliarity with the tools provided. The presentation of the tools can be overwhelming to beginners. There's the urging to help with family history and indexing, but then the willing are slammed into a wall of non-intuitiveness. The willing are whittled down to those that are still willing, and will try to muddle through and gain experience, but the muddling-through is going to be a frustrating experience when the tools aren't well-demonstrated for someone alone at home.
Particularly for the elderly alone at home.
Getting rid of feedback options is not a way to improve things.
1 -
I also wish there was a feedback option available. When I started I was confused by all the information, jargon and dry instructions which needed to be interpreted. Unfortunately there are no projects for beginners and I really wanted to help out with indexing. I was trying to make sense out of project instructions with mixed results. At the beginning I was too shy to post questions, which in hindsight, would be much better thing to do. I know I made a lot of mistakes and I would like to apologise to the reviewers for being a nuisance.
It might be helpful to have something like mock indexing batches which would have to be completed before starting to index the project - short e-learning module with the test at the end - just to make sure beginners have opportunity to gain more confidence and they do not try the patience of reviewers by making the same mistakes all over.
2 -
Do the comments here get reviewed by any kind of moderator? Could that review result in contact for the person posting?
I have constructed step-by-step, screenshot-by-screenshot, instructions in the past to help those completely unfamiliar with a computer task. That might help here.
1 -
David, can you post your instructions, please? It would be so helpful
0