2022:Review Queue (Node Type)
About
Review Queues allow further control of what Batches and tasks Grooper users have access to.
- Imagine a situation where you have several Batch Processes running in your environment and several users reviewing work in Grooper. You may want to assign certain users to certain Batch Processes based on their experience with the kinds of documents in the document set or quality of their work.
- Imagine another situation where you want restrict the kinds of review your workers do. Maybe one group only performs data review and another only performs classification review. And maybe any of them can do document scanning.
You can control the work presented to users in the Batches and Tasks Pages with Review Queues. This allows you to better filter work to your users by defining ACL settings for Batch Processes and/or steps in a Batch Process.
You can also think of this as a "soft security" measure. By filtering out work available to users, it acts as a kind of gatekeeper, controlling what comes across their desk.
- CAUTION! Please note this is not a "hard security" measure. There are conceivable ways in which a user assigned a certain Review Queue may still be able to access Batch content that is outside of their queue. For true "hard security", the best practice is to isolate that work in a separate Grooper Repository and restrict user access in the Security settings configured on the root node.
The general steps to create a Review Queue are as follows:
- Add the users to the Users list at the root node of the Grooper Repository.
- Create a new Review Queue.
- Select which Grooper Users you wish to add to the Review Queue.
- Then, the Review Queue can be implemented in one of two ways:
- On the Batch Process to restrict work accessed from the "Batches Page".
- This will prevent users from seeing any Batch using that Batch Process in the "Batches Page" interface.
- Only Grooper Users listed in the Review Queue will be able to access Batches with that Batch Process in the "Batches Page" interface.
- Use this option if you want users to "pull" work from a list of active Batches.
- On a Review step of a Batch Process to restrict work accessed from the "Tasks Page".
- This will prevent users from seeing the Review task in the "Tasks Page"
- Only Grooper Users listed in the Review Queue will be able to start the Review task from the "Tasks Page".
- Use this option if you want to "push" work to users, feeding them the tasks you want instead of allowing them to pick the Batches they want.
- On the Batch Process to restrict work accessed from the "Batches Page".