commit to Universal recommender

[r4sn4]

Features included -

1. must include particular items in result
2. return properties with items in result
3. blacklist items containing particular property such as category, brand
4. recommend products in particular price range
5. merged code of price range with date range
6. merged code of blacklisting items with blacklist category, brand

Aggregate query for above features is -

curl -H "Content-Type: application/json" -d '{ "user": "u1", "num": 4,"includeItems" : ["Iphone 4","Nexus"], "blacklistCategory" :["c1"] , "blacklistBrand": ["b1"],"blacklistItems" :["i1"]}' http://localhost:8000/queries.json

We are working on code to make it more generic.

[pferrel]

We need to be able to specify a filter like we do with properties, which include the property name so they can be used for any property not just Category or Brand. I suggest an addition to the field definition, perhaps a bias enumeration, like

"bias": {
    "type": "not"
}

"bias": {
    "value": -1 // for filter
}

the type and value would not be used together.

by default the type is None, which means current behavior.

This will allow any number of fields to be set for any named property. Likewise this could be put in the engine.json for global application or into the query.

[r4sn4]

Hi Pat

Just read your suggestions. Will work on it.
Once completed will send you PR

[pferrel]

Some good work but we need to work with any property name not just Category or Brand, all properties are defined by the JSON in the $set so any name will work. Therefor the "field" in engine.json and the query will apply to them. So perhaps an extension of the "field" definition is the best way to handle categorical property exclusions.

Likewise for the numerical range, this needs to be renamable for times when it does not apply to "price"

[r4sn4]

Hi Pat

Any suggestion on return Item properties along with Item score in recommendation result?

[pferrel]

These changes seem rather ambitious maybe create a new one for returning item properties against the master? That change is fairly simple but getting these working in a general way without hardcoded names will be more work.

The item properties are returned from Elasticsearch but not used to create the result list. You could change the PredictedResults to include more data along with the score. It should be an Option controlled by a flag in the query or engine.json. Something like "returnProperties": true, which defaults to false to work like it does now. This could be in the engine.json to work globally and in the query for use in the single results.

[r4sn4]

Thanks for response Pat. Working on this