2020-10-26 Resource Access Meeting Notes

Date

26 Oct 2020

Attendees

Discussion Items

Time	Item	Who	Description	Goals/Info
2min	Administrivia	Andrea Loigman	Thursday will be cancelled due to a low on topics this week	Notetaker - Brooks Travis
15Min	Field Restrictions in User Management	patty.wanninger	https://folio-org.atlassian.net/browse/UXPROD-206 Khalilah closed it as "won't do" back when she was UM PO but it keeps coming up. We could easily do this if we were willing to have a UI-only permission restriction, but we have been reluctant to do that for security reasons. Do we want to reconsider? What if we made the fact that the data is only restricted in the UI explicit in the permission name? UXPROD-242 - Getting issue details... STATUS	Cannot restrict contact information access because it is part of the User main schema Discussed ability to protect fields from being overwritten by User Import Cornell and Chicago are using custom loaders/middleware Pre-processing records not really a viable option for everyone (significant barrier to adoption)
10Min	Claimed returned: add search	Emma Boettcher	Limit number of searches: by service point, location, "owner"?	Discussion not needed. Covered at previous meeting.
15Min	Item statuses	Emma Boettcher	Confirm circ behavior for new statuses:	Circulation Behavior for Proposed new item statuses: Long Missing Check-in: allow, require confirmation, notify if suppressed Check-out: allow, require confirmation, notify if suppressed Requests: allow none In Process (not requestable) Check-in: Allow, require confirmation, notify if suppressed Check-out: Allow, require confirmation, notify if suppressed Requests: allow none Unavailable Check-in: Allow, require confirmation, notify if suppressed Check-out: Allow, require confirmation, notify if suppressed Requests: allow none "Dummy" Check-in: Prevent Check-out: Prevent Requests: allow none Discussion around CDL/ETAS Subgroup meeting to discuss on Thursday (10/29) during normal RA SIG meeting time
15-20Min	Fees/fines export spreadsheet	Holly Mistlebauer	Approval of thin-thread spreadsheet:	Discussed re-arranging columns such that fee/fine action items come before fee/fine detail to avoid confusion.

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue
	Emma Boettcher	Iris	Warn but ultimately allow circulation of long missing or in process (not requestable) items; prevent circulation of dummy items. Prevent requests for all three	Consistent with previously agreed-on behavior