Building a Recommender System
A beginners guide to building a recommendation system, with a step-by-step guide on how to create a content-based filtering system to recommend movies for a user to watch.
By Matthew Mahowald, Open Data Group.
Recommender systems are one of the most prominent examples of machine learning in the wild today. They determine what shows up in your Facebook news feed, in what order products appear on Amazon, what videos are suggested in your Netflix queue, as well as countless other examples. But what are recommender systems, and how do they work? This post is the first in a series exploring some common techniques for building recommender systems as well as their implementation.
What is a recommender system?
A recommender system is an information filtering model that ranks or scores items for users. There are generally two types of ranking methods:
- Content-based filtering, in which recommended items are based on item-to-item similarity and the user’s explicit preferences; and
- Collaborative filtering, in which items are recommended to users based on the preferences of other users with similar transaction histories and characteristics.
The information used in collaborative filtering can be explicit, where users provide ratings for each item, or implicit, where user preferences have to be extracted from user behavior (purchases, views, etc). The most successful recommender systems use hybrid approaches combining both filtering methods.
The MovieLens Datasets
To make this discussion more concrete, let’s focus on building recommender systems using a specific example. GroupLens, a research group at the University of Minnesota, has generously made available the MovieLens dataset. This dataset consists of approximately 20 million user ratings applied to 27,000 movies by 138,000 users. In addition, the movies include genre and date information. We’ll use this dataset to build
Simple Content-based Filtering
Let’s build a simple recommender system that uses content-based filtering ( i.e. item similarity) to recommend movies for us to watch. First, load in the movie dataset from MovieLens and multihot-encode the genre fields:
genres feature consists of one or more pipe (“|”) separated genres. The last line above adds a column for each possible genre and puts a 1 in that entry if the genre tag is present, or a 0 otherwise.
Let’s generate some recommendations based on item similarity using these tags. A very common similarity measure for categorical data (such as tags) is cosine similarity. For any two items and , the cosine similarity of and is simply the cosine of the angle between and where and are interpreted as vectors in feature space. Recall that the cosine is obtained from the inner product of these vectors:
As a concrete example, consider the films $i := $ Toy Story (genre tags “Adventure”, “Animation”, “Children”, “Comedy”, and “Fantasy”) and $j := $ Jumanji (genre tags “Adventure”, “Children”, and “Fantasy”). The dot product is 3 (the two films have three tags in common). and , so the cosine similarity between these two films is
We can compute the cosine similarity for all of the items in our dataset:
The very first film in the dataset is Toy Story. Let’s find out what the similar films to Toy Story are:
|Toy Story (1995)||Adventure,Animation,Children,Comedy,Fantasy|
|Monsters, Inc. (2001)||Adventure,Animation,Children,Comedy,Fantasy|
|Emperor’s New Groove, The (2000)||Adventure,Animation,Children,Comedy,Fantasy|
The first five films all have exactly the same genre tags as Toy Story, and hence a cosine similarity of 1. In fact, for the sample data used here, there are thirteen films with similarity 1; the most similar film without identical tags is 2006’s “The Ant Bully”, which has the additional genre tag “IMAX”.
Simple Collaborative Filtering
Collaborative filtering recommends items based on what similar users liked. Fortunately, in the MovieLens dataset, we have a wealth of user preference information in the form of movie ratings: each user assigns one or more films numeric ratings between 1 and 5 indicating how much they enjoyed the film. We can view the problem of recommending items to the user as a prediction task: given the user’s ratings of other films, what is their likely rating of the film in question?
One simple way to do this is to assign a similarity-weighted rating to each item using other users’ ratings:
where is the predicted rating of item by user , is a measurement of similarity between users and , and is the known rating of item by user .
For our user similarity measurement, we’ll look at users’ ratings of movies. Users with similar ratings will be considered similar. To work with this rating data, an important first step is to normalize our ratings. We’ll do this in three steps: first, we’ll subtract the overall mean rating (across all films and users) so that our adjusted ratings are centered at 0. Next, we’ll do the same thing for each film, to account for the mean ratings of a given film differing. Finally we’ll subtract off the mean rating for each user—this accounts for individual variations (e.g. one user giving consistently higher ratings than another).
Mathematically, our adjusted rating is
where is the base rating, is the overall mean rating, is the mean rating for item (after subtracting the overall mean), and is the mean rating for user (after adjusting for the overall mean rating and the item mean ratings). For convenience, I’ll refer to the adjusted rating as the preference of user for item .
Let’s load in the ratings data and compute the adjusted ratings:
At this point we can easily establish a reasonable baseline estimate for a given user’s rating of films they haven’t seen:
We can compute the distance to a particular user (in this case, user 0) as follows:
It turns out that the nearest user is user 12 (with distance 0):
We find two films that user 12 has seen that user 0 has not:
Unfortunately, user 12 dislikes both of the films that user 0 hasn’t seen yet! We should continue our computation to account for all of the nearby users.
The methods used in this post are neighborhood-based, and we’ve just seen above a potential pitfall when generating recommendations based on neighbors: neighbors may not actually recommend any items the user in question hasn’t already seen. Because of the need to compute pairwise distances, neighborhood-based methods also tend to scale poorly as the number of users increases.
In part 2 of this series, we’ll take a look at another approach for building recommender systems, this time using latent factor methods. Latent factor models avoid some of the pitfalls of the neighborhood-based methods described here—but as we’ll see, they come with some challenges of their own!
- On-line and web-based: Analytics, Data Mining, Data Science, Machine Learning education
- Software for Analytics, Data Science, Data Mining, and Machine Learning
- Preparing for the Unexpected
- Word Embeddings in NLP and its Applications
- State of the art in AI and Machine Learning – highlights of papers with code
|Top Stories Past 30 Days|