Skip to end of banner
Go to start of banner

2019-03-27 User Management Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Date

27 Mar 2019

Attendees

Edd Merkel

Maura Byrne

Michelle Suranofsky

Philip Robinson

Uschi Klute Klute

(OLD ACCOUNT) Erin Nettifee

Goals

The main goal was to decide whether to request development of code that would programmatically enable Permissions module to identify users by name/NetID etc rather than having to look up users from the Users module to get the UUID to pass back to Permissions.

Discussion Items

TimeItemWhoNotes

Whether to request development of code that would programmatically enable Permissions module to identify users by name/NetID etc rather than having to look up users by UUID from the Users moduleMaura

For those writing their own code to attach permissions to users in a batch way, by users’ 15-digit UUID - whereas it's far more convenient to identify people by NetID etc - more intuitive and still unique. Should we advocate for having FOLIO developers implement a bridge allowing us to look up a user (or code up a user) programmatically by the name or user-friendly IDs we know, rather than having to search for their 15-digit UUIDs? Maura has been writing custom code to assign permissions to users, and others on the project have as well. The code goes to the Users module to look up users by name, then pull the UUID to assign / list permissions etc. via the Permissions module. Should the Project code up something canonical for us in the Permissions module?  Phil will follow up with Cornellians on other FOLIO SIGs to see if this is also being discussed elsewhere.

The general consensus was that it's worth pursuing this.



UI improvements in user management interfacesUschi
  • Some UI elements need improvements. The user auto-complete field risks showing too much data insecurely. Users can change each other’s profiles and even prevent each other from logging in! Should be captured in JIRA tickets. User names should not be editable, at least not the users loaded through automated feeds. Could be handled through permissions management - only admins could do it; maybe allow wider scope for creating new users rather than updating their accounts. Need to think about deletions too. Discussion of configurability of full-on admin permissions by institution / instance of FOLIO (with regard to changing user profile information).
  • Discussion of case-sensitivity and its consistency in login names, and having user names as FOLIO user accounts vs patrons - staff account expiry dates (such as student workers / temps) vs patrons. Possible discussion point next week.

Generic borrowers (user accounts) for departments
Erin's topic, postponed until next week.

FOLIO gap analysis
Bjorn’s institution’s FOLIO gap analysis - postponed




  • No labels