Repository navigation
Replies: 5 comments 2 replies
|
Some other discussions about more rating sources: |
|
Thanks — I had read #1020 and #916 before opening this, and I should have said up front how Your answer in #804 set the bar: "this sort of functionality probably is better suited for a What the server already has. The plugin writes one admin-selected source into the Sources seen in live responses: Three things worth knowing before writing any of it, from poking at real responses:
This has already been done once, from the same plugin. Moonfin's companion plugin does Where your own plugin could come in, later. Which sources to show and in what order is a One side effect of the plugin that affects Wholphin whether or not any of this is implemented: If it helps, I am happy to put together the client-side part: a small API interface, a |
|
@damontecres — checking back in since it's been a couple of weeks — no rush if this is still in the |
|
I'm going to have a go at a PR for this: an opt-in ratings row that reads from the MDBList plugin endpoint and does nothing if the plugin isn't installed. Happy to adjust to whatever approach you prefer. |
|
This it would be an amazing edition if it was possible. This is really the only thing that's missing in that beautiful movie page |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Right now a detail page can show two numbers:
CommunityRatingas a star andCriticRatingas fresh/rotten (
listToDotStringinFormatting.kt). That is everything Jellyfin'sBaseItemDtocarries — there is no third or fourth rating field in the schema, so this is aceiling of the server API rather than a gap in the app.
Plex shows four, each with its own icon: IMDb, RT critics, RT audience (popcorn), TMDB. It has
rolled out across their clients — screenshots attached from both the Android app on an NVIDIA
SHIELD and the web client. Since the README says Wholphin "aims to provide a different app UI
that's inspired by Plex for users interested in migrating to Jellyfin", this row is one of the
more visible things a migrating user notices missing on the very first screen they open.
Plex on an NVIDIA SHIELD:
The same row in the Plex web client:
Since the schema has no room for it, anything that fills that row has to come from outside
Jellyfin's own fields. There are several ways that could go, and I have no stake in which one
you'd pick — a server-side plugin that already holds the data, something the client fetches
itself, or a source you have in mind that I don't know about. What I can describe concretely is
the one I happen to run, the
MDBList Ratings plugin, so the
rest of this is written around it. If you'd rather build on something else, the shape of the
data below is probably still worth a look.
The plugin fetches every rating MDBList has, writes one of them into Jellyfin's built-in
fields, and keeps the rest in its own cache — which it exposes over plain REST:
Live response from my own server for the same film as in the screenshots — The Man from U.N.C.L.E.,
Jellyfin 10.11.11, plugin 1.0.0.7, trimmed to the sources that carry data:
{ "hasCache": true, "cachedAtUtc": "2026-08-18T14:12:20Z", "ids": { "tmdb": 203801, "imdb": "tt1638355" }, "ratings": [ { "source": "imdb", "value": 7.2, "score": 72, "votes": 359161 }, { "source": "metacritic", "value": 56, "score": 56, "votes": 40, "url": "/the-man-from-uncle" }, { "source": "trakt", "value": 74, "score": 74, "votes": 16284 }, { "source": "tomatoes", "value": 68, "score": 68, "votes": 294, "url": "/m/the_man_from_uncle" }, { "source": "popcorn", "value": 73, "score": 73, "votes": 2699, "url": "/m/the_man_from_uncle" }, { "source": "tmdb", "value": 70, "score": 70, "votes": 6969 }, { "source": "letterboxd", "value": 3.5, "score": 70, "votes": 354165, "url": "/film/the-man-from-uncle/" } ] }The four numbers Plex shows for this film are
imdb,tomatoes,popcornandtmdbin thatpayload — 7.2, 68% and 73% match exactly; TMDB reads 70 here against Plex's 71, the two having
been fetched at different times. One HTTP call away from the client, either way.
Three things the live response taught me that the plugin's source doesn't spell out:
valueis in each provider's own scale: IMDb 7.2/10, Trakt 74/100, TMDB 70/100,Letterboxd 3.5/5. Only
score(normalised 0-100) is comparable across sources, so arenderer wants
scoreto decide fresh/rotten style thresholds andvalueto display.urlis not a URL. IMDb's came back as"1104", the rest are bare paths. Whatever itis, it isn't something to link to without per-source handling.
source, or with avalueand noscore(rogerebertdid the latter here). Both have to be filtered out.Full list of source names the plugin can return:
imdb,tmdb,trakt,tomatoes,popcorn,metacritic,metacriticuser,letterboxd,rogerebert,myanimelist,anilist.votesisthere too, though Plex doesn't show vote counts and I'd leave them out unless you want them.
Icons. The plugin serves them itself:
GET /Plugins/MdbListRatings/Assets/{fileName}(
IMDb.png,Rotten_Tomatoes.png,Rotten_Tomatoes_rotten.png,Rotten_Tomatoes_positive_audience.png,TMDB.png,Metacritic.png,Trakt.png, ...). SoWholphin would not have to bundle third-party logos at all — it can load them through the
existing image loader from the server the user already trusts and authenticates against.
Scope I'd suggest, to keep this cheap:
is obviously not acceptable there.
hasCache: falseor a 404, and the page rendersexactly what it renders today. Nothing to configure for people who don't use this, and no new
build dependency — it's just another HTTP call against the same server, in the same shape as
the existing Seerr integration.
Sketch of the client side, roughly following
SeerrService:I deliberately haven't written a UI diff for this one — where the row goes and how it should
look is your call, and guessing at it would just be work thrown away if you'd rather not depend
on a third-party plugin at all. Happy to put one together if the direction is acceptable.
To be plain about where I stand as a user: I want this row. Coming from Plex, its absence is
the thing I notice every time I open a film, and I don't think I'm alone in that — it's the
kind of small, constantly-visible difference that decides whether a migration feels like an
upgrade or a compromise. Which source it comes from I genuinely don't mind.
So the open question is only the how:
the data came from somewhere else entirely?
so another source could be wired in later without touching the UI?
All reactions