feat: Improve TF-IDF weighting, match explanations, and MovieLens enrichment - #5
Merged
Merged
Conversation
## Summary - Replaced weighted `tfidf_soup` repetition with separate TF-IDF indexes for description, genres, cast, and director - Added explicit TF-IDF field weights: - Description: 50% - Genres: 30% - Cast: 10% - Director: 10% - Updated recommender scoring so TF-IDF content similarity has more influence than IMDb/popularity - Added `match_breakdown` to recommendation results so the backend can explain how match scores are calculated - Disabled MDP diversity re-ranking for now so final results stay ordered by relevance score
cheangie
approved these changes
Jun 22, 2026
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
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.
Summary
tfidf_souprepetition with separate TF-IDF indexes for description, genres, cast, and directorratings_summary.csvmatch_breakdownto recommendation results so the backend can explain how match scores are calculated