-
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
2313 - Abandon subject without losing transcription #4217
2313 - Abandon subject without losing transcription #4217
Conversation
Ok, if there is a bracketed subject in the page, and the page is saved, then we need to save the state/fact/existence of that subject, even if it is wrong. The scenario here is "I messed up, I realized it during the subject categorization, so I'm going to cancel and go back and fix it." Subject categorization as a step takes place after the page is saved, so we'll have orphaned subjects if they cancel and go back and fix it. So here's what we think we should do:
So for your scenarios: One caveat: Project owners can upload canonical subjects via a spreadsheet, and we don't want to delete those if they are not used. If the subject record was created via a spreadsheet upload, then the Article record will have a provenance of the filename they uploaded. Every subject that was created via the transcription process will have a nil provenance. So when we "clean up orphaned subjects" at page save, we need to only delete articles with a nil provenance and no links. Removing |
63b4c80
to
aee5305
Compare
I've just tested this manually, and it looks like--between this PR and #4175--we've missed an important piece of functionality; abandoning subject creation without losing transcription. Here's what I did:
|
9600571
to
70814ee
Compare
This works as designed, and is easy to use. One question is whether--while we do this work--we want to eliminate orphaned subjects to handle this use case:
|
Because we create the subject before asking the transcriber to categorize it, I don't know of a straightforward way to keep track of this and delete the subject from an abandoned subject categorization. There's no guarantee the subject needs to be deleted -- maybe something else made them cancel -- so either we:
I'm actually fine with the first solution. |
The alternative approach that would accomplish this is to simply delete all subjects with no |
That sounds great! Let's do that. Is there a case where folks might create subjects by hand, rather than emergently? |
The only ways for subjects to be created is
|
Discussions so far with @benwbrum
I'm playing around the functionality. Correct me in if I am wrong here, but I think these should be the cases:
I want to go back and make some changes
a. We click on cancel button. This should not assign a category, BUT I would assume this should also NOT create the subject, otherwise why cancel in the first place.
I want to save my changes
a. We click on save or continue button. THIS should assign categories and redirect back to same page (in case we want to edit some texts, add new subjects, etc).
b. Regardless if they assign the category here, the subject SHOULD persist.
I want to save and continue to next page
a. It creates and assigns subject and redirects to next page
I believe this should be the case, as was described by the user on the ticket
Clicking cancel should NOT persist the subject at hand.
That being said, I first went ahead and implement what was instructed in ticket where:
I took out the third button named
next
This is because past ticket made thecontinue
dependent on the workflow. i.e. If save was clicked it should remain in same page, if done was clicked it will go to next page. So I believe only 2 buttons are relevant here (cancel and continue).Tagging @saracarl as well