Add a search help pop windows that gives advice about wild cards and boolean operators

[stuzart]

Perhaps a little ? button next to the search box, that pops up a window that explains these tricks, plus any other features that are available (see comment below)

[stuzart]

Claude has indicated:

Here is a rundown of what the current search config actually supports, verified against a live Solr index. This can feed into the help pop-up.

Query-syntax features (edismax parser)

Feature	Example	Notes
Boolean operators	cosmo OR headings, wnt AND signalling, cell NOT plant	Must be UPPERCASE
Require / prohibit	+kinase -yeast	+ term must appear, - term must not
Grouping	(kinase OR phosphatase) AND assay	Parentheses to combine clauses
Phrase	"data file"	Exact adjacent-word match
Proximity	"gene expression"~5	Words within N of each other
Wildcards	metabol*, d?tafile, *omics	* (many chars) and ? (one char); leading wildcards work too
Fuzzy	charactaristic~ or ~2	Edit-distance match — tolerates typos
Term boost	kinase^5 assay	Weight one term higher in ranking
Field-scoped	title_text:kinase	Works, but needs internal Solr field names — power-user only

Matching behaviour baked into the analyser (automatic — no operator needed)

These happen automatically because of how fields are indexed, and are arguably more useful than the operators:

• Implicit prefix / "starts-with" matching (EdgeNGram, min 2 chars) — metabol already matches metabolomics with no wildcard. Every search is effectively a prefix search.
• Accent / diacritic folding — Muller matches Müller, cafe matches café.
• Word-delimiter splitting + catenation — Thy-1, Thy 1 and Thy1 all match each other; likewise wnt3a ↔ wnt 3 a.
• Case-insensitive throughout.

Not configured (so won't help)

• No synonyms (mouse won't find murine)
• No stemming (run won't match running beyond the prefix rule)

Suggested focus for the help pop-up

For end users the two things worth surfacing are:

1. Uppercase AND / OR / NOT, +/-, "phrases", * wildcards and ~ fuzzy.
2. That partial words already match automatically, so a trailing * is rarely needed.