What you will learn
- How interlibrary loan works, step by step, for readers and staff
- How lender routing finds a library that holds the item and can lend it
- How borrowing, lending, and return are tracked without losing items
- How copyright rules shape what can be copied and supplied
- How charges, statistics, and network reporting are handled
What the project is
No library owns everything its readers need. Interlibrary loan fills the gap: a reader requests a book or a journal article, their library asks other libraries, a lender supplies the item or a copy, the reader uses it, and the item returns. That chain involves the reader, the borrowing library, the lending library, and often a courier or postal service, and without a system, requests are tracked in email and spreadsheets, where they get lost.
The system manages the request lifecycle for both sides. Borrowing libraries track their readers' requests. Lending libraries manage incoming requests, supply decisions, and returns. Both sides see the same request status, so neither has to chase the other for updates.
Core features
Request intake is the core: readers request from the catalog or a form, with bibliographic details checked against holdings so requests for owned items are redirected to local copies. Lender routing searches network holdings and routes to lenders in an order the borrowing library configures, such as nearest first or fastest first. Tracking covers every state: requested, routed, shipped, received, on loan, returned, and complete, with due dates and renewal handling.
- Reader request intake with holdings checks against local copies
- Lender routing ordered by configurable rules: nearest, fastest, or cheapest
- Request tracking across borrowing and lending sides
- Due dates, renewals, and overdue handling for borrowed items
- Copyright compliance checks for supplied copies
- Statistics and charges reporting for the network
How it is built
Start with borrowing requests and one lending partner, and prove the lifecycle end to end, including a return. Routing rules and network features follow, once requests are flowing reliably. Integration with the catalog matters early: requests should start from a catalog record where possible, so bibliographic details are correct.
- Map the request lifecycle with borrowing and lending librarians.
- Build request intake with holdings checks.
- Add lender routing for one partner, then configurable routing rules.
- Add tracking, due dates, renewals, and returns.
- Add copyright checks, charges, and network statistics.
Technology considerations
Network interoperability is the technical core. Libraries use standard protocols for holdings search and request exchange, and the system should support those standards so it can join existing networks rather than requiring every partner to adopt a new system. Request identifiers must be stable across both libraries' systems, so a request can be traced from either side.
Copyright handling needs structured support. Supplied copies, especially journal articles, are subject to copyright rules that limit what can be copied and how often, and the system should record the basis for each supply, so compliance can be shown, not just claimed.
Challenges to plan for
The main challenge is items in transit. A book shipped but not received, or returned but not checked in, creates disputes between libraries and frustration for readers. Tracking with shipping records, expected arrival dates, and overdue alerts for in-transit items reduces those disputes, but only if both sides update the request promptly.
- Items lost or delayed in transit between libraries
- Requests for items the borrowing library already owns
- Copyright limits on supplied copies, especially journal articles
- Lenders declining requests without reasons, slowing routing
Who it is for, and its limits
This system fits public library networks, academic library consortia, and individual libraries with active borrowing and lending programmes. It is most valuable where request volume makes email tracking unreliable.
It does not guarantee supply; lenders can decline, items can be unavailable, and copyright limits what can be copied. The system makes the process visible and efficient, it does not create holdings that do not exist. Costs and timelines vary with network size and protocol scope, so confirm with a quote before budgeting.
Frequently asked questions
How does a reader request an interlibrary loan?
From the catalog or a request form, with bibliographic details checked against local holdings first, so requests for owned items are redirected to local copies.
How is a lender chosen?
By routing rules the borrowing library configures, such as nearest, fastest, or cheapest, applied to network holdings, with fallback to the next lender if one declines.
What happens when the item arrives?
The borrowing library checks it in, notifies the reader, loans it for the lending library's loan period, and tracks its return by the due date.
Can journal articles be supplied?
Yes, as copies, subject to copyright rules. The system records the basis for each supply, so compliance can be shown.
What if an item is lost in transit?
Tracking with shipping records and expected arrival dates flags delays, and the borrowing and lending libraries resolve the loss from the shared request record.
How long does an interlibrary loan usually take?
It varies with lender availability and delivery distance, and the system shows the request status throughout, so readers can see whether their item is routed, shipped, or on its way back.