2018-01-04 Resource Access Meeting Notes

Date

Attendees

Discussion items

TimeItemWhoNotes
5minHousekeeping
  • Note-taker Darcy Branchini
  • No meeting on MLK Day -1/15
  • No meetings on 1/22
  • Cate Boerema (Deactivated) will do a FOLIO demo on 1/25 (several people will be absent since they'll be traveling back from the developers meeting.
15minReview 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:
Borrower and Borrower's proxy.

15minReview 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:
Requester's proxy.

25minDiscuss request cancellation

First scenario: If someone cancels an ‘in transit’ request, what happens to the item? Should it be returned to its home location? If there's another hold for the same item with the same location as the first hold, then it should it stay at that location? It gets tricky really quickly because some libraries don’t deliver to other libraries so it might need to go home first. Or are these just existing/current system limitation that can be overcome with FOLIO?

Another scenario: If it was going to a faculty member's office, 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.  Again, current system limitation?  Or is there a related staffing limitation?  Meaning is it realistic to expect the architecture library to deliver to the science faculty member?  Some existing/current systems are not able to cope with faculty deliveries. At Cornell with Voyager, they’ve created a fake location labeled “faculty office.”  The faculty member office lookup is a different system. Patron home library is important to have for this reason because each of those home library's have a system in place for knowing/ensuring faculty office lookups.  In this scenario, if a faculty member requests an item, then the item would need to be routed to the patron's home library before being routed to their office. Cate Boerema (Deactivated) informed the SIG that locations are currently a work in progress.  She hopes to be able to present something to the RA SIG soon. 

For now, it was suggested to start with some basic and less complex. 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. 

Another scenario: A patron returns an item because it was requested by another patron and then that patron cancels their request.  What happens?  It was decided that instead of re-extending the due date and notifying the original patron, it would be better to notify the original patron that the request was cancelled and give them an opportunity to renew the item.  Of course that wouldn't happen if there was another request for that same item. It was also noted that typically a patron isn't standing there waiting for an item to be checked in so it isn't realistic to notify the patron at that time and/or in person.


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.  Examples discussed include: notices sent by email to patrons, notices that are printed at libraries to inform staff that something needs to happen with an item.  A chart might be helpful to start this discussion.  Tania Hewes will start a document on Google Drive and send to SIG.  Topics that need to be discussed include: what will trigger a specific notification?  Who gets it? Is it printed, texted, emailed, popup?  Popups are probably something separate, but for now, include those too on this chart.  We’ll review the chart next Thursday, Jan 11th.

Notes