View source for Glossary

This glossary seeks to educate readers on various Grooper terms, objects and other entities. Glossary entries will be short paragraphs describing the topic. For each glossary entry, you will find links to a full article about the entry as well as articles on associated terms.

Each entry is organized according to what major Grooper entity they belong to. For example, "'''''Classify'''''" is an '''''Activity'''''. It is found in the "Activity" section of the Glossary.

== Activity ==
<section begin="Activity" />'''''[[Activity]]'''''  is a property on {{BatchProcessStepIcon}} '''[[Batch Process Step]]s'''. '''''Activities''''' define specific document processing operations done to a {{BatchIcon}} '''[[Batch]]''', {{BatchFolderIcon}} '''[[Batch Folder]]''', or {{BatchPageIcon}} '''[[Batch Page]]'''. '''Batch Process Steps''' configured with specific '''''Activities''''' are frequently referred by the name of the '''''Activity''''' followed by the word "step". For example: '''''Classify''''' step.<section end="Activity" />
<div style="padding-left: 1.5em;">
=== AI Dialogue ===
<section begin="AI Dialogue" />{{AIDialogueIcon}} '''''[[AI Dialogue]]''''' is an '''''[[Activity]]''''' that executes a scripted conversation with an {{AIAnalystIcon}} '''''[[AI Analyst]]''''' and saves the resulting conversion on the document as a [https://en.wikipedia.org/wiki/JSON JSON] file.<section end="AI Dialogue" />

=== Apply Rules ===
<section begin="Apply Rules" />{{ApplyRulesIcon}} '''''[[Apply Rules]]''''' is an '''''[[Activity]]''''' that runs {{DataRuleIcon}} '''[[Data Rules]]''' on data that has already been extracted from a {{BatchIcon}} '''[[Batch]]'''. A {{BatchProcessStepIcon}} '''[[Batch Process Step]]''' configured with the '''''Apply Rules''''' '''''Activity''''' will always need to be preceded by a '''Batch Process Step''' configured with the {{ExtractIcon}} '''''[[Extract]] Activity'''''. <section end="Apply Rules" />

=== Classify ===
<section begin="Classify" />{{ClassifyIcon}} '''''[[Classify]]''''' is an '''''[[Activity]]''''' that "classifies" {{BatchFolderIcon}} '''[[Batch Folder]]s''' in a {{BatchIcon}} '''[[Batch]]''' by assigning them a '''''[[Content Type]]''''' (e.g. a {{DocumentTypeIcon}} '''[[Document Type]]''') using patterns, lexical understanding, or rules as defined by a {{ContentModelIcon}} '''[[Content Model]]'''.<section end="Classify" />

=== Clip Frames ===
<section begin="Clip Frames" />{{ClipFramesIcon}} '''''[[Clip Frames]]''''' is an '''''[[Activity]]''''' that extracts defined areas from [https://en.wikipedia.org/wiki/Microform microfiche] card images, creating new image frames or layers for focused analysis or processing.<section end="Clip Frames" />

=== Correct ===
<section begin="Correct" />{{CorrectIcon}} '''''[[Correct]]''''' is an '''''[[Activity]]''''' that performs spell correction.  It can correct a {{BatchFolderIcon}} '''[[Batch Folder|Batch Folder's]]''' text content or specific '''[[Data Element]]''' values to resolve OCR errors, deidentify data or otherwise enhance text data.<section end="Correct" />

=== Detect Frames ===
<section begin="Detect Frames" />{{DetectFramesIcon}} '''''[[Detect Frames]]''''' is an '''''[[Activity]]''''' that locates and identifies frame lines on [https://en.wikipedia.org/wiki/Microform microfiche] card images, enabling the isolation of areas within the frames for further [[Data Extraction|data extraction]] or processing.<section end="Detect Frames" />

=== Execute ===
<section begin="Execute" />{{ExecuteIcon}} '''''[[Execute]]''''' is an '''''[[Activity]]''''' that runs one or more specified object commands. This gives access to a variety of Grooper commands in a {{BatchProcessIcon}} '''[[Batch Process]]''' for which there is no '''''Activity''''', such as the "'''''Sort Children'''''" command for '''Batch Folders''' or the "'''''Expand Attachments'''''" command for email attachments.<section end="Execute" />

=== Export ===
<section begin="Export" />{{ExportIcon}} '''''[[Export]]''''' is an '''''[[Activity]]''''' that transfers documents and extracted information to external file systems and content management systems, completing the data processing workflow.<section end="Export" />

=== Extract ===
<section begin="Extract" />{{ExtractIcon}} '''''[[Extract]]''''' is an '''''[[Activity]]''''' that retrieves information from {{BatchFolderIcon}} '''[[Batch Folder]]''' documents, as defined by '''[[Data Element]]s''' in a {{DataModelIcon}} '''[[Data Model]]'''.  This is how Grooper locates unstructured data on your documents and collects it in a structured, usable format.<section end="Extract" />

=== Image Processing ===
<section begin="Image Processing" />{{ImageProcessingIcon}} '''''[[Image Processing (Activity)|Image Processing]]''''' is an '''''[[Activity]]''''' that enhances {{BatchPageIcon}} '''[[Batch Page]]''' images and optimizes them for better [[OCR]] text recognition and [[Data Extraction|data extraction]] results.<section end="Image Processing" />

=== Initialize Card ===
<section begin="Initialize Card" />{{InitializeCardIcon}} '''''[[Initialize Card]]''''' is an '''''[[Activity]]''''' prepares and configures [https://en.wikipedia.org/wiki/Microform microfiche] card images for further processing.<section end="Initialize Card" />

=== Merge ===
<section begin="Merge" />{{MergeIcon}} '''[[Merge]]''' is an '''''[[Activity]]''''' that creates a PDF, TIF, XML or ZIP file from the page and data content of a '''[[Batch Folder]]''' and saves it to that '''Batch Folder'''.<section end="Merge" />

=== Recognize ===
<section begin="Recognize" />{{RecognizeIcon}} '''''[[Recognize]]''''' is an '''''[[Activity]]''''' that obtains machine-readable text from {{BatchPageIcon}} '''[[Batch Page]]s''' and {{BatchFolderIcon}} '''[[Batch Folder]]s'''. '''''Recognize''''' will selectively perform [[OCR]] for images and native-text extraction for digital text in PDFs.  '''''Recognize''''' can also be configured to collect "layout data" like lines, checkboxes, and barcodes.  Various other '''''Activities''''' then use this machine-readable text and layout data for document analysis and [[Data Extraction|data extraction]].<section end="Recognize" />

=== Redact ===
<section begin="Redact" />{{RedactIcon}} '''''[[Redact]]''''' is an '''''[[Activity]]''''' that visibly obscures (or "redacts") text information on an page based on results returned from a [[Data Extractor|extractor]]. Be aware, '''''Redact''''' does ''not'' alter the text data. It only alters the image.<section end="Redact" />

=== Render ===
<section begin="Render" />{{RenderIcon}} '''''[[Render]]''''' is an '''''[[Activity]]''''' that converts files of various formats to PDF.  It does this by digitally printing the file to PDF using the Grooper Render Printer.  This normalizes electronic document content from file formats Grooper cannot read natively to PDF (which it can read natively), allowing Grooper to extract the text via the {{RecognizeIcon}} '''''[[Recognize]]''''' '''''Activity'''''.<section end="Render" />

=== Review ===
<section begin="Review" />{{ReviewIcon}} '''''[[Review]]''''' is an '''''[[Activity]]''''' that allows user attended review of Grooper's results.  This allows human operators to validate processed {{BatchPageIcon}} '''[[Batch Page]]''' and  {{BatchFolderIcon}} '''[[Batch Folder]]''' content using specialized user interfaces called "Viewers". Different kinds of Viewers assist users in reviewing  Grooper's image processing, document classification, data extraction and operating document scanners.<section end="Review" />

=== Send Mail ===
<section begin="Send Mail" />{{SendMailIcon}} '''''[[Send Mail]]''''' is an '''''[[Activity]]''''' automates email notifications from Grooper based on events and conditions set by a {{BatchProcessIcon}} '''[[Batch Process]]'''. Optionally, documents in the {{BatchIcon}} '''[[Batch]]''' may be attached to the generated email.<section end="Send Mail" />

=== Separate ===
<section begin="Separate" />{{SeparateIcon}} '''''[[Separate]]''''' is an '''''[[Activity]]''''' that sorts {{BatchPageIcon}} '''[[Batch Page]]s''' into individual {{BatchFolderIcon}} '''[[Batch Folder]]s'''.  This distinguishes "loose pages" from the documents formed by those pages.  Once loose pages are separated into '''Batch Folder''' documents, they can be further processed by {{ClassifyIcon}} '''''[[Classify]]''''', {{ExtractIcon}} '''''[[Extract]]''''', {{ExportIcon}} '''''[[Export]]''''' and other '''''Activities''''' that need to run on the folder (i.e. document) level.<section end="Separate" />

=== Split Pages ===
<section begin="Split Pages" />Multi-page PDF and TIF files come into Grooper as files attached to single {{BatchFolderIcon}} '''[[Batch Folder]]s'''. '''''[[Split Pages]]''''' is an '''''[[Activity]]''''' that creates child {{BatchPageIcon}} '''[[Batch Page]]s''' for each page in the PDF or TIF. This allows Grooper to process and handle these pages as individual objects.<section end="Split Pages" />

=== XML Transform ===
<section begin="XML Transform" />{{XMLTransformIcon}} '''''[[XML Transform]]''''' is an '''''[[Activity]]''''' that applies [https://en.wikipedia.org/wiki/XSLT XSLT] stylesheets to XML data to modify or reformat the output structure for various purposes.<section end="XML Transform" />
</div>

== Application ==
<section begin="Application" />'''Grooper''' is an intelligent document processing platform that uses a wide array of sophisticated techniques to automate end-to-end content capture. From a technical standpoint, '''Grooper''' consists of a '''[[Grooper Repository]]''' and the applications that the support management and execution of configuration assets. A '''Grooper Repository''' consists of two things: (1) A series of tables in a SQL [https://en.wikipedia.org/wiki/Database database] (containing configuration nodes and their properties) and (2) a '''[[File Store]]''' (containing files associated to nodes in the database). The '''Grooper''' ''application'' is the interface by which a user can interact with that repository in an intuitive way.<section end="Application" />
<div style="padding-left: 1.5em;">
=== Grooper Command Console ===
<section begin="Grooper Command Console" />'''[[Grooper Command Console]]''' is a [https://en.wikipedia.org/wiki/Command-line_interface command-line interface] that performs system configuration and administration tasks within '''Grooper'''.<section end="Grooper Command Console" />

=== Grooper Web Client ===
<section begin="Web Client" />The Grooper user interface is accessed using a web browser from a URL. The [[Grooper Web Client]] is the application that installs the Grooper website on a web server.<section end="Web Client" />
</div>

== Behavior ==
<section begin="Behavior" />'''''[[Behaviors]]''''' refer a group of functionality configured using a '''[[Content Type]]'s''' '''''Behaviors''''' property. '''''Behaviors''''' enable different features for how documents of a specific '''Content Type''' are processed and define their settings. This includes how they are exported, if [[Label Sets]] are used for the '''Document Type''' and more.<section end="Behavior" />
<div style="padding-left: 1.5em;">
=== Export Behavior ===
<section begin="Export Behavior" />An '''''[[Export Behavior]]''''' defines the parameters for exporting classified {{BatchFolderIcon}} '''[[Batch Folder]]''' content from '''Grooper''' to other systems. This includes where they are exported to (what content management system, file system, database etc), what content is exported (attached files, images, and/or data), how it is formatted (PDF, CSV, XML etc), folder pathing, file naming and data mappings (for '''''[[Data Export]]''''' and '''''[[CMIS Export]]''''').<section end="Export Behavior" />

=== Import Behavior ===
<section begin="Import Behavior" />An '''''[[Import Behavior]]''''' defines how data is mapped from files in an external content management system to '''Batch Folders''' created on import when using '''''[[CMIS Import]]'''''.<section end="Import Behavior" />

=== Indexing Behavior ===
<section begin="Indexing Behavior" />An '''''[[Indexing Behavior]]''''' is a '''[[Content Type]]''' '''''[[Behavior]]''''' designed to enable the ability for inherited '''Content Types''' to be indexed via the '''''[[AI Search]]''''' functionality.<section end="Indexing Behavior" />

=== Labeling Behavior ===
<section begin="Labeling Behavior" />A '''''[[Labeling Behavior]]''''' is a '''[[Content Type]]''' '''''[[Behavior]]''''' designed to collect and utilize a document's field labels in a variety of ways. This includes functionality for [[Labeling_Behavior_(Behavior)#How_to_use_Label_Sets_for_classification|classification]], [[Labeling_Behavior_(Behavior)#How_to_use_Label_Sets_for_field_based_extraction|field extraction]], [[Labeling_Behavior_(Behavior)#How_to_use_Label_Sets_for_tabular_extraction|table extraction]], and [[Labeling_Behavior_(Behavior)#How_to_use_Label_Sets_for_section_extraction|section extraction]].<section end="Labeling Behavior" />

=== PDF Data Mapping ===
<section begin="PDF Data Mapping" />'''''[[PDF Data Mapping]]''''' is a '''[[Content Type]]''' '''''[[Behavior]]''''' designed to enhance PDF files generated by the '''''[[Merge]]''''' or '''''[[Export]]''''' activities with metadata, bookmarks, annotations and/or different kinds of widgets.<section end="PDF Data Mapping" />
</div>

== CMIS Connection Type ==
<section begin="CMIS Connection Type" />A '''''CMIS Connection Type''''' is defined when creating a {{CMISConnectionIcon}} '''[[CMIS Connection]]'''. The '''''CMIS Connection Type''''' (formally '''''CMIS Binding''''') establishes the communication protocols used to connect '''Grooper''' with content management systems (CMS) adhering to the [https://en.wikipedia.org/wiki/Content_Management_Interoperability_Services CMIS] standard. Even when connecting to CMS platforms that are not ''true'' CMIS systems, Grooper normalizes connection to them as if they were. This allows Grooper to use '''''[[CMIS Import]]''''' and '''''[[CMIS Export]]''''' for all content management systems.<section end="CMIS Connection Type" />
<div style="padding-left: 1.5em;">
=== AppXtender ===
<section begin="AppXtender" />'''''[[AppXtender]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to the [https://en.wikipedia.org/wiki/OpenText#AppEnhancer_(formerly_ApplicationXtender) AppEnhancer (formerly ApplicationXtender)] content management system for import and export operations.<section end="AppXtender" />

=== Box ===
<section begin="Box" />'''''[[Box]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to the [https://en.wikipedia.org/wiki/Box_(company) Box] content management system for import and export operations.<section end="Box" />

=== Exchange ===
<section begin="Exchange" />'''''[[Exchange]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to [https://en.wikipedia.org/wiki/Microsoft_Exchange_Server Microsoft Exchange] email servers (including Outlook servers) for import and export operations.<section end="Exchange" />

=== FTP ===
<section begin="FTP" />'''''[[FTP]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to [https://en.wikipedia.org/wiki/File_Transfer_Protocol FTP] directories for import and export operations.<section end="FTP" />

=== IMAP ===
<section begin="IMAP" />'''''[[IMAP]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to email messages and folders through an [https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol IMAP] email server for import and export operations.<section end="IMAP" />

=== NTFS ===
<section begin="NTFS" />'''''[[NTFS]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to files and folders in the  Microsoft Windows [https://en.wikipedia.org/wiki/NTFS NTFS] file system for import and export operations.<section end="NTFS" />

=== OneDrive ===
<section begin="OneDrive" />'''''[[OneDrive]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to [https://en.wikipedia.org/wiki/OneDrive Microsoft OneDrive] cloud services for import and export operations.<section end="OneDrive" />

=== SFTP ===
<section begin="SFTP" />'''''[[SFTP]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to [https://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol SFTP] directories for import and export operations.<section end="SFTP" />

=== SharePoint ===
<section begin="SharePoint" />'''''[[SharePoint]]''''' is a '''''CMIS Connection Type''''' that connects '''Grooper''' to [https://en.wikipedia.org/wiki/SharePoint Microsoft SharePoint], providing access to content stored in "document libraries" and "picture libraries" for import and export operations.<section end="SharePoint" />
</div>

== Classification Method ==
<section begin="Classification Method" />A {{ContentModelIcon}} '''[[Content Model]]'s''' '''''[[Classification Method]]''''' property determines the technique used for document [[Classification|classification]]. Classification sorts {{BatchFolderIcon}} '''[[Batch Folder]]s''' into categories (called "'''{{DocumentTypeIcon}} [[Document Type]]s'''"). Grooper's various '''''Classification Methods''''' can utilize text-based pattern matching, machine learning models, or other methodologies to identify and organize documents accurately.<section end="Classification Method" />
<div style="padding-left: 1.5em;">
=== GPT Embeddings ===
<section begin="GPT Embeddings" />'''''[[GPT Embeddings]]''''' is a '''''[[Classification Method]]''''' that uses an [https://en.wikipedia.org/wiki/OpenAI OpenAI] embeddings model and trained document samples to tell one document from another.<section end="GPT Embeddings" />

=== Labelset-Based ===
<section begin="Labelset-Based" />'''''[[Labelset-Based]]''''' is a '''''[[Classification Method]]''''' that leverages the labels defined via a '''''[[Labeling Behavior]]''''' to classify {{BatchFolderIcon}} '''[[Batch Folder]]s'''.<section end="Labelset-Based" />

=== Lexical ===
<section begin="Lexical" />The '''''[[Lexical]]''''' '''''[[Classification Method]]''''' classifies {{BatchFolderIcon}} '''[[Batch Folder]]s''' based on the text content of trained document examples. This is achieved through the statistical analysis of word frequencies that identify {{DocumentTypeIcon}} '''[[Document Type]]s'''.<section end="Lexical" />

=== Rules-Based ===
<section begin="Rules-Based" />The '''''[[Rules-Based]]''''' '''''[[Classification Method]]''''' employs "rules" defined on each  {{DocumentTypeIcon}} '''[[Document Type]]''' to classify {{BatchFolderIcon}} '''[[Batch Folder]]s'''. '''''Positive Extractor''''' and '''''Negative Extractor''''' properties are configured for each '''Document Type''' to positively or negatively associate a '''Batch Folder''' based on predefined criteria. 

Note where the '''''Positive''''' and '''''Negative Extractors''''' will impact ''all'' '''''Classification Method''''' results, the '''''Rules-Based''''' method classifies using ''only'' these properties and nothing else.<section end="Rules-Based" />

=== Visual ===
<section begin="Visual" />The '''''[[Visual]]''''' '''''[[Classification Method]]''''' uses image analysis instead of text data to determine the {{DocumentTypeIcon}} '''[[Document Type]]''' assigned to a {{BatchFolderIcon}} '''[[Batch Folder]]''' during [[Classification|classification]].  Instead of using text-based extractors, an "'''''Extract Features'''''" '''''[[IP Command]]''''' in an {{IPProfileIcon}} '''[[IP Profile]]''' is used to collect image-based data from a '''Batch Folder's''' image(s).  This image-based data is compared against that of previously trained document examples of each '''Document Type''' to classify the '''Batch Folder'''.<section end="Visual" />
</div>

== Collation Provider ==
<section begin="Collation Provider" />The '''''[[Collation Provider|Collation]]''''' property of a {{DataTypeIcon}} '''[[Data Type]]''' defines the method for converting its raw results into a final result set. It is configured by selecting a '''''Collation Provider'''''. The '''''Collation Provider''''' governs how initial matches from the '''Data Type's''' extractor(s) are combined and interpreted to produce the '''Data Type's''' final output.<section end="Collation Provider" />
<div style="padding-left: 1.5em;">
=== AND ===
<section begin="AND" />'''''[[AND]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors. '''''AND''''' returns results only when each of its referenced or child extractors gets at least one hit, thus acting as a logical “AND” operator across multiple extractors.<section end="AND" />

=== Array ===
<section begin="Array" />'''''[[Array]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors.  '''''Array''''' matches a list of values arranged in horizontal, vertical, or text-flow order, combining instances that qualify into a single result.<section end="Array" />

=== Combine ===
<section begin="Combine" />'''''[[Combine]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors.  '''''Combine''''' combines instances from returned results based on a specified grouping, controlling how extractor results are assembled together for output.<section end="Combine" />

=== Key-Value List ===
<section begin="Key-Value List" />'''''[[Key-Value List]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors.  '''''Key-Value List''''' matches instances where a key and a list of one or more values appear together on the document, adhering to a specific layout pattern.<section end="Key-Value List" />

=== Key-Value Pair ===
<section begin="Key-Value Pair" />'''''[[Key-Value Pair]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors.  '''''Key-Value Pair''''' matches instances where a key is paired with a value on the document in a specific layout. ''Note: Key-Value Pair is an older technique in Grooper. In most cases, the [[Labeled Value]] extractor type is preferable to Key-Value Pair collation.<section end="Key-Value Pair" />

=== Multi-Column ===
<section begin="Multi-Column" />'''''[[Multi-Column]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors.  '''''Multi-Column''''' combines multiple columns on a page into a single column for [[Data Extraction (Concept)|extraction]].<section end="Multi-Column" />

=== Ordered Array ===
<section begin="Ordered Array" />'''''[[Ordered Array]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors. '''''Ordered Array''''' finds sequences of values where one result is present for each extractor, in the order they appear, according to a specified horizontal, vertical or text-flow layout.<section end="Ordered Array" />

=== Pattern-Based ===
<section begin="Pattern-Based" />'''''[[Pattern-Based]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors. '''''Pattern-Based''''' uses [https://en.wikipedia.org/wiki/Regular_expression regular expressions] to sequence returned results into a final result set.<section end="Pattern-Based" />

=== Split ===
<section begin="Split" />'''''[[Split]]''''' is a '''''[[Collation Provider]]''''' option for {{DataTypeIcon}} '''[[Data Type]]''' extractors. '''''Split''''' separates a [[Data Instance (Concept)|data instance]] at each match returned by the '''Data Type'''. The results are used as anchor points to "split" text into one or more smaller parts.<section end="Split" />
</div>

== Concept ==
<section begin="Concept" />There are many objects and properties a user can configure in '''Grooper''', however, gaining an understanding how, why, and when to use these objects and properties is powered by one's understanding of the underlying concepts that define what what these objects and properties are doing and why.<section end="Concept" />
<div style="padding-left: 1.5em;">
=== Activity Processing ===
<section begin="Activity Processing Concept" />[[Activity Processing]] is the execution of a sequence of configured tasks which are performed within a {{BatchProcessIcon}} '''[[Batch Process (Object)|Batch Process]]''' to transform raw data from documents into structured and actionable information. Tasks are defined by Grooper '''''[[Activity|Activities]]''''', configurated to perform document [[Classification (Concept)|classification]], [[Data Extraction (Concept)|extraction]], or data enhancement.<section end="Activity Processing Concept" />

=== CMIS+ ===
<section begin="CMIS+" />[[CMIS+]] is a conceptual term that refers to '''Grooper's''' connectivity architecture to external storage platforms. CMIS+ standardizes connections to a variety of content management system based on the [https://en.wikipedia.org/wiki/Content_Management_Interoperability_Services CMIS] standard. This provides a standardized setup to allow Grooper to interoperate with both CMIS compliant systems and non-CMIS systems. It further provides normalized access to document content and metadata for import ('''''[[CMIS Import]]''''') and export ('''''[[CMIS Export]]''''') operations.<section end="CMIS+" />

=== CMIS ===
<section begin="CMIS" />[[CMIS]] ([https://en.wikipedia.org/wiki/Content_Management_Interoperability_Services Content Management Interoperability Services]) is open standard allowing different [https://en.wikipedia.org/wiki/Content_management_system content management systems] to "interoperate", sharing files, folders and their metadata as well as programmatic control of the platform over the internet.<section end="CMIS" />

=== CMIS Query ===
<section begin="CMIS Query" />A [[CMIS Query]] (aka '''''CMISQL Query''''') is Grooper's way of searching for documents in [[CMIS Repository|CMIS Repositories]] and filtering them upon import when using the '''''[[Import Query Results]]''''' '''''[[Import Provider]]'''''. CMIS queries are based on a subset of the SQL-92 syntax for querying databases, with some specialized extensions added to support querying CMIS sources.<section end="CMIS Query" />

=== CSS Data Viewer Styling ===
<section begin="CSS Data Viewer Styling" />[[CSS Data Viewer Styling]] refers to using [https://en.wikipedia.org/wiki/CSS CSS] to custom style the '''''Review''''' activity's '''''Data Viewer''''' interface. This gives you a great deal of control over a {{DataModelIcon}} '''[[Data Model]]'s''' appearance and layout during document review.<section end="CSS Data Viewer Styling" />

=== Classification ===
<section begin="Classification" />[[Classification]] is the process of identifying and organizing documents into categorical types based on their content or layout. Classification is key for efficient document management and [[Data Extraction (Concept)|data extraction]] workflows. Grooper has different methods for classifying documents. These include methods that use machine learning and text pattern recognition. In a Grooper '''Batch Process''', the '''''[[Classify]]''''' '''''[[Activity]]''''' will assign a '''[[Content Type]]''' to a {{BatchFolderIcon}} '''[[Batch Folder]]'''.<section end="Classification" />

=== Code Expressions ===
<section begin="Code Expressions" />[[Code Expressions]] (not to be confused with [https://en.wikipedia.org/wiki/Regular_expression regular expressions]) are snippets of [https://en.wikipedia.org/wiki/Visual_Basic_(.NET) VB.NET] code that expand '''Grooper's''' core functionality.<section end="Code Expressions" />

=== Content Type ===
<section begin="Content Type" />'''[[Content Type]]''' refers to objects in '''Grooper''' used to classify {{BatchFolderIcon}} '''[[Batch Folder]]s'''. These include: {{ContentModelIcon}} '''[[Content Model]]s''', {{ContentCategoryIcon}} '''[[Content Category|Content Categories]]''', and {{DocumentTypeIcon}} '''[[Document Type]]s'''.<section end="Content Type" />

=== Data Context ===
<section begin="Data Context" />[[Data Context]] refers to contextual information used to extract data, such as a label that identifies the value you want to collect.<section end="Data Context" />

=== Data Element ===
<section begin="Data Element" />'''[[Data Element]]''' refers to the objects in '''Grooper''' used to collect data from a document.  These include: {{DataModelIcon}} '''[[Data Model]]s''', {{DataSectionIcon}} '''[[Data Section]]s''', {{DataFieldIcon}} '''[[Data Field]]s''', {{DataTableIcon}} '''[[Data Table]]s''', and {{DataColumnIcon}} '''[[Data Column]]s'''.<section end="Data Element" />

=== Data Extraction ===
<section begin="Data Extraction" />[[Data Extraction]] involves identifying and capturing specific information from documents (represented by {{BatchFolderIcon}} '''[[Batch Folder]]s''' in '''Grooper'''). Extraction is performed by configurable [[Data Extractor]]s, which transform unstructured or semi-structured data into a structured, usable format for processing and analysis.<section end="Data Extraction" />

=== Data Extractor ===
<section begin="Data Extractor" />[[Data Extractor]] (or just "extractor") refers to all '''''[[Extractor Type]]s''''' and [[Data Extractor (Concept)#Extractor Objects|extractor node objects]]. Extractors define the logic used to return data from a document's text content, including general data (such as a date) and specific data (such as an agreement date on a contract).<section end="Data Extractor" />

=== Data Instance ===
<section begin="Data Instance" />A [[Data Instance]] is an encapsulation of text data within a document returned by '''Grooper's''' [[Data Extractor|extractors]]. Data instances are the hierarchy of text data created by '''Grooper's''' extractors.<section end="Data Instance" />

=== Expressions ===
<section begin="Expressions" />[[Expressions]] (not to be confused with [https://en.wikipedia.org/wiki/Regular_expression regular expressions]) are snippets of [https://en.wikipedia.org/wiki/Visual_Basic_(.NET) VB.NET] code that expand '''Grooper's''' core functionality.<section end="Expressions" />

=== Expressions Cookbook ===
<section begin="Expressions Cookbook" />The "[[Expressions Cookbook]]" is a reference list for commonly used [[Code Expressions]] in '''Grooper'''.<section end="Expressions Cookbook" />

=== Field Mapping ===
<section begin="Field Mapping" />[[Field Mapping]] refers to how logical connections are made between [https://en.wikipedia.org/wiki/Metadata metadata] content in '''Grooper''' and an external storage platform.<section end="Field Mapping" />

=== Five Phases of Grooper ===
<section begin="Five Phases of Grooper" />The "[[Five Phases of Grooper]]" is a conceptual term that seeks to build understanding of how documents are processed through '''Grooper'''.<section end="Five Phases of Grooper" />

=== Flow Collation ===
<section begin="Flow Collation" />"[[Flow Collation]]" refers to the text-flow based layout option used by various '''''[[Collation Provider]]s''''' for{{DataTypeIcon}} '''[[Data Type]]''' extractors.<section end="Flow Collation" />

=== Footer Rows and Footer Modes ===
<section begin="Footer Rows and Footer Modes" />"[[Footer Rows and Footer Modes]]" refers to how a {{DataTableIcon}} '''[[Data Table]]'s''' "footer row" provides '''Grooper''' users a quick way to validate numerical data in a {{DataColumnIcon}} '''[[Data Column]]'''. The '''Data Column's''' '''''Footer Mode''''' property controls if and how a total is determined for numerical values in a '''Data Column'''.<section end="Footer Rows and Footer Modes" />

=== Fuzzy RegEx ===
<section begin="Fuzzy RegEx" />[[Fuzzy RegEx]] is '''Grooper's''' use of [https://en.wikipedia.org/wiki/Fuzzy_logic fuzzy logic] within '''''[[Extractor Type]]s''''' that leverage [https://en.wikipedia.org/wiki/Regular_expression regular expressions] to match patterns. Fuzzy RegEx allows extractors to overcome defects in a document's OCR results to accurately return results. Fuzzy RegEx is enabled by enabling the '''''Fuzzy Matching''''' property.<section end="Fuzzy RegEx" />

=== GPT Integration ===
<section begin="GPT Integration" />Grooper's [[GPT Integration]] is refers to the usage of [https://en.wikipedia.org/wiki/OpenAI OpenAI's] [https://en.wikipedia.org/wiki/Generative_pre-trained_transformer GPT] models within '''Grooper''' to enhance the capabilities of [[Data Extractor (Concept)|data extractors]], [[Classification (Concept)|classification]], and lookups.<section end="GPT Integration" />

=== Grooper Infrastructure ===
<section begin="Grooper Infrastructure" />[[Grooper Infrastructure]] refers to the computing underpinnings of what makes up a [[Grooper Repository]] and the software that allows the Grooper platform to automate tasks and users to interface with it.<section end="Grooper Infrastructure" />

=== Grooper Repository ===
<section begin="Grooper Repository" />A '''[[Grooper Repository]]''' is the environment used to create, configure and execute objects in Grooper. It provides the framework to "do work" in Grooper. Fundamentally, a '''Grooper Repository''' is a connection to a database and file store location, which store the node configurations and their associated file content. The Grooper application interacts with the  '''Grooper Repository''' to automate tasks and provide the Grooper user interface.<section end="Grooper Repository" />

=== Grooper Service ===
<section begin="Grooper Service" />'''[[Grooper Service]]s''' are various executable programs that run as a [https://en.wikipedia.org/wiki/Windows_service Windows Services] to facilitate Grooper processing. Service instances are installed, configured, started and stopped using [[Grooper Command Console]] (Or in older Grooper versions, [[Grooper Config]]).<section end="Grooper Service" />

=== Image Processing ===
<section begin="Image Processing Concept" />[[Image Processing (Concept)|Image Processing]], as a conceptual term, refers to how Grooper applies a variety of techniques to enhance scanned documents' quality. Image processing improves [[OCR]] accuracy by removing imperfections and adjusting visual characteristics to prepare images for [[Data Extraction (Concept)|data extraction]] and [[Classification (Concept)|classification]]. Image processing may be applied permanently to an image by the '''''[[Image Processing (Activity)|Image Processing]]''''' '''''Activity''''' or temporarily prior to OCR by the '''''[[Recognize]]''''' activity.<section end="Image Processing Concept" />

=== Import Mode and Document Linking ===
<section begin="Import Mode and Document Linking" />[[Import Mode and Document Linking]] refers to the usage of the '''''Import Mode''''' property. This affects whether or not an imported document maintains a link to its original file and/or if a copy of the file is made on import or not.<section end="Import Mode and Document Linking" />

=== LINQ to Grooper Objects ===
<section begin="LINQ to Grooper Objects" />[https://en.wikipedia.org/wiki/Language_Integrated_Query LINQ] is Microsoft .NET component that provides data querying capabilities to the .NET framework.  In Grooper, you can use the LINQ syntax in [[Code Expressions]] to "[[LINQ to Grooper Objects]]". This allows expressions to access information from collections of data, such as from multi-instance '''Data Sections''' or '''Data Tables'''.<section end="LINQ to Grooper Objects" />

=== Layout Data ===
<section begin="Layout Data" />[[Layout Data]] refers to visual information such as line locations, [https://en.wikipedia.org/wiki/Optical_mark_recognition OMR] checkbox locations and states, barcode values, and detected shapes captured by certain [[Shape Detection|image processing commands]]. This data is stored in a "Grooper.LayoutData.json" file and attached to a {{BatchFolderIcon}} '''[[Batch Folder]]''' or {{BatchPageIcon}} '''[[Batch Page]]''' object. This data can later be recalled by Grooper extractors and other functionality that rely on the presence of that data to function.<section end="Layout Data" />

=== Microfiche Processing ===
<section begin="Microfiche Processing" />[[Microfiche Processing]] refers to Grooper's suite of specialized '''''[[Activity|Activities]]''''' and '''''[[IP Command]]s''''' that process [https://en.wikipedia.org/wiki/Microform#Microfiche microfiche] documents.<section end="Microfiche Processing" />

=== Microsoft Office Integration ===
<section begin="Microsoft Office Integration" />Grooper's [[Microsoft Office Integration]] allows the platform to easily convert [https://en.wikipedia.org/wiki/Microsoft_Word Microsoft Word] and [https://en.wikipedia.org/wiki/Microsoft_Excel Microsoft Excel] files into formats that Grooper can read natively (PDF and CSV).<section end="Microsoft Office Integration" />

=== Mixed Classification ===
<section begin="Mixed Classification" />"[[Mixed Classification]]" refers to leveraging a '''''[[Classification Method]]s''''' and "rules" defined on a {{DocumentTypeIcon}} '''[[Document Type]]''' to overcome the shortcomings of an individual method.<section end="Mixed Classification" />

=== OCR ===
<section begin="OCR" />[[OCR]] is stands for [https://en.wikipedia.org/wiki/Optical_character_recognition Optical Character Recognition]. It allows text on paper documents to be digitized, in order to be searched or edited by other software applications. OCR converts typed or printed text from digital images of physical documents into machine readable, encoded text.<section end="OCR" />

=== OCR Synthesis ===
<section begin="OCR Synthesis" />'''''[[OCR Synthesis]]''''' refers to a suite of [[OCR]] related functionality unique to Grooper. The '''''OCR Synthesis''''' suite will pre-process and re-process raw results from the '''''[[OCR Engine]]''''' and synthesize its results into a single, more accurate OCR result.<section end="OCR Synthesis" />

=== Object Nomenclature ===
<section begin="Object Nomenclature" />The Grooper Wiki's [[Object Nomenclature]] defines how Grooper users categorize and refer to different types of Node Objects in a '''[[Grooper Repository]]'''. Knowing what objects can be added to the Grooper [[Node Tree]] and how they are related is a critical part of understanding Grooper itself.<section end="Object Nomenclature" />

=== PDF Page Types ===
<section begin="PDF Page Types" />[https://en.wikipedia.org/wiki/PDF PDF] pages can be one of several [[PDF Page Types]]. "Page types" describe the kind of content in a PDF page. This informs '''Grooper''' how certain '''''[[Activity|Activities]]''''' should process the page. For example, "single image" pages are [[OCR|OCR'd]] by the '''''[[Recognize]]''''' activity, where "text only" pages have their native text extracted by '''''Recognize'''''.<section end="PDF Page Types" />

=== Prompt Engineering ===
<section begin="Prompt Engineering" />"[[Prompt Engineering]]" is the process of designing and refining prompts to interact more effectively with [https://en.wikipedia.org/wiki/Large_language_model large language models (LLMs)] like [https://en.wikipedia.org/wiki/GPT-4 GPT-4]. The goal is to guide the model to produce desired outputs by carefully crafting the input queries.<section end="Prompt Engineering" />

=== Regular Expression ===
<section begin="Regular Expression" />[[Regular Expression]] (or [https://en.wikipedia.org/wiki/Regular_expression regex]) is a standard syntax designed to parse [https://en.wikipedia.org/wiki/String_(computer_science) text strings]. This is a way of finding information in text. It is the primary method by which '''Grooper''' extracts and returns data from documents.<section end="Regular Expression" />

=== Separation ===
<section begin="Separation" />[[Separation]] is the process of taking an unorganized {{BatchIcon}} '''[[Batch]]''' of loose {{BatchPageIcon}} '''[[Batch Page]]s''' and organizing them into documents represented by {{BatchFolderIcon}} '''[[Batch Folder]]s''' in Grooper. This is done so Grooper can later assign a {{DocumentTypeIcon}} '''[[Document Type]]''' to each document folder in a process known as "[[Classification (Concept)|classification]]".<section end="Separation" />

=== TF-IDF ===
<section begin="TF-IDF" />[[TF-IDF]] stands for [https://en.wikipedia.org/wiki/Tf%E2%80%93idf term frequency-inverse document frequency]. It is a statistical calculation intended to reflect how important a word is to a document within a document set (or "corpus"). It is how '''Grooper''' uses [https://en.wikipedia.org/wiki/Machine_learning machine learning] for training-based document [[Classification (Concept)|classification]] (via the [[Lexical]] method) and [[Data Extraction (Concept)|data extraction]] (via the {{FieldClassIcon}} [[Field Class]] extractor).<section end="TF-IDF" />

=== Table Extraction ===
<section begin="Table Extraction" />"[[Table Extraction]]" refers to '''Grooper's''' ability to extract data from cells in tables on documents.  This is accomplished by configuring the {{DataTableIcon}} '''[[Data Table]]''' and its child {{DataColumnIcon}} '''[[Data Column]]''' elements in a {{DataModelIcon}} '''[[Data Model]]'''.<section end="Table Extraction" />

=== Test Batch ===
<section begin="Test Batch" />a "[[Test Batch]]" refers to any {{BatchIcon}} '''[[Batch]]''' created in the '''Test''' folder of the '''Batches''' folder in the [[Node Tree]]. Test Batches are used to test various configurations in Grooper, such as '''Batch Process Step''' configurations and '''Data Model''' configurations.<section end="Test Batch" />

=== Thread ===
<section begin="Thread" />A [[Thread]] is the smallest unit of processing that can be performed within an [https://en.wikipedia.org/wiki/Operating_system operating system]. In Grooper, threads are allocated for processing by '''''[[Activity Processing]]''''' services.<section end="Thread" />

=== Training-Based Approaches to Document Classification ===
<section begin="Training-Based Approaches to Document Classification" />"[[Training-Based Approaches to Document Classification]]" refers to Grooper '''''Classification Methods''''' that classify {{BatchFolderIcon}} '''[[Batch Folder]]s''' using document examples for each {{DocumentTypeIcon}} '''[[Document Type]]'''. The '''''Classify''''' activity then assigns unclassified '''Batch Folders''' a '''Document Type''' based on how similar it is to the '''Document Type's''' training data.<section end="Training-Based Approaches to Document Classification" />

=== Training Batch ===
<section begin="Training Batch" />The '''[[Training Batch]]''' is a special {{BatchIcon}} '''[[Batch]]''' created when training document examples using the '''''[[Lexical]]''''' classification method. The '''Training Batch''' service two purposes: (1) It is a '''Batch''' that holds all previously trained {{BatchFolderIcon}} '''[[Batch Folder]]s'''. Designers can go to this '''Batch''' to view these documents and copy and paste them into other '''Batches''' if needed. (2) '''Batch Folders''' in the '''Training Batch''' will be used to re-train the '''Content Model's''' classification data when the '''''Rebuild Training''''' command is executed.<section end="Training Batch" />

=== UNC Path ===
<section begin="UNC Path" />[[UNC Path]] is a conceptual term that refers to [https://en.wikipedia.org/wiki/Path_(computing)#UNC UNC (Universal Naming Convention)] which is a standard used in [https://en.wikipedia.org/wiki/Microsoft_Windows Microsoft Windows] for accessing [https://en.wikipedia.org/wiki/Shared_resource shared network folders].<section end="UNC Path" />

=== Waterfall Classification ===
<section begin="Waterfall Classification" />[[Waterfall Classification]] is a [[Classification (Concept)|classification]] technique in Grooper that prioritizes training similarity over classification "rules" set by a {{DocumentTypeIcon}} '''Document Type's''' '''''Positive Extractor'''''. This can be helpful in scenarios where {{BatchFolderIcon}} '''[[Batch Folder]]s''' get misclassified and simply retraining won't help.<section end="Waterfall Classification" />
</div>

== Export Definition ==
<section begin="Export Definition" />'''''[[Export Behavior]]s''''' are defined by adding and configuring one or more '''''[[Export Definition]]s'''''. An '''''Export Definition''''' defines export parameters to external systems, such as [https://en.wikipedia.org/wiki/File_system file systems], [https://en.wikipedia.org/wiki/Content_management_system content management repositories], [https://en.wikipedia.org/wiki/Database databases], or [https://en.wikipedia.org/wiki/Message_transfer_agent mail servers].<section end="Export Definition" />
<div style="padding-left: 1.5em;">
=== CMIS Export ===
<section begin="CMIS Export" />'''''[[CMIS Export]]''''' is an '''''[[Export Definition]]''''' available when configuring an '''''[[Export Behavior]]'''''.  It exports content over a {{CMISConnectionIcon}} '''[[CMIS Connection]]''', allowing users to export documents and their [https://en.wikipedia.org/wiki/Metadata metadata] to various [https://en.wikipedia.org/wiki/On-premises_software on-premise] and [https://en.wikipedia.org/wiki/Cloud_storage cloud-based storage platforms].<section end="CMIS Export" />

=== Data Export ===
<section begin="Data Export" />'''''[[Data Export]]''''' is an '''''[[Export Definition]]''''' available when configuring an '''''[[Export Behavior]]'''''.  It exports extracted document data over a {{DataConnectionIcon}} '''[[Data Connection]]''', allowing users to export data to a [https://en.wikipedia.org/wiki/Microsoft_SQL_Server Microsoft SQL Server] or [https://en.wikipedia.org/wiki/Open_Database_Connectivity ODBC] compliant [https://en.wikipedia.org/wiki/Database database].<section end="Data Export" />
</div>

== Extractor Type ==
<section begin="Extractor Type" />An '''''[[Extractor Type]]''''' (shorthand for '''''Value Extractor Type''''') is configured for numerous properties on a wide array of Grooper objects. They are used to return "[[Data Instance (Concept)|data instances]]" from documents for one purpose or another. The '''''Extractor Type''''' defines an operation that reads data from the text or visual content of a document and returns one or more results. Each different '''''Extractor Type''''' uses a specialized logic to return results. '''''Extractor Types''''' are consumed by higher-level objects such as '''[[Data Element]]s''', [[Object Nomenclature#Extractor Objects|extractor objects]], '''[[Content Type]]s''' and more.<section end="Extractor Type" />
<div style="padding-left: 1.5em;">
=== Ask AI ===
<section begin="Ask AI" />'''''[[Ask AI]]''''' is an '''''[[Extractor Type]]''''' that executes a chat completion using a large language model (LLM), such as OpenAI's GPT models. It uses a document's text content and user-defined instructions (a question about the document) in the chat prompt. '''''Ask AI''''' then returns the response as the extractor's result. '''''Ask AI''''' is a powerful, LLM based extraction method, that can be used anywhere in Grooper an '''''Extractor Type''''' is referenced. It can complete a wide array of tasks in Grooper with simple text prompts.<section end="Ask AI" />

=== Detect Signature ===
<section begin="Detect Signature" />'''''[[Detect Signature]]''''' is an '''''[[Extractor Type]]''''' that cant detect if a handwritten signature is present on a document.  It detects signatures within a specified rectangular region on a document page by measuring the "fill percentage" (what percentage of pixels are filled in the region).<section end="Detect Signature" />

=== Field Match ===
<section begin="Field Match" />'''''[[Field Match]]''''' is an '''''[[Extractor Type]]''''' that matches the value stored in a previously-extracted {{DataFieldIcon}} '''[[Data Field]]''' or {{DataColumnIcon}} '''[[Data Column]]'''.<section end="Field Match" />

=== Find Barcode ===
<section begin="Find Barcode" />'''''[[Find Barcode]]''''' is an '''''[[Extractor Type]]''''' that searches for and returns barcode values previously stored in a {{BatchFolderIcon}} '''[[Batch Folder]]''' or {{BatchPageIcon}} '''[[Batch Page]]'s''' [[Layout Data (Concept)|layout data]].

''Note: Find Barcode differs slightly from [[Read Barcode]]. Read Barcode performs barcode recognition when the extractor executes. Find Barcode can only look up barcode data stored in the document or page's layout data. Find Barcode runs quicker than Read Barcode, but barcode values must have previously been collected in the Batch Process by the Image Processing or Recognize activities.''<section end="Find Barcode" />

=== GPT Complete ===
<section begin="GPT Complete" />
'''''[[GPT Complete]]''''' is an '''''[[Extractor Type]]''''' that leverages Open AI's  [https://en.wikipedia.org/wiki/Generative_pre-trained_transformer GPT] models to generate chat completions for inputs, returning one hit for each result choice provided by the model's response.
:<span style="color: red;">'''''PLEASE NOTE'''''</span>: GPT Complete is a deprecated extractor type. It uses an outdated method to call the [https://en.wikipedia.org/wiki/OpenAI OpenAI] API. Please use the '''''[[Ask AI]]''''' extractor type going forward.<section end="GPT Complete" />

=== Highlight Zone ===
<section begin="Highlight Zone" />'''''[[Highlight Zone]]''''' is an '''''[[Extractor Type]]''''' that sets a highlight region on a document without performing any actual [[Data Extraction (Concept)|data extraction]]. This "extractor" is used to mark areas of interest or importance for '''Review''' users or for uncommon scenarios where a [[Data Instance (Concept)|data instance]] location is needed with no actual value.<section end="Highlight Zone" />

=== Label Match ===
<section begin="Label Match" />'''''[[Label Match]]''''' is an '''''[[Extractor Type]]''''' that matches a list of one or more values using matching options defined by a '''''[[Labeling Behavior]]'''''. It is similar to '''''[[List Match]]''''' but uses shared settings defined in a '''''Labeling Behavior''''' for '''''[[Fuzzy RegEx|Fuzzy Matching]]''''', '''''[[Vertical Wrap]]''''', and '''''[[Constrained Wrap]]'''''.<section end="Label Match" />

=== Labeled OMR ===
<section begin="Labeled OMR" />'''''[[Labeled OMR]]''''' is an '''''[[Extractor Type]]''''' used to output [https://en.wikipedia.org/wiki/Optical_mark_recognition OMR] checkbox labels. It determines whether labeled checkboxes are checked or not. If checked, it outputs the label(s) or a Boolean true/false value as the result.<section end="Labeled OMR" />

=== Labeled Value ===
<section begin="Labeled Value" />'''''[[Labeled Value]]''''' is an '''''[[Extractor Type]]''''' that identifies and extracts a value next to a label. This is one of the most commonly used extractors to extract data from structured documents (such as a standardized form) and static values on semi-structured documents (such as the header details on an invoice).<section end="Labeled Value" />

=== List Match ===
<section begin="List Match" />'''''[[List Match]]''''' is an '''''[[Extractor Type]]''''' designed to return values matching one or more items in a defined list. By default, the '''''List Match''''' extractor does not use or require [https://en.wikipedia.org/wiki/Regular_expression regular expression], but can be configured to utilize regular expression syntax.<section end="List Match" />

=== Ordered OMR ===
<section begin="Ordered OMR" />'''''[[Ordered OMR]]''''' is an '''''[[Extractor Type]]''''' used to return [https://en.wikipedia.org/wiki/Optical_mark_recognition OMR] check box information. '''''Ordered OMR''''' returns information for multiple check boxes within a defined zone based on their order and layout. The zone may be optionally fixed on the page or anchored to a static text value (such as a label).<section end="Ordered OMR" />

=== Pattern Match ===
<section begin="Pattern Match" />'''''[[Pattern Match]]''''' is an '''''[[Extractor Type]]''''' that extracts values from a document that match a specified [https://en.wikipedia.org/wiki/Regular_expression regular expression], providing data collection following a known format or pattern.<section end="Pattern Match" />

=== Query HTML ===
<section begin="Query HTML" />'''''[[Query HTML]]''''' is an '''''[[Extractor Type]]''''' specialized for [https://www.w3schools.com/html/ HTML] documents. It uses either [https://www.w3schools.com/css/ CSS] or [https://www.w3schools.com/xml/xpath_intro.asp XPath] selectors to return the inner text or an attribute of an HTML element.<section end="Query HTML" />

=== Read Barcode ===
<section begin="Read Barcode" />'''''[[Read Barcode]]''''' is an '''''[[Extractor Type]]''''' that uses barcode recognition technology to read and extract values from barcodes found in the document content. 

''Note: Read Barcode differs slightly from [[Find Barcode]]. Read Barcode performs barcode recognition when the extractor executes. Find Barcode can only look up barcode data stored in the document or page's layout data. Find Barcode runs quicker than Read Barcode, but barcode values must have previously been collected in the Batch Process by the Image Processing or Recognize activities.''<section end="Read Barcode" />

=== Read Meta Data ===
<section begin="Read Meta Data" />'''''[[Read Meta Data]]''''' is an '''''[[Extractor Type]]''''' retrieves  metadata values associated with a document. '''''Read Meta Data''''' can return metadata from a {{BatchFolderIcon}} '''[[Batch Folder]]'s''' attachment file based on its MIME type, such as PDF, Word and Mail Message ('message/rfc822' or 'application/vnd.ms-outlook'). It can also return data using a Document Link in Grooper, such as a File System Link or a CMIS Document Link.<section end="Read Meta Data" />

=== Read Zone ===
<section begin="Read Zone" />'''''[[Read Zone]]''''' is an '''''[[Extractor Type]]''''' that allows you to extract text data in a rectangular region (called an "extraction zone" or just "zone") on a document. This can be a fixed zone, extracting text from the same location on a document, or a zone relative to a text value (such as a label) or a shape location on the document.<section end="Read Zone" />

=== Reference ===
<section begin="Reference" />'''''[[Reference]]''''' is an '''''[[Extractor Type]]''''' used to reference an external [[Object Nomenclature#Extractor Objects|extractor object]] within a Grooper property configuration. This allows users to create re-usable extractors and use the more complex {{DataTypeIcon}} '''[[Data Type]]''' and {{FieldClassIcon}} '''[[Field Class]]''' extractors throughout Grooper.<section end="Reference" />

=== Word Match ===
<section begin="Word Match" />'''''[[Word Match]]''''' is an '''''[[Extractor Type]]''''' that extracts individual words or phrases from documents. It used for [https://en.wikipedia.org/wiki/N-gram n-gram] extraction. Each gram may be optionally executed against a {{LexiconIcon}} '''[[Lexicon]]''' to ensure words and phrases only match a set vocabulary.<section end="Word Match" />

=== Zonal OMR ===
<section begin="Zonal OMR" />'''''[[Zonal OMR]]''''' is an '''''[[Extractor Type]]''''' that reads one or more [https://en.wikipedia.org/wiki/Optical_mark_recognition OMR] checkboxes using manually-configured zones. The zone may be optionally fixed on the page or anchored to a static text value (such as a label).

'''''BE AWARE:''''' '''''Zonal OMR''''' is outdated compared to '''''[[Labeled OMR]]''''' and '''''[[Ordered OMR]]'''''. It requires the most manual setup of any OMR extractor to configure. Use this as a last resort when other OMR extractor options have been exhausted.<section end="Zonal OMR" />
</div>

== Fill Method ==
<section begin="Fill Method" />'''''[[Fill Method]]''''' is a configurable property for {{DataModelIcon}} '''[[Data Model]]s''', {{DataSectionIcon}} '''[[Data Section]]s''', and {{DataTableIcon}} '''[[Data Table]]s''' (aka "container elements" or "containers"). '''''Fill Methods''''' provide various mechanisms for populating these containers' child '''[[Data Element]]s'''. '''''Fill Methods''''' are ''secondary'' extraction operations. They populate descendant '''Data Elements''' ''after'' normal extraction during the '''''Extract''''' step.<section end="Fill Method" />
<div style="padding-left: 1.5em;">
=== AI Extract ===
<section begin="AI Extract" />'''''[[AI Extract]]''''' is a '''''[[Fill Method]]''''' that leverages a [https://en.wikipedia.org/wiki/Large_language_model Large Language Model (LLM)] to return extraction results to [[Data Element]]s in a {{DataModelIcon}} '''[[Data Model]]''' or {{DataSectionIcon}} '''[[Data Section]]'''. This mechanism provides powerful AI-based data extraction with minimal setup.<section end="AI Extract" />
</div>

== Functionality ==
<div style="padding-left: 1.5em;">
=== AI Search ===
<section begin="AI Search" />'''''[[AI Search]]''''' enables Grooper's document search and retrieval features in the Search page.  It provides the framework to create document search indexes by '''[[Content Type]]''' and submit documents to an index.  Once indexed, documents can be retrieved by full text searches in the [[Search Page]] with feature rich querying and filtering capabilities. Once retrieved, users can view documents in the Search page, download the results, or submit documents for further processing in Grooper.<section end="AI Search" />

=== AI Generator ===
<section begin="AI Generator" />'''''[[AI Generator]]s''''' create custom documents using the results of a [[Search Page]] query and a large language model (LLM). Both document content and instructions are fed to the LLM to produce a text-based file.<section end="AI Generator" />

=== EDI Integration ===
<section begin="EDI Integration" />[[EDI Integration]] refers to '''Grooper's''' ability to process [https://en.wikipedia.org/wiki/Electronic_data_interchange EDI] files.<section end="EDI Integration" />

=== XML Schema Integration ===
<section begin="XML Schema Integration" />[[XML Schema Integration]] refers to '''Grooper's''' ability to use [https://en.wikipedia.org/wiki/XML_schema XML schemas] to build '''[[Data Model]]s''', extract XML documents, and more.<section end="XML Schema Integration" />
</div>

== IP Command ==
<section begin="IP Command" />'''''[[IP Command]]s''''' specify an [[Image Processing (Concept)|Image Processing (IP)]] operation (such as image cleanup, format conversion or feature detection) and are used to construct {{IPStepIcon}} '''[[IP Step]]s''' in an '''[[IP Profile]]'''. '''''IP Commands''''' are configured using an '''IP Step's''' '''''Command''''' property.<section end="IP Command" />
<div style="padding-left: 1.5em;">
=== Barcode Detection ===
<section begin="Barcode Detection" />'''''[[Barcode Detection]]''''' is an '''''[[IP Command]]''''' that detects and reads [https://en.wikipedia.org/wiki/Barcode barcode] data. The detected barcode information is stored as part of the object's [[Layout Data (Concept)|layout data]].<section end="Barcode Detection" />

=== Binarize ===
<section begin="Binarize" />'''''[[Binarize]]''''' is an '''''[[IP Command]]''''' that converts a color or grayscale image to a bi-tonal (black and white) image using various thresholding methods.<section end="Binarize" />

=== Extract Page ===
<section begin="Extract Page" />'''''[[Extract Page]]''''' is an '''''[[IP Command]]''''' that removes an image from a carrier image while simultaneously removing any image warping or skewing.<section end="Extract Page" />

=== Line Removal ===
<section begin="Line Removal" />'''''[[Line Removal]]''''' is an '''''[[IP Command]]''''' that removes horizontal and vertical lines from documents. The line locations are then stored as part of the object's [[Layout Data (Concept)|layout data]].<section end="Line Removal" />

=== Scratch Removal ===
<section begin="Scratch Removal" />'''''[[Scratch Removal]]''''' is an '''''[[IP Command]]''''' detects and removes or repairs scratches from film-based images.<section end="Scratch Removal" />

=== Shape Detection ===
<section begin="Shape Detection" />'''''[[Shape Detection]]''''' is an '''''[[IP Command]]''''' that detects shapes on a document matching sample images given by the user. The shape locations are then stored as part of the object's [[Layout Data (Concept)|layout data]]<section end="Shape Detection" />

=== Shape Removal ===
<section begin="Shape Removal" />'''''[[Shape Removal]]''''' is an '''''[[IP Command]]''''' detects and removes shapes from documents. The shape locations are then stored as part of the object's [[Layout Data (Concept)|layout data]]<section end="Shape Removal" />
</div>

== Import Provider ==
<section begin="Import Provider" />'''''[[Import Provider]]s''''' enable Grooper to import file-based content from a variety of sources, such as [https://en.wikipedia.org/wiki/File_system file systems], [https://en.wikipedia.org/wiki/Message_transfer_agent mail servers], and [https://en.wikipedia.org/wiki/Content_repository content repositories]. An '''''Import Provider''''' is selected and configured when configuring Import Jobs.  Ad-hoc or "user directed" Import Jobs are submitted from the Imports Page, using the "Submit Import Job" button. Automated or "scheduled" Import Jobs are submitted by an '''[[Import Watcher]]''' service according to its '''''Poling Loop''''' or '''''Specific Times''''' specification. In all cases, the '''''Import Provider''''' is selected using the '''''Provider''''' property.<section end="Import Provider" />
<div style="padding-left: 1.5em;">
=== CMIS Import ===
<section begin="CMIS Import" />'''''[[CMIS Import]]''''' refers to two '''''[[Import Provider]]s''''' used to import content over a {{CMISConnectionIcon}} '''[[CMIS Connection]]''': '''''[[Import Descendants]]''''' and '''''[[Import Query Results]]'''''.  '''''CMIS Imports''''' allow users to import from various on-premise and cloud based storage platforms.<section end="CMIS Import" />

=== Import Descendants ===
<section begin="Import Descendants" />'''''[[Import Descendants]]''''' is one of two '''''[[Import Provider]]s''''' that use {{CMISConnectionIcon}} '''[[CMIS Connection]]s''' to import document content into '''Grooper'''.  '''''Import Descendants''''' imports files or folders in a {{CMISRepositoryIcon}} '''[[CMIS Repository]]''' folder location, including any files or folders in any sub-folders (i.e. "descendant" files or folders).<section end="Import Descendants" />

=== Import Query Results ===
<section begin="Import Query Results" />'''''[[Import Query Results]]''''' is one of two '''''[[Import Provider]]s''''' that use {{CMISConnectionIcon}} '''[[CMIS Connection]]s''' to import document content into '''Grooper'''. '''''Import Query Results''''' imports files or folders in a {{CMISRepositoryIcon}} '''[[CMIS Repository]]''' that match a "[[CMIS Query|CMISQL query]]" (a specialized query language based on SQL database queries).<section end="Import Query Results" />
</div>

== Lookup Specification ==
<section begin="Lookup" />A '''''[[Lookup Specification]]''''' defines a "lookup operation", where existing Grooper fields (called "lookup fields") are used to query an external data source, such as a database. The results of the lookup can be used to validate or populate field values (called "target fields") in Grooper. '''''Lookup Specifications''''' are created on "container elements" ({{DataModelIcon}} '''[[Data Model]]s''', {{DataSectionIcon}} '''[[Data Section]]s''' and {{DataTableIcon}} '''[[Data Table]]s''') using their '''''Lookups''''' property.  Lookups may query using all single-instance fields relative to the container element (including those defined on parent elements up to the root '''Data Model'''), but ''cannot'' be used to populate a field value on a parent of the container element.<section end="Lookup" />
<div style="padding-left: 1.5em;">
=== CMIS Lookup ===
<section begin="CMIS Lookup" />'''''[[CMIS Lookup]]''''' is a '''''[[Lookup Specification]]''''' that performs a lookup against a {{CMISRepositoryIcon}} '''[[CMIS Repository]]''' via a "[[CMIS Query|CMISQL query]]" (a specialized query language based on SQL database queries).<section end="CMIS Lookup" />

=== Database Lookup ===
<section begin="Database Lookup" />'''''[[Database Lookup]]''''' is a '''''[[Lookup Specification]]''''' that performs a lookup against a {{DataConnectionIcon}} '''[[Data Connection]]''' via a [https://en.wikipedia.org/wiki/SQL SQL query].<section end="Database Lookup" />

=== GPT Lookup ===
<section begin="GPT Lookup" />'''''[[GPT Lookup]]''''' is a '''''[[Lookup Specification]]''''' that performs a lookup using an [https://en.wikipedia.org/wiki/OpenAI OpenAI] [https://en.wikipedia.org/wiki/Generative_pre-trained_transformer GPT] model. ''PLEASE NOTE: GPT Lookup should be considered a "beta" feature. It was implemented as a prototype and has not been extensively tested.'' <section end="GPT Lookup" />

=== Web Service Lookup ===
<section begin="Web Service Lookup" />'''''[[Web Service Lookup]]''''' is a '''''[[Lookup Specification]]''''' that looks up external data at an [https://en.wikipedia.org/wiki/API API] endpoint by calling a [https://en.wikipedia.org/wiki/Web_service web service].<section end="Web Service Lookup" />
</div>

== Object ==
<section begin="Object" />In '''Grooper''', objects are defined as configurable elements within its hierarchical tree structure. These include nodes and embedded objects that can be manipulated and edited to define the system's behavior, create workflows, and manage content.<section end="Object" />
<div style="padding-left: 1.5em;">
=== AI Analyst ===
<section begin="AI Analyst" />'''[[AI Analyst]]''' is an object in '''Grooper''' that facilitates the ability to interact with a document as you might with an AI [https://en.wikipedia.org/wiki/Chatbot chatbot].<section end="AI Analyst" />

=== AI Assistant ===
<section begin="AI Assistant" />'''[[AI Assistant]]s''' are Grooper's conversational AI personas. They answer questions about resources it can access (including content from documents, databases and/or web services). This greatly increases an AI's ability to answer domain-specific questions that require access to these resources.<section end="AI Assistant" />

=== Batch ===
<section begin="Batch" />{{BatchIcon}} '''[[Batch (Object)|Batch]]''' objects are fundamental in '''Grooper's''' architecture as they are the containers of documents that get moved through '''Grooper's''' workflow mechanisms known as {{BatchProcessIcon}} '''[[Batch Process (Object)|Batch Processes]]'''.<section end="Batch" />

=== Batch Folder ===
<section begin="Batch Folder" />{{BatchFolderIcon}} '''[[Batch Folder (Object)|Batch Folder]]''' objects are defined as container objects within a {{BatchIcon}} '''[[Batch (Object)|Batch]]''' that are used to represent and organize both folders and pages. They can hold other '''Batch Folders''' or {{BatchPageIcon}} '''[[Batch Page (Object)|Batch Page]]''' objects as children. The '''Batch Folder''' acts as an organizational unit within a '''Batch''', allowing for a structured approach to managing and processing a collection of documents.
* '''Batch Folders''' are frequently referred to simply as "documents".<section end="Batch Folder" />

=== Batch Page ===
<section begin="Batch Page" />{{BatchPageIcon}} '''[[Batch Page (Object)|Batch Page]]''' objects represent individual pages within a {{BatchIcon}}  '''[[Batch (Object)|Batch]]'''. The '''Batch Page''' object is the most granular unit in the hierarchy of [[Object_Nomenclature_(Concept)#Batch_Objects|Batch Objects]] in '''Grooper'''.
* '''Batch Pages''' are frequently referred to simply as "pages".<section end="Batch Page" />

=== Batch Process ===
<section begin="Batch Process" />{{BatchProcessIcon}} '''[[Batch Process (Object)|Batch Process]]''' objects are crucial components in '''Grooper's''' architecture. A '''Batch Process''' orchestrates the document processing strategy and ensures each {{BatchIcon}} '''[[Batch (Object)|Batch]]''' of documents is managed systematically and efficiently.
* '''Batch Processes''' by themselves do nothing.  Instead, the workflows they execute are designed by adding child {{BatchProcessStepIcon}} '''[[Batch Process Step (Object)|Batch Process Steps]]'''.
* A '''Batch Process''' is often referred to as simply a "process".<section end="Batch Process" />

=== Batch Process Step ===
<section begin="Batch Process Step" />{{BatchProcessStepIcon}} '''[[Batch Process Step]]''' objects are specific actions within the sequence defined by a {{BatchProcessIcon}} '''[[Batch Process]]'''. A '''Batch Process Step''' plays a critical role in automating and managing the flow of documents through the various stages of processing within '''Grooper'''.
* '''Batch Process Steps''' are frequently referred to as simply "steps".
* Because a single '''Batch Process Step''' executes a single '''''Activity''''' configuration, they are often referred to by their referenced '''''Activity''''' as well.  For example, a "'''''Recognize''''' step".<section end="Batch Process Step" />

=== CMIS Connection ===
<section begin="CMIS Connection" />{{CMISConnectionIcon}} '''[[CMIS Connection]]''' node objects provide a standardized way of connecting to various [https://en.wikipedia.org/wiki/Content_management_system content management systems (CMS)]. These objects allow '''Grooper''' to communicate with multiple external storage platforms, enabling access to documents and content that reside outside of '''Grooper's''' immediate environment.
* For those that support the [https://en.wikipedia.org/wiki/Content_Management_Interoperability_Services CMIS] standard, the '''CMIS Connection''' connects to the CMS using the CMIS standard.
* For those that do not, the '''CMIS Connection''' normalizes [https://en.wikipedia.org/wiki/Comparison_of_file_transfer_protocols connection and transfer protocol] as if they ''were'' a CMIS platform.<section end="CMIS Connection" />

=== CMIS Repository ===
<section begin="CMIS Repository" />{{CMISRepositoryIcon}} '''[[CMIS Repository]]''' node objects in '''Grooper''' allow access to external documents through a {{CMISConnectionIcon}} '''[[CMIS Connection]]'''. They allows managing and interacting with those documents within '''Grooper's''' framework as if they were local. They are created as a child object of a '''CMIS Connection''' and used for various '''''[[Activity|Activities]]'''''.<section end="CMIS Repository" />

=== Content Category ===
<section begin="Content Category" />{{ContentCategoryIcon}} '''[[Content Category]]''' node objects are containers within a {{ContentModelIcon}} '''[[Content Model]]''' that hold other '''Content Categories''' and {{DocumentTypeIcon}} '''[[Document Type]]''' objects. They allow for further [[Classification|classification]] and grouping of '''Document Types''' within a [https://en.wikipedia.org/wiki/Taxonomy taxonomy], aiding in the logical structuring of complex document sets. Besides grouping '''Document Types''' together, '''Content Categories''' also serve to create new branches in a '''[[Data Element]]''' hierarchy. In most cases '''Content Categories''' are used as organizational buckets to group like '''Document Types''' together.<section end="Content Category" />

=== Content Model ===
<section begin="Content Model" />{{ContentModelIcon}} '''[[Content Model]]''' node objects define the [https://en.wikipedia.org/wiki/Taxonomy taxonomy] of document sets in terms of the {{DocumentTypeIcon}} '''[[Document Type]]''' they contain. They also house the '''[[Data Element]]s''' that appear on each {{ContentCategoryIcon}} '''[[Content Category]]''' and '''Document Type''' within them. '''Content Models''' serve as the root of a '''[[Content Type]]''' hierarchy and are crucial for organizing the different types of documents that '''Grooper''' can recognize and process.<section end="Content Model" />

=== Data Column ===
<section begin="Data Column" />{{DataColumnIcon}} '''[[Data Column]]''' node objects are child objects of a {{DataTableIcon}} '''[[Data Table]]''', representing individual columns and defining the type of data each column holds along with its [[Data Extraction|data extraction]] properties.<section end="Data Column" />

=== Data Connection ===
<section begin="Data Connection" />{{DataConnectionIcon}} '''[[Data Connection]]''' node objects define the settings for connecting to and interacting with a [https://en.wikipedia.org/wiki/Database database]. These interactions may include conducting lookups, exports, or other actions that relate to [https://en.wikipedia.org/wiki/Database#Database_management_system database management systems (DBMS)]. Once configured, a '''Data Connection''' object can be referenced by other components in '''Grooper''' for various DBMS-related activities.<section end="Data Connection" />

=== Data Field ===
<section begin="Data Field" />{{DataFieldIcon}} '''[[Data Field]]''' node objects are created as child objects of a {{DataModelIcon}}  '''[[Data Model]]'''. A '''Data Field''' is a representation of a single piece of data targeted for [[Data Extraction|extraction]] on a document.

'''Data Fields''' are frequently referred to simply as "fields".<section end="Data Field" />

=== Data Model ===
<section begin="Data Model" />{{DataModelIcon}} '''[[Data Model]]''' node objects serve as the top-tier structure defining the [https://en.wikipedia.org/wiki/Taxonomy taxonomy] for '''[[Data Element (Concept)|Data Elements]]''' and are leveraged during the '''[[Extract]]''' '''''[[Activity]]''''' to extract data from a {{BatchFolderIcon}} '''[[Batch Folder]]s'''. They are a hierarchy of '''Data Elements''' that sets the stage for the [[Data Extraction|extraction]] logic and review of data collected from documents.<section end="Data Model" />

=== Data Rule ===
<section begin="Data Rule" />{{DataRuleIcon}} '''[[Data Rule (Object)|Data Rule]]''' objects define the logic for automated data manipulation which occurs after data has been extracted from {{BatchFolderIcon}} '''[[Batch Folder (Object)|Batch Folders]]'''. These rules are applied to normalize or otherwise prepare data collected in a {{DataModelIcon}} '''[[Data Model|Data Model]]''' for downstream processes. '''Data Rules''' ensure that extracted data conforms to expected formats or meets certain quality standards.<section end="Data Rule" />

=== Data Section ===
<section begin="Data Section" />{{DataSectionIcon}} '''[[Data Section (Object)|Data Section]]''' objects are grouping mechanisms for related {{DataFieldIcon}} '''[[Data Field (Object)|Data Fields]]'''. '''Data Sections''' organize and segment child '''[[Data Element (Concept)|Data Elements]]''' into logical divisions of a document based on the structure and semantics of the information the documents contain.<section end="Data Section" />

=== Data Table ===
<section begin="Data Table" />{{DataTableIcon}} '''[[Data Table (Object)|Data Table]]''' objects are utilized for extracting repeating data that's formatted in [https://en.wikipedia.org/wiki/Table_(information) rows and columns], allowing for complex multi-instance data organization that would be present in table-formatted content.<section end="Data Table" />

=== Data Type ===
<section begin="Data Type" />{{DataTypeIcon}} '''[[Data Type (Object)|Data Type]]''' objects hold a collection of child, referenced, and locally defined [[Data Extractor (Concept)|Data Extractors]] and settings that manage how multiple (even differing) matches from Data Extractors are consolidated (via '''''[[Collation Provider (Property)|Collation]]''''') into a result set.<section end="Data Type" />

=== Document Type ===
<section begin="Document Type" />{{DocumentTypeIcon}} '''[[Document Type (Object)|Document Type]]''' objects represent a distinct type of document, like an invoice or contract. '''Document Types''' are created as children of a {{ContentModelIcon}} '''[[Content Model (Object)|Content Model]]''' or a {{ContentCategoryIcon}} '''[[Content Category (Object)|Content Category]]''' and are used to classify individual {{BatchFolderIcon}} '''[[Batch Folder (Object)|Batch Folders]]'''. Each '''Document Type''' in the hierarchy defines the '''[[Data Element (Concept)|Data Elements]]''' and '''''[[Behaviors (Property)|Behaviors]]''''' that apply to '''Batch Folders''' of that specific classification.<section end="Document Type" />

=== Field Class ===
<section begin="Field Class" />{{FieldClassIcon}} '''[[Field Class]]''' node objects are used to find values based on some natural language context near that value. Values are positively or negatively associated with text-based "features" nearby by training the extractor. During [[Data Extraction|extraction]], the extractor collects values based on these training weightings. 
* '''Field Classes''' are most useful when attempting to find values within the flow of natural language. 
* '''Field Classes''' ''can'' be configured to distinguish values within highly structured documents, but this type of extraction is better suited to simpler "Extractor Objects" like {{ValueReaderIcon}} '''[[Value Reader]]s''' or {{DataTypeIcon}}  '''[[Data Type]]s'''.<section end="Field Class" />

=== File Store ===
<section begin="File Store" />{{FileStoreIcon}} '''[[File Store (Object)|File Store]]''' objects define a storage location within '''Grooper''' where file content associated with nodes are saved. They are crucial for managing the content that forms the basis of the '''Grooper's''' processing tasks, allowing for the storage and retrieval of documents, images, and other "files". Not every object in '''Grooper''' will have files connected to it, but if it does, those files are stored in the location defined by this object.<section end="File Store" />

=== Form Type ===
<section begin="Form Type" />{{FormTypeIcon}} '''[[Form Type (Object)|Form Type]]''' objects represent trained variations of a {{DocumentTypeIcon}} '''[[Document Type (Object)|Document Type]]'''.  These objects store [https://en.wikipedia.org/wiki/Machine_learning machine learning] training data for '''''[[Lexical (Classification Method)|Lexical]]''''' and '''''[[Visual (Classification Method)|Visual]]''''' document classification methods.<section end="Form Type" />

=== IP Group ===
<section begin="IP Group" />{{IPGroupIcon}} '''[[IP Group (Object)|IP Group]]''' objects are child objects within {{IPProfileIcon}} '''[[IP Profile (Object)|IP Profiles]]''' that create a hierarchical structure for organizing [[Image Processing (Concept)|image processing]] commands. '''IP Groups''' may contain other '''IP Groups''' or {{IPStepIcon}} '''[[IP Step|IP Step]]''' objects.<section end="IP Group" />

=== IP Profile ===
<section begin="IP Profile" />{{IPProfileIcon}} '''[[IP Profile]]''' node objects detail the operations and parameters for image enhancement and cleanup. These operations improve the accuracy of further processing steps, like  the '''''[[Recognize]]''''' and '''''[[Classify]]''''' '''''[[Activity|Activities]]'''''.<section end="IP Profile" />

=== IP Step ===
<section begin="IP Step" />{{IPStepIcon}} '''[[IP Step]]''' node objects are the basic units within an {{IPProfileIcon}} '''[[IP Profile]]''' that define a single [[Image Processing (Concept)|image processing]] operation. '''IP Steps''' are performed sequentially within their parent {{IPGroupIcon}} '''[[IP Group]]''' or '''IP Profile'''.<section end="IP Step" />

=== Lexicon ===
<section begin="Lexicon" />{{LexiconIcon}} '''[[Lexicon]]''' node objects are dictionary objects that store a list of keys or key-value pairs. '''Lexicons''' can define local entries and/or import entries from other '''Lexicons''' and even import entries using a '''Data Connection'''. The entries in a '''Lexicon''' can be utilized in different areas of '''Grooper''', such as [[Data Extraction|data extraction]], [[Fuzzy RegEx|fuzzy matching]], or [[Correct|OCR correction]], providing a reference point that enhances the accuracy and consistency of the software's operations.<section end="Lexicon" />

=== Machine ===
<section begin="Machine" />{{MachineIcon}} '''[[Machine]]''' node objects represent servers that have connected to the '''[[Grooper Repository]]'''. They allow for the management of [[Grooper Service]] instances and serve as a connection points for processing jobs to be executed on the server hardware. '''Machine''' objects are essential for the scaling of processing capabilities and for distributing processing loads across multiple servers.<section end="Machine" />

=== OCR Profile ===
<section begin="OCR Profile" />{{OCRProfileIcon}} '''[[OCR Profile]]''' node objects configure the settings for optical character recognition ([https://en.wikipedia.org/wiki/Optical_character_recognition OCR]) leveraged by the '''[[Recognize]]''' activity. OCR converts images of text into machine-encoded text. '''OCR Profile''' objects influence how effectively text content is recognized and from {{BatchPageIcon}} '''[[Batch Page]]s'''.<section end="OCR Profile" />

=== Object Library ===
<section begin="Object Library" />{{ObjectLibraryIcon}} '''[[Object Library]]''' node objects are [https://en.wikipedia.org/wiki/.NET_Framework .NET] [https://en.wikipedia.org/wiki/Library_(computing) libraries] that contain code files for customizing the functionality of '''Grooper'''. These libraries are used for a range of customization and integration tasks, allowing users to extend '''Grooper's''' capabilities.
: Examples include:
:* Adding custom '''''[[Activity|Activities]]''''' that execute within '''[[Batch Process]]es'''
:* Creating custom commands available during the '''''[[Review]]''''' '''''[[Activity]]''''' and in the Design page.
:* Defining custom [https://en.wikipedia.org/wiki/Method_(computer_programming) methods] that can be called from [[Expressions|expressions]] on '''Data Field''' and '''Batch Process Step''' objects
:* Establish custom [[Grooper Service]]s that perform automated background tasks at regular intervals<section end="Object Library" />

=== Processing Queue ===
<section begin="Processing Queue" />{{ProcessingQueueIcon}} '''[[Processing Queue]]''' node objects are designed for tasks performed by {{MachineIcon}} '''[[Machine]]s''' and their [[Activity Processing]] services. '''Processing Queues''' are used to distribute Grooper "Code Activity" tasks among different servers and control the concurrency and/or processing rate of these tasks. 
* For example, activities such as '''''[[Render]]''''' or '''''[[Export]]''''' can be managed so that only one activity instance runs per machine or so multiple instances are processed concurrently, according to the queue configuration.<section end="Processing Queue" />

=== Project ===
<section begin="Project" />{{ProjectIcon}} '''[[Project]]''' node objects are the primary containers for configuration nodes within '''Grooper'''. The '''Project''' is where various processing objects such as {{ContentModelIcon}} '''[[Content Model]]s''', {{BatchProcessIcon}} '''[[Batch Process]]es''', [[Object Nomenclature (Concept)#Profile_Objects|profile objects]], and more are organized and managed. It allows for the encapsulation and modularization of these resources for easier management and reusability.<section end="Project" />

=== Resource File ===
<section begin="Resource File" />A '''[[Resource File]]''' node object in '''Grooper''' is essentially a file that is stored as part of a '''Grooper''' {{ProjectIcon}} '''[[Project]]'''. It can include various types of files such as text files or [[XML Schema Integration|XML schema files]].<section end="Resource File" />

=== Review Queue ===
<section begin="Review Queue" />{{ReviewQueueIcon}} '''[[Review Queue]]''' node objects are designated for human-performed tasks. They organizes the '''''[[Review]]''''' tasks that require human attention and can distribute these tasks among different groups of users based on the queue's settings. '''Review Queues''' can be assigned on the {{BatchProcessIcon}} '''[[Batch Process (Object)|Batch Process]]''' level to filter work by an entire process or '''''[[Review]]''''' '''''[[Activity|Activities]]''''' at the {{BatchProcessStepIcon}} '''[[Batch Process Step]]''' level to filter tasks at a more granular step-based level.<section end="Review Queue" />

=== Root ===
<section begin="Root" />The {{GrooperRootIcon}} '''[[Root]]''' node object represents the topmost element of the '''[[Grooper Repository]]'''. It serves as the starting point from which all other objects branch out. It is the anchor point for all other structures within the repository and a necessary element for the organization and linkage of all other objects within '''Grooper'''.<section end="Root" />

=== Scanner Profile ===
<section begin="Scanner Profile" />{{ScannerProfileIcon}} '''[[Scanner Profile]]''' node objects store configuration settings for operating a document scanner. '''Scanner Profiles''' provide users operating the "[[Scan Viewer]]" in '''[[Review]]''' a quick way to select pre-saved scanner configurations.<section end="Scanner Profile" />

=== Separation Profile ===
<section begin="Separation Profile" />{{SeparationProfileIcon}} '''[[Separation Profile (Object)|Separation Profile]]''' objects contain rules and settings that determine how groupings of scanned pages are '''''[[Separate (Activity)|separated]]''''' into individual {{BatchFolderIcon}} '''[[Batch Folder (Object)|Batch Folders]]''', often using [https://en.wikipedia.org/wiki/Barcode barcodes], blank pages, or [https://en.wikipedia.org/wiki/Patch_Code patch codes] as indicators for separation points.<section end="Separation Profile" />

=== Value Reader ===
<section begin="Value Reader" />{{ValueReaderIcon}} '''[[Value Reader]]''' objects define a single [[Data Extraction (Concept)|data extraction]] operation. You set the '''''[[Extractor Type (Property)|Extractor Type]]''''' on the '''Value Reader''' that matches the specific data you're aiming to capture. For example, you would use the '''''[[Pattern Match (Extractor Type)|Pattern Match]]''''' '''''Extractor Type''''' to return data using [https://en.wikipedia.org/wiki/Regular_expression regular expression]. You would use a '''Value Reader''' when you need to extract a single result or list of simple results from a document.<section end="Value Reader" />
</div>

== OCR Engine ==
<section begin="OCR Engine" />An "[[OCR Engine|OCR engine]]" is the part of [[OCR]] software that recognizes text from images. OCR engines analyze the image's pixels to determine where text is on the page and what each character is. In Grooper, OCR engines are selected when configuring an '''[[OCR Profile]]'s''' '''''OCR Engine''''' property.<section end="OCR Engine" />
<div style="padding-left: 1.5em;">

=== Azure OCR ===
<section begin="Azure OCR" />'''''[[Azure OCR]]''''' is an '''''[[OCR Engine]]''''' option for '''[[OCR Profile|OCR Profiles]]''' that utilizes Microsoft Azure's Read API. Azure's Read engine is an AI-based text recognition software that uses a convolutional neural network (CNN) to recognize text. Compared to traditional OCR engines, it yields superior results, especially for handwritten text and poor quality images. Furthermore, Grooper supplements Azure's results with those from a traditional OCR engine in areas where traditional OCR is better than the Read engine.<section end="Azure OCR" />
</div>

== Property ==
<section begin="Property" />A property is a mechanism by which an object in '''Grooper''' is configured that affects how the object performs its function.<section end="Property" />
<div style="padding-left: 1.5em;">
=== Alignment ===
<section begin="Alignment" />'''''[[Alignment (Property)|Alignment]]''''' is a grouping of properties found on '''''[[Fill Method (Property)|Fill Methods]]''''' and '''[[Data Element (Concept)|Data Elements]]''' that manipulate the prompt provided to an [https://en.wikipedia.org/wiki/Large_language_model LLM] [https://en.wikipedia.org/wiki/Chatbot chatbot] in an attempt to provide accurate highlighting of values displayed within the '''[[Document Viewer (UI Element)|Document Viewer]]'''.<section end="Alignment" />

=== Confidence Multiplier and Output Confidence ===
<section begin="Confidence Multiplier and Output Confidence" />Some results carry more weight than others.  The '''''[[Confidence Multiplier and Output Confidence (Property)|Confidence Multiplier]]''''' and '''''[[Confidence Multiplier and Output Confidence (Property)|Output Confidence]]''''' properties allow you to manually adjust an [[Data Extraction (Concept)|extraction]] result's confidence.<section end="Confidence Multiplier and Output Confidence" />

=== Constrained Wrap ===
<section begin="Constrained Wrap" />The '''''[[Constrained Wrap (Property)|Constrained Wrap]]''''' property allows certain '''''[[Extractor Type (Property)|Extractor Types]]''''' and the '''''[[Labeling Behavior (Behavior)|Labeling Behavior]]''''' to match values which wrap from one line to the next inside a box (such as a [https://en.wikipedia.org/wiki/Table_cell table cell]).<section end="Constrained Wrap" />

=== Content Type Filter ===
<section begin="Content Type Filter" />The '''''[[Content Type Filter (Property)|Content Type Filter]]''''' property restricts '''''[[Activity (Property)|Activities]]''''' to specific {{ContentCategoryIcon}} '''[[Content Category (Object)|Content Categories]]''' and/or {{DocumentTypeIcon}} '''[[Document Type (Object)|Document Types]]'''.<section end="Content Type Filter" />

=== Document Quoting ===
<section begin="Document Quoting" />'''[[Document Quoting (Property)|Document Quoting]]''' is a property of the '''''[[AI Extract]]''''' '''''[[Fill Method (Property)|Fill Method]]''''' that limits the text fed to the AI to reduce the amount of tokens consumed. Controlling specifically what is given can not only reduce the monetary cost of using the AI, but also the time cost of running the '''''Fill Method'''''.<section end="Document Quoting" />

=== Output Extractor Key ===
<section begin="Output Extractor Key" />The '''''[[Output Extractor Key (Property)|Output Extractor Key]]''''' property is another weapon in the arsenal of powerful '''Grooper''' [[Classification (Concept)|classification]] techniques.  It allows {{DataTypeIcon}} '''[[Data Type (Object)|Data Types]]''' to return results normalized in a way more beneficial to document classification.<section end="Output Extractor Key" />

=== Paragraph Marking ===
<section begin="Paragraph Marking" />'''''[[Paragraph Marking]]''''' alters the normal text data in a document by placing the [https://en.wikipedia.org/wiki/Carriage_return carriage return] and [https://en.wikipedia.org/wiki/Newline new line feed] pairs at the end of each paragraph, instead of the end of each line. This allows users to break up a document's text flow into segments of paragraphs instead of segments of lines.<section end="Paragraph Marking" />

=== Parameters ===
<section begin="Parameters" />'''''[[Parameters (Property)|Parameters]]''''' is a collection of properties used in the configuration of LLM constructs. Temperature, TopP, Presence Penalty, and Frequency Penalty are parameters that influence text generation in models. Temperature and TopP control the diversity and probability distribution of generated text, while Presence Penalty and Frequency Penalty help manage repetition by discouraging the reuse of words or phrases.<section end="Parameters" />

=== Permission Sets ===
<section begin="Permission Sets" />A '''''[[Permission Sets (Property)|Permission Set]]''''' is a property that allows you to restrict user access to repositories, pages, and certain activities. This helps eliminate the possibility of an unauthorized individual from editing or deleting information or {{BatchIcon}} '''[[Batch (Object)|Batches]]'''.<section end="Permission Sets" />

=== Preprocessing ===
<section begin="Preprocessing" />The '''''[[Preprocessing (Property)|Preprocessing]]''''' grouping of properties consists of settings that adjust how text is formatted and interpreted before any [[Data Extraction (Concept)|Data Extraction]] process begins. These properties are crucial for ensuring that the text data is in the most optimal format for subsequent extraction tasks, which could involve complex regular expressions or precise data parsing.<section end="Preprocessing" />

=== Scope ===
<section begin="Scope" />The '''''[[Scope (Property)|Scope]]''''' property of a {{BatchProcessStepIcon}} '''[[Batch Process Step (Object)|Batch Process Step]]''', as it relates to an '''''[[Activity (Property)|Activity]]''''', determines at which level in a {{BatchIcon}} '''[[Batch (Object)|Batch]]''' hierarchy the '''''Activity''''' runs.<section end="Scope" />

=== Secondary Types ===
<section begin="Secondary Types" />'''''[[Secondary Types (Property)|Secondary Types]]''''' allow the application of multiple '''[[Content Type (Concept)|Content Types]]''' to a single {{BatchFolderIcon}} '''[[Batch Folder (Object)|Batch Folder]]'''.<section end="Secondary Types" />

=== Tab Marking ===
<section begin="Tab Marking" />'''[[Tab Marking]]''' allows you to insert [https://en.wikipedia.org/wiki/Tab_key#Tab_characters tab characters] into a document's text data.<section end="Tab Marking" />

=== Vertical Wrap ===
<section begin="Vertical Wrap" />'''''[[Vertical Wrap (Property)|Vertical Wrap]]''''' is a property of certain '''''[[Extractor Type (Property)|Extractor Types]]''''' and a '''[[Content Type (Concept)|Content Type's]]''' ''[[Labeling Behavior (Behavior)|Labeling Behavior]]'' used to provide simplified [[Data Extraction (Concept)|extraction]] of vertically wrapped text (typically stacked labels).<section end="Vertical Wrap" />
</div>

== Repository Option ==
<section begin="Repository Option" />'''''[[Repository Option]]s''''' are optional features that affect the entire repository. These optional features enable functionality that otherwise do not work without first establishing the connections these options provide. '''''Repository Options''''' are added to a '''Grooper Repository''' and configured using the {{GrooperRootIcon}} '''[[Root]]''' node's '''''Options''''' property. <section end="Repository Option" />
<div style="padding-left: 1.5em;">
=== LLM Connector ===
<section begin="LLM Connector" />'''''[[LLM Connector]]''''' is a '''''[[Repository Option]]''''' that enables [https://en.wikipedia.org/wiki/OpenAI OpenAI-based] functionality for the local '''Grooper''' repository.<section end="LLM Connector" />

=== AI Search ===
{{#lst:Glossary|AI Search}}
</div>

== Section Extract Method ==
<section begin="Section Extract Method" />The '''''Extract Method''''' property of a {{DataSectionIcon}} '''[[Data Section (Object)|Data Section]]''' defines a "Section Extract Method" which specifies how section instances will be identified and extracted.<section end="Section Extract Method" />
<div style="padding-left: 1.5em;">
=== Clause Detection ===
<section begin="Clause Detection" />'''''[[Clause Detection (Section Extract Method)|Clause Detection]]''''' is a {{DataSectionIcon}} '''[[Data Section (Object)|Data Section]]''' '''''Extract Method'''''. It leverages [https://en.wikipedia.org/wiki/Large_language_model LLM] text embedding models to compare supplied samples of text against the text of a document to return what the AI determines is the "chunk" of text that most closely resembles the supplied samples. <section end="Clause Detection" />

=== Nested Table ===
<section begin="Nested Table" />'''''[[Nested Table (Section Extract Method)|Nested Table]]''''' is a {{DataSectionIcon}} '''[[Data Section (Object)|Data Section]]''' '''''Extract Method'''''. This method divides a document into sections by extracting table data within those sections. This gives '''Grooper''' users a method for extracting hierarchical tables as well as dividing up a document into sections where each of those sections have the same table (or at least tabular data which can be extracted by a single {{DataTableIcon}} '''[[Data Table (Object)|Data Table]]''' object).<section end="Nested Table" />

=== Transaction Detection ===
<section begin="Transaction Detection" />'''''[[Transaction Detection (Section Extract Method)|Transaction Detection]]''''' is a {{DataSectionIcon}} '''[[Data Section (Object)|Data Section]]''' '''''Extract Method'''''.  This [[Data Extraction (Concept)|extraction]] method produces section instances by detecting repeating patterns of text around the '''Data Section's''' child {{DataFieldIcon}} '''[[Data Field (Object)|Data Fields]]'''.<section end="Transaction Detection" />
</div>

== Separation Provider ==
<section begin="Separation Provider" />The '''''[[Separation Provider (Property)|Provider]]''''' property of the '''''[[Separate (Activity)|Separate]]''''' '''''[[Activity (Property)|Activity]]''''' defines the type of [[Separation (Concept)|separation]] to be performed at the designated '''''[[Scope (Property)|Scope]]'''''.<section end="Separation Provider" />
<div style="padding-left: 1.5em;">
=== Change in Value Separation ===
<section begin="Change in Value Separation" />The '''''[[Change in Value Separation (Separation Provider)|Change in Value]]''''' '''''[[Separation Provider (Property)|Separation Provider]]''''' creates a new folder and separates every time an extracted value changes from one {{BatchPageIcon}} '''[[Batch Page (Object)|Batch Page]]''' to another.<section end="Change in Value Separation" />

=== Control Sheet Separation ===
<section begin="Control Sheet Separation" />'''''[[Control Sheet Separation (Separation Provider)|Control Sheet Separation]]''''' is a '''''[[Separation Provider (Property)|Separation Provider]]''''' that uses '''Grooper''' {{ControlSheetIcon}} '''Control Sheets''' to separate documents.<section end="Control Sheet Separation" />

=== EPI Separation ===
<section begin="EPI Separation" />The '''''[[EPI Separation (Separation Provider)|EPI Separation]]''''' '''''[[Separation Provider (Property)|Separation Provider]]''''' uses embedded page information ("EPI") to '''''[[Separate (Activity)|Separate]]''''' loose pages into document folders. A [[Data Extractor (Concept)|Data Extractor]] is used to find page numbers from the text on a page and '''Grooper''' uses this information to separate the pages.<section end="EPI Separation" />

=== ESP Auto Separation ===
<section begin="ESP Auto Separation" />'''''[[ESP Auto Separation (Separation Provider)|ESP Auto Separation]]''''' is a '''''[[Separation Provider (Property)|Separation Provider]]''''' used for document separation.  It is unique in that it ''both'' separates ''and'' classifies documents at the same time.  It uses page-level classification training examples (among other things) to determine where to insert document folders in a {{BatchIcon}} '''[[Batch (Object)|Batch]]'''.<section end="ESP Auto Separation" />

=== Event-Based Separation ===
<section begin="Event-Based Separation" />'''''[[Event-Based Separation (Separation Provider)|Event-Based Separation]]''''' is a '''''[[Separation Provider (Property)|Separation Provider]]''''' that '''''[[Separate (Activity)|Separates]]''''' documents using one or more "Separation Events".  Each '''''Separation Event''''' triggers the creation of a new folder.<section end="Event-Based Separation" />

=== Multi Separator ===
<section begin="Multi Separator" />The '''''[[Multi Separator]]''''' '''''[[Separation Provider]]''''' performs [[Separation|separation]] using multiple '''''Separation Providers'''''.  It allows users to create a list of any of the other '''''Separation Providers'''''.  If the first provider on the list fails to separate a page (or, as more often is the case, a series of pages), the next one will be applied.  If that fails, the next, and so on.<section end="Multi Separator" />

=== Pattern-Based Separation ===
<section begin="Pattern-Based Separation" />'''''[[Pattern-Based Separation]]''''' is a '''''[[Separation Provider]]''''' that creates a new document folder every time a value returned by a defined pattern is encountered on a page.<section end="Pattern-Based Separation" />

=== Undo Separation ===
<section begin="Undo Separation" />'''''[[Undo Separation]]''''' is a '''''[[Separation Provider]]'''''.  Instead of putting loose {{BatchPageIcon}} '''[[Batch Page]]s''' into {{BatchFolderIcon}} '''[[Batch Folder]]s''', this '''''Separation Provider''''' removes '''Batch Folders''', leaving only loose pages.<section end="Undo Separation" />
</div>
== Service ==
<section begin="Service" />[[Grooper Service]] is a conceptual term that refers to the various [https://en.wikipedia.org/wiki/Computer_program executable programs] that run as a [https://en.wikipedia.org/wiki/Windows_service Windows Services] to facilitate '''Grooper''' processing. Service instances are installed, started and stopped using '''[[Grooper Command Console]]'''.<section end="Service" />
<div style="padding-left: 1.5em;">
=== API Services ===
<section begin="API Services" />You can perform {{BatchIcon}} '''[[Batch]]''' processing via [https://en.wikipedia.org/wiki/REST REST] [https://en.wikipedia.org/wiki/API API] web calls by installing  '''''[[API Services]]'''''.<section end="API Services" />

=== Activity Processing ===
<section begin="Activity Processing Service" />'''[[Activity Processing]]''' is a [[Grooper Service]] that executes '''[[Activity|Activities]]''' assigned to {{BatchProcessStepIcon}} '''[[Batch Process Step (Object)|Batch Process Steps]]''' in a {{BatchProcessIcon}} '''[[Batch Process]]'''. This allows '''Grooper''' to automate '''Batch Steps''' that do not require a human operator.<section end="Activity Processing Service" />

=== Grooper Licensing ===
<section begin="Grooper Licensing" />'''[[Grooper Licensing]]''' is a [[Grooper Service]] that distributes licenses to multiple workstations running '''Grooper''' applications.<section end="Grooper Licensing" />

=== Import Watcher ===
<section begin="Import Watcher Service" />An '''[[Import Watcher]]''' is a [[Grooper Service]] that schedules and runs import jobs. It periodically executes an [[Import Provider (Property)|Import Provider]] to query or poll for files in a file system or content management system that meet specified criteria. Then, these files are imported into Grooper as documents in a new '''[[Batch]]'''. Afterward, the imported files can be (and should be) moved, deleted, or modified to prevent repeat imports in the next polling cycle.<section end="Import Watcher Service" />

=== Indexing Service ===
<section begin="Indexing Service" />An '''[[Indexing Service]]''' is a [[Grooper Service]] that periodically polls the '''Grooper''' database to automate '''''[[AI Search]]''''' indexing. It checks to see if any documents in a '''Grooper Repository''' are classified as a '''[[Document Type]]''' that inherit from a '''Content Type''' configured with an '''''[[Indexing Behavior]]'''''. If there are any, and they need to be added, updated, or deleted to/from the search index, the '''Indexing Service''' will submit an "Indexing Job" to be picked up by an '''[[Activity Processing]]''' service.<section end="Indexing Service" />
</div>

== Table Extract Method ==
<section begin="Table Extract Method" />A '''''[[Table Extract Method]]''''' defines the settings and logic for a {{DataTableIcon}} '''[[Data Table]]''' to perform [[Data Extraction|extraction]]. It is set by configuring the '''''Extract Method''''' property of the '''Data Table'''.<section end="Table Extract Method" />
<div style="padding-left: 1.5em;">
=== Delimited Extract ===
<section begin="Delimited Extract" />The '''''[[Delimited Extract]]''''' '''''[[Table Extract Method]]''''' extracts tabular data from a [https://en.wikipedia.org/wiki/Delimiter-separated_values delimiter-separated] text file, such as a [https://en.wikipedia.org/wiki/Comma-separated_values CSV file].<section end="Delimited Extract" />

=== Fluid Layout ===
<section begin="Fluid Layout" />The '''''[[Fluid Layout]]''''' '''''[[Table Extract Method]]''''' will choose between '''''[[Tabular Layout]]''''' and '''''Flow Layout''''' configurations, depending on how labels are collected for a {{DocumentTypeIcon}} '''[[Document Type]]'''.<section end="Fluid Layout" />

=== Grid Layout ===
<section begin="Grid Layout" />The '''''[[Grid Layout]]''''' '''''[[Table Extract Method]]''''' uses the positional location of row and column headers to interpret where a tabular grid would be around each value in a table and extract values from each cell in the interpreted grid.<section end="Grid Layout" />

=== Row Match ===
<section begin="Row Match" />The '''''[[Row Match (Table Extract Method)|Row Match]]''''' '''''[[Table Extract Method (Property)|Table Extract Method]]''''' uses regular expression pattern matching to determine a tables structure based on the pattern of each row and extract cell data from each column.<section end="Row Match" />

=== Tabular Layout ===
<section begin="Tabular Layout" />The '''''[[Tabular Layout]]''''' '''''[[Table Extract Method]]''''' uses column header values determined by the {{DataColumnIcon}} '''[[Data Column]]s''''' '''''Header Extractor''''' results (or labels collected for the '''Data Columns''' when a '''''[[Labeling Behavior]]''''' is enabled) as well as '''Data Column''' '''''Value Extractor''''' results to model a table's structure and return its values.<section end="Tabular Layout" />
</div>
== UI Element ==
<section begin="UI Element" />A UI Element is a portion of the '''Grooper''' interface that allows users to interact with or otherwise receive information about the application.<section end="UI Element" />
<div style="padding-left: 1.5em;">
=== Document Viewer ===
<section begin="Document Viewer" />The Grooper [[Document Viewer]] is the portal to your documents. It is the UI that allows you to see a {{BatchFolderIcon}} '''[[Batch Folder]]'s''' (or a {{BatchPageIcon}} '''[[Batch Page]]'s''') image, text content, and more.<section end="Document Viewer" />

=== Node Tree ===
<section begin="Node Tree" />The [[Node Tree]] is the hierarchical list of Grooper node objects found in the left panel in the Design Page.  It is the basis for navigation and creation in the Design Page.<section end="Node Tree" />

=== Overrides ===
<section begin="Overrides" />[[Overrides]] is a tab provided to allow overriding of default properties set to a '''[[Data Element]]'''.<section end="Overrides" />

=== Search Page ===
<section begin="Search Page" />The '''[[Search Page]]''' allows users to leverage '''''[[AI Search]]''''' indexes to query indexed documents. Once queried the user can interact with returned results in several ways, including creating new batches, submitting processing jobs, or even starting a conversation with an AI assistant.<section end="Search Page" />

=== Scan Viewer ===
<section begin="Scan Viewer" />The [[Scan Viewer]] is a user interface that can be added to the user-attended {{ReviewIcon}} '''''[[Review]]''''' step in a {{BatchProcessIcon}} '''[[Batch Process]]'''. It is used to scan documents into {{BatchIcon}} '''[[Batch]]es''' from one or more scanning workstations.<section end="Scan Viewer" />

=== Summary Tabs ===
<section begin="Summary Tabs" />{{ContentModelIcon}} '''[[Content Model (Object)|Content Models]]''' and {{ContentCategoryIcon}} '''[[Content Category (Object)|Content Categories]]''' have a [[Summary Tabs (UI Element)|Summary]] tab where you can view "Descendant Node Types", {{DocumentTypeIcon}} '''[[Document Type (Object)|Document Types]]''', and '''[[Expressions (Concept)|Expressions]]'''.<section end="Summary Tabs" />
</div>

== Miscellaneous Features ==

=== URL Endpoints for Review ===
<section begin="URL Endpoints for Review" />Three different URL endpoints can be used to open '''''[[Review (Activity)|Review]]''''' tasks in the '''[[Grooper Web Client]]''', given certain information like the '''Grooper''' '''''Repository ID''''', {{BatchProcessIcon}} '''[[Batch Process (Object)|Batch Process]]''' name, {{BatchIcon}} '''[[Batch (Object)|Batch]]''' '''''Id''''' and more. This allows Grooper users to link directly to a '''Batch''' in '''''Review''''' with a URL.<section end="URL Endpoints for Review" />

== Disambiguation ==

=== Repository ===
<section begin="Repository" />A "repository" is a general term in computer science referring to where files and/or data is stored and managed. In Grooper, the term "repository" may refer to:
* PRIMARILY a '''[[Grooper Repository]]'''. This is most commonly what people are referring to when they simply say "repository".
* Less commonly a '''[[CMIS Repository]]'''<section end="Repository" />