tensorflow / tensorflow/recommenders

Define model with explicit positive feedback and explicit negative feedback

Open
#428 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2k
Forks
300
PR merge metrics
No merged PRs in 30d

Description

Hey, I am working on a problem where I have 4 different feedback signals. I am trying to recommend new videos in a playlist to a user.

My dataset is such that I have pre-defined playlists categories with each category having predefined possible videos. Now the problem is to recommend new video to a user. A user can watch a video, like a video after watching it, skip the video in the middle and abandon/leave the playlist and move on to a new playlist.

My goal is to recommend those videos that are liked by user or watched by user and avoid those videos that are skipped by user or after which user left the playlist. So I have four feedback signals available at hand

  1. Implicit positive feedback given by watched videos
  2. Explicit positive feedback given at the end of video
  3. Explicit negative feedback given by skipping of video
  4. Explicit negative feedback given by abandonment of playlist

Now how I should go about structuring the model?

Following #139, it's clear that I can define two retrieval task, First one for Implicit positive feedback and the second one for explicitly positive feedback.

But how should I use explicit negative feedback? I looked into #232 but that didn't provide an answer.
I was thinking of doing

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the retrieval-task discussion in #139 and the negative-feedback discussion in #232; the issue provides no file, test, or code entry point. Compare how watched, liked, skipped, and abandoned events should be represented, and define a model approach that distinguishes all four signals. Done means the design is settled and actionable for implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, tensorflow
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.