[Feature Request] - Update TMDb collection tags but keep custom collection tags

General Discussions
1

For example, lets say I add Dr. Strange to a collection for Marvel Comics movies. This “Marvel” collection tag would be a custom one that I would have to manually add to every movie in it. Since Dr. Strange does not currently have a collection of TMDb, the “Marvel” collection tag is the only one it would have on my server. But maybe in a couple years they will decide to make another movie called Dr. Strange 2. TMDb now has a collection for Dr. Strange because there are 2 movies. After adding the second movie to my collection, my Plex server would add the “Dr. Strange” collection tag automatically. But the first one would not be automatically added to that collection because I have used a custom “Marvel” collection tag and the tag field would be locked. So this means I would have to go back and unlock the tag field and refresh the metadata. Then I would have to add the custom tag again since it would have been overwritten during the refresh due to the field being unlocked. While this task isn’t that long, it would be a lot of work to maintain all the tags for a large movie server with several custom collections.

If there were a collection tag field reserved for TMDb or for whichever agents you’re using, I think this problem could be eliminated. So you would end up having agent collection tags and custom collection tags.

1 Like
2

Yes: +1 for this. How do I upvote?

Believe it or not, I was going to post this exact “Dr. Strange” example.

First, when refreshing collections metadata via TMDb, it could/should be a preference to only “add” collections, and never “remove” them [or as the OP suggested, differentiate between TMDb collection tags and custom tags]

Second, when adding items to collections it shouldn’t default to “lock automatically”. While it makes sense to “Lock” some fields on edit, I do not think it makes sense for the collections field. I’ve been automatically adding items to collections via the API but even when changes are made through the API it automatically locks the collections field… So unless this behaviour is also changed, it will still be a pain even if the first issue is addressed.