Hi, I think it is an interesting feature. But maybe it is not the best way to exclude the item at the end of the recommendation process.
Another way could be to just add a preference with a negative rating to the input data whenever a user rejects an item. That way this would provide more information about the user and the item would automatically be excluded from the output of the RecommenderJob as the user has already seen this item. The question is whether it's conceptually okay to add a negative preference whenever the user rejects an item. Any thoughts on this? --sebastian Am 23.08.2010 15:57, schrieb han henry: > Hi,All > > Sometimes user's dislikes some recommendation we generated ,he/she > does not want to see the recommended items again. > > Here is a example from Amazon.com (see the attachment ). > > I have written one patch for it.the logic as following : > > 1) Dump user's non-interested items to HDFS, format like > userId+"_"+item_id. before we run RecommenderJob > 2) Load user's invalid data to HashMap when > AggregateAndRecommendReducer setup > 3) Skip user's non-interested items when choose TOP N recommendations > for user. > > Does it make sense and can merge to the repository ? > >
