2025-09-17 Meeting notes

5 min

Note-taker

Lola Estelle

10 min

UXPROD-5496: Exclude users with “Patron” user type in find-user plugin search

Amelia

Closed as won't do for now. Most non-ECS libraries don't currently use the user type field. If this is needed for GDPR compliance, we may need to revisit this; Uschi will discuss this with GBV. Separate tickets for each area (Acquisitions, ERM, Metadata, User Management) might be created in the case that we proceed with this.

5 min

UXPROD-4596: Duplicate/clone User records

Amelia

Closing, but can reopen if it becomes a priority. A use case for this is to support public libraries where a family is registering and has overlapping info like email/home address; however, there is no recollection of this being raised in the Public Library SIG. Another use case is to support libraries where staff have two user accounts, one as a patron and one as a FOLIO user.

10 min

UIU-1027: Make it clear which fields are being searched in User search

Amelia

Amelia met with Kimie on this and determined two options --

1. A simple approach is to change the label for keyword in the search box to add additional fields to those currently listed in parenthesis. We could either slightly widen the left side pane so that the expanded text there displays, or we could keep the pane the same width wherein the additional text would appear truncated; group's preference is to keep the pane the same width.

2. A more complicated approach would be to remove custom fields from the keyword search option and add a separate option to search custom fields. GBV might prefer this, as it would allow searching for custom field separately; custom fields might contain values that are similar or identical to other fields' values, but with a different meaning/context, and the ability to search custom fields separately would bring more relevant results. Uschi will discuss with colleagues.

20 min

Look at the Gap list - Gap list UM SIGPreview

Amelia

• UXPROD-4712: Users - Custom Fields: Configurable Display at Checkout Analysis CompletePreview is planned for development

• UXPROD-242: Ability to Protect Fields from Being Overwritten by User ImportDraftPreview is a very old issue and it makes sense to prioritize it now. Amelia will update the tickets linked to this one to use current terminology/functionality since they are so old. This would affect user loads created with mod-user-import and also editing a record via the API. There are various ways we might implement this, some more complex than others. We could potentially create a field protection setting at the tenant level, eg a setting like "don't overwrite addresses."

• Add support for bulk deletion of users - there are multiple existing tickets for accomplishing this. This is often requested. This is currently possible via API, but it doesn’t check dependencies and just does a blanket delete. Amelia will update existing tickets to specify that we need a dependency check.

• All are welcome to add to the gap list, even if there is no existing ticket.