Re: tv_grab_sd_json: Total number of episodes missing for many TV series
Kevin Groeneveld <[email protected]>
| Newsgroups | gmane.comp.tv.xmltv.devel |
|---|---|
| Message-ID | <CABF+-6XGjz=q06yYo3VfNEOkVPgiiKMs-BXVhA+NB4gcxmNgGA@mail.gmail.com> |
On Sun, Jun 5, 2016 at 12:19 PM, Robert Kulagowski <[email protected]> wrote: > If you want to know the total number of episodes for an EP, then you > need to pull the SH record. You can programatically determine the SH > record programID based on the above pattern and description. > This is the first I have heard that you can programmatically generate an SH ID from an EP ID to get further show information. Is that in the JSON API documentation anywhere? Maybe I just missed it. I thought the SH IDs were only used when exact episode information was not known and if there was an EP record it would have all the information. Although for the specific example of this thread I am still not sure this would fully solve the problem. For totalEpisodes the docs state: 'in an "EP" program this indicates the total number of episodes in this season' and 'In an "SH" program, it will indicate the total number of episodes in the series.' It is my understanding that the xmltv_ns format is supposed to be "total number of episodes this season" as from the EP record and does not include "total number of episodes in the series" as from the SH record. In the EP023565850003 example there was no totalEpisodes field to include in the xmltv_ns data. For totalSeasons the docs state: 'totalSeasons: integer indicating the total number of seasons in the series. *SH* programs only.' Why not include this in the EP record as well? If we really need to pull the SH record in addition to the EP record how should the grabber know to update the SH record? Does the md5 in the programs array change if either the EP record or SH record changes? Kevin ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ xmltv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xmltv-devel