Current Module List for Radio Engage
We've compiled a list of the initial modules for the Radio Engage distribution. We would love to have community input on this set of modules.
Please leave your comments below. We'll be updating this list and also providing more documentation to explain their use and configuration in the coming weeks
- mrosas's blog
- Login to post comments
Comments
integration with existing playlist managers
At WPRB we're in the process of rebuilding our website using drupal, so this project looks like a promising source of future development efforts.
One of the major dilemmas that we're wrestling with is the issue of drupal station (which, from the looks of it, handles the playlist and scheduling aspects of the project). We currently have 6 years' worth of DJ playlists in an existing playlist manager (Theis Playlist Manager), a package that was put together back in 2003 by one of the staff (who are all students, myself included...)
Of course we would eventually like to modernize that bit of machinery, but in the meantime we're looking to do sort of an incremental release that would allow us to use drupal and somehow integrate with the existing playlist.
Do you have any thoughts on modules (FeedAPI was mentioned in the Lullabot interview) that would facilitate this?
Obviously, I'll need to do more experimentation with drupal station and the other drupal modules before I commit the entire station to any given solution, but I thought it might be a good idea to comment early and often.
EDIT:
I suppose I should be more clear about the specifics of the Theis output. Basically, it speaks RSS, hence the appeal of the FeedAPI mention.
Playlist/program log
At KGNU we've been struggling with two applications that could be one. We have a clunky playlist app that tracks what DJ's have played. It's used both for reporting and for display though our site. The program log is used to dictate what programmers need to announce, PSA's to read, id's, etc. This is currently paper-based, but we're working on a web-based app to do this. Ultimately, we think it would make sense for both of these apps to be combined. We've seen an interesting proof of this concept at http://www.grcmc.org/radio/playlist.php. Given that we're planning to implement some sort of Drupal-based framework for our planned site redesign, it would be nice if this sort of app were Drupal-based.
Module List
What do you plan on using for reports/queries? At my local station there is a core of eight people involved in marketing/admin etc. What would be the best way for them to run ad-hoc queries against the database?
We haven't identified tools
We haven't identified tools to replace the current back-end systems (non-Drupal) already in place. However, we will provide user search and lookup tools (Advanced User is one module) and also provide user exports for email newsletter distribution.
I would love to know the types of functions and features that you have identified that need tools. We did evaluate CiviCRM but decided that it was more than we could take on for the initial project. While CiviCRM remains to be a possibility, we need to do a fuller assessment of the marketing/admin tools that are needed first.
Hi Margaret, Our station has
Hi Margaret,
Our station has to learn to walk yet, never mind run, so we have yet to face the issue. I sent you an email about ourselves, I assume you got it?