I'm currently using the audio module and views_rss module to create podcasts. So far it is really slick. However I was hoping to add a few more tags. I've been looking at the code and it doesn't look too difficult to add the tags to both the audio node and the the views_rss file.

My big question is should I add additional tags such as itunes:category, itunes:keywords, etc to the audio module. The alternative to adding to the audio module, would be to create a new node type with cck that had an audio or multimedia field, plus other fields for the new tags or even just the additional metadata tags built in to the audio module. Then use the views_rss module for the feed. Granted I'm not exactly sure how I would translate those into the itunes:category tags without coding, but that could probably be figured out. I guess it comes down to whether or not the audio module really is "itunes friendly" with only two itunes specific tags built in.

I envision patching the audio module so that additional fields can be used when creating an audio node. The question is what is the best model to take. Things like keywords and categories could be associated with taxonomy vocabularies, the others could just be text boxes or checkboxes.

Any thoughts or suggestions? Is anyone already doing something similar to add additional podcast tags to the audio module? Should podcast particulars be built in to the audio module or left to each admin to implement however they choose?

Comments

zirafa’s picture

zirafa commented

Hi, there is some overlap with what you are envisioning and what is proposed here:

http://drupal.org/node/93968

However it needs a lot of work, especially with the views part of it. Any help is appreciated. Where did you intend to store the channel information for the podcast views feed?

But yes, this type of functionality should live as a contrib module most likely.

scafmac’s picture

scafmac commented

Hmm, I guess I don't understand the need for new modules to do what that page wants. I might not be getting it, but it is currently easy to create flexible, customized lists of playlists using the audio module and views. Adding to that the views_rss module (part of views) provides rss feeds for those playlists.

Granted theming views is not trivial, but it is getting easier with the advent of views_theme_wizard.

Either way, for my needs all that I need is the addition of some common audio meta tags to the audio module. It does not make sense to me to put them in a new module. The audio module already handles itunes & non-itunes tags; the problem is that it doesn't handle enough of them. So why wouldn't the appropriate place just be to patch the existing module? It is not new, non-audio functionality, just more of the same.

What am I missing?

drewish’s picture

drewish commented
Version: 5.x-0.1 » 5.x-1.x-dev

the problem is that some of the itunes metadata is about all the audio, not just a single node. so you need a place to put that data that allows the user the flexibility this group of audio nodes is x and this group is y. i think we should really try to work towards what zirafa's outlined.