-
Notifications
You must be signed in to change notification settings - Fork 331
Develop Event abstraction #48
Comments
Michael Ekstrand ekstrand@cs.umn.edu on 2011-07-15 20:25:52 said: In [d3a13596ca2a9e995f74e1197fef52916bcd5d78]:
Note: This comment has been automatically migrated from Bitbucket |
Michael Ekstrand ekstrand@cs.umn.edu on 2011-07-15 20:25:51 said: In [b9cbfd068f0ff714c0dc39c3d4003c1fc4cfc77f]:
Note: This comment has been automatically migrated from Bitbucket |
ekstrand on 2011-07-15 18:41:42 said: This is written and in review. Note: This comment has been automatically migrated from Bitbucket |
Michael Ekstrand ekstrand@cs.umn.edu on 2011-07-14 15:45:59 said: In [98892a010b793929006ede7ecb8e0341daffeec6]:
Note: This comment has been automatically migrated from Bitbucket |
ekstrand on 2011-07-01 16:16:27 said: Deferring unfinished tickets. Note: This comment has been automatically migrated from Bitbucket |
ekstrand on 2011-07-01 15:22:55 said: This is changing a lot - we now want an Event abstraction (and have gotten rid of Note: This comment has been automatically migrated from Bitbucket |
ekstrand on 2011-06-17 21:36:27 said: Deferring to future release. Note: This comment has been automatically migrated from Bitbucket |
ekstrand on 2011-06-15 21:46:57 said: Evaluate this for 0.1, need the API solidified. Note: This comment has been automatically migrated from Bitbucket |
ekstrand on 2011-07-15 20:47:59 said: Now done. Note: This comment has been automatically migrated from Bitbucket |
Michael Ekstrand ekstrand@cs.umn.edu on 2011-07-15 20:25:53 said: In [936be4f70e051ac06adabb6c111abafbf9560ff6]:
Note: This comment has been automatically migrated from Bitbucket |
Michael Ekstrand ekstrand@cs.umn.edu on 2011-07-15 20:25:53 said: In [214770fd7542cae20f157ef1e838fc28b531790c]:
Note: This comment has been automatically migrated from Bitbucket |
Michael Ekstrand ekstrand@cs.umn.edu on 2011-07-15 20:25:52 said: In [c692655e080de952c2f42ecc0f4fd4e2b9e25213]:
Note: This comment has been automatically migrated from Bitbucket |
(originally reported in Trac by @elehack on 2011-04-05 14:44:19)
In order to support basket-based recommenders, we need the ability to present unary purchase or click data in the data source. In order to support this, we will introducing the concept of Events which are stored in the DAO.
The upshot of this is that we no longer need a hierarchy of DAO objects - we can just have DAO which provides users, items, and history queries. This also makes all data sources available uniformly - so more exotic recommenders can operate on combinations of purchases and ratings, for example. Subclasses can, of course, introduce additional information such as item metadata.
Note: This issue has been automatically migrated from Bitbucket
Created by grouplens on 2013-02-01T21:55:47.002449+00:00, last updated: 2013-02-01T22:35:41.165673+00:00
The text was updated successfully, but these errors were encountered: