Boost service discovery (tile) results based on boosted category. #1392
Conversation
This file contains 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
schroerbrian
approved these changes
Aug 6, 2024
| // Our Algolia plan only allows for up to one optional filter, so just | ||
| // drop all but the first. | ||
| .slice(0, 1); | ||
| console.log(configureProps); |
There was a problem hiding this comment.
Did you intend to leave in this console.log?
There was a problem hiding this comment.
Whoops, nice catch! Just removed it in 46d2ceb.
|
It looks like I'm failing CI because GitHub Actions removed support for the old version of docker-compose, and the new one is just a subcommand of the Let me fix that in a separate PR, since I don't want to mix random infra changes with this PR. |
In order to surface some specific results on the tile results page, we make use of an optional filter on a newly added Algolia index property. On the backend, we've created a new column, `boosted_category`, which we can optionally set on each Service. This allows us perform an optional filter only on the tile results pages, and not the general search page, where services that match the optional filter are boosted in ranking. For now, there can only be one `boosted_category` per service, but this is sufficient for the current use case, where only two services need to be boosted, and they each only apply to one category.
richardxia
force-pushed
the
add-optional-filter-on-boosted-category
branch
from
46d2ceb to
ae58299
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In order to surface some specific results on the tile results page, we make use of an optional filter on a newly added Algolia index property.
On the backend, we've created a new column,
boosted_category, which we can optionally set on each Service. This allows us perform an optional filter only on the tile results pages, and not the general search page, where services that match the optional filter are boosted in ranking.For now, there can only be one
boosted_categoryper service, but this is sufficient for the current use case, where only two services need to be boosted, and they each only apply to one category.