2020-02-05 User Management Meeting Notes

Owned by Catherine Smith
Last updated: Feb 19, 2020 by Uschi Klute
2 min read

Meeting URL

https://zoom.us/j/488543197

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes
40 minRequirements for Ongoing Patron Loading

Erin Nettifee

Requirements for Ongoing Patron Loading Document
  • Business logic requirements (need Theo to review)
    • Initial data load can come from either legacy system load (flat file) or identity provider; post-initial data load patron data will come from identity provider
  • Handling deletions of patron records
    • CRUD functionality
    • Separate functionality needed for deleting expired patrons
    • Expiring records versus deletion for dependencies
  • Report needed to identify patron records not represented in flat file load/ongoing updates for review
    • Flat file options: JSON, XML
  • Live updates from identity provider?
    • Banner API for continuous live updates
  • Blocking vs. expiring patrons
    • Students are expired and deleted at the end of the semester; staff who leave are deleted
    • How does this work for users who return at a later time? Account re-established through updates from identity provider
  • RA SIG working on blocking features (item blocks, patron blocks, manual blocks on user record)
    • Automatic item blocks (counts of material type)
  • Requirements needed for block API
  • Protected fields?
    • Requirement needs to be added for flat file load protected field functionality
  • Matching point cannot be on UUID for external identity provider system
    • Does a matching point exist for ongoing loads? Patty will check with Theo
  • Need to determine match point and dependencies for ongoing patron data loads
  • New feature needed: Blocks
    • May need to discuss more in a future meeting (possibly with RA)
  • Please add specific requirements needed to Erin's document for consideration
20 min Permissions and Permission Sets

 Maura Byrne

 User Permissions Google Sheet
  • "Out of the box" permission sets descriptions created
    • Comments needed on Google Sheet
  • May not be updated for Edelweiss release
  • Permissions typically limited to CRUD, then additional permissions for individual functionality
  • Should this be discussed in UM, or should needed permissions be considered by individual SMEs for apps/workflows?
  • Testing needed for Permissions and Permission Sets
  • Adding different abstractions of permissions for roles?
    • Not considered MVP
    • Roles as assigned to individual users in order to push permission management to department heads rather than being a function of IT
  • Need to document how permission sets are working in the Wiki for real-time feedback on testing
    • Patty and Maura will investigate how permissions are being tested in the BugFests

Action items

  •