search

scijava / scijava-search

Search framework for SciJava applications :mag:
BSD 2-Clause "Simplified" License
2 stars 2 forks source link

Search bar improvement, add annotations/tags to plugins #19

Open k-dominik opened 4 years ago

k-dominik commented 4 years ago

The search bar is an incredibly useful feature - it made Fiji accessible for me :tada:

However, when I look e.g. at our ilastik4ij plugin, i'll have to add a small "but" to the praise above. The search bar will only show results that correspond to menu entries. For our plugin, one menu is ilastik -> run Pixel Classification. Now, only when a user types "Pixel Classification" she will get the correct result. I on the other hand would try "ilastik" as a search term first, and this command doesn't come up. There is a related discussion here: https://github.com/ilastik/ilastik4ij/issues/61.

I'll quote @haesleinhuepf to make a suggestion for improvement:

We should tag our plugins to categorize them. We might also find an automated way of setting some tags. E.g. a plugin with "Threshold" in its name can safely go to a "Segmentation" category. Last but not least: I'd say some plugins should appear in several menus. The "ilastik Pixel Classification" should for example show up in "Segmentation". Some other plugins (like the deprecated ones) should not appear in any menu and still be callable. But maybe that doesn't belong here ;-)

cc @haesleinhuepf @imagejan

haesleinhuepf commented 4 years ago

Hi all,

just adding an idea from Martin Jones on twitter: https://twitter.com/martinjones78/status/1288392449438744577?s=20

We could read the tags from NEUBIAS BIII database. Many popular plugins should be tagged in this database already.

Cheers, Robert

haesleinhuepf commented 4 years ago

See also: https://github.com/scijava/scijava-search/pull/18

ctrueden commented 4 years ago

Thanks for the feedback, @k-dominik. I think the search could be improved to make ilastik match the run Pixel Classification plugin without needing to add support for tags: if the string is also matched against non-leaf menu strings, that would do it. I can't remember whether this is already the case, but it would also be good to match against descriptions too (i.e. the description = "..." part of the @Plugin annotation). So then you could add some description for the command that also uses the string ilastik, to ensure a match.

CC @frauzufall

k-dominik commented 3 years ago

this seems to be fixed?!