The “Close request manually” action allows a user to close a request in their own tenant from any open request state. This action is intended to be used to resolve problems with requests that have been inoperable due to system errors or unresponsiveness by the other party.

Action workflow

Navigate to a request is that is an open state.
Click Actions>Close request manually.
Choose a closure state from the dropdown menu.
Click “Close request manually.”

System behavior

Closing a request manually differs from routine system closure in several ways.

Local closure only

When you close a request manually, it will only be closed for your library, and not the other party to the request. This approach prevents new discrepancies from arising when you close the request. For example, if you close a request that has been return shipped because the supplier never completed it, the supplier will not lose the ability to complete the request should they ever choose to.

Messages

If you close a request manually, the other party will receive a message that says “The request/supplier has closed this request.” This message is intended to alert the other party of your action, in case they also want to resolve the request on their end. They are not required to take action.

Notices

Closing a request manually will not send any patron notices. Because this action is intended to resolve exceptional errors, we cannot be sure that a patron notice will make sense in all contexts when this action may be used.

Resuming a request

It is possible that a request you’ve closed manually could be resumed by the other party. This may happen if, for example, you close a request that was never shipped. If the other party decides to ship that request after you’ve closed it, your version of the request will be reopened in a shipped state. The goal of this behavior is to reflect reality. If that supplier has in fact shipped the request after a long period of inactivity, the system should reflect that circumstance accurately.