Provide a framework to manage files and multimedia assets, regardless of whether they are hosted on your own site or a 3rd party site.

  • Add media from URL, upload or existing files
  • Mass importing of files.
  • Drag and drop upload (with Plupload module)
  • Customizable media browser
  • CC license settings

Comments

gusaus’s picture

The features listed above (and many more) are provided by the Media module (http://drupal.org/project/media). Now that there's a stable release and a lot of active development, I think we could include this as a base feature.

gusaus’s picture

Assigned: Unassigned » gusaus

I think the is necessary for this type of publishing platform I've been working with media on a couple projects and know it well enough to take this on.

Anonymous’s picture

Yeah I've used it a number of times as well. I agree it is ready and any issues that we may face in implementation they will not be insurmountable. Go for it!

discipolo’s picture

trying debut media as kit compliant solution

zirafa’s picture

I should update that Media will included in this distro now.

Customizable media browser

I think the newer versions of media support views for browsing.

CC license settings

Shouldn't this belong in the album/track content type?

zirafa’s picture

Version: » 7.x-1.x-dev
Status: Active » Closed (duplicate)

Marking this as a dupe of http://drupal.org/node/1263926

gusaus’s picture

Assigned: gusaus » Unassigned

I think managing media (as described in the issue summary above) should be considered a separate feature than the presentation layer or display.

zirafa’s picture

Component: Code » Admin interface
Status: Closed (duplicate) » Postponed (maintainer needs more info)

I created some new issue components, filing this under admin interface. I think most of this stuff can be handled by modules that extend the media module, yes? If so maybe we could first approach this issue with good how-to documentation and recipes for extending the base feature set.

gusaus’s picture

The question I had in #7 is similar to what discipolo is asking here. One takeaway from our recent discussion in #pushtape is that media module might not be the only solution for uploading/management media. If it was determined to be an option would it be included in Pushtape Discography, another feature, or something else?

discipolo’s picture

Component: Admin interface » Documentation

is this a feature request to manage media assets as an extension to pushtape_admin maybe?

zirafa’s picture

Somewhat related: there is currently a hidden view in pushtape_admin. Checkout /admin/pushtape/music. It is pretty rough at the moment but shows a list of all tracks and albums. It is of course on the node level, not file/media level as that is the entity level Pushtape mainly operates.

I think what is described in #10 is accurate, though I'm not even sure it has to extend any of the Pushtape modules. Media module already has its own media browser/manager so installing the media module is the solution to this.

This will have to be implemented as a separate add-on feature though, I have no interest in supporting it as a "core" feature.

Leeteq’s picture

Issue summary: View changes

FYI - "Scald: Media Management made easy"
D7: https://www.drupal.org/project/scald
D8: (successor) https://www.drupal.org/project/media_entity

From the project page:

"Features:

  • Media Atoms: full-blown fieldable entities
  • Unified Type: an image Media Atom bundle can be a local file, a photo on Flickr or on Facebook
  • Media Licensing Management: Scald includes a Media Licensing Management, which is a mandatory feature when using professional grade Media Atom sources - whether uploaded or online.
  • Standards: Scald implements a standardized mechanism for manipulating various types of Media Atoms - Files, Social Media Posts, Streamed Media
  • View mode/Context: each Media Atom can be rendered in different view modes, using different players
  • Native support for transcoders (e.g. image styles)
  • Native and extensible control access support
  • Drag and Drop Media Atoms directly to a richtext editor or a Media Atom Reference field
  • Views-based library
  • Easy to extend: module can add Types, Media Atom providers, Contexts, Transcoders and Players
  • Edit integration for inline editing, with CKEditor integration
  • Easy and intuitive multiple upload with integration with the plupload module.
  • Integration with many contrib modules: Entity API, Entity Translation, Features, Search API"

From the Scald module FAQ page:
https://www.drupal.org/node/2101855

"But we believe we need another solution because Media's approach is not extensible. Media implies a media is a file, Scald does not. Scald believes file is just a special case for a media entity. Those both approaches are not compatible and we can't fix Media. The Scald team thought carefully about many possibility before deciding to port Scald to Drupal 7 (to be based on File Entity or Scald's own entity, which is known as "atom"). Amongst reasons why Media Atom entity is not File entity:

  • We don't want that every managed file is a Media Atom entity.
  • Multple Media Atom entities (with different title, caption...) can reference to the same File entity (or any resource).
  • One Media Atom entity can have multiple revisions, each reference to a different File entity (or any resource).
  • Media Atom may not always have a filesize or mimetype like a traditional file. A "transcoded" Media Atom may have. Each transcoded Media Atom may be a file.
  • So, while it is still good for simple usage, for more advanced usage we believe Scald is a better match. Scald also has many features that Media does not, like great WYSIWYG integration, friendly library, advanced/granular permission system...

    Scald has much smaller usage because a lot of people still think Media is the standard solution, or they simply even don't know of Scald.

    PS: for Drupal 8, after the Media sprint at Drupalcon Prague 2013, a new module Media Entity (https://www.drupal.org/project/media_entity) was born with a similar approach as Scald. Because Drupal 8 is a big change, people start from scratch instead of porting a Drupal 7 module."

    gusaus’s picture

    Component: Documentation » Proposal
    Issue tags: +media, +panopoly

    Related to https://www.drupal.org/node/1698106#comment-9993829, the functionality described in the issue summary would provide non-developers an experience they are used to. Rather than creating and maintaining a stand-alone Pushtape Media feature, I'd recommend building on top of Panopoly.

    zirafa’s picture

    Status: Postponed (maintainer needs more info) » Closed (won't fix)

    Out of scope.