What do you all think about using the Media module for all Session Resources?

We could have one content type called Session Resource and use the Media Module to allow for all types of formats. Utilizing the oEmbed module we could allow session Videos, PDF's, Powerpoints or photos of the session. With oEmbed this allows the embedding of different 3rd party providers (youtube, vimeo, slideshare, flikr, scribd) without having to download each provider module. In addition this may encourage presenters to post links to external resources prior to the session.

In my use case many faculty do want to share their slides but do not want them to be downloadable. Many of them already have a Slideshare account were they post most of their slides. oEmbed and the Media module seems to have a lot of support and is the future for handling files.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kclarkson’s picture

Category: feature » task
kclarkson’s picture

Any thoughts to incorporating the media module and creating one Session resources content type that allows multiple file types ?

kclarkson’s picture

Category: task » feature
kclarkson’s picture

Status: Active » Needs review
FileSize
262.59 KB
37.93 KB

Here is a patch that creates the COD Session Resource Feature.

What this does is provides a content type "Session Resource". Session resource can be a video, PowerPoint slide, photos or just a PDF file. You may embed content from 3rd party providers such as Vimeo, Youtube, SlideShare, Scribd or other third party URL's.

This also provides a Session Resources View that can be filtered by Resource Type Taxonomy Term. Taxonomy terms must be added

The following Modules are required for this to work:
Media 7.x-2.x
File Entity 7.x-2.x
oEmbed 7.x-0.x
Context

I used Context to order the Default Content Block and the Session Resource Block. See screenshot

rootwork’s picture

I'm not in a position to provide technical review, but I think the idea of having this all integrated in one content type is great. So absent any other progress on this I just wanted to provide that feedback.

kclarkson’s picture

@rootwork

Thanks for the comments. If we could get more people to review the patch maybe it will get committed to COD.

Thanks

chrisguindon’s picture

I cannot enable this feature because mediafield is a dependency.

chrisguindon’s picture

This patch is based off the work of @kclarkson, comment #4.

I only removed the mediafield dependency and added the missing ending of the description in the the cod_session_resources.info file.

kclarkson’s picture

@chrisguindon,

thanks for fixing that sir !

Hopefully we can get some people to review this so that it can be committed.

chrisguindon’s picture

Should we include the removal of cod_session_video in the patch?

If cod_session_resources get committed I don't think we need cod_session_video anymore.

chrisguindon’s picture

In case we do here is an update that includes the removal of cod_session_video.

kclarkson’s picture

Title: Evaluation of Media Module for Session Resources - Videos, Powerpoints (slideshare) & Photos » Replace Video and Slides with Media Module for Session Resources - Videos, Powerpoints (slideshare) & Photos

changed title to reflect this patch replaces the need for both Video and Slide fields.

rootwork’s picture

It'd be nice to see some movement on reviewing this from some of the key players...I think it's great, but who am I? No one important in the COD project.

japerry, you out there?

DyanneNova’s picture

My feeling is that it might be confusing for site users to split this out as a separate content type when each resource applies to just one session. It might be better to add Session Resources as an unlimited value Media field on the Session content type itself.

I'll poke japerry to see what he thinks when he gets back to this sprint.

rootwork’s picture

@DyanneNova I like the idea of an unlimited value Media field.

japerry’s picture

We should probably loop in Devin Carlson, who is on vacation this week. We're currently working on adding media abilities to Commons, and will want to follow a similar path using Media and File Entity. At badcamp we leaned towards a multi-field instead of a new CT because we didn't see the need for referencing a piece of media from multiple sessions. Also, by using file field, I guess we are already using an entity reference, since it is an entity.

kclarkson’s picture

@japerry,

My reasoning for having its own content type was to be able to have a section of just "resources" and be able to sort them by resource type (photos, slides, video, PDF's) or by user. Again Inline Entity Forms could make this seamless from the users perspective and allow the flexibility of resources.

But I totally get the idea of just making it an unlimited field. If we did this could I still separate the different types of "media" and make a sortable page of resources? If so then I am down :) My biggest goal was one field for all related resources.

bneil’s picture

kclarkson,

With File Entity/Media you'd be able to create separate or filterable views based on file type, e.g. video, document, etc like you are requesting.

kclarkson’s picture

@bneil

I figured so, just wanted a little confirmation :)

Can we get a Hell Yeah for this feature ?

Lets get some people to +1 for this so we can build it.

kclarkson’s picture

Issue summary: View changes

Edit of text to include oEmbed