Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Results ordering for "Configuration" keyword #305

Open
rsvoboda opened this issue Jul 18, 2024 · 1 comment
Open

Results ordering for "Configuration" keyword #305

rsvoboda opened this issue Jul 18, 2024 · 1 comment

Comments

@rsvoboda
Copy link
Member

Results ordering for "Configuration" keyword should be imho improved.

I expected https://quarkus.io/guides/config and https://quarkus.io/guides/config-reference to be on the first two places, but they are on the 4th and 6th place. The guide I would expect on the first place is the one on the sixth place.

Here is the screenshot for https://quarkus.io/guides/#q=Configuration

Screenshot 2024-07-18 at 15 11 35

I get the same result for https://quarkus.io/guides/#q=Configuring search.

@yrodiere
Copy link
Member

yrodiere commented Jul 19, 2024

I think this is similar to #40.

What we have now is scoring, based on the frequency and number of tokens in a document. It is a reflection of how well a document matches a query, using an objective formula.

What you are after is something that takes into account the relative (and subjective) "importance" of a document. You want "first-class" guides to appear first, even if they don't score quite as well as lower-class guides.

In #40 as well as here, I think the answer is adding a rank to guides and taking it into account when scoring, i.e. something like #12.

@yrodiere yrodiere added help wanted Extra attention is needed and removed help wanted Extra attention is needed labels Dec 6, 2024
@yrodiere yrodiere modified the milestone: MVP Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants