Add ability to filter recording schedules by season

[Jason Musits <jmusits@…>]

Please find the attached patch which adds the ability to limit a recording schedule to a specific season.

Uses program.syndicatedepisodenumber when available.

Patch is against r24995

Modified:

Backend (Scheduler & DB Schema) Frontend (Scheduler UI) Themes MythWeb Perl & Python Bindings

I have tested this on my development box for a few weeks now and have not run into any issues. (LiveTV, Scheduling, Watch Recordings, Python Bindings and MythWeb) I don't use the Perl bindings for anything so that has not been tested.

I think I hit everything that needed to be changed, let me know if I missed anything.

[Jason Musits <jmusits@…>]

Season Limit patch

[sphery]

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.