Tracking the Search
Marking an item missing is easy. Knowing what happens next is not.
A missing item is rarely resolved the moment it is flagged. There is usually a stretch of searching, checking, documenting, and deciding. That work has always existed. The challenge is giving it a place to exist in the system.
A missing item search usually follows a predictable pattern:
1. Item cannot be located
2. Item marked Missing
3. Search begins
4. Search completed
5. Next decision made
The problem is that the work between those steps is often invisible.
Without a workflow tracked in the system, the details of that process tend to live in places that are hard to track:
- email
- spreadsheets
- staff memory
- notes
The missing piece was a way to capture that work in Alma.
In Alma, a status tells us what we know. A Work Order tells us what we're doing.
The Missing status tells us: This item cannot currently be located.
The Work Order tells us: Someone is actively working to locate this item.
Together, they give us a much clearer picture.
The item is not simply missing. It is missing and part of an active search process.
The specific steps will vary by library, but the goal is the same: create a consistent place to track the search process.
That means capturing both the checks themselves and the decisions that follow.
The goal is not to create more work. It is to document the work already happening.
Without a process, a missing item can quietly stay missing indefinitely.
A Work Order creates continuity:
- Someone owns the search.
- The search has a history.
- The next step is clear.
It also creates consistency. Two staff members looking for two different missing items should not have to reinvent the process each time.
Further, this helps solve a communication problem.
For staff, "Missing" alone does not tell the whole story. Is someone looking for it? Has the search already happened? Is a decision still pending?
The Work Order adds that context.
The same is true for patrons. A missing item appearing in Primo without explanation can send someone searching for something the library already knows is unavailable. Through Primo customizations, that information can be surfaced earlier, helping the record communicate what is actually happening with the item.
The Work Order becomes a bridge between what the library knows, what staff are doing, and what patrons see.
Work Orders are not just places to put tasks. They are places to capture the work that happens around those tasks.
A completed search is not just the end of a case. It is a record of what was checked, what was tried, and what happened next.
A missing item represents a problem. The Work Order captures everything that happens between identifying the problem and deciding what comes next.