CMIS

The level of interest in content management systems astounds me. Each year, I continue to see at CMS Report an increase of visitors looking for information on content management. Our stories tend to focus on open source CMS more than proprietary applications and evidently that's the subject matter that our readers want to read.

Below are the top ten stories of 2009 that were posted here at CMSReport.com. As you can see, stories involving Drupal, WordPress, Joomla!, Alfresco, and Nuxeo took center stage. These stories might not have been the ten I would have personally picked for this list, but I'll respect the numbers behind their ranking.

1. Mollom: A solution for comment spam
2. 2009 Best Open Source PHP CMS: Drupal wins, Wordpress and Joomla! not far behind
3. Serving a home for my Drupal site
4. WordPress leads the Packt as 2009 Overall Best Open Source CMS
5. Allen Ellis: Why the Packt CMS Competition is Broken, and How to Fix It
6. Google PageRank
7. Alfresco Module Obtains U.S. DoD 5015.02 Records Management Certification
8. Using Wordpress city saves $19,000
9. Cheryl McKinnon, Nuxeo, and Open Source
10. Drupal Gardens preview video by Acquia

The interest in Nuxeo took me by surprise and I'll be adding the CMS to my top 30 CMS Focus page as time allows. As always, our thanks to all those who continue to return to this site to read the stories, join in on the conversation, and even submit articles. As I've said before, I'm not sure we would be doing this if it wasn't for the interest shown by others visiting the site.

I'm one of the many CMS enthusiasts excited about CMIS. CMIS is the abbreviation for the OASIS Content Management Interoperability Services (CMIS). Please check AIIM's official guide to CMIS for further details.

Before you do go over to AIIM's site, you might want to also check out Stefan Waldhauser's 8 reasons why CMIS will transform the ECM industry posted at Digital Landfill. I like reason number four:

4 -- No more lock-in to one ECM-vendor because of CMIS.

Until today the ECM industry was driven by high complexity and proprietary systems that prevented to switch to other vendors. Even when a vendor dramatically increased maintenance fees (many customers know what I’m speaking about) there often was no choice to go somewhere else because of the tight and proprietary integrations between the customer build applications and the ECM-infrastructure. CMIS will help separate the applications from the ECM-platform and so there will be no more lock-in to one vendor. Doesn’t that sound great?

I think the biggest thing CMIS offers is customer satisfaction in not having to choose one vendor over another. As I stated this morning on Twitter, I see CMIS as recognition that the "total enterprise solution" is a lie. I have yet to see an enterprise software package provide the complete solution that vendors often promise their customers. Somewhere in the product's life cycle the customer finds that they need more than what the current software and/or vendor can deliver but the customer also isn't ready to leave their current system behind. CMIS hopes to solve the migration issues involved with moving from one application to another by allowing both applications to work together.

There is a cost issue here with CMIS though and, so far, I haven't seem much dicussion on the subject. While CMIS allows more than one application to share and work with the content it will not always reduce costs and maintenance fees. The fact is CMIS may now require the customer to provide ongoing support for multiple applications and platforms instead of the single platform they were once supporting. In general, when the customer's IT group has to support additional applications they also need additional time and money required to provide that support. Just like the problem CMIS is trying to solve, CMIS will not always be the total solution to your problems.

Barb Mosher has written a great summary at CMS Wire on Google's new Sites API which allows content owners to move content in and out Google Sites. As Mosher points out, this new API and some additional tools will allow content owners to "pull stuff out of SharePoint and place it into Google Sites" which is sure to bring "real heat between Redmond and Mountain View" in their quest for customers.

Until now, content and data inside Google Sites stayed inside Google Sites. And there was no easy way to migrate additional content and data into it. With the introduction of the Google Sites Data API, that has changed.

The API support almost all of the functionality currently available within Google Sites including:

• Retrieve, create, modify, and delete pages and content.
• Upload/download attachments.
• Review the revision history across a site.
• Display recent user activity.

Which brings us to the point. With these new capabilities, you can now not only move data out of Google Sites, but you can move data into Google Sites and possibly out of other similar applications, like SharePoint.

Whether Google Sites and the new API will be a threat to Microsoft and SharePoint is questionable. But, once again I think these type of events emphasize that those content management systems that get the most attention from us these days are those applications that open up and work with other third party applications.

There is a reason why such topics as CMIS, open source, and API are in the spotlight with folks interested in content management. No one really wants to be stuck with a vendor that doesn't play well with others. It just strategically isn't a good idea to have your content controlled by a single vendor, so why do it? I suppose I'm rhetorically asking that question to both customers and vendors.