[UXPROD-4048] Users app: Create specific search options for text based custom fields Created: 08/Feb/23  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Molly Driscoll Assignee: Amelia Sutton
Resolution: Unresolved Votes: 0
Labels: usermanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem: Text field/text area custom fields within the Users app are currently searchable via the keyword search option in the Users app (see https://folio-org.atlassian.net/browse/UIU-2165). However, for libraries with several custom fields or generic content within those custom fields, a more generalized keyword search often produced too many results to sift through, with potential hits coming through based on a name, email, or identifier field instead of a specific custom field. Having dedicated search options for text-based custom fields would enhance the search experience and provide more targeted search results for these kinds of queries.

Proposed solution/stories

I wonder if the filtering options developed for custom properties like license terms and supplementary properties could serve as a model for additional development in custom fields searching and filtering.

Links to additional info

From Slack, in response to https://folio-project.slack.com/archives/C22MK8NV7/p1675721679257609

Brooks Travis: 
I feel like it came up when we initially discussed filtering, but it would require back-end enhancements in custom fields.
 
The existing search/filter support was ui-only.
Patty Wanninger: 
The searching of the text custom fields was written by Mark Deutsch before he left Duke and he did not use any story from the SIG. He wrote the code so duke could use a custom field as an alternative barcode. When we wrote the stories for the rest of the fields, the team just used Mark's code so we never wrote a separate feature or story.
 
You could write a feature (not a story) because it would be new functionality. Without a feature ticket nothing can ever happen. Though I think this would rank low priority for the current dev teams. If it was something a customer really wanted and could support, then it would perhaps get done.
Questions


Generated at Fri Feb 09 00:36:51 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.