Skip to end of banner
Go to start of banner

2018-01-04 Resource Access Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

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.

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

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. 


Notes


  • No labels