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.
- Publishing House ERP
- Data model
The tables behind Publishing House ERP
Publishing House ERP ships with 11 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
- 11
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Project and content work
Projects group content items, production tasks and project costs. People own projects and content items and receive production tasks.
Editorial and edition work
Manuscripts carry an Editor reference to People; print editions point to Manuscripts.
Approval evidence
Content files and rights agreements point to content items. Content files.approved by points to People. Approval operations records an approval operation outcome.
Identity
People.User points to Users. The People record connects an approving actor to the person named on an approved file.
Every table, by feature
- Publishing projects5
- Manuscript review3
- Content production5
- Rights and approval5
- Print editions3
- Costs and reporting4
- Shared and settings1
- Projects
Publishing projects that group content production work
Linked to People - Content items
Individual content units produced within a project
Linked to Projects, People - Production tasks
Assigned production work for a project
Linked to Projects, People - Project costs
Cost entries booked against a publishing project
Linked to Projects - People
Staff and contributors of the publishing house
Linked to Users
- Manuscripts
Submitted manuscripts under editorial review
Linked to People - People
Staff and contributors of the publishing house
Linked to Users - Print editions
Print editions and ISBN records for manuscripts
Linked to Manuscripts
- Content items
Individual content units produced within a project
Linked to Projects, People - Content files
Versioned file evidence attached to a content item
Linked to Content items, People - Production tasks
Assigned production work for a project
Linked to Projects, People - Projects
Publishing projects that group content production work
Linked to People - People
Staff and contributors of the publishing house
Linked to Users
- Rights agreements
Rights coverage agreements for content items
Linked to Content items - Content files
Versioned file evidence attached to a content item
Linked to Content items, People - Content items
Individual content units produced within a project
Linked to Projects, People - People
Staff and contributors of the publishing house
Linked to Users - Approval operations
Idempotency ledger for content approval workflows: one row per approval operation key, holding the approved outcome so a duplicate submission replays instead of approving twice.
- Print editions
Print editions and ISBN records for manuscripts
Linked to Manuscripts - Manuscripts
Submitted manuscripts under editorial review
Linked to People - People
Staff and contributors of the publishing house
Linked to Users
- Project costs
Cost entries booked against a publishing project
Linked to Projects - Projects
Publishing projects that group content production work
Linked to People - Production tasks
Assigned production work for a project
Linked to Projects, People - Print editions
Print editions and ISBN records for manuscripts
Linked to Manuscripts
Keys and references
The model contains 11 tables. References carry the identity of a project, manuscript, content item or person into related work. Keep those references intact during migration. A saved list such as Content Items In Production is a view of content items; it is not another source table. The same principle applies to manuscripts, tasks, rights agreements and costs.
Migration order
- Load Users and People, then check the user binding for people who will approve files.
- Load Projects and Manuscripts with their owners and editors.
- Load content items under Projects and print editions under Manuscripts.
- Load rights agreements and content files under content items.
- Load production tasks and project costs under Projects.
- Check approval operations against the approved content file outcomes where history is being carried forward.
Set up Publishing House ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.