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.
- Data Entry & Validation
- Data model
The tables behind Data Entry & Validation
Data Entry & Validation 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
Configuration
Organizations, People and validation schemas define who sends data and which rules apply. Source mappings belongs to a definition.
Operations
Import batches holds the source revision and counts. Validation results holds row outcomes. Operation runs and operation steps keep the execution trace.
Review and evidence
Review decisions records the reviewer call. Evidence documents, follow up actions and state history preserve support, correction and transition details.
Execution
Execution attempts records individual attempts and provider references.
Every table, by feature
- Batch intake5
- Rules and mappings4
- Validation review4
- Independent decisions5
- Commit trace5
- Correction evidence6
- Shared and settings1
- Import batches
Staged inbound data submissions validated against a frozen rule set.
Linked to Organizations, People, Validation schemas - Organizations
Submitting business entities whose inbound data is validated.
- People
Operators, reviewers and owners who prepare and sign off data batches.
Linked to Organizations - Validation schemas
Frozen validation rule sets applied to imported batches.
Linked to Organizations - Evidence documents
Source documents and receipt evidence attached to a batch.
Linked to Import batches, People
- Validation schemas
Frozen validation rule sets applied to imported batches.
Linked to Organizations - Source mappings
Reviewed field-level mapping rules from source fields to target fields.
Linked to Validation schemas - Organizations
Submitting business entities whose inbound data is validated.
- Import batches
Staged inbound data submissions validated against a frozen rule set.
Linked to Organizations, People, Validation schemas
- Validation results
Row-level and field-level validation outcomes for each staged row.
Linked to Import batches - Import batches
Staged inbound data submissions validated against a frozen rule set.
Linked to Organizations, People, Validation schemas - Validation schemas
Frozen validation rule sets applied to imported batches.
Linked to Organizations - State history
Immutable status transition log for every validated batch.
Linked to Import batches, People
- Review decisions
Independent reviewer sign-off or return against an exact source revision.
Linked to Import batches, People - Import batches
Staged inbound data submissions validated against a frozen rule set.
Linked to Organizations, People, Validation schemas - Validation results
Row-level and field-level validation outcomes for each staged row.
Linked to Import batches - Evidence documents
Source documents and receipt evidence attached to a batch.
Linked to Import batches, People - People
Operators, reviewers and owners who prepare and sign off data batches.
Linked to Organizations
- Operation runs
Workflow-maintained run ledger for parse, commit and correction operations.
Linked to Import batches - Operation steps
Ordered step trace with persisted input/output identities and receipt state.
Linked to Operation runs - Execution attempts
Durable attempt record for each commit or correction execution.
Linked to Import batches - Import batches
Staged inbound data submissions validated against a frozen rule set.
Linked to Organizations, People, Validation schemas - Review decisions
Independent reviewer sign-off or return against an exact source revision.
Linked to Import batches, People
- Follow up actions
Correction and verification tasks raised against validated batches.
Linked to Import batches, People - Evidence documents
Source documents and receipt evidence attached to a batch.
Linked to Import batches, People - State history
Immutable status transition log for every validated batch.
Linked to Import batches, People - Import batches
Staged inbound data submissions validated against a frozen rule set.
Linked to Organizations, People, Validation schemas - Operation runs
Workflow-maintained run ledger for parse, commit and correction operations.
Linked to Import batches - Review decisions
Independent reviewer sign-off or return against an exact source revision.
Linked to Import batches, People
Keys and references
Import batches links an organization, owner and definition. Validation results points to its parent batch. Review decisions points to both the batch and a reviewer, while its source revision identifies the version decided. Operation steps belongs to an operation runs record; both retain execution identities. Follow up actions links a batch and assignee. State history links a batch and actor.
Migration order
- Load Organizations and People, including their organization references.
- Load validation schemas and source mappings with effective dates and field names.
- Load import batches with owners, definitions, source hashes and revisions.
- Load validation results, review decisions and evidence documents against their batches.
- Load operation runs, operation steps, execution attempts, follow up actions and state history after their parent records.
Set up Data Entry & Validation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.