What are the enterprise trends in content management? This past month, I've given a lot of thought on the evolution of content management and social media in large organizations. Perhaps the amount of time I've recently spent on the plane traveling both coasts of the United States gave me too much reflecting time on this subject. Most of us understand the impact Enterprise 2.0 has had on enterprise content management, yet I feel like we're missing pieces to the puzzle. Luckily, there are a lot of smart people out there giving us clues to what the current enterprise trends are with content management.

While I was at DrupalCon last week, Chris Pliakas sent a tweet out that he used screenshots from CMS Report in his Apache Lucene presentation. I'm always flattered when this site gets noticed for something we're apparently doing right. In this particular case, we're using the contributed Drupal module Search Lucene API for our search engine as well as for faceted search and content recommendations (recommended links).

If you had talked to me a few years ago, I would have told you that the Search module that comes with the Drupal CMS is all a site like mine needs. After I became a beta tester for the Acquia Network along with their implementation of Apache Solr called Acquia Search, my opinion quickly changed. I'm now convinced that an enterprise quality search engine is truly something that can make or break your website. If you're a smaller Drupal site that feels like Solr or Acquia Search is overkill or not in your cost range, Search Lucene API may be the answer you've been looking for all this time.

The actual name of Chris' DrupalCon presentation is: "Build a Powerful Site Search with the User-Friendly, Easy-to-Install Search Lucene API Module Suite". The video of his presentation can be viewed at Archive.org and has been embedded above. Screenshots from CMSReport.com can be seen in the time frame from 19 minutes to 21 minutes.

I spent Sunday flying to San Francisco for this year's DrupalCon. Attending this Drupal conference is a first for me. For the past few years. I've wanted to attend the conference but either personal or professional distractions came up that prevented me from attending the conference. This year is my year for DrupalCon and I'm anxious to get to know the Drupal community better than I have in the past.

Five years ago, my wife and I had a dream. Together, we wanted to start a blog called "Like that Idea" and so we registered the domain LikethatIdea.com. The idea for the WordPress blog was to have a site where we could identify and review neat ideas which we thought others would like to read about. The ideas came in the form of products, books, movies, services, and interesting article that we read ourselves. In the end though, we ran out of ideas to write about and the site never really took off.

By the time many of you read this post, Like that Idea will be never more. I'm currently working on wiping the site off the server. It's time to say goodbye to one of the few joint Internet projects that my wife and I worked on together. Instead, we'll use the time to work on our own personal projects as well as working jointly on the biggest project of our lifetime, our family.

Below the fold is a post I couldn't help but transfer from LikethatIdea.com over to this site. Thinking back at this moment in time still puts a smile on my face.

This week I have been thinking a lot about how poorly we manage data and information. The quality of the data and the lack of needed data has historically been an issue at work. We have focused a lot of our time on data mining but never really recognized that one day there would be too much data and information for our staff to sift through. Recently, our managers proposed two new data sources for the operational staff to review and I decided that it was time to hit the panic button that we're currently giving out more information to our workers than they can handle.

When a business presents too much information to their staff it is a lot like catching deer in your headlights. If the deer is too overwhelmed to run and you don't steer the car out of the way then no good can come to both car and deer. This is where I think we are at work and we're needing to slow things down a bit to give both driver and deer time to think about their next move. For the moment at least, I'm personally at a lost on how best to solve our issues with information overload.

Who really defines what is a CMS?

You do.

I'm more convinced than ever that CMS experts aren't really in the driver's seat when defining the content management system. Experts in the field of content management are more or less observant passengers that are there to help you not get lost and to point out the significant landmarks on the way. This journey takes you to places while you the customer remain in the driver seat with all the privileges and responsibilities of being the driver.

Over the past few years I've realized that my work preference is to keep things as simple as possible. Sometimes when defining information systems keeping things simple works while other times the system is new and remains too complicated to define. Thanks to my reply in a productive rant against CMS by Laurence Hart I'm not only understanding my aversion to being called a CMS expert but also my philosophy and role in defining what is a CMS. This personal philosophy is developing...

Scott Abel convinced me a few years ago on my own blog that the definition of a CMS is never static and always changing. We’re chasing our own tail when we get nit picky in our definitions of a CMS. Somewhere in all the marketing that has been done for terms such as CMS, ECM, and WCM…we have forgotten the difference between information system and information technology.

Rita McGrath at Harvard Business Review has written a blog post on why she hates micropayments.  Micropayments are financial transactions involving very small sums of money (see Wikipedia). For online publishing, a small fee would allow you to view the content for a certain period of time or for a certain number of articles.

Personally, I'm not sold on the concept of micropayments for content which is probably why I was lured to Ms. McGrath's article in the first place.

The idea has been around a long time — at least since the mid-to-late 90s — with both supporters and detractors weighing in. Millions have been lost by companies seeking to capitalize on streams of micropayments, almost all of which eventually crashed and burned. Myself, when confronted with a request to chip in 99 cents for a one-time glimpse at an article or $2.99 for a week's worth (as some of my local newspapers are doing) — well, I close that window and go away.

The author of the article discusses further the importance for any payment system adopted to consider "how the payment link of customers' consumption chains fits into their total experience". Micropayment systems have a tall order in that they need to be seamless, transparent, and achieve inevitability. Even grimmer for publishers, it's not only the micropayment experience that needs to be improved but also the non-micropayment systems too.

For the past few years, I've paid a yearly subscription to the Wall Street Journal for the print publication and the online subscription. With my yearly renewal coming up very soon, I've decided to discontinue my online subscription to the WSJ. Why would I do that? There are some very basic reasons to why I'm dropping WSJ.com. I rarely find myself reading the online content of the WSJ. I either already read the stories in the print version of the WSJ or I have found myself already familiar with the news story because I read a similar story posted elsewhere online. Stopping by the WSJ.com, unlike CNN or FoxNews, never became a daily ritual for me.

A couple years ago, Jeff Whatcott introduced to me the concept of a social publishing system. Within minutes after reading his article, I knew I wanted to expand further on his idea of social publishing and discuss the potential impact social publishing would have on content management systems. During this time period, Andrew McAfee was continuing to observe the emergence of Enterprise 2.0 into the normal day to day business world. From these two moments, I couldn't help myself from dreaming of the opportunities I had before me to learn more about social publishing and collaboration tools.