Hey there, I'm having some trouble figuring out how to get the crew to appear the same way TMDb displays it. It's easy enough for cast because of the order
key, but there is no similar key for crew.
For example, look at the "Featured crew" here: https://www.themoviedb.org/movie/329865-arrival
But when I query the same crew via the API it returns the entire known crew, so my list is populated with "property master" etc.
How can I replicate the way TMDb returns crew via the API?
찾으시는 영화나 TV 프로그램이 없나요? 로그인 하셔서 직접 만들어주세요.
이 항목을 평가하거나 목록에 추가할까요?
회원이 아닌가요?
Travis Bell님의 댓글
11월 22, 2016 at 6:44 오후
Hi @gmask
That is true, there is no API method for this. All I am doing on the website is grabbing the director and writers (screenplay, story and writer) from the crew members. You can easily filter through the array and grab whatever jobs you think are important like I do.
tmdb74556333님의 댓글
11월 23, 2016 at 11:52 오전
Hi @travisbell
Thanks for getting back to me. So I implemented a filter and just grabbed
['Director', 'Writer', 'Story', 'Screenplay']
jobs, but found it's not really enough because of movies like Inside Out: https://www.themoviedb.org/movie/150540-inside-outWhere the same person may have multiple jobs. Your handling of it is much nicer, whereas mine just returns Pete Doctor three times with different jobs. It occurs to me I could create a new array and just merge on the
credit id
May I ask what language you've written TMDb in, and how you handle this case? I'm writing my app in PHP.One more unrelated note: I've noticed the Now Playing, Upcoming, Popular, and Top Rated methods do not return an
imdb_id
even though they appear to reference the same object as the Get Details method, is there a specific reason it's like this? I'd personally use it.Anyway I just want to say thanks a lot for all the work you've put into this, I love your API, the dev community is lucky to have you.
Travis Bell님의 댓글
11월 23, 2016 at 12:04 오후
Good call. There is a little extra polish I'm putting on there. After I get the job records, I group them by person to join all of their jobs together. Then I just comma separate the list of job names. There's actually one more outstanding ticket I have to do on this which is order them by director first. I totally forgot but I never got to that last task.
TMDb is written in 2 languages, the website is Ruby and the API is about 50/50 Ruby/Lua. Lots of the website features consume the API directly now days though, so it's really both languages. Front end website is still 100% Ruby though.
None of our list methods (search, popular, top rated, etc...) return any external ids. This is by design because I didn't want to get in the game of saying if the IMDB ID is present, why isn't the TVDB ID? And people have social ids now (Twitter, Facebook, Instagram) so one person might find it useful to only have Twitter while others want Facebook. You probably get the idea now, too much data that is unique to each application.
Thanks so much for saying so!