Content Retirement
- Content Retirement
- the
content management
task during which obsolete
content is removed from one or more
systems or
applications and optionally archived for future use
As illustrated in the preceding figure, Content Retirement is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Task
- Subclasses:
The typical responsibilities of Content Retirement are to:
- Remove obsolete content from applications and access by their users.
- Archive potentially reusable obsolete content for possible future reuse.
Content retirement typically can begin when the following
preconditions hold:
Content retirement is typically complete when the following
postconditions hold:
Content retirement typically involves the following teams
performing the following steps in an iterative, incremental,
parallel, and time-boxed manner:
Content retirement can be performed using the following
techniques:
- Tagged data (metadata)
- Reuse
Content retirement typically results in the production of
the following work products:
- Content retirement should be performed iteratively,
incrementally, and in parallel with the other content
management tasks during the usage phase.
- Content retirement is an ongoing task during the usage
phase, with content being retired as it becomes obsolete.
Thus, content retirement should not be deferred until the
retirement phase.
- There is potential overlap between this task and the
retire data components task of the retirement activity.