Trakt collection scraping and automatic removal from watchlist after scraping

[deepvalu]

Low priority request for after you implement trakt scraping, but my current workflow for plex_debrid is plex or trakt watchlist -> removed from watchlist by plex_debrid -> added to my trakt collection by plextraktsync -> trakt collection monitored by plex_debrid for new episodes. It would be nice to recreate this experience in iceberg.

[dreulavelle]

This should be split up into 3 feature requests I think.

• Scraping with Trakt is already on the list though, so you dont need to do that one.
• Do people want to be able to delete items on their lists that were scraped/downloaded? @Gaisberg, We need to make this a toggleable feature at some point. Low priority for now though?
• Plex Watchlist will be getting redone and I'll see about adding that as a setting users can set if they want to delete the scraped items after they've been downloaded..
• Could be a feature request as well to send to a Trakt list/library/collection... need more information about this. Perhaps you should create a new issue and detail out as much as you can what you would like to see for that. If PlexTraktSync already does a good job, then we may not.. need more thoughts/opinions/ideas for this one.
• Being able to select a collection in our frontend would also be kept in mind as a viable option.

Thanks for the ideas @deepvalu ! Much appreciated!

[deepvalu]

1 - Yes you can use the other request - just want to make sure you also cover trakt collections in addition to lists
2 - I think this would be a good feature for people who use there watchlists to add new content, but want to keep the list from getting too large. This follows how trakt views watchlists as well. For example after fully watching a show in trakt it is removed from the users watchlist and kept in the users collection
3 - Plextraktsync works perfect for adding plex content to your trakt collection as well as scrobbling so no need to add anything there.

[dreulavelle]

I'll be working on this today and over the next couple days.

Currently I'm thinking to implement:

1. Fetch Lists
2. Fetch Collections
3. Remove items from Watchlist that were downloaded. (tougher, may take some time)

[layezee20]

I'll be working on this today and over the next couple days.

Currently I'm thinking to implement:

1. Fetch Lists
2. Fetch Collections
3. Remove items from Watchlist that were downloaded. (tougher, may take some time)

Number 3 would be massive I'd deffo like to see this feature.

[dreulavelle]

Okay, just a quick update on this.

We support fetching content from Trakt now. Now we just need to handle deleting from the lists once it's completed.

Is that something that can be done without a Trakt OAuth authentication?

[anonymous-user000]

Just wondering, will this feature include automatic removal from Plex watchlist after scraping?
Or is it solely focused on Trakt collection only?

I had very similar workflow as @deepvalu when I was using plex_debrid, but without the Trakt part. My workflow was like this:
add item to plex watchlist -> plex_debrid searchers for the watchlist item -> removed from plex watchlist after adding scrapped torrent to debrid.
Would be keen to have this feature included too.

Very much the .gif demo shown on plex_debrid Github