Grooper Colloquialisms: Difference between revisions

From Grooper Wiki
Tag: Reverted
Line 1: Line 1:
== Glossary==
== Glossary==
'''Content Model''': {{#lst:Glossary|Content Model}}
<big>'''Content Model'''</big>: {{#lst:Glossary|Content Model}}


'''Content Category''': {{#lst:Glossary|Content Category}}
<big>'''Content Category'''</big>: {{#lst:Glossary|Content Category}}


'''Document Type''': {{#lst:Glossary|Document Type}}
<big>'''Document Type'''</big>: {{#lst:Glossary|Document Type}}


'''CMIS Connection''': {{#lst:Glossary|CMIS Connection}}
<big>'''CMIS Connection'''</big>: {{#lst:Glossary|CMIS Connection}}


== ABout ==
== ABout ==

Revision as of 12:18, 30 April 2024

Glossary

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.

Content Category: collections_bookmark A Content Category is a container for other Content Category or description Document Type nodes in a stacks Content Model. Content Categories are often used simply as organizational buckets for Content Models with large numbers of Document Types. However, Content Categories are also necessary to create branches in a Content Model's classification taxonomy, allowing for more complex Data Element inheritance and Behavior inheritance.

Document Type: description Document Type nodes represent a distinct type of document, such as an invoice or a contract. Document Types are created as child nodes of a stacks Content Model or a collections_bookmark Content Category. They serve three primary purposes:

  1. They are used to classify documents. Documents are considered "classified" when the folder Batch Folder is assigned a Content Type (most typically, a Document Type).
  2. The Document Type's data_table Data Model defines the Data Elements extracted by the Extract activity (including any Data Elements inherited from parent Content Types).
  3. The Document Type defines all "Behaviors" that apply (whether from the Document Type's Behavior settings or those inherited from a parent Content Type).

CMIS Connection: cloud CMIS Connections provide a standardized way of connecting to various content management systems (CMS). CMIS Connections allow Grooper to communicate with multiple external storage platforms, enabling access to documents and document metadata that reside outside of Grooper's immediate environment.

  • For those that support the CMIS standard, the CMIS Connection connects to the CMS using the CMIS standard.
  • For those that do not, the CMIS Connection normalizes connection and transfer protocol as if they were a CMIS platform.

ABout

  • "Step"
    • Batch Procss Step
    • IP Step
  • "Recognize Step"
    • Batch Process Step who's Activity property is set to Recognize
  • "Page"
    • Batch Page
  • "Folder"
    • A folder in the node tree
    • Batch Folder
    • A browsable location in a CMIS repository
  • "Document"
    • A Batch Folder with content
      • May include an attachment, or Batch Pages
    • May or may not be classified
  • "Extractor"
    Always refer to extractor properties by their full property name
    • Data Field's Value Extractor property
    • Extractor Type
      • such as Labeled Value, Pattern Match, etc.
    • Extractor object
      • Data Type, Field Class, Value Reader
  • "Field"
    • Data Field only
  • "Section"
    • Data Section
  • "Table"
    • Data Table
  • "Column"
    • Data Column
  • "Cell" (not "Field")
    • The singular Data Column instance for a single row instance
  • "Doc Type"
    • Always refer to Document Types as Document Types
  • "Model"
    • Always refer specifically to either a Content Model or Data Model
  • "Expression(s)"
    • specifically refers to a .NET expression, not a regular expression pattern
  • "Profile"
    • used to refer to the group of "Profile Objects", never an individual Profile Object
  • "Level 1"
    • May refer to the Scope of Folder and Folder Level of 1 as "Level 1"


Glossary

Click to expand/collapse the Glossary (partial)

OBJECTS (click to expand/collapse)


Batch Objects (click to expand/collapse)


Batch (click to expand/collapse)


Batch Folder (click to expand/collapse)

Colloquialisms

  • Referred to as "document" when the Batch Folder has content (child Batch Pages or an attachment), ie not an empty Batch Folder
  • Referred to as "folder" when the Batch Folder is empty or is used only when creating hierarchy in a Batch

Batch Page (click to expand/collapse)

Colloquialisms

  • Referred to as "page"

Process Objects (click to expand/collapse)


Batch Process (click to expand/collapse)


Batch Process Step (click to expand/collapse)

Colloquialisms

  • Referred to as "step"
  • A Batch Process Step who's Activity property is set to Recognize may be referred to as "Recognize Step" (the same is true for any other activity)

ACTIVITIES (click to expand/collapse)

Click to expand/collapse the Glossary (all)

OBJECTS


Batch Objects


Batch


Batch Folder

Colloquialisms

  • Referred to as "document" when the Batch Folder has content (child Batch Pages or an attachment), ie not an empty Batch Folder
  • Referred to as "folder" when the Batch Folder is empty or is used only when creating hierarchy in a Batch

Batch Page

Colloquialisms

  • Referred to as "page"

Process Objects


Batch Process


Batch Process Step

Colloquialisms

  • Referred to as "step"
  • A Batch Process Step who's Activity property is set to Recognize may be referred to as "Recognize Step" (the same is true for any other activity)

ACTIVITIES


Activities