View source for Content Type

<blockquote>{{#lst:Glossary|Content Type}}</blockquote>

== About ==
<section begin="Content Type Objects" />
=== Types of Content Types ===
In '''Grooper''', the "Content Type" nodes consist of:
: {{ContentModelIcon}} '''[[Content Model]]''' ...
: {{ContentCategoryIcon}} '''[[Content Category]]''' and ...
: {{DocumentTypeIcon}} '''[[Document Type]]''' nodes.
These nodes create a classification taxonomy in Grooper. They define how documents are classified, what data to collect from a document, how different kinds of documents are related, and even how certain activities like [[Export]] should behave based on how a document is classified.

Content Types work together in Grooper to enable sophisticated document processing workflows. With different types of documents properly classified, they can have their data extracted and are handled according to the rules and behaviors defined by the '''Document Types''' within a '''Content Model'''.

The relationship between these Content Types is established through a hierarchical inheritance system. '''Content Categories''' and '''Document Types''' are building blocks within a '''Content Model''' seen as the "tree". '''Content Categories''' act as the "branches". '''Document Types''' are the "leaves" of the hierarchy.

=== Content Types and document classification ===

Documents are classified by having a Content Type (usually a '''Document Type''') assigned either by the [[Classify]] activity, manually by a user, or other mechanisms in Grooper.

The '''Content Model''' plays a special role in defining the "Classify Method" used to classify documents. Classify Methods define the logic for

=== Content Types and data extraction ===

"[[Data Element]]s" represent information written on the document and contain instructions on how to collect it.

Data Elements can be defined for each Content Type by adding a '''Data Model'''. Data Elements (including '''Data Fields''', '''Data Sections''' and '''Data Tables''') are added these '''Data Models'''. Data Elements are inherited down the "tree" of the Content Type hierarchy.
* Data Elements defined at the '''Content Model''' level are applied to all Content Types within the '''Content Model''' and will apply to the whole "tree".
* Data Elements defined at the '''Content Category''' level are applied to all Content Types that exist within that specific "branch".
* Data Elements defined on a '''Document Type''' will apply to that specific "leaf".


*<li class="attn-bullet"> This is why documents must be "classified" in order to have their data extracted. It is the Content Type that determines which '''Data Model''' is used to collect data when the Extract activity runs.

=== Content Types and "Behaviors" ===

"Behaviors" are a set of different configurations that affect certain Activities and other areas of Grooper based on how a document is classified. They include:
* [[Import Behavior]]s - Defining how documents and metadata are imported from '''CMIS Repositories''' based on their classification.
* [[Export Behavior]]s - Defining how documents and data are exported based on their classification.
* [[Labeling Behavior]]s - Defining how Label Sets are used for documents based on their classification.
* [[PDF Data Mapping]] - Defining several PDF generation capabilities for documents based on their classification.
* [[Indexing Behavior]] - Defining how documents are added to a Grooper search index based on their classification.

Behaviors also respect the Content Type hierarchy.
* Behaviors defined at the '''Content Model''' level are applied to all Content Types within the '''Content Model''', unless a child Content Type has its own Behavior configured. '''Content Category''' and '''Document Type''' Behavior configurations will override the '''Content Model''' configuration.
* Behaviors defined at the '''Content Category''' level are applied to all Content Types within that branch, unless a child Content Type has its own Behavior configured. Child '''Content Category''' and '''Document Type''' Behavior configurations will override a parent '''Content Category''' configuration.
* Behaviors defined at the '''Document Type''' level are applied to that '''Document Type''' only. '''Document Type''' Behavior configurations will override all parent '''Content Category''' and/or '''Content Model''' configurations.


<div style="padding-left: 1.5em">
=== Related Node Types ===
<div style="padding-left: 1.5em">
==== Content Model ====
{{#lst:Glossary|Content Model}}

==== Content Category ====
{{#lst:Glossary|Content Category}}

==== Document Type ====
{{#lst:Glossary|Document Type}}
</div>

=== What about Form Types and Page Types? ===
Technically speaking, '''Form Types''' and '''Page Types''' are also Content Types, but they aren't typically used in the same way.  '''Form Types''' and '''Page Types''' are created automatically when training example documents for classification.  They hold the feature weighting data for documents.

* '''[[Form Type]]s'''
** When a '''Document Type''' is trained for classification, the training samples are created as '''Form Types'''.
** '''Form Types''' are generated automatically when training documents for Lexical classification (and less commonly for Visual classification).
* '''[[Page Type]]s'''
** The '''Page Types''' are the individual pages of a '''Form Type'''.  All training weightings are stored on the '''Page Types''' for each page of the training document.
** '''Page Types''' are generated automatically when training documents for Lexical classification (and less commonly for Visual classification).
</div>
<section end="Content Type Objects" />

== Object Model info ==

<big>Grooper Type Name</big>
:''{{TypeName|Content Type}}''

{{Inheritance|Grooper Object|Connected Object|Node|Content Type}}

<big>Derived Types</big>
:::: '''Content Type''' (''{{HelpLink|Content Type}}'')
::::: {{WikiHelpLinks|Content Category}}
::::: {{WikiHelpLinks|Content Model}}
::::: {{WikiHelpLinks|Document Type}}
::::: {{WikiHelpLinks|Form Type}}
::::: {{WikiHelpLinks|Page Type}}

[[Category:Content Type]]