Get the real story via our bi-monthly newsletter

Search

    4
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > Survey on university CMS adoption

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends

Enterprise Social Software Trends


Report Excerpt

The Web CMS Report 2009 looks at... Content Server's Web Services API

"Java APIs are also exposed as Web Services, with SOAP bindings and WSDL files automatically configured. Like other vendors, however, results in the field using these new APIs have been mixed at best. For one thing, the WSDL files point to JSP pages (so that FatWire can access its tag library) and not actual Java APIs. This limits substantially what you can do and brooks performance problems as well..."

(p. 273)

More about The Web CMS Report 2009

Our customers say

"This excellent report has saved weeks of work reviewing the market place to enable a tender to be sent out to just a handful of potential vendors in record time. Well done.
- - Martin Beake,
ITT Consultant, 2Sys Limited, Malmesbury, UK

NEW at CMS Watch

The Digital & Media Asset Management Report 2009 The Digital & Media Asset Management Report 2009: This report provides comparative evaluations of 18 digital media and asset management offerings... Read more
Fundamentals of Digital Asset Management Digital & Media Asset Management Online Education Course: This course will provide you with a thorough grounding in Digital and Media Asset Management technology... Read more
The Search & Information Access Report 2009 The Search & Information Access Report 2009: This report provides comparative evaluations of 20 search and information access offerings... Read more

 

TrendWatch Blog

Survey on university CMS adoption

07-Nov-2007

A Web CMS survey conducted by the University of California at Davis (preliminary results of which were released October 22, 2007) made official what many of us suspected all along: Even the best minds in the world can't agree on how to do content management. Of the 81 (out of 129) respondents who are currently using a Web CMS, roughly 20% (18 respondents) have rolled their own solution. The other 63 institutions are using 39 different branded solutions. The fragmentation of this market is really quite stunning. Can you imagine 63 colleges using 39 different word processor programs?

Quantitatively, the UCD numbers are a bit on the thin side. What survey lacks in statistical significance, however, it makes up for in qualitative poignancy. The comments page makes interesting reading. The usual themes emerge: Know your requirements up front. Get buy-in from all constituencies, not just IT. Budget for training. Expect things to take longer than you thought.

An interesting bit of subtext that seems to weave together many of the survey respondents' comments is that when rolling out a Web CMS, the cost of failure is often better-defined than the cost of success. If a system rolls out within budget and fails due to (say) poor adoption, the cost of the exercise is well known. If, on the other hand, a system rolls out to great fanfare, unanticipated costs can surface.

"Adding a CMS changes how people think about the web," one survey respondent said, pointing out that when authors are able to post content in real- or near-real-time, it gives them a new sense of what's possible. "In the days when you needed a programmer to do just about anything in a site, people settled for getting very little done. Now they may assume they can have a lot for very little cost, so expectations management becomes a real educational endeavor."

One survey respondent said: "Be very conscious that if you do succeed with a vision of centralized management of a decentralized publishing system . . . the infrastructure (server and database) may not be able to handle the load of success, even with a scalable system."

Several of those surveyed warned against buying more functionality than needed, lest users add unexpected administrative (or other) burdens. This corroborates our research suggesting that most Web CMS customers face a greater risk of over-buying than under-buying. As one person said: "Getting the right system to meet your needs is the trick, not getting a great system."

- Submitted by: Kas Thomas, Analyst

All CMS Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (customer service)

+1 617 763 5336 (int'l customer service)

Fax: +1 214 242 3048