2017-06-05 Resource Access Meeting Notes

Date

Attendees

Goals

  • Finalize requirements & naming conventions for proxy functions

Discussion items

TimeItemWhoNotes
5 minHousekeepingAndrea
  • Note-taker - Rameka Barnes
55 minProxy requirementsAndrea
  • what components do we need
  • naming conventions

Notes

Continued Proxy User discussion from 6/1/17.

Followed up on needing to establish more clear language for Proxy:   “Proxy For” and “Proxy By” or “Proxy” and “Sponsor”   

Decided on  Proxy and Sponsor

“Sponsor” is someone who authorizes another person to do something on his or her behalf i.e.  checkout, renew, recall, etc.   

“Proxy” is a person who is authorized (by a sponsor) to act on their behalf to checkout, renew, recall, etc.  

Discussed the following:

Notice options

Discussed needing an indicator of active or inactive and the ability to see why they are inactive on the same screen.  

Discussed and agreed on the following:

Need to know who checked item out.  Loan history/audit trail to reflect that the proxy checked it out versus the account holder.

API to allow sponsor patrons to see this information from their account pages in the discovery layer.

If a proxy is blocked, they should still be able to check out for their sponsor

If the sponsor is blocked, the proxy cannot pick up, checkout etc. for the sponsor

Need expiration dates for relationship and both parties included.

Would like time and date on expiration.  Need to know that if we manually expire a proxy relationship that it takes effect on the date, not the following day.

Would like to have levels for proxies: Levels would allow sponsors to identify what they want their proxy user to do on their behalf:  To pick up only, to only place requests (recall and renewals), have responsibility for fines/fees of proxy or to do everything, etc. Levels can be defined but have this as an options for the sponsor to decide.

What about Proxys who do not have Library or University affiliation? Such as spouse to spouse, children, etc.  Decided that a manual way to input user is how this would be resolved along with some housekeeping of these accounts

 Andrea will inquire about cancelling the June 22nd and June 26th meeting due to travel for those who are attending ALA

 

Recording  - Available through 6/19/2017

https://zoom.us/recording/play/IWEfsGvbkg025xAsI2HeOW4wXyAKZ1-q-SicmeXtkGPDFSXKTYFb7OpwMQiI_kcJ