[Discover] Add Search Functionality for Field Values in Field Stats Popover

[ninoslavmiskovic]

WHY:

In Discover, users often need to explore or filter data based on specific field values. Currently, the field stats popover displays top values, but when there are numerous options, users may struggle to quickly locate a particular value. This impacts usability, especially in datasets with high cardinality.

WHAT:

Introduce a search input field within the field stats popover. This input will allow users to search and filter through the field values. It will provide a search that refines the values, making it easier to pinpoint the value of interest.

BENEFITS:

• Efficiency: Users can quickly locate specific field values without manual scrolling and saving time
• Usability: Improves the user experience by simplifying navigation in large datasets.
• Enhanced Filtering: Makes filtering more precise, enabling faster decision-making during data exploration.

Figma file

https://www.figma.com/design/nM03IVLSwQZatLtzRCwcEg/Search-in-Field-stats-popover?m=auto&node-id=6044-9273&t=tjZY5Qj4tJFbGjUn-1

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[l-suarez]

Design needs to define a few flows, such as empty state and search behaviour inside the popover: https://github.com/elastic/platform-ux-team/issues/451

[elasticmachine]

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

[ryankeairns]

While the proposed solution may help, I am not convinced it will materially address the stated problem...

...but when there are numerous options, users may struggle to quickly locate a particular value.

In part, it won't provide an exhaustive list of values and the assumption here is that users know the particular value. As we've also seen with field names, they may not know the exact name or value and are desiring to browse. Imagine long values of a similar pattern - discerning the exact value you want will be difficult to see and do. Even if they are able to find the desired value, we now return a single result with a now out-of-context percentage associated to it.

I suspect what would move the needle in a more material way would be to provide some sort of solution for browsing data sources > fields > and field values.

[ninoslavmiskovic]

@ryankeairns I think what you are describing is something we can enhance in the field list. We have "recommended fields extension point" being specified and that would help users navigate and understand their data better.

[jughosta]

@ryankeairns Currently, we are showing maximum 10 top values. Would it help if we add a button to allow loading more? Then we could fetch 20, 30, ... top values.

[ryankeairns]

@ryankeairns Currently, we are showing maximum 10 top values. Would it help if we add a button to allow loading more? Then we could fetch 20, 30, ... top values.

Oooo that's a nice idea. I do think that would be nice enhancement in lieu of a more general-purpose data browsing capability.

[jughosta]

@ryankeairns Created a small PoC for the "Load more" idea

• [Discover] PoC Allow to load more Top Values in the field popover #198710