Date
Attendees
- Cheryl Malmborg
- Joanne Leary
- William Weare
- Sharon Wiles-Young
- Tania Hewes
- Maria Grzeschniok
- Rameka Barnes
- Deb Lamb
- Marc Keepper
- Darcy Branchini
- Ginny Boyer (Deactivated)
- Michael Winkler
- Cate Boerema (Deactivated)
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
5min | Housekeeping |
| |
15min | Review revised proxy checkout mockups | The size of the font for ‘borrowing patron’ has been increased. Some people suggested they're not sure it’s any clearer. Wendy Wilcox was most concerned about this screen and she is absent from today's meeting. Decided to stick with the suggested change that Kimie drew up with one change ‘borrower’ instead of ‘borrowing patron’ and ‘borrower’s proxy’ instead of ‘proxy’. That will allow us to get something out there. Darcy Branchini suggested task-based user testing as a followup to be sure these screens are user-friendly. This topic has been added to the new Submit User Research Requests page. Mockup has been updated with new labels: | |
15min | Review request as proxy mockups | Added a column titled ‘proxy’. On the results page, you go to the request details, then you can drill down into details, such as requester details. There is no way to get to requester details from the results page. SIG thought that was fine and screens were approved by the group. Mockup has been updated with new label of: | |
25min | Discuss request cancellation | Rough notes (will edit later): If someone cancels an ‘in transit’ request, what happens to the item? Would it automatically go home? If the next hold inline is for the same location as the first, then it would stay at that location and it would go on hold. It gets tricky really quickly because some library’s don’t deliver to other libraries so it might need to go home first. If it was going to a faculty member, then it might need to go through a specific library. Example given is that if a science faculty member requests an architecture book, then it needs to go to the science library first, then the faculty member. Systems are currently not able to cope with the We’ve created a fake location at Cornell labeled “faculty office” The faculty member lookup is a different system. Patron home library is important to have. Cate is saying the location and idea of libraries is still a work in progress. She hopes to be able to present something to the RA SIG soon. If something is cancelled, then it goes to where it’s needed based on the next request in line. Anything more complex then that will need to rely on the workflow engine, which isn’t ready yet. You have to let the book be returned, you could inform the patron that it’s no longer requested/needed, so it’s now available. The system would have to tell you… cancelled request. But patrons are typically not present… there’s always a possibility that the original borrower layered another request on the other request. Should a cancelled request restore to the original due date? Decided against that… re-extended due date iwould cause more confusion. If there’s only one request, and that request is cancelled then it would be preferable that a notice is sent out to the original borrower saying it was cancelled and give them an opportunity to renew. | |
Notifications | Notifications - need more time to consolidate notes and come up with a strategy for a guided discussion. Need to define what we mean by notifications. Notices sent by email to patrons, notices that are printed at libraries to inform staff that something needs to happen with an item. Chart might be helpful to start this discussion. Tania will start a document on Google Drive and send to everyone. What will trigger the notification, who gets it, is it printed, texted, emailed, popup? Popups are probably something separate, but for now, include those too. We’ll review next Thursday, Jan 11th. |