Open ryscher opened 1 year ago
@ryscher : I suspect the author may have de-selected the PPR checkbox which then placed the submission in our queue. Can you confirm?
If this is true, what if we disallow authors from de-selecting the PPR checkbox for Pathogens titles. Similar to what was implemented with this ticket. This way, only an 'accept' decision will move the data submission to the curation queue OR a request to our team to take action to manually move it.
Here's an example I've been putting back in PPR every few days for a while: DOI 10.25338/B8ZP83
What happened on this one is that the original journal rejected the MS, so it was withdrawn, and when the author went back in to put in the new journal metadata and update the submission, they missed the radio button (or checkbox, not sure) and accidentally submitted it for curation before they were ready. To make it more complicated, the MS has now been accepted at the new journal, but the author still isn't ready for curation, so I've been putting it back into PPR until they email me back about it.
Once a dataset has started curation, it automatically returns to curation for each new version until it is published. Normally, this is the desired behavior, because a curator wants to know when a dataset has been updated by an author.
However, in some cases, this behavior is problematic. If a curator starts to work on a dataset and the author/journal decides that the dataset needs to be in PPR, any new version will immediately go to curation status, and may be accidentally published before the curator notices any notes about keeping it in PPR. For example, this was the cause for #2257. Although this is infrequent, users get very upset when it happens.
Is there a better way to handle this behavior? Possibilities: