In most of the buckets in the AI OA Workflow, there is a way for a publication to be "weird" and get stuck in the bucket. For example:
Publications in the DOI review bucket that are not yet published: We anticipate they will get a DOI, but we don't know it yet. Or we anticipate that they won't, but we can't be sure until they are published.
Publications where the file has tracked changes that need to be accepted or extra content that shouldn't be deposited in ScholarSphere (such as a letter from the journal editor) (issue #947 would allow us to resolve these in the workflow -- until then I am resolving them outside it)
These files end up stuck at the top of the list of publications/files to review until I (Ana) get a chance to clean them up. It would be great to have another bucket for these items and a Boolean to toggle so that they won't show up in any of the other buckets (except the troubleshooting bucket -- everything in the workflow should be there). This bucket could be the second-to-last one on the list, about the troubleshooting bucket.
Suggested wording for this bucket:
Flagged for Review
Publications that an admin user has flagged due to unusual issues with the publication or associated files
In most of the buckets in the AI OA Workflow, there is a way for a publication to be "weird" and get stuck in the bucket. For example:
These files end up stuck at the top of the list of publications/files to review until I (Ana) get a chance to clean them up. It would be great to have another bucket for these items and a Boolean to toggle so that they won't show up in any of the other buckets (except the troubleshooting bucket -- everything in the workflow should be there). This bucket could be the second-to-last one on the list, about the troubleshooting bucket.
Suggested wording for this bucket: Flagged for Review Publications that an admin user has flagged due to unusual issues with the publication or associated files