RA - Loans 3/28/2018

Agenda

Claims returned (45 or less)

Anonymizing closed loans (5)

Overrides (5)

Next steps, upcoming meetings (5)

Not for V1, but someday: having a way for patrons to claim returns from their online account
Permissions: not broken down by desk, but by staff member
Store date, operator, and desk, with a generous notes field (Duke's online form indicates examples of what staff could need to record in notes field)
Claims returned information (# unresolved, # resolved in favor of library, # resolved in favor of patron) is helpful to have on patron page. In current systems historical info might appear in notes field, but # unresolved is important
No new requests can be placed on items that are claim returned
Is claim returned a status?
- Having a compound status of Checkout-claim returned-recalled (in extreme cases) is undesirable
- Having Claims return overwrite Checkout, Overdue or Lost-and-billed as a status is also less desirable (might make it more difficult to do reporting, would seem to obscure information)
- Very robust flag, instead of compound status?

V1: Need to have hooks for patron's online account so that they can anonymize their own loan history
Not V1: Staff-mediated anonymization

V1: If a person can override one thing, they can override it all (later: separate overrides, e.g. for financial matters)
System needs to log operators who override