User 2568 | 5/10/2016, 1:59:14 AM
I've been experimenting using the popularity_recommender to predict hotel selection using the Expedia log data. I found that adding user and item side data doubles the validation score (MAP@5), which is probably expected.
What I don't get is why popularityrecommender doesn't support observational data. My understanding is user data is data specific to the user like their country or city, and item data is specific data for the item, e.ge., hotel country etc. Then there is observational data beyond the userid that specific to the log entry, e.g., day of week or hour etc, device attributes or search parameters like destination.
My question is, why doesn't popularity_recommender support this additional observation data, is it not appropriate or is it just not implemented.
My thought is I probably need to look at using rankingfactorizationrecommender, however I'm still working up to that.