2025-11-05 Meeting notes

2025-11-05 Meeting notes

 Date

Nov 5, 2025

Meeting recording: https://recordings.openlibraryfoundation.org/folio/user-management-sig/2025-11-05T10:00/

 Participants

@Maura Byrne

@Amelia Sutton

@Scott Peterson

@Tara Barnett

@Martina Tumulla

@Karen White

 Goals

  • Discuss UIU-3485 - “Do not display in this session” in pop-up modal in User record

  • Discuss UXPROD-242 - Protect user record/user record fields from being overwritten by user import

Take a closer look at the User fields protections feature. Discuss our prioritization process.

 Discussion topics

Time

Topic

Presenter

Notes

Time

Topic

Presenter

Notes

5 min

Note-taker

 

Maura and Amelia will compare notes

25 min

Pop-up modal: “Do not display again in this session”

Amelia

UIU-3485

The mockup looks good. Should the checkbox for “Do not display again in this session” be clicked or unclicked by default?

  • If it’s checked by default, student staff at a circ desk will encounter the message once, and other student staff may not see the note if the patron returns to the desk.

  • Students may click through a pop up without looking at it if it appears often enough.

  • Having the box unchecked by default might result in missed barcode scans - this might be more common in a bookstacks environment, when checking out multiple items to a dummy patron.

  • Default behavior cannot defend against carelessness.

  • What does “this session” mean in this modal message? Check out has an “end this session” button. Does it apply to that session? No. It means the login session. The wording should be changed to reflect that.

  • The “delete note” button does not appear if the user doesn’t have permission to delete a user note.

  • Return key and escape key both close the modal.

After some discussion, it was decided to have the click box unclicked by default.

10 min

Protect user record and/or user record fields from being overwritten by User load.

 

Amelia

UXPROD-242

First, there appeared to be a need to separate the story into two parts: protect the whole record, and protect individual fields.

  • All of the sub-tickets would be immensely complicated if we asked to protect individual fields on individual records.

  • The sub-tickets:

We decided the following:

  • We will not ask for individual fields in individual records to be protected.

  • We will, however, ask for certain fields to be protected across all User records in a tenant-level setting. This is for instances where the “source of truth” and the Folio system differ on handling of certain parts of the User record (ex.: Preferred first name)

  • As far as Bulk Edit, records that are not overwritten should be marked in the error log with one of a specific set of reasons, so those running Bulk Edit will know those records were protected on purpose.

10 min

Feature prioritization

Amelia

Amelia will replace our manually generated and maintained Gap List with a list of User-related Jira tickets. We are encouraged to use the votes in Jira to prioritize our features.

 Action items

 Decisions

 Related info