<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sethuiyer.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Typical features of a CMS solution</title><link>http://sethuiyer.com/wikis/content-management/typical-features-of-a-cms-solution.aspx</link><description>This wiki is a distillation of the key concepts of Content Management Systems based on experiences from the field.  Since the advent of WCMS in late 90’s the products and the market have undergone many changes. Many of the terminologies that we have come to accept as standards, have evolved over time, including the terms Web 2.0, Semantic Web and Social Media. All of these whether blogs, wikis or forums are based on the foundation of a CMS solution.</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 SP1 (Build: 31106.3070)</generator><item><title>Typical features of a CMS solution</title><link>http://sethuiyer.com/wikis/content-management/typical-features-of-a-cms-solution.aspx</link><pubDate>Sat, 21 Mar 2009 03:54:58 GMT</pubDate><guid isPermaLink="false">9e0003b4-e479-46e1-a57a-5cb54f303b0f:5</guid><dc:creator>Sethu Iyer</dc:creator><comments>http://sethuiyer.com/wikis/content-management/typical-features-of-a-cms-solution/comments.aspx</comments><description>Current revision posted to Content Management by Sethu Iyer on 3/20/2009 8:54:58 PM&lt;br /&gt;
&lt;p&gt;Some of the
basic features available in most content management systems include
&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;b&gt;Content Creation Capability:&lt;/b&gt; The core feature of a
content management system is the ability for users to create and manage
content. Most content management systems provide this capability through an
editing interface also known as a content input form (CIF). For enterprise
class content management systems these CIF are configurable and would contain
one or many form fields including fields for capturing content metadata such as
authors name, date, and embedded WYSIWYG editing interface for editors to
create and edit content.&amp;nbsp; &lt;br /&gt;Content Acquisition/Consumption: This can be defined as
the ability to consume structured and unstructured content from third party
sources. For example ability to directly consume Microsoft Word documents, PDF
documents etc.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Content Transformation:&lt;/b&gt; is typically referred to as
transformation of XML through XSLT, but can also mean the ability for on demand
PDF conversions (on the fly), dynamic content assembly such as content from a
database and file system assembled to provide a single unified view to the
end-user etc., or in the world of digital asset management could mean
resampling of image and audio files to transcoding of video to multiple
formats.&lt;/li&gt;
&lt;li&gt;
&lt;b&gt;Library Services:&lt;/b&gt; this includes capability such as
check-in and check-out of content to ensure there are no conflicts during content
editing, and multi-stage content approvals.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Versions:&lt;/b&gt; ability to store multiple versions of the
same content object with capability to roll back to previous versions as and
when required. Many CMS solutions also provide capabilities for visual comparison
of versions.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Workflow:&lt;/b&gt; is the process used to manage content through
its life cycle from content creation, authoring to content reviews (example
editorial review, technical review, and legal review) through to publishing and
ensuring the content is retired on its expiration date. &lt;/li&gt;
&lt;li&gt;&lt;b&gt;Audit Trails:&lt;/b&gt; ability to log any changes made to a
content item such as edits, deletes, versions changes etc.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Notifications:&lt;/b&gt; these are triggers sent out based on
predefined events such as content edits, or for notifying any workflow tasks.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Search:&lt;/b&gt; &amp;nbsp;ability
for users to search based on various attributes such as content title, metadata,
author, publish date, content body etc. &lt;/li&gt;
&lt;li&gt;&lt;b&gt;Metadata Management:&lt;/b&gt; &amp;nbsp;ability to appropriately tag a content item
such that it can be easily classified and categorized. Extensible metadata
management ensures easier content storage and retrieval.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Taxonomy/Categorization:&lt;/b&gt; ability to categorize content
based on predefined attributes. There are several types of taxonomies but the
typical ones are the hierarchal organization of content based on a parent child
relationship. Some search engines too have capabilities to dynamically generate
taxonomies based on occurrences of frequently used tags and keywords. &lt;/li&gt;
&lt;li&gt;&lt;b&gt;Publishing:&lt;/b&gt; &amp;nbsp;is
the process of delivering the content to the right end-point (or website) such
that users may be able to view the content. The end-points in this case are
also known as Content Delivery Applications (CDA). This is one of the core
features of a content management system. High-end or enterprise class content
management systems are capable of delivering content to multiple
end-points/sites, while in the lower end ones the Content Management and
Delivery happens in the same application.There are
several checks and controls required when publishing involves physical delivery
of content from a CDA to CMA. This includes capabilities such as guaranteed content
delivery, automatic error handling, ability to configure publishing queues etc.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Archival:&lt;/b&gt; &amp;nbsp;this
is the ability to store the content after its expiration date to an archival
database prior to its disposition.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Disposition: &lt;/b&gt;&amp;nbsp;is
the process of removing content objects from a datastore at on a predefined
schedule after expiration. Legal/Compliance needs may dictate the need for an
objective evidence of content disposition.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Analytics:&lt;/b&gt; &amp;nbsp;there
are several type of analytics such as content operational metrics to web
analytics. Operational Metrics show the efficiencies of the content management
process such as the cycle time from content creation to publishing clearly
identifying bottlenecks in the process. Web Analytics shows statistics such as content
usage, most used content; least used content, general traffic patterns, page
views, number of hits etc. This is usually done with a web-analytics tool, and
some of the high end tools have capabilities to narrow down collection of data
for individual page elements/components, and may be used for marketing purposes
such as A/B tests and multivariate testing etc.&lt;/li&gt;
&lt;li&gt;&lt;b&gt;Security:&lt;/b&gt; Content security has several connotations,
but at a minimum it means the ability to ensure that only user with sufficient
privileges are allowed to see content items that they are entitled to.
Typically content management systems filter the content based on user
privileges that are stored to database or LDAP repository. &lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description></item></channel></rss>
