-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
recommendation_models.md: Fix anchor links (#323)
- Loading branch information
1 parent
d86b4b3
commit c6b421f
Showing
1 changed file
with
4 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -224,8 +224,8 @@ They work best in straightforward cases when you filter by the value of the attr | |
|
|
||
| Dynamic attribute submodels: | ||
|
|
||
| - operate only on [nominal attributes](recommendation_models#nominal-attributes) (numeric attributes are not supported) | ||
| - can be used for [popularity](recommendation_models#popularity-models) and [collaborative](recommendation_models#collaborative-models) types of models (as they support submodels) | ||
| - operate only on [nominal attributes](#nominal-attributes) (numeric attributes are not supported) | ||
| - can be used for [popularity](#popularity-models) and [collaborative](#collaborative-models) types of models (as they support submodels) | ||
| - have limitation of max. 50 attribute values (if more, you need to follow the procedure of manual configuration by [[= product_name_base =]] Team) | ||
| - operate on scenarios with the selected `Submodels` data type option | ||
| - require sending a request and building a model | ||
|
|
@@ -248,7 +248,7 @@ Dynamic attribute submodels: | |
| ## Time-slot based models | ||
|
|
||
| Time-slot based models consider only a particular range of time rather than the full day when calculating recommendations. | ||
| They can be used for [popularity](recommendation_models#popularity-models) and [collaborative](recommendation_models#collaborative-models) types of models. | ||
| They can be used for [popularity](#popularity-models) and [collaborative](#collaborative-models) types of models. | ||
|
|
||
| These models can be an optimum answer for customers who notice variable consumption of their content or products throughout the day, with different content being popular, for example, in the morning and afternoon. | ||
| Time-slot based models can cover these needs, as you can request to configure and set specific time slots. | ||
|
|
@@ -267,4 +267,4 @@ To use time slot-based models, this feature must be enabled. | |
| !!! note "Enable time slots" | ||
|
|
||
| Time slots must be enabled and configured by [[= product_name_base =]] Team. | ||
| To start using this functionality and request that a specific model is created, contact customer support ([email protected]). | ||
| To start using this functionality and request that a specific model is created, contact customer support ([email protected]). | ||