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
+25-11Lines changed: 25 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -40,10 +40,6 @@ class RecommendItemsToItem extends Request {
40
40
* @var int $count Number of items to be recommended (N for the top-N recommendation).
41
41
*/
42
42
protected$count;
43
-
/**
44
-
* @var float $user_impact If *targetUserId* parameter is present, the recommendations are biased towards the user given. 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`.
45
-
*/
46
-
protected$user_impact;
47
43
/**
48
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.
49
45
*/
@@ -60,6 +56,12 @@ class RecommendItemsToItem extends Request {
60
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.
61
57
*/
62
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;
63
65
/**
64
66
* @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.
65
67
* Example response:
@@ -118,6 +120,10 @@ class RecommendItemsToItem extends Request {
118
120
* ```
119
121
*/
120
122
protected$included_properties;
123
+
/**
124
+
* @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
+
*/
126
+
protected$user_impact;
121
127
/**
122
128
* @var float $diversity **Expert option** Real number from [0.0, 1.0] which determines how much mutually dissimilar should the recommended items be. The default value is 0.0, i.e., no diversification. Value 1.0 means maximal diversification.
123
129
*/
@@ -166,9 +172,6 @@ class RecommendItemsToItem extends Request {
166
172
* @param int $count Number of items to be recommended (N for the top-N recommendation).
167
173
* @param array $optional Optional parameters given as an array containing pairs name of the parameter => value
168
174
* - Allowed parameters:
169
-
* - *userImpact*
170
-
* - Type: float
171
-
* - Description: If *targetUserId* parameter is present, the recommendations are biased towards the user given. 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`.
172
175
* - *filter*
173
176
* - Type: string
174
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.
@@ -181,6 +184,11 @@ class RecommendItemsToItem extends Request {
181
184
* - *scenario*
182
185
* - Type: string
183
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.
184
192
* - *returnProperties*
185
193
* - Type: bool
186
194
* - 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.
@@ -237,6 +245,9 @@ class RecommendItemsToItem extends Request {
237
245
* ]
238
246
* }
239
247
* ```
248
+
* - *userImpact*
249
+
* - Type: float
250
+
* - 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`.
240
251
* - *diversity*
241
252
* - Type: float
242
253
* - Description: **Expert option** Real number from [0.0, 1.0] which determines how much mutually dissimilar should the recommended items be. The default value is 0.0, i.e., no diversification. Value 1.0 means maximal diversification.
@@ -261,13 +272,14 @@ public function __construct($item_id, $target_user_id, $count, $optional = array
Copy file name to clipboardExpand all lines: src/RecommApi/Requests/RecommendItemsToUser.php
+15-1Lines changed: 15 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,12 @@ class RecommendItemsToUser extends Request {
40
40
* @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.
41
41
*/
42
42
protected$scenario;
43
+
/**
44
+
* @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.
45
+
* See [this section](https://docs.recombee.com/recommendation_logic.html) for list of available logics and other details.
46
+
* The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
47
+
*/
48
+
protected$logic;
43
49
/**
44
50
* @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.
45
51
* Example response:
@@ -145,6 +151,11 @@ class RecommendItemsToUser extends Request {
145
151
* - *scenario*
146
152
* - Type: string
147
153
* - 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.
154
+
* - *logic*
155
+
* - Type: string|
156
+
* - Description: Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain (e-commerce, multimedia, fashion ...) and use case.
157
+
* See [this section](https://docs.recombee.com/recommendation_logic.html) for list of available logics and other details.
158
+
* The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
148
159
* - *returnProperties*
149
160
* - Type: bool
150
161
* - 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.
@@ -228,6 +239,7 @@ public function __construct($user_id, $count, $optional = array()) {
0 commit comments