Taste already exposes a web service layer, so I'm not sure how much more there is on the Mahout end for recommenders. Still, would be great to see and I'm sure it would help iron out API issues, etc. These are definitely the kinds of things I'd love to see.
On Mar 22, 2010, at 5:56 PM, Ted Dunning wrote: > What kind of integration would you be thinking of? > > Drupal is largely PHP based which should make it relatively easy to build a > module that uses thrift to call java recommendation functions. > > Would that be what you are talking about doing? That might be of real > value. > > The questions I have are: > > a) how stable could the module be given the famously "no backward > compatibility guarantee" in Drupal? > > b) what does the Drupal community want/need for recommendations? > > c) would the GPL of Drupal interact poorly with the Apache licensing of > Mahout? > > d) where would the resulting code live? In Drupal as a contributed module? > (that makes more sense to me) > > e) how would a Drupal admin configure the recommendation capability? Could > that configuration be made web accessible? > > This proposal is exciting, not because of the technical difficulty, but > because it would make Mahout much more usable to a large number of sites. > > > On Mon, Mar 22, 2010 at 12:51 PM, Daniel Xiaodan Zhou (JIRA) < > j...@apache.org> wrote: > >> >> I'm a PhD student at University of Michigan, with a research focus on >> recommender systems. Last year I participated GSOC 2009 with Drupal.org, and >> developed a recommender system for Drupal. But that module was not as >> sophisticated as Mahout. And I think it would be nice just to integrate >> Mahout into Drupal rather than developing a separate Mahout-like module for >> Drupal. >> >> Any comments? I can provide more information if people here are interested. >> Thanks.
