Content and Versions

A content item has a title, type, due date, publication time, status, project and owner. The producer uses it to follow a piece from Draft through Editing and Review to Approved, Published or Archived. The project reference places the item within the broader production effort, while its People owner identifies who should answer questions about the current version.

Content files holds attached file versions. Each file belongs to one content item and records a version, upload time and reviewer attribution. The file count on the content item helps a reader see when another version was added, but the attached version is the object the editor should inspect. Approval of a content item is meaningful only when the decision is tied to the exact version under review.

The producer prepares and submits; the editor reviews and publishes.

• Name the item. Use the title and content type to make work identifiable.
• Keep versions attached. Add the file under its parent item, with its version and upload time.
• Decide on the reviewed version. Check the attached file and rights coverage before approval.

Agree a version naming convention and define when a content item moves into Review. Decide who is allowed to attribute approval to a reviewer and how a revised attachment returns for review. Prepare an example where the producer uploads an initial version, receives a correction and uploads a second version. The team should be able to identify which version an editor accepted without guessing from the latest filename.

A producer creates an interview segment under a project and marks it Draft. The producer edits it, uploads a file marked with a version and moves the item into Review. The editor checks the submitted version and the linked rights agreement for the planned use. If corrections are needed, the producer can attach another version while retaining the earlier one. Once the exact version is accepted, the content item can be Approved.

For publication, the editor checks that the item is approved and that the rights window covers the use. The publication time records the acknowledged release. A linked production task can then be completed. The content item’s Published status should reflect that sequence, not merely a file upload.

• Content Lifecycle Board — See items grouped by their current content status.
• Content Awaiting Review — Find items ready for editorial and rights checks.
• Projects in Production — Follow the related project’s schedule and owner.

• Version and rights review: Check the exact submitted version and permitted use.
• Content production: See the surrounding project work.

Review the data model before importing older content versions.