Library records and current availability
The librarian wants to distinguish book titles from individual copies, track which learner borrowed a copy and record its return. The current public module directory includes Library, but the reviewed application does not yet provide a dedicated lending workspace. This guide identifies what can be prepared without pretending a checkout workflow is live.
On this page
Check availability before rolloutPrepare your migration recordsUse existing tools within their limitsCheck availability before rollout
Do not treat the Library tile or a catalogue label as proof that issuing, returns or reservations are enabled. Confirm availability with your administrator and use only working actions in the deployed application.
The current module route does not expose a dedicated library controller view. There is no verified issue/return form to follow in this release, so this guide does not direct you to create fictional loans.
Prepare your migration records
- Keep title, author and catalogue identifiers distinct from each physical copy identifier.
- Prepare current borrower references, issue dates, due dates, return dates and unresolved exceptions.
- Keep reservations separate from issued copies and retain the order and expiry evidence.
- Reconcile physical stock and legacy loan records before any approved future import.
Use existing tools within their limits
Documents can store authorized reference files; Projects can track a library stocktake as a task plan. Neither creates a library loan ledger or enforces borrowing rules.
If an actual fee or supplier purchase is required, use its normal finance or procurement source document with supporting evidence. Do not create a fee simply because a reservation was written in a note.