2020-10-26 Resource Access Meeting Notes

Date

Attendees



Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia
  • Thursday will be cancelled due to a low on topics this week
15MinField Restrictions in User Managementpatty.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)
10MinClaimed returned: add searchEmma BoettcherLimit number of searches: by service point, location, "owner"?Discussion not needed. Covered at previous meeting.
15MinItem statusesEmma 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-20MinFees/fines export spreadsheetApproval of thin-thread spreadsheetDiscussed 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

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue

Emma Boettcher IrisWarn but ultimately allow circulation of long missing or in process (not requestable) items; prevent circulation of dummy items. Prevent requests for all threeConsistent with previously agreed-on behavior






















Notes