You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/RecommApi/Requests/RecommendItemsToItem.php
+52-42
Original file line number
Diff line number
Diff line change
@@ -41,27 +41,15 @@ class RecommendItemsToItem extends Request {
41
41
*/
42
42
protected$count;
43
43
/**
44
-
* @var string $filter Boolean-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to filter recommended items based on the values of their attributes.
45
-
*/
46
-
protected$filter;
47
-
/**
48
-
* @var string $booster Number-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to boost recommendation rate of some items based on the values of their attributes.
44
+
* @var string $scenario Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing".
45
+
* You can set various settings to the [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com). You can also see performance of each scenario in the Admin UI separately, so you can check how well each application performs.
46
+
* The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
49
47
*/
50
-
protected$booster;
48
+
protected$scenario;
51
49
/**
52
50
* @var bool $cascade_create If item of given *itemId* or user of given *targetUserId* doesn't exist in the database, it creates the missing entity/entities and returns some (non-personalized) recommendations. This allows for example rotations in the following recommendations for the user of given *targetUserId*, as the user will be already known to the system.
53
51
*/
54
52
protected$cascade_create;
55
-
/**
56
-
* @var string $scenario Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing". You can see each scenario in the UI separately, so you can check how well each application performs. The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
57
-
*/
58
-
protected$scenario;
59
-
/**
60
-
* @var string| $logic Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain (e-commerce, multimedia, fashion ...) and use case.
61
-
* See [this section](https://docs.recombee.com/recommendation_logic.html) for list of available logics and other details.
62
-
* The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
63
-
*/
64
-
protected$logic;
65
53
/**
66
54
* @var bool $return_properties With `returnProperties=true`, property values of the recommended items are returned along with their IDs in a JSON dictionary. The acquired property values can be used for easy displaying of the recommended items to the user.
67
55
* Example response:
@@ -120,6 +108,23 @@ class RecommendItemsToItem extends Request {
120
108
* ```
121
109
*/
122
110
protected$included_properties;
111
+
/**
112
+
* @var string $filter Boolean-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to filter recommended items based on the values of their attributes.
113
+
* Filters can be also assigned to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
114
+
*/
115
+
protected$filter;
116
+
/**
117
+
* @var string $booster Number-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to boost recommendation rate of some items based on the values of their attributes.
118
+
* Boosters can be also assigned to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
119
+
*/
120
+
protected$booster;
121
+
/**
122
+
* @var string| $logic Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain and use case.
123
+
* See [this section](https://docs.recombee.com/recommendation_logics.html) for list of available logics and other details.
124
+
* The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
125
+
* Logic can be also set to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
126
+
*/
127
+
protected$logic;
123
128
/**
124
129
* @var float $user_impact **Expert option** If *targetUserId* parameter is present, the recommendations are biased towards the given user. Using *userImpact*, you may control this bias. For an extreme case of `userImpact=0.0`, the interactions made by the user are not taken into account at all (with the exception of history-based blacklisting), for `userImpact=1.0`, you'll get user-based recommendation. The default value is `0`.
125
130
*/
@@ -172,23 +177,14 @@ class RecommendItemsToItem extends Request {
172
177
* @param int $count Number of items to be recommended (N for the top-N recommendation).
173
178
* @param array $optional Optional parameters given as an array containing pairs name of the parameter => value
174
179
* - Allowed parameters:
175
-
* - *filter*
176
-
* - Type: string
177
-
* - Description: Boolean-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to filter recommended items based on the values of their attributes.
178
-
* - *booster*
180
+
* - *scenario*
179
181
* - Type: string
180
-
* - Description: Number-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to boost recommendation rate of some items based on the values of their attributes.
182
+
* - Description: Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing".
183
+
* You can set various settings to the [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com). You can also see performance of each scenario in the Admin UI separately, so you can check how well each application performs.
184
+
* The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
181
185
* - *cascadeCreate*
182
186
* - Type: bool
183
187
* - Description: If item of given *itemId* or user of given *targetUserId* doesn't exist in the database, it creates the missing entity/entities and returns some (non-personalized) recommendations. This allows for example rotations in the following recommendations for the user of given *targetUserId*, as the user will be already known to the system.
184
-
* - *scenario*
185
-
* - Type: string
186
-
* - Description: Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing". You can see each scenario in the UI separately, so you can check how well each application performs. The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
187
-
* - *logic*
188
-
* - Type: string|
189
-
* - Description: Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain (e-commerce, multimedia, fashion ...) and use case.
190
-
* See [this section](https://docs.recombee.com/recommendation_logic.html) for list of available logics and other details.
191
-
* The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
192
188
* - *returnProperties*
193
189
* - Type: bool
194
190
* - Description: With `returnProperties=true`, property values of the recommended items are returned along with their IDs in a JSON dictionary. The acquired property values can be used for easy displaying of the recommended items to the user.
@@ -245,6 +241,20 @@ class RecommendItemsToItem extends Request {
245
241
* ]
246
242
* }
247
243
* ```
244
+
* - *filter*
245
+
* - Type: string
246
+
* - Description: Boolean-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to filter recommended items based on the values of their attributes.
247
+
* Filters can be also assigned to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
248
+
* - *booster*
249
+
* - Type: string
250
+
* - Description: Number-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to boost recommendation rate of some items based on the values of their attributes.
251
+
* Boosters can be also assigned to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
252
+
* - *logic*
253
+
* - Type: string|
254
+
* - Description: Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain and use case.
255
+
* See [this section](https://docs.recombee.com/recommendation_logics.html) for list of available logics and other details.
256
+
* The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
257
+
* Logic can be also set to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
248
258
* - *userImpact*
249
259
* - Type: float
250
260
* - Description: **Expert option** If *targetUserId* parameter is present, the recommendations are biased towards the given user. Using *userImpact*, you may control this bias. For an extreme case of `userImpact=0.0`, the interactions made by the user are not taken into account at all (with the exception of history-based blacklisting), for `userImpact=1.0`, you'll get user-based recommendation. The default value is `0`.
@@ -272,13 +282,13 @@ public function __construct($item_id, $target_user_id, $count, $optional = array
0 commit comments