-
Notifications
You must be signed in to change notification settings - Fork 2
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
[REQ] thetvdb_season
field
#5
Comments
The more I look into this, the more problems I find with it. First, sure, we could add this to the mapping-list but not as a
However, as I said above, the more I look into this, the more problems or inconsistencies I find that the generator would need to fix or address that could even be a problem for your "fetching episode information". The first one is that
The Problem here is that AniDB has only one Entry (id=19) with 24 episodes, but TheTVDB has one show with 2 seasons with 12 episodes each. This would mean that while we could use the But there is more, because the The Show Crest of the Stars has 3 Seasons with a Specials Season. There are 7 entries in the anime-lists XML file that have
But then you also have:
The episodes are part of the Specials season, from top to bottom:
This means that while the To make this more robust, we would also need to add the episode information to this which opens another can of worms. So, to wrap this up: Yes, we could add the I mean, if those information are required, a consumer could get the anime-lists JSON, search for the entry of the ID that it has, get the anime-lists XML and search for the corresponding anidb ID and you already have all of the information available to you that you then can process. |
I'd forgotten about the The use I first had in mind was pairing it with Flexget to assign the proper season so it can fetch the metadata and save to media-center compatible paths |
I don't know about that. While I add Data to the entries (by searching for IMDB/TMDB IDs etc) I wouldn't want to make much data manipulation to the original sources. When we have the Because of that inconsistency, I would rather not provide that information in the first place. From a consumer point of view, I would think that it should be easy to understand without having to keep caveats in mind. I mean, most won't read the documentation anyway so the JSON should be fairly self-explanatory. But when we say that we add a "season" element and add "thetvdb" with one of those edge cases, then this could be easily overlooked by the sheer number and size of the list. So someone would, for example, see season 0 and deduce from that it is the Specials season without realizing directly that this is, in fact, not the whole season but rather only one episode of it. This then would raise the question (and probably feature request) of adding the episode mapping, which I really want to avoid. My plan would be the following:
|
Seems like a good compromise to me 👍
|
Seeing as it is available on Anime-Lists as
defaulttvdbseason
, it would be nice to have this field available to fetch episode information for example.The text was updated successfully, but these errors were encountered: