Grooper Repository (Concept): Difference between revisions

Revision as of 13:39, 28 October 2024

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.

This environment consists of:

a database connection and
a file store location.

The database stores Grooper nodes and their property settings (such as a Content Model or a Data Type or any other Grooper object). The file store location houses content associated with these nodes (such as the image file for a Batch Page object).

For more information

Glossary

Batch Page: contract Batch Page nodes represent individual pages within a inventory_2 Batch. Batch Pages are created in one of two ways: (1) When images are scanned into a Batch using the Scan Viewer. (2) Or, when split from a PDF or TIFF file using the Split Pages activity.

Batch Pages are frequently referred to simply as "pages".

Content Model: stacks Content Model nodes define a classification taxonomy for document sets in Grooper. This taxonomy is defined by the collections_bookmark Content Categories and description Document Types they contain. Content Models serve as the root of a Content Type hierarchy, which defines Data Element inheritance and Behavior inheritance. Content Models are crucial for organizing documents for data extraction and more.

Data Type: pin Data Types are nodes used to extract text data from a document. Data Types have more capabilities than quick_reference_all Value Readers. Data Types can collect results from multiple extractor sources, including a locally defined extractor, child extractor nodes, and referenced extractor nodes. Data Types can also collate results using Collation Providers to combine, sift and manipulate results further.

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.

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

@@ Line 1: / Line 1: @@
-{{stubs}}
 <blockquote>{{#lst:Glossary|Grooper Repository}}</blockquote>
@@ Line 9: / Line 7: @@
 The database stores Grooper nodes and their property settings (such as a '''Content Model''' or a '''Data Type''' or any other Grooper object).  The file store location houses content associated with these nodes (such as the image file for a '''Batch Page''' object).
-{|class="fyi-box"
+=== For more information ===
-|
-'''FYI'''
-|
-Creating (or connecting to) a Grooper Repository is one of the first things you will do after installing Grooper to start designing (or implementing already architected) document processing solutions.
-For more information on how to create or connect to a Grooper Repository, visit the [[Install and Setup]] and/or [[Grooper Config]] articles.
+* [[Install_and_Setup#Creating_a_new_Grooper_Repository|How to create a new Grooper Repository]]
-|}
+* [[Install_and_Setup#Connecting_to_an_existing_Grooper_Repository|How to connect to an existing Grooper Repository]]
+* [[Grooper Infrastructure#Grooper Repository details|Grooper Repository details (includes a list of tables in the Grooper Database)]]
 == Glossary ==