Ok my friends....fresh from the team...they are making changes to the transaction error button. They are listening to your requests! I'm not sure of the timing but keep an eye out for the change. In the meantime, you can do as others have suggested and check "Other" then comment "Not a Name" in the box. Hopefully this change will be quick! We really appreciate your patience!!! I know some of this has been really frustrating but you are making a huge difference in not only the project but the tool! Thank you!
It would also HELP the process if the Transcription Error Icon would be MOVED to the left (next to unsure)
Doing UTAH names now, seem to getting many more of these 'errors' - It takes MUCH longer to enter these errors, than simply clicking (or correcting) names (Primary goal of this exercise) BECAUSE of all the unnecessary scrolling back & forth to enter the transcription error - from middle to bottom right to middle of page in box, back to . . . .
HOW ABOUT ONE SIMPLE CHECK BOX FOR "Not a Name" located next to "UNSURE"
It is taking MORE TIME to do ONE "Not a Name" than 10 to 20 name verifications (even if a change is needed) - not to mention the time to point it out here! Just found more (mow with 3 errors for 'Not at home' on each line - requiring 12 clicks - plus scrolling, versus ONE CLICK to verify a name.
One more page, 30 lines, 51 names (51 clicks, with auto advance to next name), 3 lines 'not at home' (36 clicks, plus scrolling back & forth)
We perhaps have completed less that 1% of this project - it would be very nice to get this UPDATED sooner, rather than later!!!! I see other posts on the subject, PLEASE FORWARD to TECH SUPPORT for action.
Same issue as above comments. Preferred solution: put a "Not A Name" button next to the "Unsure" button.
If not, at least make "Not A Name" the default for the transcription error screen, as that is the vast majority of transcription error markings.
YES!!! Please change how this is set up, it's incredibly frustrating and is wasting so much time that could be spent better!
It seems they took - "Not a Name" of the list of choices. Why?
I was just wondering that. Maybe they're making it its own button? Fingers crossed!
Well, they've changed the form. Slippery program. Now the Transcription Error form looks like this. No problem. I'll adapt, choose "Other" and "type" the reason in the white space. It has changed again. No need to keep the image of the work-in-progress form. Anyway, I changed my coordinates accordingly, and everything works OK again.
I'm just "Unsuring" them for now.
I have to admit the name recognition software seems like it is picking up 90%+
What has happened? All of a sudden, the “not a name” option has disappeared! Bring it back or explain why please.
I have been doing thousands and following the 1950 census project rules. It says the we click on transcription error and select “not a name” for those “not at home” and “vacant”.
PERHAPS, that is a GOOD sign and it will be replaced by a better system.
One can always HOPE!
I hate to suggest that if a change is forthcoming as a result of forum comments, it might have been nice to see some comment herein. (could be on one of the other comments)
eg: Sent to Tech Support or,
under consideration or,
We are looking at a repair or, ????
Some folks are never happy : ) - in the meantime I will simply add a comment "Not a Name" in the Transcript Error box (Well, I just tried that a half dozen times successfully, & now it seems locked up, so I'll retire for the day.
There's another post near the top of the page where we were just talking about this. I'm wondering too. I'm hoping they're in the process of making "not at home" its own button next to "unsure" because clicking the flag etc. was incredibly inefficient!
Maybe if we all retire indefinitely, someone will get the picture and fix it. The development team at FamilySearch seriously needs some useabilty testing before they release their apps.
Yes, I have to wonder if anyone there actually tried doing this themselves before it went live.
I am going to politely ask that you refrain from putting others down (including those associated with FamilySearch and/or speculating on what FamilySearch does in our community. This is a violation of our code of conduct.
I'm not sure if this was directed at me, but mine was a sincere question, not a put-down. Was this system tested prior to release?
I have doggedly tried to teach the AI to recognize Not at home, No one home, Vacant and the like until my fingers hurt. It clearly can't learn this from us! I'm taking time off, too.
I am confident they will fix this "not at home" issue soon. I have to give the team credit on the mobile app. I made a suggestion that they change the input arrow from a light blue to a darker color and they have done that. It is such much easier now. Thank you!
Thanks for trying - So AI can't recognize it; AND it's now back to the way it was - (which is likely the LEAST efficient way)
There were other possible 'solutions' listed to at least make it easier:
"HOW ABOUT ONE SIMPLE CHECK BOX FOR "Not a Name" located next to "UNSURE""
"at least make "Not A Name" the default for the transcription error screen"
Turn off the checked default of "Not Readable" and make "Not a Name" the default
Relocate the links so scrolling is minimized, rather than needing to scroll back & forth, up & down for each entry.
How about an "Ignore" button?
Could something be done in the highlight to eliminate the duplicate "not a name" selection TWO or THREE times for EACH line??
I agree with @CaptBob. How about separate buttons for "Not a Name" and "Incomplete". And please - provide keyboard shortcuts for all the actions.
EG: Alt+B for Back, Alt+M for Match, Alt+E for Edit, Alt+U for Unsure, Alt+N for Not a Name, and Alt+I for Incomplete.
Transcription Error feature seems to cause the indexing to crash more frequently.
I was in middle of any of these 20, 30, 50, No limits - when I get error on this page and tell me to refresh - I get not refreshed page but get a new one and start over.
Then I noticed something is wrong - the length of time for "Error Reported" to clear up, it just piled up to 5 or more in queue, causing the page to "crash".
Now as of this message, Oregon, Idaho and Arizona are frozen, "We didn't find any names.... "
Arizona has been online since Monday, stalled at 49, Idaho stalled at 84, Oregon at 71. All has been online since Monday.
Crashes are driving away the volunteers per comments in several Facebook pages
This is weird.
for "No one home" and I get these, from a single page.😃
No One Home
When convenient, I trigger a Transcription Error for missing names on a page and choose "Incomplete." It may compromise a genuine name for a moment, but the back button should allow me to fix that without withdrawing the "Incomplete" message.
If the missing names occur at the end of a page, as you said, you can't move back from the new page to the previous one - I tried - but it does trigger an error. That error might draw attention to the page and the missing names. In the end, hopefully, the Family Reviewer will catch and add the missing names.
I took a day off from Name Review, hoping that something may have IMPROVED. (regrettably, it has NOT) Please see my comments above.
Conclusion to today's experience:
This was an incredibly inefficient waste of time - which will likely be responded to with: 'don't worry it will be reviewed AGAIN when the "Family" review is done. This ALSO sounds like a lot of repetition and may make the NAME review an absolute waste of time. I assume the family review may ALSO have the the same difficulties with 'Vacant", etc. This review has barely begun for Millions of records, which appears will present Tens to hundreds of Thousands of "vacants" - PLEASE Fix it!!!! (See multiple suggestions above!
I requested AZ 20 names, got a page containing 22 lines, 8 were vacant or 'no one home' - The verify program ran thru 17 lines (NOT 20). One record was a questionable 1st letter of M vs W; after completing the supposed 20 (actually 17), I had to ask for more & it continued on the same page with the same 22 lines (with 2 of the vacant entries) I then found another records with the questionable 'W vs M' which was clearly a "W" - BUT I wasn't able to go 'Back' to correct the First 'W vs M' because it was my 'second' PAGE. I spent Entirely too much time with the "Not a Name" corrections (incredibly inefficient so far)
PLEASE create a "Not a Name" button next to "Unsure" or at least read some of the suggestions above.
My apologies, if this seems harsh, BUT . . .
Addendum: FWIW, I have not taken this review task lightly (I firmly believe in the concept of attaining "records worth of ALL ACCEPTATION" (D&C 134); I believe I have now (attempted) to review well over 1,000 reviews (UT, ID AZ, etc) for THIS process & nearly 200K in indexing. I'm slowly beginning to think my time can be better used going back to my own research!
@CaptBob There are a couple of reasons why it's valuable for Name Review to be done, even though they will be reviewed again. For one, we often like having a 2nd (technically 3rd) pass at names. It helps with accuracy when multiple people look at it. Additionally, if we are reviewing and correcting surnames before the Family Review step, it makes it that much more likely that families will be found when they are spelled correctly. :)
They are working on a separate Not a Name button! I know that piece has been frustrating for everyone.
I don't mind at all the Transcription Error button..
Just move it to the left closer to the other choices. It is too far to the right.
AND remove the "Not readable" checkmark default..
Leave all Transcription error options unchecked.. Leave the Reviewer choose which option to checkmark.
The new "Not A Person" button is live this morning!
@Marianne Merawi Sorry it took me a while to respond. Yes the system was tested. But no testing is foolproof and bugs do still come out when launched to production. We're sorry for the frustration everyone is having but we also thank you immensely for helping us make this tool better.
Thank you, Thank you, Thank you!!!! I returned today to 'index' some 1950 Florida census records and was pleasantly surprised to see the "Not a Name" button! It did exactly what it should (the Florida records did not have any way as many as the previous states, BUT 'No one Home, Vacant, et al' were rapidly !!!!!).
You have saved an enormous amount of wasted time for the remaining millions of record.
Thanks specifically to @ishkabibble & @Sam Sulser & @Janell Vasquez (are you a Mod or employee, you seem to provide an abundance of good inputs) & others I likely missed & ALL the other fellow users who weighed in the various forum postings herein.
No if you had just put it about 3 inches to the left . . . (kidding)
I did several hundred FL records and was likely 20-30% more efficient!!