You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mahout.apache.org by Octavian Covalschi <oc...@gmail.com> on 2011/10/04 16:56:56 UTC
Taste + filters
Hi there.
I'm working on a small project that is using taste for user based
recommendations. We were able to integrate MongoDb with it using
MongoDBDataModel instead of file feeds. Results are pretty good in our
opinion, however we'd like to go further and add some kind of filters, to
have even more relevant results. For example each item may have some
attributes and we'd like to use them part of results... I don't want to
apply filters after getting results from taste since we may end up by
excluding all of them, which will make us querying taste again, if that
makes sense...
So, is there anything out of the box that could help us? Or we'll have to
tweak out datamodel in order to accomplish that?
Any suggestions are welcome. Thank you in advance.
Re: Taste + filters
Posted by Octavian Covalschi <oc...@gmail.com>.
The project is at it's early stages... so far we have only 100 users and
2000 items.. so nothing to show right now.
On Tue, Oct 4, 2011 at 10:20 PM, Lance Norskog <go...@gmail.com> wrote:
> Can you post any database sizing/performance numbers?
>
> Lance
>
> On Tue, Oct 4, 2011 at 9:02 AM, Octavian Covalschi <
> octavian.covalschi@gmail.com> wrote:
>
> > That's good to know too. Thank you!
> >
> > On Tue, Oct 4, 2011 at 10:44 AM, Sebastian Schelter <ss...@apache.org>
> > wrote:
> >
> > > You can implement a custom CandidateItemsStrategy. This class
> determines
> > > which items are initially selected for the recommendation process.
> > >
> > > --sebastian
> > >
> > > On 04.10.2011 16:56, Octavian Covalschi wrote:
> > > > Hi there.
> > > >
> > > > I'm working on a small project that is using taste for user based
> > > > recommendations. We were able to integrate MongoDb with it using
> > > > MongoDBDataModel instead of file feeds. Results are pretty good in
> our
> > > > opinion, however we'd like to go further and add some kind of
> filters,
> > to
> > > > have even more relevant results. For example each item may have some
> > > > attributes and we'd like to use them part of results... I don't want
> to
> > > > apply filters after getting results from taste since we may end up by
> > > > excluding all of them, which will make us querying taste again, if
> that
> > > > makes sense...
> > > >
> > > > So, is there anything out of the box that could help us? Or we'll
> have
> > to
> > > > tweak out datamodel in order to accomplish that?
> > > >
> > > > Any suggestions are welcome. Thank you in advance.
> > > >
> > >
> > >
> >
>
>
>
> --
> Lance Norskog
> goksron@gmail.com
>
Re: Taste + filters
Posted by Lance Norskog <go...@gmail.com>.
Can you post any database sizing/performance numbers?
Lance
On Tue, Oct 4, 2011 at 9:02 AM, Octavian Covalschi <
octavian.covalschi@gmail.com> wrote:
> That's good to know too. Thank you!
>
> On Tue, Oct 4, 2011 at 10:44 AM, Sebastian Schelter <ss...@apache.org>
> wrote:
>
> > You can implement a custom CandidateItemsStrategy. This class determines
> > which items are initially selected for the recommendation process.
> >
> > --sebastian
> >
> > On 04.10.2011 16:56, Octavian Covalschi wrote:
> > > Hi there.
> > >
> > > I'm working on a small project that is using taste for user based
> > > recommendations. We were able to integrate MongoDb with it using
> > > MongoDBDataModel instead of file feeds. Results are pretty good in our
> > > opinion, however we'd like to go further and add some kind of filters,
> to
> > > have even more relevant results. For example each item may have some
> > > attributes and we'd like to use them part of results... I don't want to
> > > apply filters after getting results from taste since we may end up by
> > > excluding all of them, which will make us querying taste again, if that
> > > makes sense...
> > >
> > > So, is there anything out of the box that could help us? Or we'll have
> to
> > > tweak out datamodel in order to accomplish that?
> > >
> > > Any suggestions are welcome. Thank you in advance.
> > >
> >
> >
>
--
Lance Norskog
goksron@gmail.com
Re: Taste + filters
Posted by Octavian Covalschi <oc...@gmail.com>.
That's good to know too. Thank you!
On Tue, Oct 4, 2011 at 10:44 AM, Sebastian Schelter <ss...@apache.org> wrote:
> You can implement a custom CandidateItemsStrategy. This class determines
> which items are initially selected for the recommendation process.
>
> --sebastian
>
> On 04.10.2011 16:56, Octavian Covalschi wrote:
> > Hi there.
> >
> > I'm working on a small project that is using taste for user based
> > recommendations. We were able to integrate MongoDb with it using
> > MongoDBDataModel instead of file feeds. Results are pretty good in our
> > opinion, however we'd like to go further and add some kind of filters, to
> > have even more relevant results. For example each item may have some
> > attributes and we'd like to use them part of results... I don't want to
> > apply filters after getting results from taste since we may end up by
> > excluding all of them, which will make us querying taste again, if that
> > makes sense...
> >
> > So, is there anything out of the box that could help us? Or we'll have to
> > tweak out datamodel in order to accomplish that?
> >
> > Any suggestions are welcome. Thank you in advance.
> >
>
>
Re: Taste + filters
Posted by Sebastian Schelter <ss...@apache.org>.
You can implement a custom CandidateItemsStrategy. This class determines
which items are initially selected for the recommendation process.
--sebastian
On 04.10.2011 16:56, Octavian Covalschi wrote:
> Hi there.
>
> I'm working on a small project that is using taste for user based
> recommendations. We were able to integrate MongoDb with it using
> MongoDBDataModel instead of file feeds. Results are pretty good in our
> opinion, however we'd like to go further and add some kind of filters, to
> have even more relevant results. For example each item may have some
> attributes and we'd like to use them part of results... I don't want to
> apply filters after getting results from taste since we may end up by
> excluding all of them, which will make us querying taste again, if that
> makes sense...
>
> So, is there anything out of the box that could help us? Or we'll have to
> tweak out datamodel in order to accomplish that?
>
> Any suggestions are welcome. Thank you in advance.
>
Re: Taste + filters
Posted by Octavian Covalschi <oc...@gmail.com>.
Thank you for the quick reply.
Yes, it looks like it's what I need, I'll read further.
Thanks!
On Tue, Oct 4, 2011 at 10:13 AM, Sean Owen <sr...@gmail.com> wrote:
> Yes, you want exactly the Rescorer interface which will let you push
> around the results as you like.
>
> On Tue, Oct 4, 2011 at 3:56 PM, Octavian Covalschi
> <oc...@gmail.com> wrote:
> > Hi there.
> >
> > I'm working on a small project that is using taste for user based
> > recommendations. We were able to integrate MongoDb with it using
> > MongoDBDataModel instead of file feeds. Results are pretty good in our
> > opinion, however we'd like to go further and add some kind of filters, to
> > have even more relevant results. For example each item may have some
> > attributes and we'd like to use them part of results... I don't want to
> > apply filters after getting results from taste since we may end up by
> > excluding all of them, which will make us querying taste again, if that
> > makes sense...
> >
> > So, is there anything out of the box that could help us? Or we'll have to
> > tweak out datamodel in order to accomplish that?
> >
> > Any suggestions are welcome. Thank you in advance.
> >
>
Re: Taste + filters
Posted by Sean Owen <sr...@gmail.com>.
Yes, you want exactly the Rescorer interface which will let you push
around the results as you like.
On Tue, Oct 4, 2011 at 3:56 PM, Octavian Covalschi
<oc...@gmail.com> wrote:
> Hi there.
>
> I'm working on a small project that is using taste for user based
> recommendations. We were able to integrate MongoDb with it using
> MongoDBDataModel instead of file feeds. Results are pretty good in our
> opinion, however we'd like to go further and add some kind of filters, to
> have even more relevant results. For example each item may have some
> attributes and we'd like to use them part of results... I don't want to
> apply filters after getting results from taste since we may end up by
> excluding all of them, which will make us querying taste again, if that
> makes sense...
>
> So, is there anything out of the box that could help us? Or we'll have to
> tweak out datamodel in order to accomplish that?
>
> Any suggestions are welcome. Thank you in advance.
>