The Content Supplier Application (CSA) is an easy to use Drupal 6 module to upload, transcode, publish, maintain MediaMosa video conents and share them between different client applications.
As a MediaMosa owner you can create a main client application. This client application will be visible for the end users. With the CSA you can easily and safely allow others to publish their videos on your main site.
To do this first you can create new client applications per users (app1, app2, app3 ...), who want to upload to your main client, and you must share your main client application with them (see "Master/slave settings" on the edit page of your MediaMosa client application).
Then you must install CSA as a common video publisher platform. You can get your CSA from our SVN repository (see below). The SVN repository contains not only the CSA module, but a complete Drupal 6 CSA installation with CSA install profile.
After the installation you need to do some setup. First of all you have now two new user roles: "CSA Admin" and "CSA User". "CSA Admin" is you, or somebody you trust. As "CSA Admin" you must create a MediaMosa connection (admin/mediamosa/config/connector) and you should do the basic CSA settings, like required and multiple metadata fields (csa/settings).
Then you should create "CSA User" users. You must setup MediaMosa connection per user. So the first user will connect to app1, the second to app2 etc. And you can make default preferencies per user, like "generate still", "metadata", "transcoding", "access rules".
After that all of your "CSA User" can work on their client application and easily share video content with the main application.
The CSA users have different batch tools to easily upload, publish, transcode video.
The CSA users can upload multiple files on the "upload" page. Then they can publish these videos, or part of them with the main application on the "unpublished" page. The users can add metadata, or add videos to collections, browse videos, delete them, transcode them, or the users can create still images for videos on the very same page.
On the "published" page they can remove shared videos from the main application. They can search on the "search" page using eg. title, or the more complex CQL search. The users can maintain their collections on the "collection" page, and they can change their preset preferencies on the "preferencies" page.
A very handy tool, that all the users can see their disk space quota on top of their pages, like: total ammount, used, and free spae in mega bytes.
Because the users, who want to share videos, aren't MediaMosa expert necessarily, the CSA was designed to support a simple and clean user interface. Also it was plan, that the users can reach every process (still image generation, transcode, access rules etc.), that is available in MediaMosa. This is one of the stronges side of CSA.
Finally as an admin, you can easily remove unwanted content or all the videos from a user from your main client applications. This make this solution very flexible and safe.