You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OLS currently does not have a way to display how a search hit was established.
In particular, the autocomplete field does not show the field where the hit was done, like say Protege does:
It would be super useful if at least the autocomplete, but maybe even the search results page, would indicate which field in the index was matched by the search so you can more immediately mentally discard or zone in on a specific match.
Use cases
Make it easier to understand the relevance of a search.
User communities
All OLS users
Describe the solution you'd like
I don't know. There must be some guidelines for search design for this kind of thing. Protege is a but dated, but that's one solution (that does not fit in the search paradigm of OLS, but maybe can serve as inspiration). Maybe just list the "match field" as a little green box?
New feature description.
OLS currently does not have a way to display how a search hit was established.
In particular, the autocomplete field does not show the field where the hit was done, like say Protege does:
It would be super useful if at least the autocomplete, but maybe even the search results page, would indicate which field in the index was matched by the search so you can more immediately mentally discard or zone in on a specific match.
Use cases
Make it easier to understand the relevance of a search.
User communities
Describe the solution you'd like
I don't know. There must be some guidelines for search design for this kind of thing. Protege is a but dated, but that's one solution (that does not fit in the search paradigm of OLS, but maybe can serve as inspiration). Maybe just list the "match field" as a little green box?
Describe alternatives you've considered
None.
Additional context
See for example my worries in #843
The text was updated successfully, but these errors were encountered: