Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IBX-8918: Time-slot based models described in User Documentation #316

Merged
merged 8 commits into from
Oct 22, 2024
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 23 additions & 1 deletion docs/personalization/recommendation_models.md
Original file line number Diff line number Diff line change
Expand Up @@ -244,4 +244,26 @@ The logic used for resolving a submodel is as follows:
for requesting recommendations.
Recommendation are fetched from all the submodels and merged based on the weight (relevance).
If one of the submodels delivers recommendations with better relevance,
the results of other models can disappear from the list.
the results of other models can disappear from the list.
julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved

julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
### Time-slot based models

julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
Time-slot based models consider only a particular range of time rather than the full day, while creating recommendations.
julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
They can be used for [popularity](recommendation_models#popularity-models) and [collaborative](recommendation_models#collaborative-models) types of models.
julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
With time-slot based models, user can configure and set specific time slots.

These time slots:

julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
- can cover any time frame, including minutes, and don't necessarily have to start and end with full hour
julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
- cannot overlap, for example, you cannot set up 8 a.m - 11 a.m and 9 a.m - 12 a.m slots at once
julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
- cannot pass between two days, for example, you cannot set slot 11 p.m - 3 a.m

julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
In these models, recommendations are created for both configured time slots and for the main model (for example, for the last 30 days).
julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
However, time-slot based recommendations are shown as priority in the hours for which time slots are configured (if requested in recommendation call).

julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
To use time slot-based models, this feature must be enabled.

!!! note "Enable time slots"

julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
Time slots must be enabled by the administrators.
julitafalcondusza marked this conversation as resolved.
Show resolved Hide resolved
To start using this functionality, first contact the Support Team.
Loading