Date
Attendees
Discussion tems
| Time | Item | Who | Description | Goals |
|---|---|---|---|---|
| 5min | Housekeeping |
| ||
| 30min | Loans permissions | Emma Boettcher | Determine behavior for when user cannot view open and/or closed loans | |
| 30min | Call number display inconsistencies | Emma Boettcher | Inconsistencies between Loans and Requests, where call number is concatenated with enumeration data in Loans but split out from enumeration and copy in Requests. | Determine: Is this intentional? If not, what is preferred? Should shelving location also be part of call number, or listed separately as it currently is? |
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Comments |
|---|---|---|---|---|
| e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | Clearly stated decision | |
Notes
- Please send the names and contact information of your off site storage representative to Andrea by Wednesday (3/20/19).
- Loans Permissions: Emma walked us through several questions about who should be able to see patron information on open and closed loan screens. We all agreed that anything about the use of an item that doesn’t identify the patron is fine on the other apps. It is important to keep use data such as number of times checked out and dates to use for a variety of decisions. We are not sure about GDPR, so inquiries should be made at ascertain their needs.
- Call Number Display: Call numbers currently display differently in different apps. What do we really want? We are not sure of the definitions of enumeration and volumes in this situation. That would help us understand what we need. We do want to be able to sort by location, prefix, body and suffix. Service points are not a part of this sort. What do we want for the display and what do we want for the exported version. Todd Olson at Chicago has done a lot of work on this and David shared the way this looks and sorts. This conversation will continue.