Another competing media asset management module called Asset has been developed for Drpual 7, still in dev release. It'd be worth taking a look at it and seeing what pieces could be adopted. Based on the module description it seems the only major differences are the following:

Pros:

  • Custom asset types (Image, Video, Audio, Document, Image Gallery, Free HTML)
  • Asset override form to manage optional fields (like description, view mode: small, large image/video) directly in the CKEditor for the in-place embedding. This is similar to the 'Embed format' form when selecting a media item in the WYSIWYG Media Browser, but maybe has better support for more fields like alt/title?

Cons:

  • Creates its own new entity type (asset) rather than re-using managed files, which means inter-operability with other modules is a problem. Also doesn't support anything that's been uploaded via file or image fields already prior to install. Assets no longer available after uninstall.

Comments

damienmckenna’s picture

pkej’s picture

Pros:

  • Tight integration with CKEditor, each asset type gets a button to create the asset in the editor
  • Allows override of data in the bundle; for an image the default image description can be overriden with a local one, can also override styles of images etc
  • Assets can be copied and pasted within the editor
nigelw’s picture

THe latest release of the Asset module is pretty slick. It would be great to see the features of both media and asset come together.

Check out the demo site to see it in action. http://demo.assets.adyax.com/

socialnicheguru’s picture

I agree

gmclelland’s picture

I like that under Text formats it provides a filter "Remove asset tags from output"
This filter will remove [[asset:...]] from output

I think the Media module could be benefit to adding something like this.

damienmckenna’s picture

@gmclelland: That's a good idea: #2165457: Create text filter "Remove media tags"

chris matthews’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Closing this issue as outdated. However, if you think this issue is still important, please let us know and we will gladly re-open it for review.
sincerely,
- the Drupal Media Team