Feature Overview (aka. Goal Summary)

Users are getting more accurately ordered search results when they filter the OperatorHub catalog view, based on relevancy rather than mere lexical order.

Goals (aka. expected user outcomes)

User experience improves when browsing the catalog and we are more accurately representing the OpenShift value-add when searching for popular terms like "gitops" or "servicemesh".

Requirements (aka. Acceptance Criteria):

Search results in the OperatorHub catalog are based on relevance by default. That means results with search term matches in the operator's title or keywords are ranked higher than those with matches in the operator description. A litmus test is searching for "serverless" which should yield the Red Hat OpenShift Serverless operator ahead of Red Hat Camel-K, or "gitops" which should ran Red Hat OpenShift GitOps higher than "Sandbox"

Questions to Answer (Optional):

• can we do this solely on the Console / client side?

Out of Scope

• search result ranking based on usage stats or popularity

Background

There is currently a lot of noise in the search results of OperatorHub due to the fact that search results are simple displayed in alphabetical order, which yields strange proposal like "Camel-K" being listed first when search for "serverless". When implemented successfully, relevance-based ordering would ensure that the layered products are displayed first.

Customer Considerations

none

Documentation Considerations

none

Interoperability Considerations

This impacts all OpenShift flavors and form factors that include OLM, the Console and our default operator catalogs.