[
https://issues.apache.org/jira/browse/MAHOUT-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683251#action_12683251
]
Sean Owen commented on MAHOUT-103:
----------------------------------
The comparison would be to Item. You could say that's as domain-specific as
Click; I'd suggest that User/Item are the 'abstract' concepts in this context
since collaborative filtering is invariably explained in terms of users and
items, though of course your user or item can be whatever you like.
At least, there is no need to have both "Click" and "Item" -- unless this
particular context requires one to store more information about a click as an
item, in which case it should at least implement Item. But I don't think that's
the case.
The good news is that this work doesn't seem to only apply to processing click
logs, so, I'm suggesting it might be even more useful to express it in terms of
the 'abstract' concepts in this context.
> Co-occurence based nearest neighbourhood
> ----------------------------------------
>
> Key: MAHOUT-103
> URL: https://issues.apache.org/jira/browse/MAHOUT-103
> Project: Mahout
> Issue Type: New Feature
> Components: Collaborative Filtering
> Reporter: Ankur
> Assignee: Ankur
> Attachments: jira-103.patch
>
>
> Nearest neighborhood type queries for users/items can be answered efficiently
> and effectively by analyzing the co-occurrence model of a user/item w.r.t
> another. This patch aims at providing an implementation for answering such
> queries based upon simple co-occurrence counts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
