2019-4-29 Resource Access Meeting Notes

Time	Item	Who	Description	Goals
5min	Housekeeping	Andrea Loigman	Notetaker Deb Lamb
20min	Request whitelist	Cate Boerema (Deactivated)		-Review wireframe for whitelist configuration and get initial feedback Q2 2019 Requests Discussions PPT (with this topic and more): https://docs.google.com/presentation/d/1hNYBxUdy3pGKKpo5BkY7bJFfBEVdEG1idCecY1xVwko/edit?usp=sharing
15min	Anonymized loans	Emma Boettcher		Given fields on user record that are currently in place, how should this appear? Given proposed fields on user record (statistical code/affiliation, custom fields), to what extent are these fields helpful to show on an anonymized loan (as opposed to just in reporting)
20min	Notice /item history	Darcy Branchini and Cate Boerema (Deactivated)	Continuation of conversation around patron notice reports	Determine needs for patron and item notification history.

Review wireframe for whitelist configuration and get initial feedback: Please see Cate’s very fine summary of this discussion on the outcome table.
Anonymized loans: Emma lead the discussion of what sort of statistical information should be available when a loan has been anonymized. It was agreed that we like consistent screens and so no additionally information should be on the patron screen. However, we all want this information for reporting and trouble shooting. We agreed that it was okay if that information was “only 1 click” away. We do not know what the GDRP will need and this should be investigated. Please see Emma’s very fine summary of our discussion.
Notice/Item History: A good discussion with examples of circ logs from Aleph and Illiad to demonstrate what such a long could look like. Please see Cate’s very fine summary of our discussion.
Bug: Currently there is a bug in the request screen that duplicates each entry, making it very unwieldly. For now, it would be easier for developers if only those transactions that change the due date are listed with the assumption that a circ log exists and we can get to it.
Thanks from Deb! Many thanks to Andrea for her leadership of this SIG. Also thanks to David, Cheryl and Mark for sharing their Ole experience with us, keeping us from making the same mistake twice. Thanks to the PO’s for their efforts on the RA-SIG’s behalf. And many many thanks to you all. I have really enjoyed working with you in this very transformative experience. I know you will knock it out of the park!

Aleph patron history

Aleph Item history

ILLiad patron notifications These are not loan related notices, they are system action (e.g. registration, block) notices.

ILLiad transaction history n.b. each ILLiad 'item' is unique to a given patron

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
Requests	Cate Boerema (Deactivated)	Unknown	Reviewed wireframes for configurable whitelist: Decided wireframes makes sense Some questioned priority and felt they might just enable all kinds of requests for all item states and then use request policies to limit what can be done Others felt this would be useful and is better than what they have today	A few people thought it would be nice to be able to do this configuration by location or library (as opposed to by tenant) But people also felt that different configurations with a single tenant invited a great deal of complexity for the system and patrons In the end we agreed by tenant made sense
Requests	Cate Boerema (Deactivated)	Q2 2019	Revisited decision about which requests should display in the loan action history table: In light of the fact that we are designing a "circ log" with detailed info about requests on items by patrons, do we really need to display all requests in the loan action history? This is complex development Developers say it would be much easier to fix the bug if we just showed requests that affect due date SIG would still prefer to see all, as requests that don't change the due date can also impact the loan. Holds may make it impossible to renew a loan, for example BUT SIG agreed that if we had the circ log easily accessible and also a link to the request queue, it would be fine
Loans	Emma Boettcher	Q2 2019	Of the fields currently on an anonymized loan, display some text where a name has been scrubbed, and display the patron group always Of the proposed user record fields to retain on an anonymized loan (statistical codes, custom fields such as department), show, but having them one click away is also fine	Further question: should what fields are retained on loans also be included in anonymization settings?