Page 1 of 1

Taxonomy of programid uniquness

PostPosted: Sun Jan 01, 2017 9:01 pm
by gtb
Apologies if this is answered elsewhere (I could not find anything definitive), but are the middle eight characters of the programid (after the EP/SH/SP/MV) unique for unique series. That is, if there is an programid of the form EP00000001xxxx, which there ever be a MV000000010000, or SP000000010000 or SH000000010000 which is not directly related to the EPisode? Asked another way, are those substr(programid, 2, 8) values reused for other categories (for SHows and EPisodes they clearly are because those are related, but what about SPorts and MoVies)?

If those values are not unique, can the resourceid be used this way (and what is the definition of the resourceid)?

Re: Taxonomy of programid uniquness

PostPosted: Mon Jan 02, 2017 1:30 pm
by rmeden
They are unique for SHows (aka series) and EPisodes.

EP00000001xxxx is episode xxxx of SHow/series 00000001
SH000000010000 is an unknown episode of Show/series 00000001 (Gracenote doesn't know what episode)

SP000000010000 is bring/or has been discontinued. (not sure about the namespace)

MV000000010000 I think is a different namespace. I can check if you really need to know.

Re: Taxonomy of programid uniquness

PostPosted: Tue Jan 03, 2017 11:17 am
by gtb
rmeden wrote:They are unique for SHows (aka series) and EPisodes.
....
MV000000010000 I think is a different namespace. I can check if you really need to know.


Thanks. Yes, it seems to be, but it turns out that it probably does not matter (maybe) for my purposes, so do not bother checking.

Thinking of this slightly differently (I have not decided how one can convert from here to there, but lets leave that for a moment)....

I note that in the Gracenote API there is a field called seriesid. For scheduling purposes one sometimes wants a "this series" match, and having that value might be useful. Is it viable to make that available in the Schedules Direct JSON API?

I am not yet sure I can actually easily use that value (the issue, again, is how one gets from a different "made up" seriesid to this one), but if it exists, it would seem to be the right choice moving forward.

But before I spend time trying to figure that part out, the question would be is the data element available to Schedules Direct, and could it be made available via the JSON services?



[EDITED]: Or is the "resourceID" the seriesid? In which case I already have my answer (I guess).



Thanks for thinking about this (and enjoy CES).

Re: Taxonomy of programid uniquness

PostPosted: Thu Jan 05, 2017 6:57 am
by rmeden
rmeden wrote:EP00000001xxxx is episode xxxx of SHow/series 00000001
SH000000010000 is an unknown episode of Show/series 00000001 (Gracenote doesn't know what episode)

I'm pretty sure in the above examples 00000001 is also the series ID.

Re: Taxonomy of programid uniquness

PostPosted: Thu Jan 05, 2017 10:57 am
by gtb
rmeden wrote:
rmeden wrote:EP00000001xxxx is episode xxxx of SHow/series 00000001
SH000000010000 is an unknown episode of Show/series 00000001 (Gracenote doesn't know what episode)

I'm pretty sure in the above examples 00000001 is also the series ID.

Not according to the Gracenote site, which has an an example response (where, in this case, the rootid and the seriesid is the same (is that always the case?), but in any event, has no obvious translation from the SH<digit> values).

{
"tmsId":"SH006883590000",
"rootId":"185044",
"seriesId":"185044",
"subType":"Series",
"title":"House",
"origAirDate":"2004-11-16",
"titleLang":"en",
"descriptionLang":"en",
"entityType":"Show",
"genres":["Drama", "Mystery", "Medical"],

....

Re: Taxonomy of programid uniquness

PostPosted: Fri Jan 06, 2017 4:55 pm
by rmeden
interesting.. good to know... I haven't looked at the SD-JSON data much.. I'm a SD-DD kinda guy :)

Re: Taxonomy of programid uniquness

PostPosted: Tue Feb 21, 2017 3:28 pm
by rkulagow
The resourceID that's in the Schedules Direct JSON output is the same field as "seriesId" in the raw JSON from Gracenote.

So all episodes of "The X-Files" will have the same resourceID - "183870", even if they're broadcast in another language.