Skip to content

Commit 76b68bb

Browse files
committed
Changed blacklistEvents to blacklistIndicators
1 parent c44f0c3 commit 76b68bb

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

h_ur_advanced_tuning.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,11 +46,11 @@ If training and query times are not a factor these can safely be increased with
4646
4747
The default `blacklistIndicators` in the engine parameters is the single primary event. This means that if the user took the primary event on an item it will not be returned in recommendations. This is often the right thing to do but there are exceptions.
4848
49-
In some cases an item may be consumed periodically like Clothing, or Food so reminding a user that they like an item may be good. To disable the blacklist set the following `"blacklistEvents": []`, which means to return all recommendations without restriction.
49+
In some cases an item may be consumed periodically like Clothing, or Food so reminding a user that they like an item may be good. To disable the blacklist set the following `"blacklistIndicators": []`, which means to return all recommendations without restriction.
5050
5151
It is possible with this setting to get only things the user is already familiar with. Disabling the blacklist may not be the best way to handle this. For instance lets say you have 10 recommendations to show; it might be better to get 9 recommendations (with the blacklist) and put in one item you already know the user prefers from your own data. Any mixing of items the user is familiar with and recommendations can be done as part of the application logic, not implemented by the recommender.
5252
53-
In other cases you may want to be more restrictive and use more than the primary event to filter out items from recs. Setting to `"blacklistEvents": ["buy", "view"]` is a good example, where anything the use bought or any item detail page the user viewed will will result in those items not being returned as recommendations.
53+
In other cases you may want to be more restrictive and use more than the primary event to filter out items from recs. Setting to `"blacklistIndicators": ["buy", "view"]` is a good example, where anything the use bought or any item detail page the user viewed will will result in those items not being returned as recommendations.
5454
5555
## Anti Flood
5656

h_ur_config.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ How to read config settings:
9595
},
9696
...
9797
],
98-
"blacklistEvents": ["<list>", "<of>", "<indicator>", "<names>"],
98+
"blacklistIndicators": ["<list>", "<of>", "<indicator>", "<names>"],
9999
"maxEventsPerEventType": <some-int>,
100100
"maxCorrelatorsPerEventType": "<some-int>",
101101
"maxQueryEvents": <some-int>,
@@ -167,7 +167,7 @@ How to read config settings:
167167
},
168168
...
169169
],
170-
"blacklistEvents": ["primary-indicator-name"], // OPTIONAL
170+
"blacklistIndicators": ["primary-indicator-name"], // OPTIONAL
171171
"maxEventsPerEventType": 500, // OPTIONAL
172172
"maxCorrelatorsPerEventType": 50, // OPTIONAL
173173
"maxQueryEvents": 100, // OPTIONAL

0 commit comments

Comments
 (0)