Grooper Node: Difference between revisions

Revision as of 15:30, 20 September 2023

Any single item (or "object") in the Node Tree is a Grooper Node. Also simply referred to as a "node". Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.

There are six main nodes in the Node Tree. These nodes serve the purpose of organizing Grooper objects to assist Node Tree navigation.

Batches
Projects
Processes
Queues
File Stores
Machines

Every Grooper Repository will contain these nodes and their base child node contents. All other objects created, including (but not limited to) Batches, Content Models, and Data Extractors, will be created as children of one of these six nodes (or folder nodes within these nodes).

Nodes pass information to and from each other through "inheritance".

The parent node dictates inheritance. It controls what child objects can be created underneath it in the tree hierarchy, as well as what information is passed to and from the parent and child nodes.
- The parent node will always determine what objects (if any) can be created as children.
  - For example, a Data Table can only have Data Columns as its children.
- The parent node may simply be a folder containing child objects.
  - For example, a Content Model's Local Resources folder.
- The parent node may have a complex inheritance relationship.
  - For example, a Data Type's children Value Readers will pass all results they return to the parent Data Type. Those results will then be collated according to the Data Type's configuration.

In Grooper, nodes and their properties are stored in the database connected to a Grooper Repository.

@@ Line 1: / Line 1: @@
 <onlyinclude>
 <blockquote style="font-size:14pt">
-Any single item (or [[Object|object]]) in the [[Node Tree]] is a '''Grooper Node'''.  Also simply referred to as a "[[Node|node]]".  Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.
+Any single item (or "object") in the [[Node Tree]] is a '''Grooper Node'''.  Also simply referred to as a "node".  Each new node creates a new branch under an existing one, creating the hierarchical structure of the tree.
 </blockquote>
 There are six main nodes in the Node Tree.  These nodes serve the purpose of organizing Grooper objects to assist Node Tree navigation.
-* '''[[Batch Processing Folder]]'''
+* '''Batches'''
-* '''[[Content Models Folder]]'''
+* '''Projects'''
-* '''[[Data Extraction Folder]]'''
+* '''Processes'''
-* '''[[Global Resources Folder]]'''
+* '''Queues'''
-* '''[[Infrastructure Folder]]'''
+* '''File Stores'''
-* '''[[Reports Folder]]'''
+* '''Machines'''
-Every [[Grooper Repository]] will contain these nodes and their base [[Child|child]] node contents.  All other objects created, including (but not limited to) '''[[Batch]]es''', '''[[Content Model]]s''', and [[Data Extractor]]s, will be created as children of one of these six nodes (or folder nodes within these nodes).
+Every [[Grooper Repository]] will contain these nodes and their base child node contents.  All other objects created, including (but not limited to) '''[[Batch]]es''', '''[[Content Model]]s''', and [[Data Extractor]]s, will be created as children of one of these six nodes (or folder nodes within these nodes).
-Nodes pass information to and from each other through "[[Inheritance|inheritance]]".  The [[Parent|parent]] node dictates inheritance.  It controls what [[Child|child]] objects can be created underneath it in the tree hierarcy, as well as what information is passed to and from the parent and child nodes.
+Nodes pass information to and from each other through "inheritance".
-* The parent node will always determine what objects can be created as children.  For example, a '''Data Table''' can only have '''Data Columns''' as its children.
+* The parent node dictates inheritance.  It controls what child objects can be created underneath it in the tree hierarchy, as well as what information is passed to and from the parent and child nodes.
-* The parent node may simply be a folder containing child objects, as is the case in a '''Content Model's''' '''Local Resources''' folder.
+** The parent node will always determine what objects (if any) can be created as children.
-* The parent node may have a complex inheritance relationship.
+***For example, a '''Data Table''' can only have '''Data Columns''' as its children.
-** For example, a '''Data Type's''' children '''Value Readers''' will pass all results they return to the parent '''Data Type'''.  Those results will then be collated according to the '''Data Type's''' configuration.
+** The parent node may simply be a folder containing child objects.
+*** For example, a '''Content Model's''' '''Local Resources''' folder.
+** The parent node may have a complex inheritance relationship.
+*** For example, a '''Data Type's''' children '''Value Readers''' will pass all results they return to the parent '''Data Type'''.  Those results will then be collated according to the '''Data Type's''' configuration.
-In Grooper, nodes and their properties are stored in the database connected to a [[Grooper Repository]].
+In Grooper, nodes and their properties are stored in the database connected to a Grooper Repository.
 </onlyinclude>
 [[Category:Articles]]