[mythtv] [mythtv-commits] Ticket #8535: Add ability to filter recording schedules by season

Jason Musits jmusits.mythtv at gmail.com
Mon Jun 7 19:52:22 UTC 2010


On Mon, Jun 7, 2010 at 9:28 AM, MythTV <mythtv at cvs.mythtv.org> wrote:

> #8535: Add ability to filter recording schedules by season
>
> ----------------------------------------------+-----------------------------
>  Reporter:  Jason Musits <jmusits@…>          |        Owner:  gigem
>      Type:  patch                             |       Status:  closed
>  Priority:  minor                             |    Milestone:  unknown
> Component:  MythTV - Scheduling               |      Version:  Unspecified
>  Severity:  medium                            |   Resolution:  invalid
>   Mlocked:  0                                 |
>
> ----------------------------------------------+-----------------------------
> Changes (by mdean):
>
>   * status:  new => closed
>  * resolution:  => invalid
>
>
> Comment:
>
>  program.syndicatedepisodenumber does not contain any usable information
>  for filtering by season (see below).  The syndicatedepisodenumber is a
>  string whose format is decided by the producers of a show--there is no
>  standard for its construction.  Therefore, parsing the
>  syndicatedepisodenumber to determine season or episode information is
>  unreliable, at best.  And, the syndicatedepisodenumber may not be provided
>  for a large percentage of users.  The only users for which the
>  syndicatedepisodenumber is generally usable are those XMLTV users whose
>  listings providers specify an "xmltv_ns" episode-num (versus the
>  "onscreen" episode-num values, which is what syndicatedepisodenumber is
>  designed to hold--see the documentation for episode-num at
>  http://xmltv.cvs.sourceforge.net/*checkout*/xmltv/xmltv/xmltv.dtd ).
>
>  Anyone wanting to be able to use ordinal season and episode information
>  should not attempt to parse such information from any existing fields
>  (syndicatedepisodenumber, programid, ...), but should instead add columns
>  to the database for season and episode numbers and modify XMLTV, EIT, and
>  DataDirect (Schedules Direct) grabbers to properly (directly) pull such
>  information from listings, when present, and save it directly to the
>  database.
>
>  Furthermore, we're actually in the process of removing extra information
>  from ProgramInfo, not adding new information.  Also, when adding
>  additional information to ProgramInfo, it should be added to the end, not
>  inserted randomly into the middle--where inserting into the middle
>  requires a significant amount of changes so that all users agree on the
>  meaning of each field.
>
>  Below is a random sampling of syndicatedepisodenumber values, just to show
>  they're not parsable.
>  {{{
>  5139
>  S115
>  FF08120
>  102405
>  040
>  16246W
>  710A/711A
>  HD010605
>  LIKI104
>  92/466618
>  CAB103
>  091209
>  }}}
>
>  If you choose to use syndicatedepisodenumber in your recording rules,
>  anyway, you should do so using a "Custom Recording Rule"/"Power Recording
>  Rule".
>
>  Thank you for the patch.  If you have any additional questions about, for
>  example, how to add the season and episode ordinals to program, please
>  follow up on the mailing lists.
>
> --
> Ticket URL: <http://svn.mythtv.org/trac/ticket/8535#comment:1>
> MythTV <http://www.mythtv.org/>
> MythTV
> _______________________________________________
> mythtv-commits mailing list
> mythtv-commits at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-commits
>

Thanks for reviewing my patch.  I realize that syndicatedepisode number
wasn't the perfect solution, but I didn't see any other one.  I would be
interested it getting the real season and episode numbers in the
grabbers, but according to
http://forums.schedulesdirect.org/download/file.php?id=2 (TMS
DataDefinition) that information does not seem to be provided.  If
anyone knows where this information can be obtained I would gladly
update the grabber(s) to pull it and then modify my existing patch to
work with the new fields, as suggested.

I could potentially interface with http://thetvdb.com and post-process
the grabber data, but that seems a little cumbersome.  Any thoughts on
this?

Thanks,

Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-dev/attachments/20100607/1792ba35/attachment.htm>


More information about the mythtv-dev mailing list