-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usability of "save" and " done" buttons #3773
Comments
I think the third option, "save draft" & "done", is the most reasonable fix. |
I finished working on this: https://docs.google.com/spreadsheets/d/1uyujxzXtHMu54aRbJeE5E3AlmhVQVqSz3rfs_YvifWk/edit?usp=sharing |
I think this is ready for @WillNigel23 to work on, given the other work on page status and flow. #4159 should be done first; then we can review the items left here. (I suspect that the only work remaining here is to rename "Save" to "Save Draft", but I could be wrong.) |
When you transcribe a page right now, you have two buttons at the top that make sense to click: "Save" and "Done"
"Save" marks it as transcribed but not completed. "Done" marks is as transcribed and completed. Both buttons actually save the transcribed text.
Right now, folks who have pages that are done think they have to click "save" and then "done". Which is twice the work they actually have to do; "done" would do the same thing.
I've got three options for fixing this. The buttons continue to do the same thing, but are relabelled:
We'll need to think through & experiment with what happens if a page is reviewed and approved, and then edited again.
The easiest way to capture some of this is via the page's "settings" tab which has "page status". Maybe a spreadsheet? ;)
I think to figure this out you'll need to create a private project, upload a work, and work through 2 configuration scenarios; one with optional review and one with required review. You might need 2 users (but maybe not?); a transcriber one and a reviewer one.
Please also read issue #2651 which is related. Maybe we can solve that one here, too? If not, at least it will help explain what's going on with page statuses, which is useful for this issue.
The text was updated successfully, but these errors were encountered: