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

[Feature] Allow to include _some_ of the historic contents #10

Open
erhant opened this issue Dec 1, 2023 · 0 comments
Open

[Feature] Allow to include _some_ of the historic contents #10

erhant opened this issue Dec 1, 2023 · 0 comments

Comments

@erhant
Copy link
Member

erhant commented Dec 1, 2023

Our SDK is capable of storing content ids in a history, and make sure if a content exists in history it is not returned, and a new one is given instead. This makes sense for a number of use-cases, but a relaxed version of this should also be possible.

In my case, the user is solving a set of questions; say A B C D. The following happens:

  • She solves A, and does not want to see this question again in a batch. The SDK moves away from questions like A as well.
  • She solves B but signals that she would like to see it again in a future batch. The SDK stays around similar questions for personalization.
  • She cant solve C and definitely wants to try more related questions.
  • She didn't attempt D at all, so it should be returned again in a future batch.

The described scenario is similar to flash-card training programs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant