search

galaxyproject / galaxy

Data intensive science for everyone.
https://galaxyproject.org
Other
1.42k stars 1.01k forks source link

Workflowhub search: term with / isn't found, subset of that term is found. #19059

Open hexylena opened 4 weeks ago

hexylena commented 4 weeks ago

Steps to Reproduce

  1. Copy SeqSero2/SISTR from https://workflowhub.eu/workflows/407
  2. Navigate to workflows/import and use the ga4gh tab to search (could that be renamed 'search' someday? like what is the difference between "GA4GH servers" (all TRS servers) and "TRS ID" (also TRS servers). 'Search' and 'Search by TRS ID' would be better.)
  3. Paste SeqSero2/SISTR into the search form
  4. Find Nothing.
  5. Delete until you have SeqSero2
  6. Find the workflow!

Galaxy Details

Galaxy Version: 24.1.3.dev0 Commit: https://github.com/galaxyproject/galaxy/commit/1a6b7fefd373a7a8f8233c08be6bbe30961b6508

Related

https://github.com/galaxyproject/galaxy/issues/16519

wm75 commented 4 weeks ago

name:"SeqSero2/SISTR" is working.

From the help pop-up: Search by workflow description. Tags (key:value) can be used to also search by metadata - for instance name:example. Available tags include organization and name. A bit weird to not include the name by default, but, well, behaves as documented.

hexylena commented 4 weeks ago

That's... good to know. Thanks for the tip! I now vaguely remember encountering this before with one of your workflows in the GTN actually :disappointed:

So the documentation is right, but the behaviour is dead wrong from an end user perspective. This isn't how most other search fields in other software works, nor in galaxy work (tool search, history search I guess is silently doing name: until you add other tags but can still find full exact matches.)

I'm given a plain text search box with additional hints hidden under ?, I'm going to enter my search term as it appears in the title of the workflow I want to import.

I think the behaviour should be changed in Galaxy because this isn't intuitive at all. if name: and quotes are required , then maybe it should just be a split search field to start with (or the parsing should be fixed.)