Developers

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.

This are working drafts, so PLEASE offer feedback. The naming of the fields hasn't been finalized either. I didn't change many of the prefixes to make it easier to track where fields have been move to. Much of the naming will be determined by CCK's naming conventions. Other field names may change based on the modules we end up building on (like Media Mover), but if you think there is a better/more logical term we should be using please suggest alternatives BEFORE we write a bunch of code referencing these field names.

We are going to define as much of these content types as possible/logical with CCK. That will allow us to leverage all of the great work being contributed to CCK as well as allow each location to extend the schema. The updated schema reflects the core fields required by the Open Media System modules.

Ok, so I have a question if there's any interest for a module for management of DV tapes. The purpose would be to keep a library of all DV tapes at a station, to know how to find the right tapes and know what tapes that can be used and reused.

My thinking goes like this:

Due to many people having trouble connecting/staying connected to the SILC server, Daniel and I suggest we move to a general IRC channel. We're both sitting in #drupal-openmedia on irc.freenode.net (same place as the standard Drupal channels).

The current plan to share files between locations and provide an off site backup of the broadcast quality MPEG2 is to move the files to Archive.org using the advanced interface to their Contribution Engine. Due to the size of these files, users will be able to configure when these transfers happen (ie. from 1AM-4AM) or tigger an immediate upload.

Was great to see everyone at the Alliance for Community Media conference. In an effort to improve communication between everyone working on this project, or tools related to this project, Open Flows agreed to host an Open Media group on their SILC (encrypted irc) server. The server is emma.openflows.com, and the channel is #om. There are already a few people living in there and we would love to see as many people available as possible. There are several SILC ready clients, for osx there is colloquy . On Windows Pidgin works (http://www.pidgin.im/).

As we move forward with the Open Media Project, we've found ourselves in the "age old" debate of developing modules with functionality built on top of CCK or building a custom modules with full control over their tables and functionality. This was recently discussed here, but we have a different set of feature needs than davidm had so I'm bringing it up again.

The current codebase that drives Denver Open Media is primarily in one monolithic module. One of the step we are taking as we update this code for Drupal 6 is to break functions out into sub-modules. This will make both development and deployment easier. Public Access Stations, Independent Media Centers, and other groups interested in the Open Media Project can add modules/features as they transition to an Open Media driven system.