Content management

From Wikipedia, the free encyclopedia

Jump to: navigation, search

Not to be confused with Information management or Knowledge management.

Content management (CM), is a set of processes and technologies that supports the collection, managing, and publishing of information in any form or medium. When stored and accessed via computers, this information may be more specifically referred to as digital content, or simply as content. Digital content may take the form of text (such as electronic documents), multimedia files (such as audio or video files), or any other file type that follows a content lifecycle requiring management. The process is complex enough to manage that several large and small commercial software vendors such as Interwoven and Microsoft offer content management software to control and automate significant aspects of the content lifecycle. .

Contents

 [hide] 

• 1 The process of content management
• 2 Implementation
• 3 See also
• 4 References
• 5 External links

The process of content management[edit]

Content management practices and goals vary by mission and by organizational governance structure. News organizations, e-commerce websites, and educational institutions all use content management, but in different ways. This leads to differences in terminology and in the names and number of steps in the process.
For example, some digital content is created by one or more authors. Over time that content may be edited. One or more individuals may provide some editorial oversight, approving the content for publication. Publishing may take many forms: it may be the act of "pushing" content out to others, or simply granting digital access rights to certain content to one or more individuals. Later that content may be superseded by another version of the content and thus retired or removed from use (as when this wiki page is modified).
Content management is an inherently collaborative process. It often consists of the following basic roles and responsibilities:

• Creator – responsible for creating and editing content.
• Editor – responsible for tuning the content message and the style of delivery, including translation and localization.
• Publisher – responsible for releasing the content for use.
• Administrator – responsible for managing access permissions to folders and files, usually accomplished by assigning access rights to user groups or roles. Admins may also assist and support users in various ways.
• Consumer, viewer or guest – the person who reads or otherwise takes in content after it is published or shared.

A critical aspect of content management is the ability to manage versions of content as it evolves (see also version control). Authors and editors often need to restore older versions of edited products due to a process failure or an undesirable series of edits.
Another equally important aspect of content management involves the creation, maintenance, and application of review standards. Each member of the content creation and review process has a unique role and set of responsibilities in the development or publication of the content. Each review team member requires clear and concise review standards. These must be maintained on an ongoing basis to ensure the long-term consistency and health of the knowledge base.
A content management system is a set of automated processes that may support the following features:

• Import and creation of documents and multimedia material
• Identification of all key users and their roles
• The ability to assign roles and responsibilities to different instances of content categories or types
• Definition of workflow tasks often coupled with messaging so that content managers are alerted to changes in content
• The ability to track and manage multiple versions of a single instance of content
• The ability to publish the content to a repository to support access

Increasingly, the repository is an inherent part of the system, and incorporates enterprise search and retrieval. Content management systems take the following forms:

• Web content management system—software for web site management (often what content management implicitly means)
• Output of a newspaper editorial staff organization
• Workflow for article publication
• Document management system
• single source content management system—content stored in chunks within a relational database
• Variant Management system—where personnel tag source content (usually text and graphics) to represent variants stored as single source "master" content modules, resolved to the desired variant at publication (for example: automobile owners manual content for 12 model years stored as single master content files and "called" by model year as needed)—often used in concert with database chunk storage (see above) for large content objects

Content management expert Marc Feldman defines three primary content management governance structures: localized, centralized, and federated—each having its unique strengths and weaknesses.^[1]
Localized Governance:
By putting control in the hands of those closest to the content, the context experts, localized governance models empower and unleash creativity. These benefits come, however, at the cost of a partial-to-total loss of managerial control and oversight.
Centralized Governance:
When the levers of control are strongly centralized, content management systems are capable of delivering an exceptionally clear and unified brand message. Moreover, centralized content management governance structures allow for a large number of cost-savings opportunities in large enterprises, realized, for example, (1) the avoidance of duplicated efforts in creating, editing, formatting, repurposing and archiving content, (2) through process management and the streamlining of all content related labor, and/or (3) through an orderly deployment or updating of the content management system.
Federated Governance:
Federated governance models potentially realize the benefits of both localized and centralized control while avoiding the weaknesses of both. While content management software systems are inherently structured to enable federated governance models, realizing these benefits can be difficult because it requires, for example, negotiating the boundaries of control with local managers and content creators. In the case of larger enterprises, in particular, the failure to fully implement or realize a federated governance structure equates to a failure to realize the full return on investment and cost savings that content management systems enable.

Implementation[edit]

Content management implementations must be able to manage content distributions and digital rights in content life cycle.^{[citation needed]} Content management systems are usually involved with digital rights management in order to control user access and digital rights. In this step, the read-only structures of digital rights management systems force some limitations on content management, as they do not allow authors to change protected content in their life cycle. Creating new content using managed (protected) content is also an issue that gets protected contents out of management controlling systems. A few content management implementations cover all these issues..^{[citation needed]}.

See also[edit]

• List of content management systems
• Enterprise content management
• Enterprise information management
• Content management system
• Content Management Website
• Information architecture
• Website architecture
• Web content lifecycle
• Website governance
• Web design
• Digital asset management
• Content engineering
• Content delivery
• Content Management Interoperability Services
• Single source publishing

References[edit]

1. Jump up ^ http://www.clickz.com/clickz/column/1715089/governance-issues-content-management

External links[edit]

• Boiko, Bob (2004-11-26). Content Management Bible. Wiley. p. 1176. ISBN 0-7645-7371-3. 
• Rockley, Ann (2002-10-27). Managing Enterprise Content: A Unified Content Strategy. New Riders Press. p. 592. ISBN 0-7357-1306-5. 
• Hackos, JoAnn T. (2002-02-14). Content Management for Dynamic Web Delivery. Wiley. p. 432. ISBN 0-471-08586-3. 
• Glushko, Robert J.; Tim McGrath (2005). Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services. MIT Press. p. 728. ISBN 0-262-57245-1. 

Retrieved from "http://en.wikipedia.org/w/index.php?title=Content_management&oldid=665261557"

Categories:

• Technical communication
• Data management