Searching is not user-friendly

[misev]

The search interface could definitely be improved with more user-friendly defaults:

1. Do partial matching by default, as it is you need to wrap the search term with % in order to find things (and this only works for Title which is hidden in Additional filters). Exact match is usually done explicitly with double quoting the search terms
2. Case-insensitive by default
3. Support for full-text search that matches everything in the catalog entries; this could be put on top as the first field
4. Temporal/spatial filtering should be lower priority, maybe down in the Additional filters

cc @KathiSchleidt

[KathiSchleidt]

Agreed with all points above, aligned with what we've been requesting from EOX. See Minutes of the meeting 2024_06_11 : general overview and discussion on data ingestion and provisioning

Additional search functionality I'm just seeing in a different project on soil data, they allow for search based on data source, e.g. INSPIRE, Copernicus, etc. This seems like a useful functionality. Wondering if an additional metadata field for this purpose would be useful.

@baloola am I correct that there is no formal specification on catalog functionality?

[jetschny]

the search had indeed been identified as a real bottleneck. a first "easy" solution is to change the layout of the search so that "filters" come up first, afterwards time and space extend appear. further, searchable filter items should go beyond the 3 current items (id, title, acquired). it might not cover all meta data fields but an agreed subset of the most important ones. finally, if we cannot have partial search but rely on "%" characters, we should give an example "%no2%" ...