View a related screencast at:
http://www.screencast.com/users/JohnMontgomery/folders/Jing/media/aa154b...
Required Modules
Enable Modules. Be sure to enable the Content and Content Copy. This will allow the Open Media Project module to create its related content types without errors.
Navigate to Administer > Site Building > Modules and enable Open Media Project.
Review Content Types. Check and make sure that the Open Media Project module has created the Project, Project Type, Timeslot Theme content types. Project will be set as Organic Group's group node.
Navigate to Administer > Content Management > Content Types to do this review.
and
);
return;
On the website, navigate to Administer > Content Management > Content Types > Import. Set the content type to <Create>, paste the content just copied from om_project_content_type.inc into the Import Data field and hit the Import button.
Set Permissions. Enable 'create om_project content' for the approriate role(s).
Navigate to Administer > User Management > Permissions to manage user permissions.
Configure String Overrides. Import "stringoverride-import".
On the web server, navigate to sites > all > modules > om_project > installs > stringoverride_import. Save this file locally.
Navigate to Administer > Site Configuration > String Overrides > Import to import the stringoverride_import file.
Additional Content Type. Create additional content types for other items we you like posted to a project, i.e., blogs, events, wikis. On each newly created content type, select Standard Post or Wiki Post in the Organic Group area.
The Open Media Project module includes the option creating a "personal project" for each new user that signs up for an account. By default those projects are not listed in the project directory and named <username>'s Videos. Navigating to a personal project will redirect to the project owner's profile page. This solves the problem of user who aren't working on a series and just want to quickly upload a few videos.

In addition to the access to create, delete, and edit both any and nodes the user authored, CCK's Content Permissions module takes this a step further and defines view and edit permissions on every field. By default, no role has access to new fields.
