2017-06-012 Resource Access Meeting Notes

2017-06-012 Resource Access Meeting Notes

Date

Jun 12, 2017

Attendees

  • @Andrea Loigman

  • @Cate Boerema (Deactivated)

  • @Charlotte Whitt

  • @Cheryl Malmborg

  • @Joanne Leary

  • @Maria Grzeschniok

  • @Mark Canney

  • @Wendy Wilcox

  • @William Weare

  • @David Bottorff

  • @Matthew Sullivan

  • @Michael Winkler

  • @Rameka Barnes

Goals

  • Finalize missing details related to proxy relationships

  • Review wire-frames related to loan actions

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

5 min

Andrea

Housekeeping

  • Note-taker - Joanne Leary

5 min?

Cate and Matt

Proxy

Follow-up questions (if any)

 50 min

Cate and Matt

Loan actions

  • Review wire-frames

  • Discuss needed / lacking components

Notes

We began a discussion about the wireframes Matt produced for working with (viewing and updating) patron loan records. In order to work with these records, a great deal of information is required. Ideally, the crucial information should be displayed on one screen, and secondary information should be displayable via clicking on elements to a secondary screen in a new tab. Screens include the Current transactions (items currently checked out by the patron), and Closed transactions (patron checkout history) and Item Transaction History (not patron-specific). Because some institutions retain patron information in circ transaction history, and some do not, this has to be configurable.

Features that we need on patron transaction screens: 

  • Required fields include: full-detail call number, full-detail location, title, author, barcode number, due date, loan status (such as renewed, recalled/requested); action pulldown; item selection check boxes

  • Secondary fields include:

    • click to full-detail bib/holdings/item info;

    • click to full-detail patron transaction history, including notices sent;

    • click to full-detail item transaction history (not specific to a patron);

    • click to requestor information

Functionality:

  • We need to be able to apply the actions to one, several or all items

  • There should be a way to enter transaction-related comments to one / many / all selected items

  • We need to be able to filter and sort on field column headers; sorting and filtering applies to entire list, not just the items that can be displayed on one screen

  • We should be able to print/export list of items (all or selected)

 We will continue discussing these wireframes at the upcoming meeting (Thursday June 15).