CCTV's Main Programming Tables

CCTV in Burlington, VT has recently released their Drupal Powered site http://www.cctv.org. CCTV has detailed scheduling requirements and needs schedules to the second and often times will run almost live multi-hour meetings, the day after taping and they show them in their entirety. This means they know the length of the program only one day prior to its airing sometimes and are updating schedules frequently and aren't running in a regular blocky on the half hour or hour system.

I wrote the back end module, http://triangul.us/pegevent_module, that allows schedulers to build schedules for airing and export those schedules to the MaestroVision playback system and also some code that syncs up info form the playback system into Drupal. CCTV is interested in how the shared vision is moving forward and possibilities for integration.

For schedule building and export purposes, it looks like I'll be able to morph my code to cooperate with the underlying structure in the Drafts published here. I talked with Mark Libkuman of OpenFlows last week about sensible default actions. He said that if you created an airing with only a field_om_show_nid and field_start_time_value and field_duration_value, the system would be happy (and not complain about empty fields).

CCTV project/episode/showing structure is a bit different from the draft. Our main focus is on the Program. Series and Showings are very slim. A program can have zero or one associated series and zero, one or many associated showings. The diagram below shows the main CCTV program scheduling tables. There is some vestigal cruft in the program fields (last 5 fields). The five fields that start with field_mv refer to the MaestroVision playback system. These are the minimum info needed to export a playlist to MV.

I hope this isn't too far afield from where the OMP is headed, but it might be a good example of an integration challenge ;-)