2026-06-17 Meeting notes

2026-06-17 Meeting notes

 Date

Jun 17, 2026

 Participants

  • @Amelia Sutton

  • @Robert Heaton

  • @Steve Strohl

  • @Jacob Dudley

  • @Art Gutierrez

  • Aaron Bales

  • Jay Lantrip

  • @Erin Weller

  • @Karen White

  • @Uschi Klute

 Goals

  • Discuss potential change to or removal of the “Delete note” button from Users pop-up notes

  • Assessing Users Search requirements

 Discussion topics

Time

Topic

Presenter

Notes

Time

Topic

Presenter

Notes

5 min

Note-taker

@Amelia Sutton

 

  • Who will take notes today? - Steve!

15 min

Pop-up notes

@Amelia Sutton

  • https://folio-org.atlassian.net/browse/UIU-3485

  • Change or remove the “Delete note” button?

  • Check box at the bottom – needed? Is it confusing? How about “Hide for this session” instead? Tie in the note to a button? What would be consistent across modules (perhaps later)?

  • Where would we want the note to STAY hidden? 

    • Moving from module to module and like Circ Log back to Users? 

    • How often should it pop up upon returning back to where the note can be seen?

  • Decisions:

    • Delete note button is still a requirement. Preferred approach would be to add a confirmation modal before a note is actually deleted

    • Instead of a “Do not show this again” checkbox, folks would prefer that notes that pop-up in the users app only pop up the first time the record view pane is opened until the user closes the view screen completely. Doing any of the following should not reset the display of those notes:

      • Creating/editing Blocks, Fee/fines, Requests, Notes

      • Editing the user record

      • If the user navigates to another app, then returns to the users app (essentially the note should only pop up once as long as the same user is opened in the view pane when returning to the Users app)

40 min

Searching in Users

@Amelia Sutton

  • https://folio-org.atlassian.net/browse/UXPROD-4915

  • Suggested Search options

    • Created date

    • Updated date

    • Created by

    • Updated by

    • Source (like in Orders: User vs. API)

    • Presence of a username (maybe like the “Agreement content” filters in Agreements; maybe same for Presence of a preferred first name or pronouns or proxy/sponsor relationships...)

    • Presence of user roles (or filter by specific ones?)

    • Patron blocks (maybe by type, Manual or Automated; maybe by blocked actions, Borrowing, Renewals, Requests)

    • Open loans

    • Open requests

    • Open fees/fines

    • Service points (maybe a separate filter for Default pickup service point)

    • Maybe bring the in-app reports (users with items claimed returned, etc.) into filters

  • Use cases for the suggested search options are primarily for regular cleanup with consistent parameters.

    • These are better covered by the Lists app

    • There are some privacy concerns around being able to search by “updated by” or “created by” metadata in Lists.

    • Problem with using lists: Unable to link directly from results in the Lists app to a User record

  • Adding Source (like in Orders: User vs. API)?

    • no differentiation here. Don’t know how it was created.

    • For most automated loading; can find out in Lists which should be sufficient and can use NOT EQUAL TO to find out records not added via the API user.

    • We want to avoid the list of searching filters we see in Orders.

  • Would be nice to be able to configure which search/filter options are available in the Users app.

 Action items

 Decisions

 Related info