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.
- Library Management System
- Features
- Loan Intake
Loan Intake
Give each request an owner, branch, material and traceable status.
OverviewDraft Loan Requests×
Library Management System · Loan Intake
New
Draft Loan Requests
Submission waits for the library circulation operator
| Number | Name | Submitted date | Library branch | Owner | Material | |
|---|---|---|---|---|---|---|
| LR-94000 | Request 164 | 27 Oct | LB-2120 | LM-6729 | ||
| LR-24727 | Request 778 | 22 Oct | LB-4907 | LM-5804 | ||
| LR-98862 | Request 685 | 03 Oct | LB-7811 | LM-3930 | ||
| LR-77942 | Request 244 | 07 Oct | LB-5016 | LM-6777 | ||
| LR-92208 | Request 107 | 08 Oct | LB-3762 | LM-7808 |
6 of 6 records
Request 164Loan requests · LR-94000
DraftSubmitted date27 Oct
Library branchLB-2120
MaterialLM-6729
What you can do
Keep the loan record understandable
Give each request an owner, branch, material and traceable status. The team should be able to start at a request and reach the branch, material, people and evidence that explain the next decision. The main work screen is the Loan Requests Workspace, where the status board and selection-driven request detail keep the current case beside its history, requirements and pending decisions.
A patron asks for a material held by a particular branch. The operator records the request number, name, submitted date, branch, material and owner, then submits it. The owner can locate that case in My Loan Requests and the team can see it on the Loan Request Board.
How the work is organized
- Ownership. The operator prepares and owns the request. The reviewer sees submitted and verified work in context; administrators can read it to answer branch questions.
- Evidence. Keep the request’s linked records and source revision together so a later reader can reconstruct the action.
- Status. Read the saved status and decision values before moving the case forward or assigning a correction.
What to agree during setup
Agree how a request number is assigned, when the submitted date is recorded and who owns a case if it crosses branches. Staff should agree which material definition applies before marking a request submitted. The applicant reference and service code are request identifiers; their meaning should be explained to everyone who enters them.
The request number connects a patron conversation to the case. The Library Circulation Operator records the named material, branch, submitted date and owner, then checks that the selected material belongs to that branch. A status change should leave enough history for the next operator to tell when the case entered the queue.
Check the handoff on an actual case
Open a real request in Draft, then record the required intake context and submit it. Confirm that the board shows the new status, the owner sees the same request, and the material and branch match the patron conversation. Read the status history before correcting a wrongly selected material.
Ask another circulation operator to find the submitted request by its number. They should confirm the owner, branch and material without asking the preparer. If a material or owner is wrong, correct the request before evidence review and keep the status history readable. The reviewer should see the same current revision when the case reaches a decision.
What your team sees
- Submitted Loan Requests — Requests awaiting requirement review, with the assigned owner and material.
- Loan Request Board — Requests grouped by their current status for a quick handoff check.
Follow the work through
Follow request intake, evidence review and decision and delivery. Use the data model to check record ownership and references during setup.
What it keeps track of
Data model- Loan requests
- Loan requests, applications and cases submitted for a library loan.
- Library branches
- Branches, departments and library sites that own library materials and loan requests.
- Library materials
- Published material definitions, collections and lending entitlements offered by a library branch.
- People
- Staff, officers, reviewers and assigned team members.
Who uses it
Permissions- Library Circulation Operator
- , Library Reviewer.
- Each person should use the permissions associated with their assigned role and branch.
Set up Library Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.