│ Grooper Help - Version 25.0
25.0.0024 2,166

Content Type

Node Grooper.Core

Represents a distinct type or category of document, defining the data elements and behaviors that apply to documents of this class.

Remarks

Overview

A Content Type defines the structure, extraction logic, and behaviors for a specific class of document within a Content Model. It serves as a building block for organizing and processing documents, enabling both simple and highly complex document hierarchies.

Structure and Inheritance

Data Extraction and Modeling

  • The Data Model associated with a Content Type determines which data elements are extracted, validated, and presented for documents of this type.
  • To create a Data Model, right click the Content Type and use the Content Type - Create Data Model command.
  • Data extraction is performed by the Extract activity, which uses the Data Model to populate structured data for each document.
  • Inheritance allows common data elements to be defined once and reused across multiple document types, while still supporting customization through overrides.

Local Resource Folders

A Local Resources Folder is a special child node of a Content Type used to store resources that are closely associated with that type. These resources can include Lexicons, Data Rules, Extractor Nodes, Resource Files, OCR Profiles, and IP Profiles. By organizing resources in a Local Resources Folder, you make them directly available to the Content Type and all its descendants, supporting inheritance and modular configuration.

Purpose:

  • Store supporting resources required for extraction, validation, classification, or export.
  • Make the Content Type more self-contained and portable.
  • Reduce clutter in the Project by localizing resources to only where they are needed.
  • Enable inheritance of resources by descendant Content Types.

Creation:

Best Practices:

  • Place resources in the Local Resources Folder of a Document Type if they are only used by that type.
  • For resources shared by multiple types, use the Local Resources Folder of a common ancestor (such as a Content Category or the Content Model).
  • Use Project-level resources only for items that are global or shared across many unrelated types.

Inheritance and Portability:

  • Resources in a Local Resources Folder are inherited by all descendant Content Types.
  • When exporting or moving a Content Type, its Local Resources Folder and all contained resources are included, ensuring the type remains functional and self-contained.

Behaviors and Processing

  • Behaviors encapsulate processing logic, rules, or UI settings that apply to a Content Type and its descendants.
  • Behaviors are inherited and can be overridden to tailor functionality for specific document types or categories.
  • Examples include data validation rules, extraction logic, or custom rendering options.

Hierarchical Relationships

  • Content Types can define both hierarchical and peer relationships using the 'Child Of' and 'Sibling Of' properties.
  • These relationships are leveraged by the Data Model Compiler, which exposes data for the related types in expressions.
  • This enables advanced scenarios such as:
    • Validating a child field against a value stored on the parent.
    • Sharing or comparing data between sibling documents or folders.
    • Including parent or sibling data in export file names or mappings.
  • Defining these relationships does not force a strict hierarchy in the batch structure - it only affects how data is accessed in expressions.
  • For more details, see the Data Model Compiler documentation on exposing parent and sibling data in the expression environment.

Appearance and Naming

  • The 'Kind' property controls whether the Content Type appears as a folder or document in the batch hierarchy.
  • The 'Caption' property allows for dynamic naming of documents based on extracted data or custom expressions.
  • Numeric suffixes and other display options can be configured for clarity and consistency.

Usage Guidance

  • Use Content Types to model the full range of document classes in your solution, organizing them into logical categories as needed.
  • Define Data Models and Behaviors at the appropriate level to maximize reuse and maintainability.
  • Leverage inheritance and property overrides to adapt shared configurations for specialized document types.
  • Configure hierarchical relationships and appearance settings to match business requirements and user expectations.

For more information, see the documentation for Content Model, Document Type, Content Category, Data Model, and Behavior.

Properties

NameTypeDescription
General
Relationships
Appearance

Design Tabs

General View or edit properties of a node.
Documents View a list of documents which are classified this content type or one of its descendants.
Reports View reports for a node.
Training Samples View a list of training documents for this content type and its descendants.
Labels Edit Label Sets for this content type or its descendants.
Overrides Override Data Element property values for this content type.
Weightings View the classification weightings associated with this Content Type.
Advanced View or edit advanced details about a node.

Context Menu Commands

Command Shortcut Description
playlist_remove Clean Overrides Removes unnecessary property overrides from this Content Type and all descendants.
list_alt Create Data Model Adds a Data Model to the selected Content Type.
folder_open Create Local Resources Folder Creates a new Local Resources Folder as a child of this Content Type.
plagiarism Create Search Index Creates an Azure AI Search index for the selected Content Type, enabling search and retrieval features.
plagiarism Delete Search Index Deletes an Azure AI Search index previously created for this Content Type, removing all associated search and retrieval capabilities.
document_scanner Generate Control Sheets Command to generate Grooper Control Sheets for selected document types within a content model or content category.
model_training Purge Training Removes all classification training data and training samples from this Content Type and all descendants.
model_training Rebuild Training Removes all existing training and retrains the classification model from the current training set documents.
manufacturing Submit Indexing Job Submits an indexing job for the selected Content Type, updating the associated search index with new, updated, or deleted documents.

Derived Types

There are 5 implementations of Content Type.

Content Category A Content Category is a container for organizing Document Types and other Content Categories within a Content Model.
Content Model Defines the taxonomy, classification, and data extraction structure for a set of documents.
Document Type Represents a distinct type of document within a Content Model, such as an invoice, contract, or letter.
Form Type Represents a trained variation or version of a Document Type, used for classification and extraction in Grooper.
Page Type Represents a logical page within a Form Type, used for page-level classification in Grooper.

See Also

BehaviorContent CategoryContent ModelDocument TypeForm TypePage Type

Used By

BatchBatch FolderBatch ProcessContent CategoryContent ModelDocument TypeForm TypePage TypeExport BehaviorJSON Data MappingText RenderingSeparate ActionCheckbox InstanceLabeled InstanceTable Header InstanceSection Instance CollectionPDF Data MappingImport BehaviorOPEX ImportData View

Notification