Improve user search relevance by boosting staff, contributors, and active users #12633
+43
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hiviexd
reviewed
Dec 31, 2025
| if ($boost_groups === null) { | ||
| $getGroupId = fn ($identifier) => app('groups')->byIdentifier($identifier)?->getKey(); | ||
|
|
||
| $boost_groups = [ |
Member
There was a problem hiding this comment.
would suggest adding the following groups to boosts so all relevant usergroups are covered:
5boost:2boost:
Contributor
Author
There was a problem hiding this comment.
Done. but I'm not sure if the group tags support, featured_artist, beatmap_spotlights, tournament_staff are 100% correct
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #12579
Rationale
Currently, user search results are often dominated by inactive accounts, making it difficult to find active community members or staff. This PR introduces a boosting mechanism in Elasticsearch to prioritize relevant users without affecting the accuracy of string matching
Changes
groupsfield to theusersindex mappingUserSearchtrait to include user group IDs in the search indexUserSearch::getQuery()to use a nestedboolquerymustblock to maintain strictminimum_should_match: 1requirementsshouldclauses for boosting:boost: 5boost: 2boost: 1.5staticvariables to ensure zero database overhead