Easier way to get from MediaFile or Airing to SeriesInfo?

[evilpenguin]

Right now the only way (I know of) to get from a MediaFile to its associated SeriesInfo is to make a map of all series info then pull out the subgroup based on the GetMediaTitle().

How about GetSeriesInfo(MediaFile|Airing|String)?

Edit: And while i'm making requests, how about a few more along the same lines:

GetMediaFiles(SeriesInfoObject) - Get list of media files that share that SeriesInfo object
GetAllSeriesInfo(bool HasMediaFiles) - Get a list of SeriesInfo objects that have a non-zero count of media files

[Slugger]

I was actually looking at this just a few mins ago and came to the same conclusion. +1 for the new API call.

[Opus4]

Have you tried GetShowSeriesInfo(MediaFile) and GetShowSeriesInfo(Airing)?

- Andy

[evilpenguin]

Yeah, but that only applies to recordings, i'm talking about any MediaFile.

[PLUCKYHD]

Originally Posted by evilpenguin

Yeah, but that only applies to recordings, i'm talking about any MediaFile.

The Map method we use in diamond is best. I don't think they can do what you are asking as I think technically they are only suppose to allow guide data for recorded shows. Just guessing on their user agreement.

[stuckless]

Originally Posted by evilpenguin

Yeah, but that only applies to recordings, i'm talking about any MediaFile.

I guess technically, only recordings (or Airings) will have a SeriesInfo associated with it.

Phoenix does associate SeriesInfo with non recorded tv files as well.. so you could use...

SeriesInfo = SeriesInfoAPI.GetSeriesInfoForID(MediaFileAPI.GetMediaFileMetadata(MediaFile, "SeriesInfoID"));

EDIT: Phoenix also adds a SeriesInfo object for any TV series that does not exist.

[PLUCKYHD]

Originally Posted by stuckless

I guess technically, only recordings (or Airings) will have a SeriesInfo associated with it.

Phoenix does associate SeriesInfo with non recorded tv files as well.. so you could use...

SeriesInfo = SeriesInfoAPI.GetSeriesInfoForID(MediaFileAPI.GetMediaFileMetadata(MediaFile, "SeriesInfoID"));

EDIT: Phoenix also adds a SeriesInfo object for any TV series that does not exist.

Without looking but are you grouping all the series objects and storing the titles as keys to do this? This is how we are doing it in diamond with great success just curious if you were doing it differently.

[stuckless]

Originally Posted by PLUCKYHD

Without looking but are you grouping all the series objects and storing the titles as keys to do this? This is how we are doing it in diamond with great success just curious if you were doing it differently.

I'm just using the sage apis. SeriesInfoID is a core sagetv field that references the ID of the SeriesInfo Object. When Phoenix add a new SeriesInfo object for a non-recording, it will set that field to be SeriesInfoID... so the mediafile is joined by the seriesinfo id. I don't have any maps or stuff... although I do loop through the series info objects to find an existing series info for a non-recording...but once it is found, I just set that field.

[PLUCKYHD]

Originally Posted by stuckless

I'm just using the sage apis. SeriesInfoID is a core sagetv field that references the ID of the SeriesInfo Object. When Phoenix add a new SeriesInfo object for a non-recording, it will set that field to be SeriesInfoID... so the mediafile is joined by the seriesinfo id. I don't have any maps or stuff... although I do loop through the series info objects to find an existing series info for a non-recording...but once it is found, I just set that field.

Ahh I didn't resize you had already implemented that.

[Narflex]

The way the core links to SeriesInfo is through the 'external ID' (i.e. SH/EPXXXXX) and not by title. This is because you can't uniquely identify a SeriesInfo object based on title. Just execute these two statements and you'll see why:

Size(GetAllSeriesInfo()) returns 5331
Size(GroupByMethod(GetAllSeriesInfo(), "GetSeriesTitle")) returns 5132

So you lose 199 of them if you index them by title. Now I'm curious which ones those are....(I love the expression evaluator in Studio). It's possible this is due to me having extra crap in my development system database...but I also tried this on a 'cleaner' system and found similar results. These may be due to errors on Tribune's end since we never actually clean out the SeriesInfo table. (and I did look at which ones it was and it was just a bunch of random ones)

So since we can't actually ensure that SeriesInfo objects are unique by title; don't expect us to add API calls based around that.

But the other 2 proposed by the OP can easily be done with a GroupByMethod() call along with a couple other operations.