CCK

I believe the evil credentials of views and CCK are well established. I wanted to unveil a new module that combines the two into an unbelievably devilish system: viewfield.

Viewfield allows content type administrators to add view reference fields into CCK content types. When a user creates one of these nodes, he/she can select from a list of views to embed into the node. When the node is viewed, the view runs and is output as one of the node fields. (Of course this can be themed).

Earl Miles has integrated some very cool audio/playlist functionality into his Views Bonus pack. After trying it out on my test site (filtered on audio per user), and some helpful feedback, it's looking like there are all sorts of possibilities and applications.

Here are just a few of the things (I think) we can create:

• playlist for any sort of music related article (posted about that here)
• event and/or venue specific playlists - specific to those performing an event; upcoming/previous shows for a particular venue
• location based - bands coming to a certain area
• artist/album specific playlists
• genre-based playlists
• playlists for a specific year
• maybe even playlists based on organic groups or buddy lists?

In addition to music, wouldn't the same sort of dynamic functionality work for other node types such as podcasts or even video?

Update: Bumping this rather old post up and over to the Drupal Dojo in hope that it can spur some 'can drupal do this' learning and workshopping.

In the context of a music-arts community site, I'm looking to provide an easy way for registered users to create some of the following types of content:

It seems like there are a lot of questions (and answers) regarding how to create a newspaper and/or magazine style site. I also noticed the WillieBHines just added this very helpful site recipe:
Use CCK to make a unique front page

Following his lead, I'd like to help contribute more ingredients that would ideally be mixed into a complete site recipe/install profile for a music/arts-centric newspaper/magazine style site. Having said that, here are a few examples, suggested ingredients and questions for something that could be titled 'use cck, contemplate, views, panels, and some other special ingredients to create structured sections and article pages'. Unfortunately I can't cook or write a good recipe.

It will likely be important to replicate the old profile.module functionality for clicking on a profile value to search for all of the other profiles that match that field. Obviously this doesn't make sense for long text fields but it does for any shorter text fields (favorite book=>'Old Yeller' ,) and for many other field widgets.

Could this be done using views or would it be much better to do in cck, or in cck output widgets?

IMHO: it should likely be done in cck, but not in the widgets.

If response dictates I can take this discussion to the cck group.

What?

A few days ago, I compiled a list of all the node review modules I could find at the time, and wrote up an article comparing them: http://www.lullabot.com/articles/a_review_of_node_review_modules. The amount of overlap in these modules is, quite frankly, stunning. Yet they all do slightly different things. Node Review handles multiple axes. Simple Vote merely stores the aggregate score for a node. User Review allows you to place a comment with your vote. Vote Up/Down handles a simple "yes/no" style of voting.

It occurred to me that if we took a step back, we might be able to develop "one voting module to rule them all." Rather than having to keep implementing these new voting modules because others "almost" do what we want but not quite.

I've looked briefly at customvote.module, which looks as though it endeavors to be that tool. But I'm thinking something slightly different: a voting API field for CCK.