Colin, It's not trivial but it's certainly possible. The approach you'll want to take is write a box that stores your playlists in a separate table, where each record (one record per song presumably) would be tied to a story SID. Modify the block edit_story_form to include fields for your new playlist data, attach the box that writes and updates the playlist data to the story_new and story_update hooks, so when you save or alter a story, the playlist data is properly handled. You'll then want to add a box for display of the playlist data that takes a story SID and checks the DB for a playlist associated with that story, then if one exists, displays it. This is similar to what was done over at http://www.hotelchatter.com and http://www.jaunted.com where location data is added to stories such that visitors can browse stories related to locations in which they're interested. Likewise, you could expand your design to include search by song with links for the user to purchase the music, see how frequently a song makes the playlist, find each show where a given song was played, (and with proper licensing) listed to podcasts of each shows playlist etc. Best Regards, Colin Hill -- Scoophost.com - a service of Pinnacle Digital Scoop consulting and hosting services scoop-help-request at lists.kuro5hin.org wrote: > Date: Sun, 5 Mar 2006 10:56:41 -0500 (EST) > From: scoop at juicer.orange-carb.org (Colin Henein) > Subject: [Scoop-help] Non-freeform story content > > Hi folks, > > I am looking seriously at Scoop to manage content for a community > radio show's website. The core content is expected to be a "playlist" > section which will receive a story per week with that week's playlist > of songs. > > My co-host is likely to create stories with comma-separated Artist, > Album, Track and Label information. I don't think a whole category of > comma-separated text things is going to look very inviting. > > Writing some perl code to parse text and output HTML is no big deal > for me, but I want to know whether it's going to be easy to plug into > the story output of a single section so that I can format things on > the fly. > > The real solution would be to somehow guide the story author to enter > the data in multiple fields at the outset, is there an easy way to > override the simple text boxes for story entry and replace them with > something more structured? > > Cheers, > Colin