search

ome / omero-mapr

An OMERO.web app allowing to browse the data through attributes linked to the image
https://pypi.org/project/omero-mapr/
GNU Affero General Public License v3.0
5 stars 12 forks source link

"wildcard" config value acts counter-intuitive; also there are no wildcards in the search function #80

Open JensWendt opened 1 year ago

JensWendt commented 1 year ago

The config setting "wildcard": {"enabled": true} leads to all Values being visible in the search function before putting any search string in. But it does not actually enable using wildcards ?/* in the search function. I assume the search "engine" is the same as the one utilized for the "main" search function. If so, why are wildcards not working?

My proposal is to change the current wildcard setting to visibility and either implement a "real" wildcard setting enabling the use of wildcards in the search or enable them by default.

JensWendt commented 1 year ago

sorry, have to "store" these here to use them in the upcoming PR for the readme.rst additions. Example2

Example3

will-moore commented 1 year ago

I'm afraid omero-mapr doesn't use the same Lucene-backed search as the main webclient. It actually generates specific SQL queries for the OMERO database, which can get pretty complex.

It should be possible to support wild-card searches, since that's already what's being used to generate the auto-complete values (although that is a trailing wild-card instead of 'any' wild-card).