Extract (Activity) - Revision history

Dsmith: /* What is the Extract Activity? */

2025-11-21T21:21:30Z

What is the Extract Activity?

@@ Line 27: / Line 27: @@
 When the Extract Activity runs, it uses these elements to extract data from each document in the [[Batch]], populating the corresponding [[Data Model]] for each document.
 === Value Extractors ===
@@ Line 34: / Line 41: @@
 These are properties that you can configure on a Data Field, Data Table, and/or Data Section.
-=== Data Hierarchy ===
+=== Extractor Nodes ===
-As discussed earlier, you can create hierarchical relationships within a single Data Model using Data Sections and Data Tables.  As a direct child of a Data Model a Data Field will execute against the entire document.  However, as a child of a Data Section a Data Field will only execute against the portion of the document described by that Data Section.
+<big>Field Class</big>
-Data Models also benefit from a Content Model's inheritance structure.  For example, the Content Model itself may have a Data Model but a Document Type may also have its own Data Model.  The Document Type, as a child of the Content Model, will inherit all Data Elements' from the parent Content Model's Data Model.
+A Field Class is for situations where several similar candidates appear (multiple dates, totals, names) and only one is correct. It uses training: you review examples, mark correct and incorrect instances, and it learns which nearby words or layout patterns signal the right one.
 == Why use the Extract Activity? ==

Dsmith: /* Why use the Extract Activity? */

2025-11-21T20:55:29Z

Why use the Extract Activity?

← Older revision		Revision as of 15:55, 21 November 2025
Line 41:		Line 41:

	== Why use the Extract Activity? ==		== Why use the Extract Activity? ==
	~~The Extract Activity is essential because it is part of the '''Collect Phase''' in Grooper’s five-phase processing model. This phase is where data is gathered from documents in a [[Batch]]. Without~~ extraction, there would be no data to review, validate, or export in later phases.		Simply put, without extraction, there would be no data to review, validate, or export in later phases. So, if you want to gather ANY data from a document in Grooper, this Activity is vital.

	Key reasons to use the Extract Activity:		Key reasons to use the Extract Activity:

Dsmith: /* What is the Extract Activity? */

2025-11-21T20:53:18Z

What is the Extract Activity?

← Older revision		Revision as of 15:53, 21 November 2025
Line 18:		Line 18:
	* Deliver		* Deliver
	** Documents are exported from Grooper to wherever the user or organization deems fit.		** Documents are exported from Grooper to wherever the user or organization deems fit.


	Extraction is defined by extraction objects within the Node Tree, and then organized by the Data Model through Data Hierarchy. These objects (which are child objects of the Data Model) are:		Extraction is defined by extraction objects within the Node Tree, and then organized by the Data Model through Data Hierarchy. These objects (which are child objects of the Data Model) are:

Dsmith: /* What is the Extract Activity? */

2025-11-21T20:53:01Z

What is the Extract Activity?

@@ Line 5: / Line 5: @@
 == What is the Extract Activity? ==
 The '''Extract Activity''' in Grooper is a core step in document processing that performs data extraction from documents in a [[Batch]]. Its main purpose is to populate the [[Data Model]] with extracted information, making it available for review, validation, and export.
 Extraction is defined by extraction objects within the Node Tree, and then organized by the Data Model through Data Hierarchy. These objects (which are child objects of the Data Model) are:

Dsmith: /* Configuring the Extract Activity */

2025-11-21T20:23:34Z

Configuring the Extract Activity

← Older revision		Revision as of 15:23, 21 November 2025
Line 49:		Line 49:

	* '''Mode''': Choose how extraction handles existing data (Normal, Additive, or Recalculate).		* '''Mode''': Choose how extraction handles existing data (Normal, Additive, or Recalculate).
			** '''Normal''': Existing extraction results will be overwritten.
			** '''Additive''': Data Elements that already have a value from previous extraction will not have those values overwritten — Grooper will only perform extraction for Data Elements that do not have extracted data already.
			** '''Recalculate''': All calculated fields will be recalculated, and full validation performed.
	* '''Default Content Type''': Set a fallback [[Content Type]] for unclassified folders.		* '''Default Content Type''': Set a fallback [[Content Type]] for unclassified folders.
	* '''Content Type Filter''': Optionally restrict extraction to specific [[Content Type]]s.		* '''Content Type Filter''': Optionally restrict extraction to specific [[Content Type]]s.

Dsmith: /* Configuring the Extract Activity */

2025-11-21T20:17:40Z

Configuring the Extract Activity

← Older revision		Revision as of 15:17, 21 November 2025
Line 61:		Line 61:


	[[file:2025_Extract_(Activity)_How_to_add_the_Extract_Activity_Configuring_the_Extract_Activty_01.png]]		[[file:2025_Extract_(Activity)_How_to_add_the_Extract_Activity_Configuring_the_Extract_Activty_01(1).png]]

	{\|class="fyi-box"		{\|class="fyi-box"

Dsmith: /* How to add the Extract Activity */

2025-11-21T20:03:59Z

How to add the Extract Activity

← Older revision		Revision as of 15:03, 21 November 2025
Line 62:		Line 62:

	[[file:2025_Extract_(Activity)_How_to_add_the_Extract_Activity_Configuring_the_Extract_Activty_01.png]]		[[file:2025_Extract_(Activity)_How_to_add_the_Extract_Activity_Configuring_the_Extract_Activty_01.png]]

			{\|class="fyi-box"
			\|-
			\|
			'''FYI'''
			\|
			When adding the Extract Activity to your Batch Process, it is ''crucial'' that the step be added AFTER Recognize. This will ensure that there is text and layout data to extract.
			\|}

	===To test the Extract Activity on the Batch Process Step:===		===To test the Extract Activity on the Batch Process Step:===

Dsmith: /* How to add the Extract Activity */

2025-11-21T19:50:38Z

How to add the Extract Activity

← Older revision		Revision as of 14:50, 21 November 2025
Line 38:		Line 38:

	# Open the desired [[Batch Process]] in Grooper Design Studio.		# Open the desired [[Batch Process]] in Grooper Design Studio.
	# Right-click on the process tree and select ~~'''~~Add Activity~~'''~~.		# Right-click on the process tree and select "Add Activity".
	# In the activity type list, choose ~~'''~~Extract~~'''~~ and click ~~'''~~OK~~'''~~.		# In the activity type list, choose "Extract" and click "OK".
	# Select the new Extract Activity node.		# Select the new Extract Activity node.
	# Configure properties if need be.		# Configure properties if need be.

Dsmith: /* Why use the Extract Activity? */

2025-11-21T19:47:44Z

Why use the Extract Activity?

← Older revision		Revision as of 14:47, 21 November 2025
Line 30:		Line 30:

	Key reasons to use the Extract Activity:		Key reasons to use the Extract Activity:
	* It collects structured data from documents, enabling ~~downstream~~ review and export.		* It collects structured data from documents, enabling review (if necessary) and export.
	* It ensures that the [[Data Model]] is populated, making extracted data available for business processes.		* It ensures that the [[Data Model]] is populated, making extracted data available for business processes.
	* It is a required step for ~~any solution that needs to transform unstructured~~ documents ~~into usable data~~.		* It is a required step for getting data from documents.

	== How to add the Extract Activity ==		== How to add the Extract Activity ==

Dsmith: /* Data Extractors */

2025-11-21T19:37:48Z

Data Extractors

← Older revision		Revision as of 14:37, 21 November 2025
Line 14:		Line 14:
	When the Extract Activity runs, it uses these elements to extract data from each document in the [[Batch]], populating the corresponding [[Data Model]] for each document.		When the Extract Activity runs, it uses these elements to extract data from each document in the [[Batch]], populating the corresponding [[Data Model]] for each document.

	=== ~~Data~~ Extractors ===		=== Value Extractors ===

	After defining what Data Elements you want to extract, you need to define how to populate those fields, tables, and sections with data. This is done with [[~~Data~~ Extractor]]s, often shorthanded to just "extractors".		After defining what Data Elements you want to extract, you need to define how to populate those fields, tables, and sections with data. This is done with [[Value Extractor]]s, often shorthanded to just "extractors".

	These are properties that you can configure on a Data Field, Data Table, and/or Data Section.		These are properties that you can configure on a Data Field, Data Table, and/or Data Section.