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
- Evidence
Evidence
Keep linked files and operation outcomes explainable after a handoff.
OverviewPending Operation Receipts×
Public Library System · Evidence
New
Pending Operation Receipts
Operation receipts
| Parent | Operation key | Action | Expected revision | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| LNS-57856 | OK-381 | ACT-923 | 790 | Pending | 18 Oct | |
| LNS-26393 | OK-372 | ACT-532 | 570 | Needs review | 08 Oct | |
| LNS-86584 | OK-170 | ACT-840 | 360 | Failed | 09 Oct | |
| LNS-73260 | OK-788 | ACT-114 | 330 | Pending | 14 Oct | |
| LNS-87517 | OK-784 | ACT-874 | 70 | Needs review | 12 Oct |
6 of 6 records
OK-381Operation receipts · OR-95578
PendingParentLNS-57856
ActionACT-923
Expected revision790
Occurred at18 Oct
Failure reasonCut to length
What you can do
Keep the evidence with the loan
An attachment links a file to the loan it supports. Its title, evidence type, uploader, upload time and visibility help staff understand what was supplied and who can see it. A handover note or copy condition image should be attached to the relevant loan rather than stored in an unrelated personal folder. The Collection Reviewer can then judge the same case the coordinator prepared.
An operation receipt records the guarded action’s operation key, expected revision and result state. A receipt can be pending, completed, failed or in need of review. It can also retain linked effect references and a failure reason. Read it alongside the loan, custody events and reviewer decision. A completed receipt is useful when its effects match the expected work; an exception gives the team a specific record to investigate.
How the work is organized
- Files. The attachment carries a title, evidence type, visibility and uploader.
- Operations. The receipt ties an action and operation key to an expected loan revision.
- Exceptions. The result state and failure reason show where reconciliation needs attention.
What to agree during setup
Choose what documents belong on the loan and when a file is marked internal or shared. Decide who reviews a shared attachment before it leaves the owning library. A title should explain its purpose to a later reviewer, while the evidence type should distinguish a handover record from a condition image. Staff should avoid uploading duplicate files merely because a request is retried.
Agree how an operation key is assigned for repeated actions and who investigates failed or pending receipts. The reviewer needs a rule for comparing the expected revision and linked effects to the current loan and custody history. An unresolved discrepancy belongs in the visible queue until a person explains it. A new receipt should not be invented to make an older failure disappear.
Check the handoff on an actual case
Attach a condition record to a loan, marking its visibility deliberately. Submit an interlibrary request and have the reviewer read that attachment with the loan’s custody history. Record an operation receipt for the accepted action and check whether its effect references match the events actually present. The Auditor should be able to trace from the receipt to the loan and the review decision.
For an exception, use a receipt whose expected revision disagrees with the linked loan or whose effect reference is absent. Pending Operation Receipts should surface it for investigation. The reviewer can record a discrepancy and determine the next correction path without deleting the original receipt or custody event. The evidence trail remains useful precisely because it keeps unsuccessful attempts visible.
What your team sees
- Pending Operation Receipts — Pending, failed and review-needed action records.
- Loan Evidence — Files attached to loans with type, visibility and uploader.
Follow the work through
Use review and reconciliation to check receipt effects. See custody and exceptions for the physical events those records explain.
What it keeps track of
Data model- Operation receipts
- Durable receipts for guarded operations and reconciliation
- Record attachments
- Linked evidence files for loan records
- Loans
- Circulation loans with copy custody and patron entitlement
- Loan events
- Custody and condition events recorded against a loan
- Review decisions
- Independent review decisions on frozen revisions
Who uses it
Permissions- Collection Reviewer
- , Collection Coordinator, Auditor.
Set up Public Library System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.