Skip to content

Lesson 7 — Lifecycle Activities & Supporting Tools

Chapter 9 groups operating work into three activity families.

1. Plan for Lifecycle Management

  1. Plan for Records Management — define record criteria, inventory sources/formats, identify copies of record, storage/archive needs and obligations.
  2. Develop a Content Strategy — align audiences, objectives, ownership, lifecycle, reuse and delivery.
  3. Create Content Handling Policies — define use, ownership, access/security, retention/disposal, versioning, social media, devices/BYOD, sensitive information and litigation response.
  4. Define Content Information Architecture — Metadata, vocabulary, taxonomy/ontology, navigation, search and retrieval structure.

2. Manage the Lifecycle

  1. Capture Records and Content with enough Metadata/classification from the beginning.
  2. Manage Versioning and Control appropriate to risk.
  3. Backup and Recovery for operational protection.
  4. Manage Retention and Disposal, including archive and holds.
  5. Audit Documents and Records to test whether controls actually operate.

3. Publish and Deliver

  1. Provide Access, Search and Retrieval.
  2. Deliver Through Acceptable Channels while preserving rights, version and lifecycle consistency.

Supporting capabilities

DMS: capture/index/store/check-in/check-out/version/workflow/rights/retrieval for documents.
Records Management System: formal record classification, retention, legal/compliance, archive and disposition.
CMS: creation, organization, workflow, publication and reuse of content.
Workflow: routing, assignments, approvals, escalation and status tracking.
ECM: enterprise coordination of multiple content capabilities and processes.

Formats/semantic technologies

  • XML: explicit markup/tags and schemas; supports structured exchange.
  • JSON: lightweight text interchange format.
  • RDF: subject–predicate–object style resource relationships.
  • SKOS/OWL: knowledge structures / ontologies and richer semantic representation.

Exam priority is purpose and distinction, not coding syntax.

Source: pp. 306–323.

← Previous · Next →