Publish/Review workflow options

One area that is varied across universities is the reviews process in relation to reading lists. One of these issues is what happens when an academic has completed their list, can they send it for review or do they just publish it? The option before was that an academic could publish their list and the library would not know this had happened so the following options have been created and can be enabled on your tenancy.

  • Review & Publish: both publish and request review actions are available to a list publisher and they have the choice of which action to take. 
  • Review & Publish with reminder:  this option behaves as the previous option, i.e. both publish and request review actions are available but if the publish action is chosen, the user is reminded about requesting a review. The user will still need to publish after requesting a review.
  • Force Review  - UPDATED: Both the publish and request review actions are available, but publishing will always force a review request unless you have the View review data permission within your role/s held. If a librarian/library staff wants to raise a review request, they have to request a review manually as the publish action will no longer force this workflow. This change is designed so that when quality checking a list or making a small change such as an edition swap doesn't trigger a review request unnecessarily.
  • Review only: the publish action is not available and the only option is to submit a review request, on completion of the review the list is automatically published

So if you want to ensure the library sees all reviews you will want to choose the "Force Review" or "Review only" option. But if you are happy to trust that your academics will send their item for review then you will want to choose one of the first two options, it maybe having a reminder will be enough to prompt them to send for review.

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk