Maybe, my hunch is that it will affect so much in the code as to be hard to
support. It is rare you want to filter the data in different ways repeatedly
I think. And if you're filtering one way probably better to not have it in
memory.
On Oct 8, 2010 6:43 PM, "Steven Bourke" <[email protected]> wrote:
> It would be a nice feature to have build into the api for sure. You could
> use the getPreferencesFromUser to determine which users have the
appropriate
> level of options.
>
> On Fri, Oct 8, 2010 at 6:27 PM, Sean Owen <[email protected]> wrote:
>
>> There's nothing built-in. Yeah I'd view that as a step outside the core
>> library.
>>
>> On Fri, Oct 8, 2010 at 5:56 PM, Chris Schilling
>> <[email protected]> wrote:
>> > Hello,
>> >
>> > I am wondering if it is possible to place selection criteria when
reading
>> in the preference data used by taste to make predictions. For instance: I
>> only want to use users who have reviewed more than 15 items. This is a
data
>> cleansing step that I can take care of before feeding the data to taste.
If
>> there is something built in though, it would make my life a bit easier :)
>> >
>> > Thanks
>> > ChrisS
>> >
>> >
>> >
>> >
>>
