2017-10-09 Resource Access Meeting Notes

Date

09 Oct 2017

Attendees

• Andrea Loigman

• Darcy Branchini

• Holly Mistlebauer
• Cate Boerema (Deactivated)
• Kimie Kester
• Mark Canney
• Tania Hewes
• William Weare
• Joanne Leary
• David Bottorff
• Charlotte Whitt
• Chris Manly
• Marc Keepper
• Maria Grzeschniok
• Rameka Barnes

Goals

Discussion items

Notes

Calendar subgroup: Andrea did not get volunteers for the calendar subgroup, but this needs swift action. May need to make this a priority action item with the full group. (Deb mentioned that she would step in if nobody came forward, but she was not at this meeting to confirm.) Cate said it would wait a week, but the timeline is still very short.

Checkout screen showing Proxy choice: David clarified that the "Sponsor" is the person on whose behalf the proxy is acting. This was not correctly understood by the developers; Holly will let them know.

User app: Cate reviewed some issues that arose from the last meeting:

• Should some fields be repeatable? Specifically, fields related to contact (email, text, phone, address) - it's common for people to have more than one of any of these.
• Should the user be able to select more than 1 preferred contact method? Having multiple preferred contact methods is possible, but would be difficult to implement from a systems operation perspective. To clarify the need for this, look at / add to the user stories in JIRA. As an alternative to allowing multiple preferred contact methods, the institution could decide what method will be the default contact method for everyone (for example, email), and the user could change the preferred method as necessary. For text messaging, the user would have to opt in. This issue needs further discussion with the User Management SIG and in the context of sending notifications. User stories would be very helpful here.
• User metadata organization on the page: primary information at top (static) includes Patron Name (Last, First, Middle), Patron Barcode, Patron Status, Patron Group, Expiration Date. The group of demographic data fields below it can be toggled to view or hide: username, password, birth date, Statistical categories (college/major), affiliation (such as consortia), external system ID (the match point for external automated feeds)
• In designing this info page, we need to make it possible to add ID fields later as the need arises (beyond V1). Cate and Chris agreed this will be possible. We will also need to add a "home library" field; where to put it depends on how the information is defined (a later discussion)

Checkout screen data organization:

• Is the placement of the Call Number field OK?
• Should the call number be concatenated with enum/chron/copy fields, or should the components be separate? The concern is sortability. The call number needs to be normalized to be sortable (but the normalized format does not have to display, but just be working in the background). OK to be concatenated as long as the field is sortable. The call number is generally found in the Holdings record but the enum/chron/copy data may be found in the item record. Charlotte, David, Holly and Tania will discuss.