Thoughts on Day 3 will be coming later. Depending on my Internet access today, I may just do one big conference wrap-up later. It is always a strange day on Thursday as people start flying-out and more people are a little wiped out from the final party, though not as much this year, but that is another story. In the meantime, let’s see what Brian Quigley, Product Manager for the Interactive Content Group. The rest of the title is “What are the New Ways that Customers are Working with their Rich Media”.
WCM
Enterprise Content Management 2.0, Still in Beta
The Big Men on Content, Lee to be precise, recently joined the ECM 2.0 discussion, stating that they are going to wait for EMC’s sp2 before they jump on-board. That could be a long wait. After all, we are still in Beta as far as I am concerned.
This was prompted by a reading OpenText’s Enterprise 2.0 Content Management strategy. Note the placement of the 2.0. We’ll be getting back to that.
SharePoint for Web Content Management, The Movie
A month ago I invited people to attend the Washington, DC Web Content Mavens meeting for March to hear a Microsoft partner explain how SharePoint could be used for Web Content Management. Well, that day was yesterday then you missed a great presentation.
Before I dive in, I want to thank Rob Garrett of Portal Solutions, LLC for answering my questions and being, or at least appearing, honest regarding the ability of SharePoint to provide Web Content Management. He shared areas that weren’t perfect and agreed with me on some of the limitation issues with SharePoint when dealing with large enterprises. If I had to deploy a public facing website with SharePoint, I’d bring him on board to help out.
Of course, I’d probably never use SharePoint for such a purpose.
The Architecture and Features
To use SharePoint for a website, you need the full featured Office SharePoint Server (MOSS) and not the free SharePoint Services. In general you would setup a SharePoint Farm, consisting of one database server/cluster, multiple SharePoint/Web servers, and some sort of load balancer in the front.
SharePoint for Web Content Management
Before continuing, I’ll pause to let the laughter die down. Done yet? Don’t worry, I’ll wait…
Seriously, Microsoft continues to push SharePoint 2007 for Web Content Management. I’m sure it can be done, but it seems a bad fit. SharePoint’s primary weakness, in my opinion, is the inability to scale for the large Enterprise. Now imagine managing a large website. There are two options here:
- Host on SharePoint. Bad. Beyond bad. The security and scalability issues are challenging on a good day.
- Store an manage on SharePoint and publish out. Definitely not out-of-the-box. At a minimum, a WCM system should be able to handle this.
It appears that I’m not the only person that thinks that SharePoint isn’t a good fit for WCM. Janus Boye over at CMS Watch shared a couple of stories from some Danish companies that wanted to use SharePoint for WCM. They couldn’t find anyone that would do is for them, and one of them even asked Microsoft directly. The closest they got was one that offered to do it on SharePoint 2003!
X-Hive and the Content Server
On the 17th, I had the fortune of attending a briefing/seminar on X-Hive. It was a series of presentations given by Jeroen van Rotterdam, one of the founders and architects of X-Hive. Jeroen is now the General Manager of XML Solutions for EMC. I was able to learn more about the product and its future within the Content Server.
Defending Enterprise Content Management
So the other evening, I was out at a Web Content Mavens gathering, and someone asked me what I meant when I talked about ECM. This person had years of experience in Web Content Management and a few years working with a leading ECM provider before returning to their roots in WCM. His basic premise was that ECM was a marketing ploy cooked up by the vendors, analysts, and consultants out there and that there is no rational reason to force them all into one system.
This was, at the same time, one of the best, and most painful, conversations I have had in quite a while. On the one hand, it is good to have to occasional defend your convictions in order to make sure that they are still on solid ground. On the other hand, sometimes you want to hit your head into a wall when someone doesn’t get it. However, I can see why that opinion exists. The vendors and analysts are to blame.
The Web Content Mavens
At last weeks AIIM seminar, I was invited to attend a meetings of Web Content professionals in the DC area. I decided to attend, figuring that the worst case scenario would be a couple of pints and listening to someone ramble on about WCM. This was far from worst case.
What X-Hive Means to EMC’s Documentum
Back on July 12, X-Hive was acquired by EMC. At the time, I did a quick glance and was a little confused. I started wondering why they made the acquisition. This was worrisome as I hadn’t had that thought in years about any acquisition in the ECM industry. Maybe the new leadership of the Documentum unit didn’t have the same touch as those recently departed. After all, Documentum has traditionally worked with XML better than any of their major competitors. Even after a few weeks, I wasn’t the only one trying to figure this out. This acquisition seemed to be either an admission of weakness or a purely anti-competitive play. Then I learned some more.
Taxonomies, Good, Bad, or Ugly?
Sumanth Molakala posted a great look at determining the amount of effort that should go into creating a taxonomy for a new Enterprise Content Management solution. This brings up a debate that I have had/observed among ECM professionals for years. Do we make Search the primary access method, or the second? I find that every professional has a leaning, and I have yet to find a solid predictor for any practitioners’ preference.
I prefer a good hierarchy, while Sumanth appears to favor searching. I find that the creation of a hierarchy helps me organize my thoughts and determine what is important about any given piece of content. Also, while Google may be trying to take the world over via the Internet, most users are more intimate with their old-fashioned network file structures. The ability to browse to a piece of content adds to user acceptance of their first Document Management application. Over time, many users transition into Search-first users. Until that happens and ECM becomes transparent, I believe that a good taxonomy is important.
Redefining Enterprise Content Management
Several months ago, Russ Stalter posted on how he was Disillusioned with the Current Definition of ECM. Russ provides a new definition for ECM, which I believe is better, but still suffers some of the same deficiencies of the current definitions. Tower Software picked up on the thread, deriding the box-checking definitions out there.