-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sort order prefix field for sites, studios, tags and ratings #10
Comments
Hmm... how would you do this programmatically? Do you mean like prefixing Site with "00:", Studio with "01:", Tags Collections with "02:" sort of thing? Guess I need more of an example |
I don't think it's possible to change a collection's "Sort Title" via Agents in Plex (though hard to say 100% certain because they removed all their public documentation years ago, huge pain...) So I'd recommend doing what Darklyter said, it'd be pretty simple change in your local plugin's |
I think possible via API (from within metadata agent) https://www.plexopedia.com/plex-media-server/api/library/movie-update/#fields but may be possible as metadata agent purely. I could add this to new feature PR I have for formatted titles (ie. providing same functionality to sort titles) |
https://github.com/Darklyter/StashPlexAgent.bundle/pull/21/files#diff-5a1c53b30f3d1fb8b6febec06ae69a8342a215da4ef68c2796ada7d80a5e9597R160 is example of using the PLEXTOKEN already provided to agents with the Plex API to save user ratings |
A specific sort order prefix for sites, studios, tags and ratings would be neat.
Would allow users to have a set order to where these things load in Plex. allowing say having ratings over tags and those over sites and studios.
While users can easily edit this one at a time. but once you get hundreds of them and you are adding more ontop of that. keeping that in order and correct becomes more troublesome, having a set prefix sort option makes sense.
Note this is not the title for the collection but the Sort Title specifically.
The text was updated successfully, but these errors were encountered: