User ratio request / Watch tracking

[stanyslassz]

Description

Is your feature request related to a problem?

Additional Context: Request Blocking Based on Watch Ratio

The main goal of this feature is to provide admins the ability to block users from making new requests if they haven’t watched enough of their previously requested content or if their watch-to-request ratio has dropped below a defined threshold.

It is related to understanding and managing user behavior in relation to their content requests. As an admin, it is difficult to gauge the consumption habits of users based solely on the requests they make. For example, some users might request a large number of movies or shows, but do not watch most of them, leading to a backlog of requested content that isn’t consumed.

This creates inefficiencies, especially when prioritizing or approving new requests. A clearer understanding of how many requests are actually watched would help better allocate resources, especially in shared Plex environments with limited storage or bandwidth.

Desired Behavior

I would like a feature that tracks a user’s request-to-watch ratio. The ratio would show how many pieces of content (movies or TV shows) a user has requested versus how many of those they’ve actually watched.

The ratio can be displayed as a numerical value (e.g., 0.75 meaning 75% of requested content has been watched) or as a percentage or progress bar in the user’s profile.

The ideal implementation would:

• Track the number of requested items (which Overseerr already does).
• Track the number of requested items that the user has actually watched, utilizing Plex API data to retrieve watch status.
• Show this ratio as part of the user profile interface or on the admin dashboard.

Example ratio formula:
Watch Ratio = (Total Watched Content / Total Requested Content)

Additional Context

Additional Context: Request Blocking Based on Watch Ratio

The main goal of this feature is to provide admins the ability to block users from making new requests if they haven’t watched enough of their previously requested content or if their watch-to-request ratio has dropped below a defined threshold.

Key Details:

• Blocking New Requests: If a user’s watch-to-request ratio is below a configurable threshold (e.g., 0.5 or 50%), they would be temporarily blocked from making new requests. This ensures users are engaging with the content they’ve already requested before asking for more.
• Threshold Configuration: Admins should be able to define the ratio limit and set how strict the request-blocking mechanism is. For example, if a user has a ratio of 0.4, the system could prevent them from submitting further requests until they raise the ratio by watching more content.
• Admin Override: Admins should also have the option to manually override this block for individual users when needed, allowing flexibility for special cases.

This functionality will promote fairer use of resources, ensuring that users watch content they’ve requested and reduce unnecessary backlog in the system.

Code of Conduct

• I agree to follow Overseerr's Code of Conduct