⭐️ Name Review Is now LIVE! ⭐️
You can be among the first people to review names for the 1950 US Census Community Project. The states of Nevada and Oregon are now available for Name Review at https://www.familysearch.org/getinvolved/1950.
Please share your experience with others.
Comments
-
There are a couple things to be aware of as we are getting started:
______________________
What if the highlight isn't covering the full name?
Capture the requested information, whether or not the highlights cover the words exactly.
For example, both the first and middle names should be included in the First Name field, even though the highlight often doesn’t cover them entirely.
_______________________
How do I handle notes that are indexed as names—for example, “Vacant” or “No one is at home”?
Only names should be included in Name Review, so report these when you see them. To do so, click the flag on the right, then select the “Not a Name” option. You will be taken to the next name.
______________________
As of right now (Saturday evening), name review is available on the web and on Android phones. You might get some 1950 images on iPhones but the full experience is waiting on an update of the app.
2 -
As I was indexing a census sheet for Oregon, I submitted an entry (it was a match) on the next to the last line of the census sheet and the review indicator skipped right to the next page of the census. The name on that last line was totally missed. This only happened for one name amongst the many census sheets I reviewed.
Hopefully a family group review will pick up on some names that may be missed (?)
0 -
I think that the review indicator, the box where you see the computer-generated name, should be made a bit more flexible for us to move around. In a few cases it covers up the tail end of a letter in the script - examples: "g", "y", "q." Or it covers parts of a name where the census-taker tried to squeeze in a name down into the next line a bit. Just an observation ...
2 -
Like KH46, I too am reviewing sheets in Oregon, and finding the last few lines of a sheet are sometimes missed. I think I've done about 10 sheets and it has happened twice.
0 -
I did some Review Names in Oregon 1950 census this morning. Here are my questions:
- "No one home" should be marked as Not a Name but should I put a comment in the box? What comment?
- A line ( _____________ ) to indicate surname is the same as the one above--should I fill in the surname from the person above this line?
2 -
Hello,
Thank you so much for working so hard to get the 1950 Census project available so quickly! I am super excited to help out with this. I helped index the 1940 census, so it's fascinating to see how much the process has changed after a decade of technological development.
I just had a few comments for FamilySearch; maybe these are things you're already working on:
- When I go to flag an entry as a transcription error, the pop-up comes up with "Not Readable" already checked. Usually the error is due to something that is not a name, but when I go to check the "Not a Name" box, "Not Readable" stays checked, and I have to un-check it before I submit. It's a minor issue, but it gets a little annoying having to take an extra second to un-check that box when I'm constantly running into transcription errors.
- After I submit the transcription error, the system does not always seem to process it, as it keeps me on that entry. In previous review projects, the system automatically moves me to the next entry after I've submitted the error, but on the census page I'm working on, it doesn't do that no matter how many times I submit a transcription error for a single entry. There is no option to manually move on, so I have to click "Unsure" to get to the next entry even though that's technically not accurate.
- Are you working on anything to resolve the fact that the software keeps marking the surname ditto dashes as names? I'm finding it a little annoying to have to mark these dashes as transcription errors every other name (since the system gives me all the entries in sequential order, I get a last name, then a first name, then a last name, etc.). Or as Mary Louise suggested, should we be editing these dashes and writing in the surname instead? (After encountering several instances of the above-mentioned issue, for the last few entries in my batch, the software seemed to have skipped the dashes entirely and was just giving me first names.)
Thanks again for everything you are doing! This is probably a very large and complicated project.
5 -
Have been working on the Review Names and run into 2 problems:
1) Sometimes I will review the next to last person on page and once submitted, the system SKIPS the last name on page and moves to the next page. How can missing entries be entered?
2) FREQUENTLY when I select 'Transcription error' and select the appropriate check box(es) & hit submit, it just stays there and does nothing. I have had to check & uncheck boxes & hit submit multiple times to get it to submit and move on to next name. Further it doesn't tell me what is 'wrong' or what I need to do. So far I have been able to eventually submit name & move on, but sometimes only after a dozen or more tries. Frustrating! 😫 Other times it works fine on first attempt. I had thought a couple of times to have figured out a work-around by checking & unchecking boxes in a certain order and holding my tongue in just the right place, only to find out on next 'name' that required 'transcription error' that it wasn't a reliable work-around. 😫
For the troubleshooters - I'm running current & fully patched - Windows & Firefox while working on this project.
Hope we can get some solutions.
thanks,
0 -
Would really speed things along if the "transcription error" button was working consistently instead of very intermittently. And perhaps adding a "vacant/ no one at home" option might be a thought?
5 -
I like the idea of adding a "vacant/no one at home" button at the bottom of the screen like the dedicated 'Edit' button as this is a very common occurance, that would avoid going into the Transcription Error fiasco which is VERY problematical.
2 -
It would be great to have an Instruction Section for reviewing names to help us understand how to handle various common entries done by AI. Such as the underline in the surname field. Indexing does give us field helps on each field, but I don't see anything here to help us, and I am afraid I am just creating more errors that will have to be corrected further on in the process.
0 -
Instructions have been added to the FAQ: https://www.familysearch.org/en/info/1950-us-census-project-frequently-asked-questions
The FAQs about Reviewing the index are a bit down, after the information about the project itself.
0 -
Wow! This is so much fun. I've been editing on the NARA page for the last few days.That special algorithm Ancestry cooked up for improving the beginning index really worked, because the NARA base index is awful compared to what I'm seeing in the Get Involved section. And kudos to the people who created the review tool for names for FamilySearch. It's hard to tear myself away.
1 -
Very curious about why Utah was available first. My thoughts are that most Utahans during that time were predominently LDS so their family work most likely already has been done. Why wouldnt you start with other states with less percentage of LDS so this information could be accessed first and handled by the families? Just an innocent question
0 -
Answering some questions from the entire thread...
There are some great suggestions above - for the moment, the best place to send in your suggestions for change to the tool is using the Feedback link on this page - https://www.familysearch.org/getinvolved/1950
@KH46 - Yes, Family Review will pick up names that look like they were missed.
@Mary Louise Lillian - No need to put in any text in the box. No need to fill in a surname that's not there in Name Review, that will be done in Family Review.
@Teresa Arispe and @Taysom, Daniel B. - Hopefully the problem with it taking so long with the Transcription Error click has been fixed! They were working on it. Regarding the dittos as dashes instead of names - just accept those. No need to mark them as not a name. They will be expanded in Family Review.
@Marcia Bryan - I don't know all the reasons around the order of the states, but these first ones are smaller states that could be finished more quickly.
1 -
Last night and this morning I have reviewed names in the census project for New Mexico. Often, as I would submit the name of the last person on a page I would get a pop-up message:
"Something went wrong on this page.
An error occurred on this page. Please wait a few minutes and try again."
I have several questions. First, is this a known problem that is being worked on? Second, should I avoid New Mexico for now? Third, does this kind of error message mean that the entire page's review has been thrown out?
0 -
The fields are saved with each name field so that does nothing for the last name submitted. I've seen that problem as well, I think they are aware but in general you can report problems through the Feedback button on this page: https://www.familysearch.org/getinvolved/1950
1 -
Oh you mean THAT feedback button! It's almost invisible. I tried using the one at the bottom of the page and got taken back to regular community discussion. OK. Done.
0 -
Thank you for the fixes and improvements that have been implemented! I especially appreciate the addition of the "Not a Person" button. It makes all those "Vacants" and "No one homes" so much quicker and easier to process! Thank you for your hard work, programmers!
1 -
0