Approve request as is

When a new request is placed, ReShare performs a number of checks (if enabled) before it validates the incoming request and assigns it to the first lender in the rota. These include the borrower check against your local library management system using NCIP, a check to see if the patron’s max number of duplicate requests has been reached, and whether the request has a clusterID that can be used to look up the title in the shared inventory.

If any of these checks fail and the request cannot be validated the Approve request as is action can be used to override the failed check and allow the request to proceed anyway.

This action can be useful for a number of reasons:

You have determined that the patron will be allowed to make the request, but you can’t resolve the issue in your local system.
The duplicate request is not a true duplicate as it is for a book club request where multiple copies of the same title are needed.
The request may have come in without a clusterID to search for in the shared inventory and you would like the request to be passed “as is” to the lender of last resort.

Note: The Approve request as is action will apply to all three of the above checks, no matter which state the request was in when the action was applied. For example, if a request lands in a state of Invalid patron and the request happens to also be a duplicate request for that patron, applying the Approve request as is action in the state of Invalid patron will allow the duplicate request check to pass.

Note: The Approve request as is action replaced the Override borrow check starting in release 1.15

Action workflow

Navigate to a request in the “Invalid patron”, “Requires review - possible duplicate”, or “Requires review - blank form” state.
Click the “Approve request as is” action from the More options list.
The request will pass the failed check and will continue to move through the workflow.