These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Content Management System
- Data model
The tables behind Content Management System
Content Management System ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 14
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Definitions and people
Organizations own category definitions and people.
Editorial work
A content item belongs to an organization, owner and category; revisions belong to the item.
Review and evidence
Documents, review decisions, follow-up actions and state history refer back to the item.
Execution trace
Runs and attempts refer to the item; steps belong to a run.
Every table, by feature
- Content categories
Published content categories and editorial definitions offered by an organization.
Linked to Organizations - Organizations
Agencies, departments and service organizations that own public services and cases.
- Content items
Editorial content items tracked through revision capture, independent review and publication.
Linked to Organizations, People, Content categories - Source mappings
Reviewed field mappings and transform rules between source payloads and target fields.
Linked to Content categories
- Content items
Editorial content items tracked through revision capture, independent review and publication.
Linked to Organizations, People, Content categories - Content categories
Published content categories and editorial definitions offered by an organization.
Linked to Organizations - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations - Organizations
Agencies, departments and service organizations that own public services and cases.
- State history
Immutable workflow-written status transition history for each case.
Linked to Content items, People
- Content revisions
Observation-level revision, document and line detail captured against a content item.
Linked to Content items - Content items
Editorial content items tracked through revision capture, independent review and publication.
Linked to Organizations, People, Content categories - Evidence documents
Uploaded and verified supporting documents and source evidence.
Linked to Content items, People - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Content items, People
- Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Content items, People - Content items
Editorial content items tracked through revision capture, independent review and publication.
Linked to Organizations, People, Content categories - Content revisions
Observation-level revision, document and line detail captured against a content item.
Linked to Content items - Evidence documents
Uploaded and verified supporting documents and source evidence.
Linked to Content items, People - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations
- Content items
Editorial content items tracked through revision capture, independent review and publication.
Linked to Organizations, People, Content categories - Operation runs
Workflow-maintained execution runs with operation key, input hash and persisted result reference.
Linked to Content items - Operation steps
Ordered steps inside an operation run with input, output and external receipt state.
Linked to Operation runs - Execution attempts
Each recorded attempt to execute an approved action for a content item.
Linked to Content items - State history
Immutable workflow-written status transition history for each case.
Linked to Content items, People
- Follow up actions
Assigned outstanding actions, corrections and outstanding requests for a case.
Linked to Content items, People - Content items
Editorial content items tracked through revision capture, independent review and publication.
Linked to Organizations, People, Content categories - Content revisions
Observation-level revision, document and line detail captured against a content item.
Linked to Content items - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Content items, People - State history
Immutable workflow-written status transition history for each case.
Linked to Content items, People
Keys and references
Use the content item number for human handoffs and its internal identifier for record links. Each revision has a source record ID and parent item. A review decision records the source revision it decided. An operation run also stores its source revision, operation key and input hash so a result can be reconciled with the intended input. The relationships below show the exact references.
Migration order
- Organizations and people. Establish owning organizations and the people who prepare, review and own content.
- Definitions. Add category definitions and any source mappings required for those definitions.
- Items. Bring in content items with owners, categories, dates and current states.
- History. Link revisions, evidence, decisions, actions and state history to each item.
- Execution results. Attach runs, steps and attempts only where their source and result references can be reconciled.
Set up Content Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.