Is this largely the same as T286529: Friendly interface for searching through and choosing tools for list creation or intended for some other search activity?

Change 738286 had a related patch set uploaded (by Raymond Ndibe; author: Raymond Ndibe):

[wikimedia/toolhub@main] Feature: Auto-complete/lookahead search for adding tools

https://gerrit.wikimedia.org/r/738286

Change 738286 merged by jenkins-bot:

[wikimedia/toolhub@main] Feature: Auto-complete/lookahead search for adding tools

https://gerrit.wikimedia.org/r/738286

The search looks great @Raymond_Ndibe!
One question I had was what does the toolname in parentheses mean?
e.g.

I would assume the "pills" being added would display the same title as what's shown on the home list page.

In T294932#7523726, @sdkim wrote:

The search looks great @Raymond_Ndibe!
One question I had was what does the toolname in parentheses mean?

The display in the select list is "tool.name (tool.title)".

e.g.

I would assume the "pills" being added would display the same title as what's shown on the home list page.

The literal value needed for the API POST call is the "name" value from the toolinfo record which is required to be a globally unique string. The value shown on a card view that you are referencing is the toolinfo record's "title" attribute which can be freeform text. I'm sure we can do some cosmetic work to have the data model display one thing in the UI and send another related thing to the backend if it can be shown that the toolinfo name is somehow confusing to users.

@bd808 Great idea, we can maybe do some quick usability testing with a few users? Likewise, an alternative is if we have the ability to see what strings are being searched for and whether they're more aligned to the tool name or tool title.

Thoughts?

In T294932#7523974, @sdkim wrote:

@bd808 Great idea, we can maybe do some quick usability testing with a few users?

Go for it. The code is live on the demo server.

Likewise, an alternative is if we have the ability to see what strings are being searched for and whether they're more aligned to the tool name or tool title.

I'm not quite sure what you are suggesting here. Can you rephrase or expand your description? If you are suggesting that we refine the feature over time based on data analysis of the search input vs the document corpus that would be technically possible if we had an analyst and data collected from a production deploy. Currently we have neither of these.

Where is a good place to find volunteers to test this out?

Change 749220 had a related patch set uploaded (by BryanDavis; author: Bryan Davis):

[operations/deployment-charts@master] toolhub: Bump container version to 2021-12-20-122341-production

https://gerrit.wikimedia.org/r/749220

Change 749220 merged by jenkins-bot:

[operations/deployment-charts@master] toolhub: Bump container version to 2021-12-23-121200-production

https://gerrit.wikimedia.org/r/749220