These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Public Library System
- Features
- Interlibrary
Interlibrary
Prepare handoff requests and keep the independent decision linked to the loan.
OverviewHandoff Review Inbox×
Public Library System · Interlibrary
New
Handoff Review Inbox
Approval conditions
| Status | Revision | Owning library | Requested at | Requested copies | Due date | |
|---|---|---|---|---|---|---|
| Submitted | 510 | OL-704 | 12 Oct | 950 | 15 Oct | |
| Submitted | 640 | OL-476 | 19 Oct | 320 | 25 Oct | |
| Submitted | 810 | OL-781 | 03 Oct | 880 | 10 Oct | |
| Submitted | 180 | OL-662 | 26 Oct | 170 | 02 Nov | |
| Submitted | 100 | OL-468 | 03 Oct | 850 | 11 Oct |
6 of 6 records
OL-704Interlibrary requests · IR-29927
SubmittedRevision510
Requested at12 Oct
Requested copies950
Due date15 Oct
ParentLNS-34465
What you can do
Put the request beside the loan
An interlibrary request belongs to a loan and an organization. It names the owning library, requested copies and relevant dates. Its status moves from draft to submitted and then to an approved, rejected or completed outcome. The linked loan supplies the patron reference, item and current circulation state that the reviewer needs before deciding whether a handoff makes sense.
A coordinator prepares the request using the same loan the desk is already handling. Suppose a patron needs a copy from another library. The coordinator names the owning library and number of copies, checks the due date, attaches the relevant evidence to the loan and submits the request for review. The Collection Reviewer reads the submitted revision against the loan and custody history. The decision is a human act with a recorded reason.
How the work is organized
- Preparation. Draft holds the owning library, dates, copy request and linked loan for checking.
- Decision. Submitted work appears in the review inbox with its revision and parent loan.
- Outcome. Approved, Rejected and Completed distinguish decision from completed handoff.
What to agree during setup
Agree how libraries identify one another and what an owning library name means in a request. Set a rule for matching the requested copy count to the loan and available custody record. Decide what evidence the reviewer needs to see before acting, including condition and handover information where relevant. The coordinator should submit a complete revision rather than expecting the reviewer to infer missing details.
Choose who may prepare and who may decide. The Collection Reviewer should not be the same person preparing the action under review. Agree how a returned decision is corrected and resubmitted, and how the revised source is identified. An approval records a decision; staff still need to see the actual handoff effects and receipt before calling a transfer complete.
Check the handoff on an actual case
Take one requested loan with a collection item in another organization. Prepare a draft interlibrary request and attach a clear handover record to the parent loan. Check that the review inbox shows the submitted revision, owning library, copies and due date. Ask a Collection Reviewer to read the loan’s status and custody events, then record a decision with a reason. Confirm the decision record still identifies the source revision and operation key later.
Now inspect a rejected case. The coordinator should see why it failed and retain the earlier decision while preparing a corrected request. The Auditor should be able to connect the request, reviewer decision, loan and any operation receipt without guessing which revision was judged. That chain is what allows the next library to understand the handoff.
What your team sees
- Handoff Review Inbox — Submitted requests ready for the Collection Reviewer’s decision.
- Interlibrary Request Board — Requests grouped by their current decision and completion state.
Follow the work through
Use interlibrary handoff for preparation, review and outcome. See review and reconciliation to check a decision against its recorded effects.
What it keeps track of
Data model- Interlibrary requests
- Interlibrary loan handoff requests and their review lifecycle
- Loans
- Circulation loans with copy custody and patron entitlement
- Collection items
- Catalogued collection items and their eligibility notes
- Review decisions
- Independent review decisions on frozen revisions
- Record attachments
- Linked evidence files for loan records
- Operation receipts
- Durable receipts for guarded operations and reconciliation
Who uses it
Permissions- Collection Coordinator
- , Collection Reviewer, Auditor, App Administrator.
Set up Public Library System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.