[Feature] A job to recommend items to delete

[f3lixding]

We would eventually run out of space. We need a job to do the following: p

• Query for items whose last accessed date is past certain threshold.
• Present a list of items that fulfills said requirement.
• Checks regularly if anything on this item has been marked for deletion.
• Delete these marked items.

Some resources:

• This is the api you would need to use to query this information: https://plexapi.dev/docs/plex/get-session-history
• You would also need a api token, follow this guide here to retrieve it: https://support.plex.tv/articles/201998867-investigate-media-information-and-formats/

[f3lixding]

There are two categories of items: items that had been watched, items that not been watched.

For items that had been watched, we would mark it for deletion if the following are true:

• If the item has not been exempt permanently or temporarily
• If the item's last watched date is over the specified threshold 1

For items that had not been watched, we would mark it for deletion if the following are true:

• If the item has not been exempt permanently or temporarily
• If them item's last watched date is over the specified threshold 2

Threshold 2 is to be greater than threshold 1.

[f3lixding]

Also on the deletion front, it is complicated by the fact that we would need to do this for three possible locations:

• sonarr for shows (assuming we do not want to keep tracking said show)
• radarr for movies (assuming we do not want to keep tracking said movie)
• the actual location of where the file is saved (local ssd or external hard drive)

It's quite cumbersome to do the deletion at each spot. The following alternatives might be better.

For manual deletions:

• we can start from their rightful control plane (which would be the indexer managers).
• periodically, we take a snapshot of the library from the indexer managers (this can be in sqlite or some other database).
• at the time of delete, we can retrieve the current state and compare it with the last known snapshot, and delete the items that are present in the snapshot but not in the current state.

For auto deletions:

• the delete routine would already know what to delete so there is no need to consult the snapshot here.
• send an api call to the indexer managers to delete it from there first
• and then (if the file in the target directory is a symlink) follow the symlink to delete it from its real destination (the external drive).