Revision and version management

Overview

Based on a model of storing saved changes, PageSeeder creates an auditable history of every structural and content edit, including moved fragments. With different presentation options for different use cases, changes can be presented according to:

  • Content changes between any two document versions,
  • Structural changes between any two document versions including inserted and deleted fragments,
  • All edits to a particular fragment including incoming cross-references,
  • Document changes according to versions created by multiple parent publications.

Developers

Access revision and version functionality from API services or batch API (Publisher). Add a version on upload to create, or overwrite, content. Publish or rollback to previous versions.

Access change history or metadata to create new views of the content lifecycle (see Comment table).

Analysts

Present changes to stakeholders in format optimized for productivity or usability. Views such as an automatically generated “comment table” can reduce reviews to only the changes and comments, rather than presenting entire documents. Semantics or commit comments can improve auditing. Get genuine reuse of content by versioning “shared” documents according to each publication that includes them. Enforce the capture of edit notes for each change committed.

Users

Create versions for a complete publication with one command. Find all edits by person, date or location.

Track Changes

Compare

Compare versions of the same document or different documents side-by-side.

Structural changes

Check any structural changes made in the document.

Shared Components

Publication versions

Check the version for the whole publication.

Status

Status is a value that can be assigned to a document using a workflow or task. The document status applies to the workflow associated with the document. The status of the last workflow step is the status of the document. The task status applies to comments in a discussion. The status of the last comment is the status of the task.

Workflow

A workflow is a special type of task that uses document status values (e.g. Initiated, In Progress, Complete, Approved, Terminated). There can only be one workflow per document and the status of the document is the workflow status. It can have a current priority, due date and assigned to like other tasks and can use comment labels. Workflows can be created on multiple documents at the same time (using batch processing), but they are independent from each other.