Schemas
A record schema defines:- Record type name.
- Fields and field types.
- Required and optional fields.
- Relationships to other record types.
- Evidence expectations.
- Review rules and ownership where configured.
Candidates
TextMine can suggest candidates from source evidence. A candidate may propose:- A new record.
- A field value for an existing record.
- A relationship between records.
- A changed value.
- A missing-field recommendation.
- A duplicate or merge candidate.
Candidate review flow
- Generate or discover candidates from documents, tags, entities, tables, or workflows.
- Group candidates by schema, record, field, or source document.
- Inspect the proposed value and confidence where available.
- Review the source evidence.
- Accept, reject, edit, or defer the candidate.
- Record the review outcome and keep the evidence link.
Evidence
Each record field should remain connected to the documents and extracted evidence that support it. Evidence can include:- Vault document IDs and names.
- Extracted default or custom tags.
- Entity extraction outputs.
- Table rows or line items.
- Source passages and page numbers.
- Image tags or embedded image regions.
- Workflow run outputs.
- Reviewer decisions.
Schema design guidance
Good schemas are specific enough to be useful but not so rigid that every document creates exceptions.- Start with the business object users already understand.
- Keep fields stable and reviewable.
- Use relationships for connected objects instead of packing everything into one record.
- Prefer controlled fields where reporting depends on consistent values.
- Keep source evidence mandatory for high-risk or regulated fields.