Hey ,

I really love the TV Shows feature, once you get into it, it has a well thought top to bottom hierarchy, there is an obvious changes logic that is to be implemented

Thanks, I tried to make it as clean as I could. TV can be very complicated though! It's not nearly as flat of a model as movie data.

1. What happens when the order of two episodes change? (Do their id's stay the same - or are they both deleted / re-added?)

Their ids stay the same but their episode_number will get updated. This is why it's the episode_id that gets added to the associated change log.

1. How should one know when an episode gets deleted? (Is there a "deleted" update for episodes at the "season changes"?)

Yes, there is a corresponding change in the season change log. Here's a recent example actually:

• Change at the season level
• Change at the series level

1. Same concerns apply for seasons too - both the season and episode data that appears on tv shows / seasons don't have "id"'s listed - which makes things harder

There's an open ticket I have to add the season ids and episode ids. It will make this considerably easier since we track changes by ids.

Does the deletion appear at /tv/season/{id}/changes for example?

Yes, see the 24 example above.

if you have any more specific questions, I am happy to help answer them. The TV change section is fairly new so there could still be a few areas that need massaging (like adding those ids).

Cheers.

Thanks a lot for the quick answer, Indeed the 24 example is a great one

I also agree that tv shows are much more complex than movies (generally speaking - not specific to the moviedb design), but considering each episode is like a movie in most cases, I guess the complexity is justified

It's great to hear that the episode_id's live on

In my opinion the complexity arises from the deleted seasons/episodes / order changes - if both seasons and episodes had their own root changes methods, similar to movies/tvs/persons, the integration could have been simpler

Instead of triggering episode updates from a season for example, the updates would be triggered from /tv/episode/changes - the deletions would be simpler

Things would come together naturally (There would be no need to parse the /tv/id/changes and /tv/season/id/changes - which would simplify things a lot - I don't parse them for movies and persons for example)

However the current state/design of the API obviously handles these scenarios well - again thanks for the API - I often wish other API's similar to themoviedb existed for other stuff