2019-08-21 User Management Meeting Notes

Meeting URL

https://zoom.us/j/488543197

Date

21 Aug 2019

Attendees

• Michelle Suranofsky
• (OLD ACCOUNT) Erin Nettifee
• patty.wanninger
• Kelly Drake
• Maura Byrne
• Todd Wallwork
• Uschi Klute
• Philip Robinson
• Sobha Duvvuri
• Björn Muschall
• Khalilah Gambrell
• Michelle Suranofsky
• Carole Godfrey
• Kimie Kester
• Jana Freytag

Discussion items

Notetaker: Philip Robinson

Maura proposed the following meeting agenda:

1. Khalilah will present on Custom Fields, and discuss UI designs and requirements for said Fields.
2. We’ll cover what the canonical, supported approach for doing a bulk import of users.  This was brought up in Slack, and I think it’s important to make sure we all see it.  (I don’t expect to take terribly long with it.)
3. If there’s time, I’d like to put on the table what to expect when one searches Users, especially regarding diacritics.

Notes:

We only had time to cover topic #1.

Khalilah invited a few developers who are working on Custom Fields. https://folio-org.atlassian.net/browse/UXPROD-33 has a lot of user stories attached to it. Stephanie who works for Filip has developed a prototype, seeking user input. Khalilah presented a demo of the front end mockups. 

Settings > Users > Custom fields, click New button. The section name (“Custom fields” by default) will appear on the accordion header. Can set the field order. One accordion per app.

There’s a custom fields video in Slack at https://folio-project.slack.com/archives/C22MK8NV7/p1566333979092200 demo’ing how it works. Note: that may be an older version of the video.

A video is also at https://folio-org.atlassian.net/browse/UXPROD-33 .

Team has started the back end development of the custom fields. All the subject areas may have different custom fields assigned to them. Text box / paragraph / dropdown / check boxes / radio buttons / date fields etc will be available. Can set each field name. The UI shows a preview of the field as you build it out. Can set formatting requirements (like URL format), helper text, and flag it as required. Q about whether custom field formats and validations can be built, analogous to what Quatrics has. Q about max size - text box is a one-liner, paragraph is a block. They may build in numeric validation rules etc. Date picker will already contain date validation (reuse FOLIO’s extant one). 

Required status is enforced on the UI. Discussion of cases where the registrar import etc contains a new value in a data element. Need to support adding the new value. Departments are a great example. 

Discussion of support for different unique IDs associated with a user. Should they be in custom fields? Look up a patron by their Apple Watch ID etc. Or do they belong in a dedicated external ID field, so it could be used as such. Patty will follow up on the loadable department field, as well as multiple external IDs, and make the issue rankable etc. 

Question about how to manage giant lists like departments. Patty offered to write a user story about it, working with Kelly. 

mod_custom_fields is the new module the dev team is building. Searchability from the Users should also be available when the data appears in other apps. Like Apple IDs on users etc, searching in inventory and so on. Confirming whether the users app is the source of record. 

A field group is a pre-populated dropdown with free entry boxes on the right. Not developed yet but it’s on the docket. 

Topics Requested from Meeting Attendees / POs