If You Liked This, You're Sure to Love That (2008)
nytimes.com
nytimes.com
There's a paragraph about this in the article that discusses automated identification of clusters, but it makes it sound like there was a lot of human judgment/guesswork in figuring out why any given set of movies clusters the way it does.
> Each new algorithm takes on average three or four hours to churn through the data on the family’s “quad core” Gateway computer.
Huh. I don't think I would have guessed that Gateway was still around in the days of quad-core desktops.
The Core2 Quad series released early 2007. I'm not 100% that was the first Intel consumer quad chip (memory is pretty fuzzy by now) but it was close.
You could ask people "What did you like about this movie?" and they could tag various things they liked about it, e.g. "was smart," "cheesy humor" or "had Jennifer Lawrence."
Heck, that sounds like something that might be worth building, a tag-based movie recommendation engine.
https://en.m.wikipedia.org/wiki/The_Thirty-Six_Dramatic_Situ...
As for who will enjoy what etc., there are entire industries that spend their efforts on knowing that, like Nielsen and Rotten Tomatoes.
One category listed here is Pursuit:
> the fugitive flees punishment for a misunderstood conflict. Example: Les Misérables
By this logic, 'Les Miserables', 'Mission Impossible', and 'Catch Me if You Can' are all just rehashing the same basic idea. On an existential level, sure, but is there any practical use to a category that broad?
Like 'Shrek'? Enjoy recommendations for kids movies for the next 3 months.
Like 'Before Sunrise'? You're going to love The Tall Girl!
There is tons of scheduled maintenance. And there are also lots of common unscheduled maintenance items. These were basically worthless in any naive prediction. Basically "Ah, I see that an engine failure is always preceded by dozens of oil changes." There's a tiny predictive value, because number of oil changes is a proxy for age/use; older engines are more likely to fail.
But that sort of prediction wasn't helpful. We ended up proposing a strategy that I shorthand to "without which, not". Basically we wanted to classify the events which precede a specific type of failure, but which we don't see in similar vehicles without the failure. This is grossly oversimplified.
An analog would be the idea of necessary vs sufficient pre-conditions. We were trying to identify the sufficient pre-conditions.
To draw the analogy to a recommendation engine, a common failure mode is that popular things get recommended a lot. Another failure mode is that they basically become genre filters. This is discussed elsewhere.
So in a movie context, we wouldn't be looking for "what do other people who like this movie watch"? Because that's a genre popularity contest. We would ask "Given that a user likes Movie A, what did they watch before that other Movie A likers didn't watch?" And then look for clusters there.
Again, I'm grossly oversimplifying this, because I didn't get to implement the solution I mentioned. The approach seemed promising, though. You might consider this a nuance on "down-weighting popular things", but it's not quite that.
Could be I'm misremembering, but if I am I think I'm in good company.