RA - Loans 3/28/2018

Agenda

Claims returned (45 or less)

Anonymizing closed loans (5)

  • System makes it possible for patron to anonymize closed loans: V1?
  • Staff can anonymize closed loans on behalf of patron: V1?

 Overrides (5)

  • Existing lists of item blocks?

Next steps, upcoming meetings (5)

  • 3/30 – confirm that we’ll have a quorum
  • 4/6 – no meeting

Notes

Claims returned

  • 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? 

Anonymizing closed loans

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

Overrides

  • 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

Next meeting and action items

  • Next meeting: March 30, 11am Eastern
  • No meeting April 6
  • Emma: start wireframing claims returned

Recording

Recording for March 28