Looking inside of a Drupal database. Gross…
Managing News is a “robust news and data aggregation engine with pluggable visualization and workflow tools.” Mo Jangda set up an instance on his server that I finally had the chance to check out. My initial impression was that, like the website, the development team put a tremendous amount of effort into polishing the user interface. It’s a super shiny way to aggregate RSS feeds.
There are nuggets I was able to suss out, however. If you’ve indexed your feeds, there are search capabilities that will also give you the frequency of any given term. The mapping functionality is also very slick. You can get all of the recent stories on a map, or stories limited to a specific term. It’s misleading to have the initial view of the map be the entire world, though, because the most useful view to an end user will be whatever region they’re interested in.
This brings me to my biggest observation: a tool like this would be most useful for managing feeds of raw data, not feeds of news articles. News articles are products where the data has already been through the rock tumbler. Where Managing News wants to be headed, I think, is towards building a tool that allows you to map and visualize all manners of data.
The difficulty then is both building the visualization tools and finding, or even brainstorming, properly geo-coded RSS feeds of the data you’re interested in.
Just a gentle reminder that the first ever CoPress survey is online and looking for respondents. We want input preferably from the online editors at student news organizations, although others are welcome to contribute if the online editor has not been hired yet.
This first survey is to gauge the current state of the ecosystem. We want to know how what CMS you’re running, how many developers you have, and what languages they know, among other things. The survey will be open until 5 PM PST on 10 October. After we’ve spent time creating bar graphs and geo-mashups, we’ll release our first report. It should answer questions such as, “What is the average satisfaction with College Publisher 4 versus Drupal?” As far as we can tell, this hasn’t ever been done in our sector.
Along with the release of the report, we’ll be announcing our second CoPress survey. Our intent with this follow up survey will be to have a better understanding of what people want from a digital distribution platform. We truly value your input.
Also, props to Bryan Murley of Innovation in College Media for pointing out that it is not, in fact, September 2009. Not to be too stuck in the future, we’ve updated the survey title and links accordingly.
On my argument against College Publisher, and for an open source coalition of student newspapers, Brad Arendt of The Arbiter presents several good points about the advantages of using College Publisher. Considering the time he took writing a well-detailed comment, I thought I would clarify on a several things I think he missed.
First, I think student newspapers should actively work on developing 1 or 2 alternatives to CP. This may not mean collaboratively building a CMS from scratch, rather it’s more likely to be facilitating a developer ecosystem specific to our needs around common platforms. For anyone familiar with WordPress, which I’ve helped implement for the Whitman Pioneer and most recently, Oregon Direct Action (which is a work in progress), it’s strength is an abundance of plugins and themes you can add to your install. A developer ecosystem is important for continued innovation and, as far as I can tell, CP doesn’t have one.
Cost is certainly an issue. Both CP and WordPress, Django, or Drupal are “free,” but the critical difference is that CP comes working out of the box for student newspapers and the others require a developer. One stated goal is to have an open source alternative that can be quickly up and running with full functionality. If the paper has resources to develop their platform beyond point, they would be able to do so with the support of other developers across the country. This platform would also be available to local papers, although that is not the intended market. Furthermore, I do see a business model in this, in a very Ubuntu and WordPress-esque fashion.
There are some rather innovative and creative things which the CP4.0 system does offer. I would not say it limits creativity, rather it is the students you have on staff who know what to do with the tools that limits your creativity more than CP4.0. The Daily Pennsylvanian has done some very creative stuff in the LAMP environment, which is open source. The Daily Tar Heel has also figured out an interesting work around for blogs, granted done via WordPress but the 4.0 system and the students figured out how to “fit” it in.
Personally, I think arguing that College Publisher allows for innovation is completely erroneous. LAMP, which means Linux, Apache, MySQL, and PHP, is an open source stack and doesn’t stand for anything specific. I don’t mean to discount your example, I’m just not sure how you mean to imply CP is innovative by allowing hacking outside the platform. Furthermore, any server environment should allow working with and around the software running on it. Allowing WordPress to be installed as a blogging platform is not a sellable strength of College Publisher
Brian also mentions that CP does provide backups of your site for the scenario in which it disappears. Unfortunately, these, I imagine, are only backups of your data, not the content management system your data is living in. If your site were to go down, you would have to install and develop an alternative CMS, as well as port your database, before you have a live site. You shouldn’t have to completely rebuild your website if College Publisher disappears. When the web presence becomes the only presence, having your site suddenly not exist would have very real consequences.
When you control the platform, you also control the content and innovation associated with it.
In the school news industry, College Publisher, now branded as the College Media Network, desperately needs a competitor. Owned by MTV, a subsidiary of Viacom, College Publisher provides a content management system now used by “550 going on 600” student newspapers across the country. It offers under-staffed and under-funded newsrooms an easy way to get their content online at a price that can’t be beat.
Why is Viacom interested in managing the online platforms for as many college newspapers as possible? To deliver advertising, of course. As a part of the contract for a cheap, if not free, way to get your stories and images online, College Publisher reserves the top placements on your site for their own use. This allows an even bigger media giant (Viacom) to directly make money off a school newspaper’s content, either by selling advertising slots to big corporations like T-Mobile and Bank of America or by running advertisements for their other properties. Student newspapers are especially valuable to Viacom because they largely produce for its key demographic: the college student. Most, too, are held captive to this partnership because there isn’t the motivation, manpower, or vision for more innovative options.
Should any independent student newspaper want in a part of this? No.
College Publisher, unfortunately, is not the innovation aspiring journalists and reporters should depend on in this changing media environment. Claiming RateMyProfessors.com and a CMN Facebook app are “national media outlets” is not creativity. Rather than outsourcing the heavy-lifting to College Publisher, student newspapers need to allocate resources internally to running and developing their own platform. This can seem somewhat paradoxical, adding to your staff when you’re losing more and more revenue, but it is a necessity for survival. The future isn’t all that bleak, we’re just in a time of transition.
At Publishing 2.0, Scott Karp argues that newspapers need to take a hint from General Motors and learn how to innovate. Most newspapers have had roughly the same business model since the 1950’s which they’re now largely attempting to reapply to the internet. It’s not the same medium, though. Advertising and classifieds were king in past years, but the playing field is now open to the most ambitious entrepreneurs. Maybe a model like Spot.us will succeed, maybe it won’t. Without trying new things, there’s no way to find out.
One component of a strategy for student newspapers to move forward is a consortium dedicated to collaboratively building an open source content management system which best fits everyone’s needs. We need a robust, free to use platform that thrives under many of the same values which the open source movement holds dear. The growth of such a community around the publishing software used by student newspapers would be of tremendous value to everyone, especially because most papers aren’t in competing markets. Collaborative innovation is a win-win for these types of organizations, a fact I think few have realized.
As the start for a transition I hope to begin with the Oregon Daily Emerald in the winter, I’m taking steps forward. At this point, my work involves researching mature platforms already in the ecosystem, such as WordPress, Drupal, and Django, contacting people at what I think are progressive school newspapers, and working to identify the crucial features for any online newsroom (like managing media assets and placing advertisements). While I recognize there are already many content management systems on the market, my paradoxical goal is for a platform as easy to use and install as WordPress that also offers advanced management features. Software that any student newspaper can install, but also be able to develop further if they have the resources to do so.
I’m passionate about making this happen. Let’s do it.
Ironically, the College Media Network blog runs WordPress. They obviously aren’t drinking their own Kool-Aid.