Deprecated - Media and document management

I am looking to start a conversation with all parties that have deployed the Asset Manager Module ( am.module ) on client sites and that are involved in ongoing support for those sites.

If you have deployed am.module or are looking to deploy this module with the intention to support and upgrade the scope and utility/usability of the module through Drupal 6 please subscribe to this thread and post a bit of information:

Have you deployed am.module?

1. How many client sites?
2. Do you provide ongoing support for the site?
3. Are you planning upgrades projects for the client?
4. What types of assets are you planning on offering support for?
5. How would you rate your experience with the module to date?

Feel free to add more information as you see fit, of course. These just occurred to me as important context setting questions.

Currently I(we) are planning deployment of an asset management architecture for 3 large sites.
We will provide ongoing support for the sites.
We are planning development projects which will extend the module for different assets, and for various programmatic theming tasks.
Video, and especially 3rd party video handling
Only testing of the module to date. Seems well put together so far.

High!

Meanwhile, I changed the the input format for story content to "Full HTML", inserted a syntactically correct statement, but nevertheless, the image doesn't show up, regardless of having it listed in the upload section or not! Are there still any less obvious,l somewhat "hidden" option settings which I didn't take into account yet?

See you in Khyberspace!

Yadgar

High!

I just started posting some story content onto my local "practising site" and now wonder why is it obviously impossible to include inline images, even though the "Upload" module is enabled, I used the admin account (with an administrator rule capable of doing everything except manipulating PHP) and of course used the tag inside the content... what went wrong?

See you in Khyberspace!

Yadgar

Just for sharing my receipe about a mixed solution with public and private files.
I'm not a Drupal guru ... and still in my learning curve of Drupal ;-) So if you see a "security hole" or a better way (simple way ;-) to achieve the same goal, let me know !

Goal:

I wanted a simple solution to control the access by role to some folder. In my example: a folder specifique to my cck content type

The problem:

- if I set all the file system for private, some fonctionalty don't work (color chooser of garland, performance css, etc ...), and I will overload my server
- only a small part of the files uploaded to my site need to be private (all the css, img etc can stay public)
- I want to control the file access by the internal Drupal Role system.

Pre-requies:

- apache mod_rewrite (if clean url work for you, you're ok)
- cck, cck filefield and a content type of your own

Solution:

For restrict the acces to a folder we will redirect automaticaly all request to /files/private/xxx to /system/files/xxxx and handle the security in Drupal:

Hi,

I'm completely new to this forum and Forum, so excuse the noob questions!

I'm trying to create a website where users can upload their own video clips. Is this possible with Drupal? If so what plug ins do I need to make it happen ? Are these plug ins free? and can these uploaded clips be displayed on the front page, in a grid formation?

thanks for any help.
flashculture

I am in the process of finalizing a media management module, which is modular, easily extensible, and capable of presenting different media types in multiples of ways.

As it stands, media can be uploaded and specified to be either a node or a file. The original file is stored in a private storage area (best not located with the webserver directory), and derivatives (which are generated via a series of transformations, such as cropping, watermarking of image files) can be either public or private. In the case they are private, they are served via the drupal installation reading the file from the private storage area. In the case they are public, they perform the same was as a cached image file, somewhat similar to the imagecache module.

There are default viewers for various media types, which are organized around the extension it has. For instance, I have jw_player functioning for FLV files, 1pixelout for MP3s, and ordinary display of images for JPG, PNG and GIF extensions.

Since the transformations, presenters and extensions are all modular, it is possible to quickly add more functionality quickly. Also, each media file can have meta data stored with it, including licensing, authorship, or other things. (Although at the moment, there doesn't exist a way to modify this through administration settings).