Program problem with 1950 census
I've been reviewing names on the 1950 census.
Problem: when selecting "Transcription Error" .... "Not a Name" it takes several tries of "submit" before it's accepted.
This may sound like a minor problem but it's really frustrating when your rolling along matching or correcting and then coming to a complete stop because "transcription error" is not working correctly.
Hoping the program manager sees this message and has the problem corrected.
John, Atlanta
Comments
-
Yep, you are not the only one in this boat. Lots of folks experiencing issues getting the Transcript Error to commit.
2 -
Thank you for reporting this challenge. We have notified the engineering team. We appreciate your contributions and patience!
2 -
Agree 100% getting the Transcription Error function to regularly accept the 'submit'. Sometimes it will take the 1st attempt, most of the time I find myself clicking over and over, and clicking different checkboxes, etc. just to get it to take. No joking, for many I have had to 'submit' more than a dozen times on one 'name' before the system takes.
On the plus side I am astonished at how well the handwriting recognition is working on the names. MUCH better than I was expecting!
1 -
Agree 100% this is a major problem.
On the other hand I am astonished at how well the handwriting recognition is working. MUCH better than I was expecting.
0 -
Transcription error seems to be working for me, but with a slight delay in accepting my notations.
It is pretty fast to index this way when the handwriting is fairly legible.
I do notice the blue box is not always centered on the name, sometimes it is halfway between two names.
Also, there are pages where the last name is a continuation of the last name from the previous page, and no way to go back to see what that was, so hopefully that will be fixed in family groupings.
Overall, it seems to be working well.
1 -
If I wait 2-5 seconds after submitting the transcription error then it always returns a successful notification.
0 -
Ditto everything Daniel Taysom said. That's my experience, using the web interface on a computer.
Clearly, when you report a Transcription Error, much more processing is happening, for some reason, and it's happening in "real time". If it were truly an error--something you don't expect to happen often--that might make sense. But Not-A-Name is routine here; I estimate at least 5% of the census lines I've checked were Not-A-Name, either because a house was vacant or no one was home.
The processing for Transcription Error (at least for Not-A-Name) needs to be streamlined. Capture where the non-name was, then schedule the rest of the processing for later, in a separate thread that doesn't block the user interface thread.
2 -
I, too, have had trouble with Transcription Error. I try over and over then finally just stop reviewing this batch. I'm sure it will get fixed. FamilySearch always gets the job done!
The computer indexed names are nearly 100% correct. What a success.
0 -
I think one of the main problems here is people clicking submit for the Not a Name error, over and over....
STOP DOING THAT!
You are just overloading the server with requests, hence, making it slower.
I have some take 10 minutes to 30 minutes. I would not repeat for the same submission until after 10 miutes.
0 -
Please Fix that Transcription error reporting for web reviewing...
I have some sit here for 30 minutes and nothing happen.
I am not repeatedly hitting the submit button.. Sometimes I will click submit after 5 or 10 minutes and have waited 30 minutes to hit the submit button again before it went through..
0 -
I agree this is a major issue. I will never wait 30 minutes for a response. If the system does not respond within a minute there needs to be some modification to the software. I have not found a consistent way to get a response. Sometimes repeating the submit will finally get a response and other times nothing. I indexed 2 sets of 20 name and the delay in doing not a name was more that 50 % of my time. Please stop the operation until this is fixed. It is really discouraging.
0 -
Update: today, April 4 ...... I worked on the three states and the Transcription Error -- Not a Name went through just about instantly ............ so, thank you for fixing this problem.
I have one other "wish" ....... remove the check mark from the "Not Readable" box and put the check mark in the "Not a Name" box. 100% of my Transcription Errors were for "Not a Name" ....... or as an alternative, don't have any of the boxes checked. Thanks.
3 -
Thanks everyone for sticking with it through this frustrating issue, we're all grateful that one is fixed! It will get even better in the next day or so, stay tuned...
In general for suggestions or bug reports, to get them directly to the engineering team, you can send them through the Feedback button on this page: https://www.familysearch.org/getinvolved/1950
1 -
Thanks for the info on how to reach the engineering team.
I would just like to point out that on the web interface, the feedback button is a tab on the side of the page. It is not at all obvious that you can report bugs or share suggestions by using it. The text box is not visible at all until you click on a "feelings" emoji. So, I can see why these issues are being shared through numerous threads in the community.
I rate the feedback tab 😞
1 -
Yeah, I understand....
1