Return-Path: Delivered-To: apmail-lucene-mahout-dev-archive@minotaur.apache.org Received: (qmail 43253 invoked from network); 27 Jan 2010 05:16:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Jan 2010 05:16:14 -0000 Received: (qmail 60750 invoked by uid 500); 27 Jan 2010 05:16:13 -0000 Delivered-To: apmail-lucene-mahout-dev-archive@lucene.apache.org Received: (qmail 60633 invoked by uid 500); 27 Jan 2010 05:16:13 -0000 Mailing-List: contact mahout-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mahout-dev@lucene.apache.org Delivered-To: mailing list mahout-dev@lucene.apache.org Received: (qmail 60614 invoked by uid 99); 27 Jan 2010 05:16:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jan 2010 05:16:12 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ted.dunning@gmail.com designates 209.85.216.186 as permitted sender) Received: from [209.85.216.186] (HELO mail-px0-f186.google.com) (209.85.216.186) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jan 2010 05:16:04 +0000 Received: by pxi16 with SMTP id 16so3795566pxi.29 for ; Tue, 26 Jan 2010 21:15:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=NG4/YzVXZpVC9YAs6140/qbXcmx+gwaZ+ojqs/iPqfA=; b=M1yegJsdYquvSnf96rrQJi0111uagxFO/g2N85L6Nrf9GE7n8yGzClhWvihSp+qze3 Bi9dqHWUoYBS4OiXxjlu/EuFJvVxPSY2egO33h/rpS15lfc9+X5AYUtdEDeA2S04rjLv X1acNo1koLvUbFeY66OrkOlU8FC9oPvkJb8c8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=gz+/qRSzA02mcO/6oRexeALEqHf1CWIUDWK0atA0ltKET8Z11WaXVFGspPrX6miVW3 VIq6RQd9BmxmNRnX2VpAD8BUFyXv4TlrlCxZhs2e450FMx5AvCsw9e5qpSmM4QQitAZu lKPRAc1XzzeLMI+0nxHUIvZdrpeuq0RB6Py+8= MIME-Version: 1.0 Received: by 10.114.99.11 with SMTP id w11mr6065129wab.131.1264569343103; Tue, 26 Jan 2010 21:15:43 -0800 (PST) In-Reply-To: <4b124c311001261815n1c173dadj2b3fc6a96de15f42@mail.gmail.com> References: <4b124c311001261815n1c173dadj2b3fc6a96de15f42@mail.gmail.com> From: Ted Dunning Date: Tue, 26 Jan 2010 21:15:23 -0800 Message-ID: Subject: Re: What is content based recommendation, to you To: mahout-dev@lucene.apache.org Cc: mahout-user@lucene.apache.org Content-Type: multipart/alternative; boundary=001636b14ab77d550c047e1e7e31 X-Virus-Checked: Checked by ClamAV on apache.org --001636b14ab77d550c047e1e7e31 Content-Type: text/plain; charset=UTF-8 This is a fine way to go (and I have often (mis)used search engines as recommendation engines). Another angle is to consider the item level recommendations for a single item to simply be additional attributes. You can also look at user level cooccurrence analysis of attributes (including SVD) as simply a way to smooth out the attributes a bit so that sparsity doesn't take such a big bite out of serendipity. This makes cooccurrence analysis look a whale of a lot like anchor text propagation which speaks to your final point. On Tue, Jan 26, 2010 at 6:15 PM, Jake Mannix wrote: > On Tue, Jan 26, 2010 at 3:36 PM, Ted Dunning > wrote: > > > I define it a bit differently by redefining recommendations as machine > > learning. > > > > On Tue, Jan 26, 2010 at 1:44 PM, Sean Owen wrote: > > > > > I would narrow and specify this, in the context of Mahout, to have a > > > collaborative filtering angle: > > > > Since Ted (Mr. Machine Learning) wants to describe content-based > recommendations > as machine learning, and Sean (Mr. Taste/CF) goes and describes it it terms > of > collaborative filtering, I suppose I'll put on my "search guy" hat, and > describe it the > way I see it: > -- Ted Dunning, CTO DeepDyve --001636b14ab77d550c047e1e7e31--