Content Approval
- Content Approval
- the
content management
task during which edited
content is approved and therefore authorized for publication to one or more
applications
As illustrated in the preceding figure, Content Approval is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Task
- Subclasses:
The typical responsibilities of Content Approval are to:
- Ensure that the content has been properly edited (if
necessary).
- Ensure that edited content is correct and
appropriate.
- Ensure that edited content is ready for publication prior
to being published.
Content approval can typically begin when the following
preconditions hold:
Content approval is typically complete when the following
postconditions hold:
- All content is approved (i.e., content approval is an
ongoing task).
- The
retirement phase has started.
Content approval typically involves the following teams
performing the following steps in an iterative, incremental,
parallel, and time-boxed manner:
-
Content Management Team:
- Obtain edited content from the
draft content database.
- Evaluate the edited content.
- Approve or disapprove the edited content for
publication.
- Update the status of the content‘s metadata in
the
content metadata database.
- If approved, transfer the content to the
published metadata database.
- If disapproved, either:
- Notify the content creator, content translator, or
content editor to have the necessary changes made.
- Delete the content from the draft content database if
the content should never be published.
Content approval typically can be performed using the
following techniques:
Work Products
Content approval typically results in the production of the
following work products:
-
Data Components:
- Approved or disapproved Content:
- Textual content.
- Numerical content.
- Audio content.
- Graphical content.
- Video content.
- Updated Content Metadata
- Content approval should be performed iteratively,
incrementally, and in parallel with other content management
tasks.
- Content approval may not be necessary if all content is
in essence preapproved (e.g., product catalog data from
legacy content sources or news feeds from external content
sources).