Skip to content

Commit

Permalink
Merge branch 'master' into search-page
Browse files Browse the repository at this point in the history
# Conflicts:
#	docs/js/custom.js
  • Loading branch information
adriendupuis committed Dec 5, 2024
2 parents 8018bc7 + 69d5727 commit ddea17a
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 4 deletions.
6 changes: 6 additions & 0 deletions docs/js/custom.js
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,12 @@ $(document).ready(function() {
}
});

$('.md-content a:not(.md-icon):not(.md-source):not(.instantsearch__entry)')
.filter(function() {
return this.hostname && this.hostname !== location.hostname;
})
.addClass('external');

const hitsPerPage = 10;
let search = docsearch({
container: '#docsearch',
Expand Down
8 changes: 4 additions & 4 deletions docs/personalization/recommendation_models.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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.
Expand All @@ -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]).

0 comments on commit ddea17a

Please sign in to comment.