Developers

As a part of the Curriculum and Training Group, we have a work group exploring possible solutions for mapping Drupal production roles / job functions to competencies and to learning content. The objective may ultimately be to build a new module that will allow for the easy collection of topics and sub-topics across all curriculum and learning content, as well as a mechanism for managing and distributing such records. (Curriculum and Training Group: http://groups.drupal.org/curriculum-and-training)

So I've finally made the move to St. Paul, MN and am working for Tightrope full time and only partially helping out my old PEG station through the internet. This means that I finally have some "free" time to do some developing for the Open Media Project. There has been a bunch of talk on IRC lately about separating some of the functionality in the different modules and I think Krenyen has already done a lot towards that with the simpler om_show module and the new om_airing module.

Just wanted to drop a line and let others know there are some auto-installation options that might be helpful for ffmpeg newbies. I wrote a small article on one setup and gave some tips. You can view the details here:
http://www.elvisblogs.org/other/howto-install-ffmpeg-ffmpeg-php-and-code...

Been discussing with Craig from Amherst, Daniel from Sweden, and Kevin from Denver, ways that help requests or questions could be captured for purposes of creating better documentation. Here is one idea that is pretty simple actually. We would have to set up and agree to some rules.

The first rule. If anyone has a help request or question about some aspect of Open Media Project implementation, whether on IRC, GDO, ichat, etc., that question or request needs to be routed to one central location.

So I know this is something of a wide-ranging question but I was wondering if there were essential pieces I should know before trying out OM_Install+OM_Me? Seems to presently be the same moduleset kreynen mentioned in a previous post as OM_Lite.

I'm hoping to get CMAP to a point where they can begin using CiviCRM and OM_Project on a local dev install by next week and have enough information and configuration done for them to be able to move forward with MERCI deployment on their own.

Hi,

We are finally in the process of moving our entire site to Drupal and gradually start using the OM tools. I was thinking of starting with just managing our metadata in Drupal, that is shows and what you call projects (we organize only be member, but I suppose we'd have to use one project for each member).

However, trying to install om_show lots of other modules are also required, most of which we wouldn't use at this stage. Are all those really required to manage show metadata? Particularly I'm wondering about these:

I don't know if anyone else has come across this issue but we can overbook node in bucket content types. If there are two inventory nodes in a bucket content type, you are able to make three+ overlapping reservations.

You only receive an error AFTER applying the two inventory nodes to reservation. Any overlapping reservation edited after that will return an error stating the item is no longer reservable.

Our only workaround is to have all bucket content types only reservable by staff and make reservation for the related equipment first come, first served.

I cannot transfer shows from the website to the playback servers. The SOAP insert shows up in content but the media file is held up even though the status shows up as "on server". I check the server status and go this error: Unable to connect: Firefox can't establish a connection to the server at admin.

I tried transferring the show to another server and got the same results. SOAP insert but no media file.

I then checked openmedia/om-timeslot-princeton, as far as I can tell everything looks fine.

System Health for 56.

This is a discussion about what is the best approach in MERCI for dealing with Resources that comprise a number of additional Resources, Buckets, and/or Accessories, such as a Studio.

The Open Media Project Handbook section on MERCI defines 3 types of equipment available for checkout:

Resource - Individual items that are unique. Example: Studio A vs. Studio B

Bucket - Items that are identical or so similar that users don't care which one they get. Example: DV Cameras

Accessories - Items that you don't track other than to ensure that if someone takes one or more with other equipment, it is returned. Examples: Batteries, lens cap, usb cable.

channelAustin is adopting PBCore as a metadata standard for video genre types. PBCore is the metadata standard for the exchange of Public Broadcasting content. With this decision, channelAustin joins the Bay Area Video Coalition (BAVC) and Denver Open Media in using PBCore. channelAustin is including the PBCore Module in its Open Media Project implementation (in development) and will model its configuration after BAVC.