Grooper Node

Grooper Nodes are objects which appear in the main tree structure of a Grooper repository.

List of Grooper Node Types

Name	Description
Batch Processing
Batch	A Batch is a hierarchy of folders and pages which serves as the fundamental unit of capture in Grooper.
Batch Folder	A Batch Folder is a container object within the hierarchical structure of a Batch, which is used to represent logical folders and multipage documents.
Batch Page	A Batch Page object represents an individual page within a Batch.
Batch Process	Defines a repeatable sequence of steps which achieve a specific information processing objective in Grooper.
Batch Process Folder	Represents the 'Batch Processing / Processes' folder found in the root of a Grooper repository.
Batch Process Step	Represents a logical step in a Batch Process.
Batch Processing Folder	Represents the 'Batch Processing' folder found in the root of a Grooper repository.
Batches Folder	A Batches Folder object is a folder which contains Batches.
Control Sheet	A Control Sheet Object is a special page that can be printed out and inserted into stacks of pages that are to be scanned to dynamically perform various functions within Grooper as the pages are scanned.
Project	A Project is defined as a collection of billing items, and can be assigned to Batch Processes.
Content Models
Content Category	A Content Category is a container for other Content Category and Document Type objects within a Content Model.
Content Model	A Content Model defines the taxonomy of a document set, in terms of the Document Types it contains, and the Data Elements which appear on each document type.
Document Type	A Document Type is an object in a Content Model which represents a distinct type of document, such as an invoice or contract. Document Types are ultimately assigned to documents in a batch in a process called classification
Form Type	A Form Type represents a variation or version of a Document Type.
Page Type	A Page Type represents a logical page within a Form Type. A Form Type with 5 pages will contain 5 Page Types as children. Page Types are not configured manually by users, but created internally by Grooper as documents are trained into a Content Model, and are used to store sample pages and the features extracted from those sample pages. The Page Type object has no configurable properties.
Training Page	A Training Page represents an individual page which was used to train a Page Type. Training pages are not created or configured by users - they are created and managed internally by Grooper as documents are trained into a Content Model. Do not delete or edit Training Page objects except as directed by Grooper support staff.
Data Extraction
Data Column	Represents a column in a Data Table.
Data Extraction Folder	Represents the 'Data Extraction' folder found in the root of a Grooper repository.
Data Field	Represents a field.
Data Format	Data Format objects are children of Data Type objects, and represent a distinct format for the Data Type. For example, a date could appear on one document as 05/17/2013, and as May 17, 2013 on another document. Each of these formats is defined by a Data Format object which is a child of the 'Date' Data Type object.
Data Model	Defines the data elements for a content type.
Data Section	A Data Section allows the content of a document to be subdivided into sections for further processing.
Data Table	Data Table objects are used to describe tabular data for the purposes of Data Extraction during Extract and Data Review. The columns in the table are defined by adding child Data Column elements to a Data Table object.
Data Type	A Data Type defines logic for extracting data values or data structures from the text content of a document.
Field Class	A Field Class is a trainable binary classifier, used for locating specific instances of a data pattern on a document.
Infrastructure
CMIS Connection	Defines a connection to an external content storage platform.
CMIS Content Type	Represents a content type defined in a CMIS Repository, and defines import/export mappings between the CMIS Content Type and a Grooper Content Type.
CMIS Repository	Represents a logical container for documents on an external storage platform, when using a CMIS Connection.
Data Connection	Defines a connection to a database.
Database Table	A Database Table object represents an externally-stored database table which can be queried from Grooper.
File Store	A File Store defines a storage location where Grooper can store content files associated with nodes in the Grooper tree structure.
Infrastructure Folder	Represents the 'Infrastructure' folder found in the root of a Grooper repository.
License Server	A License Server object is used to store connection information for a running instance of the Grooper Licensing service.
Machine	The Machine object represents the a server or workstation in the Grooper Enterprise.
Machines Folder	The Machines Folder provides consolidated listings of servers, workstations, and Service Instances.
Object Library	An Object Library is a .NET library containing objects which customize the way Grooper works.
Thread Pool	A Thread Pool is a collection of worker threads which execute Unattended Activities.
Miscellaneous
Folder	Represents a folder object in which objects can be stored.
Grooper Root	Represents the root node of a Grooper repository.
Report Instance	Represents a named configuration of a Grooper Report.
Resources
Global Resources Folder	Represents the 'Global Resources' folder found in the root of a Grooper repository.
IP Group	An IP Group is a container object which is used to create hierarchy and within an IP Profile. IP Groups may contain IP Step or other IP Group objects as children.
IP Profile	An IP Profile defines a sequence of image processing operations which are to be applied to an image.
IP Step	Represents an individual image processing operation in an IP Profile. Specifies an IP Command to execute, along with options which control how the step behaves.
Lexicon	A Lexicon is a dictionary which stores a list of keys or key-value pairs which are indexed for high-speed lookup.
OCR Profile	Defines settings which control how OCR is performed.
Scanner Profile	Defines a connection to a capture device, and settings which control how the device operates.
Scanner Profile Folder	The Scanner Profiles Folder stores Scanner Profile objects created by the Scan Control, and provides a user interface for creating, configuring, and testing Scanner Profiles in Grooper Design Studio.
Separation Profile	Separation Profiles are used to specify how pages will be separated into documents and folders within a batch.

Properties

The following 1 properties are defined.