World Library  
Flag as Inappropriate
Email this Article

Web content lifecycle

 

Web content lifecycle

The web content lifecycle is the multi-disciplinary and often complex process that web content undergoes as it is managed through various publishing stages.

Authors describe multiple "stages" (or "phases") in the web content lifecycle, along with a set of capabilities—such as records management, digital asset management, collaboration, and version control—that may be supported by various technologies and processes. One recognized technology for managing the web content lifecycle is a web content management system.[1]

Concepts often considered in the web content lifecycle include project management, information management, information architecture, and, more recently, content strategy, website governance, and semantic publishing.

Contents

  • Stages 1
    • Two stages 1.1
    • Three stages 1.2
    • Four stages 1.3
    • Five stages 1.4
    • Six stages 1.5
    • Seven stages 1.6
    • Governance rather than workflow 1.7
  • Role of technologies 2
  • Role of information management 3
  • See also 4
  • References 5
  • Further reading 6
  • External links 7

Stages

Various authors have proposed different "stages" or "phases" in the content lifecycle. Broadly speaking, the stages include content creation/development, revision, distribution, and archiving. The lifecycle processes, actions, content status, and content management roles may differ from model to model based on organizational strategies, needs, requirements, and capabilities.

Two stages

In 2003, McKeever[2] described "two iterative phases": "the collection of content, and the delivery or publishing of that content on the Web." She also explains a Web Content Management (WCM) "four layer hierarchy"—content, activity, outlet, and audience—intended to illustrate the breadth of WCM.

Three stages

Bob Boiko's Content Management Bible[3] emphasizes three major parts: collect (creation and editing is much more than simply collecting), manage (workflows, approvals, versioning, repository, etc.), and publish. These concepts are graphically displayed in a Content Management Possibilities poster[4] developed by Boiko. The poster details such content management concepts as metadata, syndication, workflows, repositories, and databases.

Gerry McGovern also sees three "processes," designating them creation, editing, and publishing.[5]

Four stages

JoAnn Hackos' Content Management for Dynamic Web Delivery[6] argues for four "components": authoring, repository, assembly/linking, and publishing.

In Managing Enterprise Content,[7] Ann Rockley argues for the planning of content reuse through four stages: create, review, manage, deliver. A stage can have sub-stages; for example, the "create" stage has three sub-stages: planning, design, and authoring and revision. She notes that content is often created by individuals working in isolation inside an enterprise (the coined term is the Content Silo Trap). To counter this content silo effect, she recommends using a "unified content strategy," "a repeatable method of identifying all content requirements up front, creating consistently structured content for reuse, managing that content in a definitive source, and assembling content on demand to meet your customers’ needs."[8]

Five stages

Nakano described five "collaboration operations": Submit, Compare, Update, Merge, and Publish.[9]

The State government of Victoria (Australia) produced a flowchart with a diagrammatic view of the web content lifecycle with five stages: Develop, Quality Approval, Publish, Unpublish, and Archive. Some of the stages include sub-stages (for example, Archive consists of Storage, Archived, and Disposed) intended to further delineate content status. In addition, this model depicts three aspects—Status, Process, and Roles—as part of the flow for web content. The four roles in this model are content author, content quality manager, business quality manager, and records manager.[10]

The AIIM speaks of managing content “to achieve business goals”.[11] AIIM ECM 101 Poster from 2003, and the AIIM Solving the ECM Puzzle Poster from 2005, present the same five stages: Capture, Manage, Store, Deliver, Preserve.[12]

Six stages

The Content Management Lifecycle Poster[12] devised by CM Pros suggests six "steps":

  1. Plan
  2. Develop
  3. Manage
  4. Deploy
  5. Preserve
  6. Evaluate

Each step contains sub-steps. For example, step 1, Plan, consists of Align, Analyze, Model, and Design; and step 2, Develop, consists of Create, Capture, Collect, Categorize, and Edit.

Seven stages

Bob Doyle[13] suggests seven stages of the Web content lifecycle:

  1. Organization
  2. Creation
  3. Storage
  4. Workflow
  5. Versioning
  6. Publishing
  7. Archives

Doyle argues for seven stages based on the psychologist "seven plus or minus two " limit on human information processing. He notes this is merely a suggestion and that one should "add or subtract a couple of your own favorites."

Governance rather than workflow

In a 2005 article, Woods[14] addressed governance of the content lifecycle. In his model, there are categories of issues to address, rather than a simple, cradle-to-grave pathway. He writes that most content governance questions fall into one of the following categories:

  • Legacy Content Migration
  • Template Considerations
  • New Content Creation
  • Content Modification and Reuse
  • Version Control and Site Rollback
  • Content Rotation and the End of the Road
  • Monitoring Progress, Managing for Success

More recently, Halvorson has humorously suggested 15 discrete steps in the web content lifecycle: Audit, Analyze, Strategize, Categorize, Structure, Create, Revise, Revise, Revise, Approve, Tag, Format, Publish, Update, Archive.[15]

Role of technologies

Enterprise content management as a business strategy might incorporate web content management:

When integrated with an ECM system, WCM enables organizations to automate the complete Web content lifecycle. As soon as new content is developed, the system ensures that it goes live the moment it is intended to—not a minute earlier. By specifying timed releases and expiration dates, content is published to and removed from the Web according to recommendations, requirements and even regulations.
—Jenkins (2004)[1]

A web content management system can support and enhance certain processes because of automation, including document management, templates, and workflow management. However, the absence of well defined roles and process governance will greatly dilute the effectiveness of any technology intended to augment/enhance the publishing process overall.

Role of information management

[16] The goal of information lifecycle management is to use policies, operations, and infrastructure to manage information throughout its useful life. However, businesses struggle to manage their data and information.[17][18][19]

The missing stage in all the major sources is the organization of information, structuring it where possible, for example using XML or RDF, which allows arbitrary metadata to be added to all information elements. This is the secret that the knowledge managers describe as turning mere data or information into knowledge. It allows information to be retrieved in a number of ways and reused or repurposed in many more.
—Doyle (2005)[13]

Using semantic markup in the publishing process is part of semantic publishing. Tim-Berners Lee's original vision for the Semantic Web has yet to be realized, but many projects in various research areas are underway.

See also

References

  1. ^ a b Jenkins, Tom; Glazer, David; Schaper, Hartmut (2004). Enterprise Content Management Technology: What You Need to Know. Waterloo, Ontario, Canada: Open Text Corporation. p. 300.  
  2. ^  
  3. ^ Boiko, Bob (2004). Content Management Bible (2nd ed.). Hoboken, NJ: Wiley. p. 1176.  
  4. ^ "The Content Management Possibilities Poster". Metatorial Services, Inc. Retrieved 20 July 2010. 
  5. ^ McGovern, Gerry; Norton, Rob (2001). Content Critical. Upper Saddle River, NJ: FT Press. p. 256.  
  6. ^ Hackos, JoAnn (2002). Content Management for Dynamic Web Delivery. Hoboken, NJ: Wiley. p. 432.  
  7. ^ Rockley, Ann (2002). Managing Enterprise Content: A Unified Content Strategy. Reading, Mass: New Riders Press. p. 592.  
  8. ^ "What is a Unified Content Strategy?". The Rockley Group. Retrieved 20 July 2010. 
  9. ^ Nakano, Russell (2002). Web content management: a collaborative approach. Boston: Addison Wesley Professional. p. 222.  
  10. ^ "Web Content Lifecycle". State Government, Victoria, Australia. November 2005. Retrieved 29 June 2010. 
  11. ^ "What is ECM?". AIIM. Retrieved 20 July 2010. 
  12. ^ a b "CM Lifecycle Poster". Content Management Professionals. Retrieved 20 July 2010. 
  13. ^ a b Bob Doyle (September 2005). "Seven Stages of the CM Lifecycle". EcontentMag.com. Retrieved 20 July 2010. 
  14. ^ Randy Woods (September 2005). "Defining a Model for Content Governance". Retrieved 22 July 2010. 
  15. ^ Halvorson, Kristina (2009). Content Strategy for the Web. Reading, Mass: New Riders Press. p. 192.  
  16. ^ "What is Information Management?". AIIM. Retrieved 24 July 2010. 
  17. ^ Aaron Zornes (May–June 2010). "10 Key Trends in MDM". Information Management. Retrieved 23 July 2010. 
  18. ^ Helen D'Antoni (August 1, 2001). "Companies Struggle With Data Classification". Information Week. Retrieved 23 July 2010. 
  19. ^ Ladley, John (2010). Making Enterprise Information Management (EIM) Work for Business: A Guide to Understanding Information as an Asset. Burlington, MA: Morgan Kaufmann. p. 552.  

Further reading

  • In an April 2009 research article Semantic Publishing: the coming revolution in scientific journal publishing, David Shotton described recent developments in Web technologies can be used for semantic enhancement of scholarly journal articles.

External links

  • CM Pros' CM Lifecycle poster
  • The Content Management Possibilities Poster
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 



Copyright © World Library Foundation. All rights reserved. eBooks from World eBook Library are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.