Commentary

Peter Hagopian
 

Content Management Acronym Soup

I was recently (justly) taken to task for assuming that readers of this blog would know what the acronyms in the content management space mean. Not just what the three- and four-letter acronyms we throw around stand for, but also what technologies and processes they actually represent. The funny thing is that even within the content management community, there isn't always agreement. So here's an attempt to try to demystify things a bit.

I was recently (justly) taken to task for assuming that readers of this blog would know what the acronyms in the content management space mean. Not just what the three- and four-letter acronyms we throw around stand for, but also what technologies and processes they actually represent. The funny thing is that even within the content management community, there isn't always agreement. So here's an attempt to try to demystify things a bit.• A content management system (CM or CMS) is software used to create and edit content, or in some cases manage existing content. It's often used to post materials to a Web site, but it also can be used within an organization to manage documents within a repository.

• A Web content management system (WCM or WCMS) is basically the same thing, but is generally limited to creating and posting materials on the Web. Blogging tools such as WordPress and Movable Type and systems such as Drupal and Joomla are examples of CMS and WCM tools.


More Business Intelligence Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

• A document management system (DM or DMS) is generally a searchable system used to store and keep track of documents, both as electronic files and scanned versions of paper documents. Some document management systems also include tools to help support workflow. This is particularly good for organizations with a high volume of documentation that needs to be easily searchable, as well as organizations with regulatory restrictions and requirements.

• Digital asset management (DAM) covers content and files of every imaginable type, including images, video and audio files, Microsoft Office files -- just about anything that can be electronically digitized. DAM usually refers to a hardware/software system that helps to store and manage these digitized files.

• Enterprise content management (ECM) tends to be a bit of a catch-all but generally refers to feature-rich systems that include content management and digital asset management components. ECM systems are usually fairly expensive and hardware intensive, and often require a significant level of IT experience to set up and run.

Prescient Digital Media's Web site has an interesting piece by Jed Cawthorne titled "CMS Or ECM -- What Is The Difference?" that does a good job of dissecting the two:

The first obvious difference we see here is that the CMS definition explicitly mentions software; it's a software system (or systems) for a specific use (managing and publishing content -- whatever that is!). On the other hand, the ECM definition mentions both strategies and tools.

Tip of the hat to Toby Ward's IntranetBlog.com, where I first read about Cawthorne's piece.

These definitions just scratch the surface of the jargon that comes up in the content management community, but hopefully it will help conversations and articles on the topic make a bit more sense. Did I miss anything, or is my definition different than yours? Let me know in the comments.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links