I have, in the past, written about the importance of taking time away to enjoy the important things in life, like Baseball’s Opening Day. With this important day falling the Monday after Easter this year, I thought I would share one of the feelings common among baseball fans this week…
Hope.
There is continuing debate about whether or not WordPress is a CMS, which I have participated in already. There are two things fueling the debate:
So the fight continues. While I am in no way trying to resolve the argument in this post, I am trying to solve the crux of a matter….What is a CMS?
I recently dissected a “comparison” between Documentum and SharePoint. Karma was paying attention and I found myself performing a comparison of CenterStage and SharePoint for one of my long-time eRoom customers last week.
A little background. This client has had eRoom Enterprise since 2004. There has been some isolated success in some pockets of the organization, but not everywhere. The initial champions left during the deployment and there was no real concerted push to use the system afterwards. It had grown slowly over time, but hadn’t become a must-use system for many.
A while back, I discussed the Three Fundamental Use Cases for CMIS. Since then, there have been some additional thoughts on this topic. Since CMIS has been officially submitted as a standard to OASIS 🙂 I thought I would look at a couple of those thoughts.
The first was the EMC presentation on CMIS and DFS from the Momentum Europe in the fall. It presented four cases, most notably a Migration use case. This has popped-up in Twitter as well, so it obviously has some mindshare.
The other was a post by The Burton Group, specifically Larry Cannell, on How Will CMIS Be Adopted. Larry focused on the business applications and had some good thoughts, especially regarding CMIS Clients.
So I ranted a week ago about the term CMS. I was more upset how people used “CMS” than the term itself. Assuming that the term has legs, how does it fit in the grand scheme of things, like the world of ECM?
So today, instead of tearing things apart, I thought I would try and help add to the world. This will also let people tear my thoughts apart.
Enterprise Content Management is not a system. You can’t install it and expect it to just work. You can do that with systems, but ECM is a little more than that. It is the strategy to managing content in the organization. Have content, need control.
I last visited the definition of ECM around the New Year. Pulling the update from the comments and adding the word Strategy gives the following.
Enterprise Content Management (ECM) is a strategy for the coordinated management of all content throughout an organization, allowing for people and systems to find and use content from within any business context using platform agnostic standards.
Saw a tweet today that was pretty exciting. It was referencing a “comparison” between SharePoint and Documentum. I was initially excited. I’d love to see CenterStage and SharePoint compared. I compared SharePoint to eRoom a couple of years back and wasn’t planning on a comparison with CenterStage until the database/list functionality was ported over.
My excitement was short-lived.
I instead encountered a piece that resembles propaganda more than a fair and balanced comparison. That may sound harsh, but I will defend the charge.
When visiting a local company last month, I was given a glimpse of their requirements for their new Knowledge Services Framework vision and requirements. It was inspiring and incredible. They had mapped all the functions that they perform, identified existing systems that matched, and then had measured each of them to the following vision.
Here is their requirements as presented. The highlights are theirs.
leverage consumer applications proven to augment existing work processes (parity plus)
specifically targeted to business requirements and opportunities
access with only a browser and an internet connection
no reliance on proprietary systems or technology
development based on open industry standards
built upon a semantic web framework
embraces and enables BYOC model
no operating system dependency
provides web service capabilities
tuned options for mobile devices
no browser dependency
no net cost increase
no desktop footprint
100% cloud ready
The focus of this session is on use cases in using Social Networking in the Health IT world. I thought I would attend to see how these tools are being used here.
This is a rant. I rarely write rants, but here is one. It is based on one of my largest pet peeves in the technology industry. It is about a commonly accepted term and not about the people who use it.
It is about “CMS”. This is a term that for many is synonymous with Web Content Management. This just gives me the screaming heebie jeebies. Let me illustrate.
There has been a lot of debate of late on Twitter about whether or not WordPress is a CMS (ignoring the “WCM v CMS v ???” issue for now). Peter Monks is an proponent against the concept [Edit: He isn’t, see comments], as is Irina Guseva, a senior editor for CMS Wire. Ron Miller over at Fierce Content Management says that WordPress is a CMS and Tony Byrne at CMS Watch says it is for a simple reason: Many organizations are using WordPress as a CMS. That makes it a CMS.
That is a fallacious argument. I’ll explain why in a second, but some important facts. This blog, Word of Pie, is hosted by WordPress.com and I love it. If I decided to host the blog personally, I would use WordPress. For my blogging needs, it is perfect.
So do not read into any of this as an indictment against WordPress.
Word of Pie 