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.
- E-library / Digital Repository
- Data model and import order
The tables behind E-library / Digital Repository
E-library / Digital Repository 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
Content intake:
Content items links Organizations, Projects and People to the submitted item.
Requirements and evidence:
Application requirements and content files belong to content items; content files also names its verifier in People.
Independent review:
Review decisions belongs to content items and names a reviewer in People.
Tasks and corrections:
Production tasks belongs to content items and names its assignee in People; state history preserves the item's transitions and actor.
Delivery and execution:
Execution attempts and operation runs belong to content items; operation steps belongs to operation runs.
Configuration:
Organizations owns Projects and People; source mappings links to Projects. Users contains the application role values.
Every table, by feature
- Content intake5
- Requirements and evidence5
- Independent review6
- Tasks and corrections6
- Delivery and execution5
- Projects and provenance6
- Shared and settings1
- Content items
Content items submitted for a project and tracked through draft, review, approval and delivery.
Linked to Organizations, People, Projects - Projects
Repository projects and collection definitions offered by an organization.
Linked to Organizations - Organizations
Agencies, departments and repository organizations that own projects and content items.
- People
Staff, officers, reviewers and assigned team members.
Linked to Organizations - State history
Immutable workflow-written status transition history for each content item.
Linked to Content items, People
- Application requirements
Observation-level requirement, document and line detail captured against a content item.
Linked to Content items - Content files
Uploaded and verified supporting documents and source evidence.
Linked to Content items, People - Content items
Content items submitted for a project and tracked through draft, review, approval and delivery.
Linked to Organizations, People, Projects - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations - Production tasks
Assigned outstanding tasks, corrections and outstanding requests for a content item.
Linked to Content items, People
- Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Content items, People - Content items
Content items submitted for a project and tracked through draft, review, approval and delivery.
Linked to Organizations, People, Projects - Application requirements
Observation-level requirement, document and line detail captured against a content item.
Linked to Content items - Content files
Uploaded and verified supporting documents and source evidence.
Linked to Content items, People - State history
Immutable workflow-written status transition history for each content item.
Linked to Content items, People - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations
- Production tasks
Assigned outstanding tasks, corrections and outstanding requests for a content item.
Linked to Content items, People - Content items
Content items submitted for a project and tracked through draft, review, approval and delivery.
Linked to Organizations, People, Projects - Review decisions
Independent reviewer decisions recorded against an exact source revision.
Linked to Content items, People - Content files
Uploaded and verified supporting documents and source evidence.
Linked to Content items, People - State history
Immutable workflow-written status transition history for each content item.
Linked to Content items, People - People
Staff, officers, reviewers and assigned team members.
Linked to Organizations
- Content items
Content items submitted for a project and tracked through draft, review, approval and delivery.
Linked to Organizations, People, Projects - Execution attempts
Each recorded attempt to execute an approved action for a content item.
Linked to Content items - 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 - State history
Immutable workflow-written status transition history for each content item.
Linked to Content items, People
- Organizations
Agencies, departments and repository organizations that own projects and content items.
- People
Staff, officers, reviewers and assigned team members.
Linked to Organizations - Projects
Repository projects and collection definitions offered by an organization.
Linked to Organizations - Source mappings
Reviewed field mappings and transform rules between source payloads and target fields.
Linked to Projects - Content items
Content items submitted for a project and tracked through draft, review, approval and delivery.
Linked to Organizations, People, Projects - State history
Immutable workflow-written status transition history for each content item.
Linked to Content items, People
Keys and references
Use a stable item number and retain source identifiers when importing content. The project and organization references must resolve before an item is accepted. Keep requirement and file references with the source item. A review decision includes the source revision; a run includes the source revision and operation key. Preserve prior decisions, receipt evidence and state history when a successor is created.
Migration order
- Load Organizations, People and Users; confirm the intended roles and organization scope.
- Load Projects and source mappings with their codes, policy references and effective dates.
- Load content items with organization, project and owner references.
- Load application requirements, content files and production tasks against their parent items.
- Load review decisions and state history in revision order, then execution attempts, operation runs and operation steps with their receipts.
- Reconcile item numbers, source revisions, delivery references and open task owners before the operating cycle begins.
Set up E-library / Digital Repository your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.