2023.1:Batch (Object): Difference between revisions

From Grooper Wiki
No edit summary
No edit summary
 
(24 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<onlyinclude>
{{AutoVersion}}
<blockquote style="font-size:14pt">
'''Batches''' are the fundamental units of encapsulating documents in Grooper.  They are a hierarchy of folders and pages used to represent documents and process them.
</blockquote>


'''Batch''' objects in Grooper house two child objects.
<blockquote>{{#lst:Glossary|Batch}}</blockquote>
# The root '''[[Batch Folder]]''', containing a hierarchy of '''Batch Folders''' and '''[[Batch Page]]s'''.
 
# A read-only '''[[Batch Process]]''', containing the list of processing instructions for the '''Batch Folders''' and '''Batch Pages'''
{|class="download-box"
</onlyinclude>
|
[[File:Asset 22@4x.png]]
|
You may download the ZIP(s) below and upload it into your own '''Grooper''' environment (version 2023.1). This contains one or more '''Batches''' of sample documents.
* [[Media:2023.1 Wiki Batch Batch.zip]]
|}


== About ==
== About ==
=== What is a Batch? ===
A '''Batch''' is an object in '''Grooper''' that contains the documents brought into '''Grooper''' via scanning or import.


There are three components to a batch:
There are three components to a batch:


# The [[Batch]] itself
# The '''Batch''' itself
# [[Batch Folder]]s
# '''Batch Folders'''
# [[Batch Page]]s
# '''Batch Pages'''
 
'''Batch''' objects in '''Grooper''' contain two child objects:
* The root '''Batch Folder''', containing a hierarchy of '''Batch Folders''' and '''Batch Pages'''.
* A read-only '''Batch Process''', containing the list of processing instructions for the '''Batch Folders''' and '''Batch Pages'''
 
Below is an example of a '''Batch'''.
 
# The Test '''Batch''' is located here on the node tree.
# The Test '''Batch''' has two child objects, the root '''Batch Folder''' and a read-only '''Batch Process'''.
[[File:23.1 Batch 01 About 01 What is a Batch 01.png]]
 
 
# If we open up the root '''Batch Folder'''...
# We can see the '''Batch Pages'''. We can also view the hierarchy of '''Batch Folders''' and '''Batch Pages''' here after [[Separation]].
[[File:23.1 Batch 01 About 01 What is a Batch 02.png]]
 
 
# If we click on the '''Batch''' object in the node tree...
# We can click on the "Viewer" tab to see the "Batch Viewer".
# Here we can see the contents of the '''Batch'''.
[[File:23.1 Batch 01 About 01 What is a Batch 03.png]]
 
 
# At the top level is the '''Batch''' itself.
# Here we have the '''Batch Pages''' in the '''Batch'''.
# Here we can see the '''Batch''' and '''Batch Pages''' as objects in the node tree.
[[File:23.1 Batch 01 About 01 What is a Batch 04.png]]
 
 
# Through the process of separation, '''Batch Pages''' will be separated into document folders.
# These '''Batch Pages''' are at the '''''Scope''''' of ''Page''
# Here we can see the hierarchy of '''Batch Folders''' and '''Batch Pages''' within the '''Batch''' in the node tree.
[[File:23.1 Batch 01 About 01 What is a Batch 05.png]]
 
=== Folder Levels ===
When scanning paper into '''Grooper''', the '''Batch Pages''' come in one at a time and there is no differentiation between one document or another. As part of '''Grooper''''s workflow, '''Batch Pages''' are normally separated into '''Batch Folders''' (each folder containing one complete document) so that '''Grooper''' knows where one document begins and ends.
 
A '''Batch''' can be as simple as a series of '''Batch Pages'''. A '''Batch''' may also consist of a complex hierarchy of '''Batch Folders'''.
 
For certain activities, it is important to tell '''Grooper''' which '''''Folder Level''''' the '''''Activity''''' needs to be executed on.
 
* The '''''Scope''''' of ''Batch'' refers to the top most '''Batch Folder'''. All '''Batch Folders''' and '''Batch Pages''' exist within this main '''Batch Folder'''. While never referred to as "Level 0" anywhere in '''Grooper''', considering 0 indexing, it may be easy to think of it as such.
* The first set of '''Batch Folders''' under the main '''Batch Folder''' is considered '''''Folder Level''''' ''1''.
* A '''Batch Folder''' that is a child of a '''Batch Folder''' at '''''Folder Level''''' ''1'' is considered at '''''Folder Level''''' ''2''. A '''Batch Folder''' that is a child of a '''Batch Folder''' at '''''Folder Level''''' ''2'' is considered at '''''Folder Level''''' ''3'', etc.
* A '''Batch Page''' is always considered to be at the '''''Scope''''' of ''Page''.
**Sometimes you will have '''Batch Pages''' inside '''Batch Folders''' at different '''''Folder Levels''''' in the '''''Scope''''' of the '''Batch''', but you always want to run certain activities on all '''Bath Pages'''. You would set those activities to a '''''Scope''''' of ''Page''.
 
For example, OCR text is obtained from images by running a '''''[[Recognize]]''''' '''''Activity''''' at the '''''Scope''''' of ''Page''. Document classification is done by running a '''''[[Classify]]''''' '''''Activity''''' at the '''''Scope''''' of ''Folder''. '''[[Export]]''' is an example of an '''''Activity''''' that could possibly be run at either a '''''Scope''''' of ''Batch'' or ''Folder''.
 
---------
[[File:23.1 Batch 01 About 02 Folder Levels 01.png]]
---------
[[File:23.1 Batch 01 About 02 Folder Levels 02.png]]
---------
 
=== Production vs Test Batches ===
'''Batches''' exist in two environments:
 
* '''"Production"'''
** Stored in the "Batches > Production" branch of the '''Grooper''' node tree.
** The '''Batch''' is contained in a folder according to the '''Batch Process''' being applied to the '''Batch'''.
* '''"Test"'''
** Stored in the "Batches > Test" branch of the '''Grooper''' node tree.
 
# In the image below you can see a '''Batch''' within the "Production" folder.
# A '''Batch''' is also seen existing within the "Test" folder.
 
[[File:23.1 Batch 01 About 03 Production vs Test Batches 01.png]]
 
 
So, what are the differences between a "Test" and "Production" '''Batch'''?
 
* '''"Test Batches"''': These are only visible to '''Grooper''' Design users. They are used to test extraction and '''Batch Process''' steps being designed. These '''Batches''' are not exposed to '''[[Activity Processing]]''' services.
* '''"Production Batches"''': These '''Batches''' are visible from the "Batches" page and. Production '''Batches''' are "visible" to '''Activity Processing''' services and are actively run through a '''Batch Process''' that has previously been designed and published.
 
Both "Test" and "Production" '''Batches''' can be created and processed from the '''Grooper''' Design page by Design users. However, typically, production '''Batches''' are created and processed using the "Batches" page. This also means that different users that are part of different [[image:GrooperIcon_ReviewQueue.png]] '''[[Review Queue]]s''' can affect '''Batch''' workflow.
 
Test '''Batches''', however, will only be seen by "Design" users.


Below is an extremely simple Batch.  We are viewing it Grooper Dashboard, using the "Batch Viewer" tab.  Multiple folder levels can be created in a batch depending on how complicated your documents are.
# This is the "Design" page icon
# This is the "Batches" page icon


[[File:23.1 Batch 01 About 03 Production vs Test Batches 02.png]]


{|cellpadding="10" cellspacing="5" style="margin:auto"
== How To ==
|-valign="top"
=== Creating a Test Batch ===
|style="width:33%"|At the top level is the '''[[Batch]]''', named here "Simple Batch".
Creating a Test '''Batch''' is relatively simple. First, you must create an empty '''Batch'''. Then you can just drag and drop the files from your computer into the '''Batch'''.
|style="width:33%"|Contained inside are Batch Folders and Batch Pages.  Here, it is just a collection of .TIFF '''[[Batch Page]]''' images of invoices.
 
|style="width:33%"|We create can create a hierarchical structure by separating pages into folders.  In the example below, one '''[[Batch Folder]]''' was created for every Batch Page.
# To add a Test '''Batch''', right-click on the "Test" folder in the node tree.
|-
# Hover over "Add" and then click on "Batch..."
|[[image:1572881419282-110.png|center|300px]]||[[image:1572881490382-273.png|center|300px]]||[[image:1572881745304-100.png|center|300px]]
 
|}
[[File:23.1 Batch 02 How To 01 Creating a Test Batch 01.png]]
 
 
# In the "Add" dialog box give your '''Batch''' a name.
# Click "EXECUTE" to create the '''Batch'''.
 
[[File:23.1 Batch 02 How To 01 Creating a Test Batch 02.png]]
 
 
# Select the newly created '''Batch'''.
# Select the "Viewer" tab.
# Now you can see that we have an empty '''Batch'''. All you need to do now is to drag and drop a file from your computer to this area and your file(s) will be added to '''Grooper'''.


[[File:23.1 Batch 02 How To 01 Creating a Test Batch 03.png]]


A Batch can have one or more levels of [[Batch Folder]]s.  A Batch may even start out having no folder levels.  [[Batch Page]]s can exist at any level in the batch, but will most often be bottom-most level. 


Documents are represented as [[Batch Folder]]s with [[Batch Page]]s inside.  So, a two-page document would be a Batch Folder with two Batch Pages inside, one for the first and one for the last.  Part of Grooper's document processing workflow is (usually) separating documents from loose pages by setting up logical points to create new Batch Folders and put Batch Pages inside.
# A PDF file has been "drag-and-dropped" onto the '''Batch Folder''' of the '''Batch''', thus creating a '''Batch Folder''' with the PDF as an attachment.  


However, all [[Batch Process]]ing [[Activity|Activities]] in Grooper are performed at some level within the Batch, either at the [[Batch Page]], at a certain [[Batch Folder]] level, or at the top level, the Batch itself.
[[File:23.1 Batch 02 How To 01 Creating a Test Batch 04.png]]


For example, OCR text is obtained from images by running a Recognize activity at the Page level.  Document classification is done by running a Classify activity at the Folder level.  Exporting is done by running a Document Export activity at the Batch level.
=== Creating a Production Batch ===
There are two ways to create a Production '''Batch''' in '''Grooper''':


[Category:Articles]]
# '''Scanned content''': Scanned documents are brought into '''Grooper''' from the "Batches" page. For more information on scanning documents into '''Grooper''', see our [[Desktop Scanning in Grooper]] article.
# '''Imported content''': Importing digital content into '''Grooper''' happens in the "Imports" Page. An article detailing how to import '''Batches''' via the "Imports" page will be coming soon.

Latest revision as of 17:34, 28 February 2025

This article is about an older version of Grooper.

Information may be out of date and UI elements may have changed.

20252023.120232.80

inventory_2 Batch objects are fundamental in Grooper's architecture as they are the containers of documents that get moved through Grooper's workflow mechanisms known as settings Batch Processes.

You may download the ZIP(s) below and upload it into your own Grooper environment (version 2023.1). This contains one or more Batches of sample documents.

About

What is a Batch?

A Batch is an object in Grooper that contains the documents brought into Grooper via scanning or import.

There are three components to a batch:

  1. The Batch itself
  2. Batch Folders
  3. Batch Pages

Batch objects in Grooper contain two child objects:

  • The root Batch Folder, containing a hierarchy of Batch Folders and Batch Pages.
  • A read-only Batch Process, containing the list of processing instructions for the Batch Folders and Batch Pages

Below is an example of a Batch.

  1. The Test Batch is located here on the node tree.
  2. The Test Batch has two child objects, the root Batch Folder and a read-only Batch Process.


  1. If we open up the root Batch Folder...
  2. We can see the Batch Pages. We can also view the hierarchy of Batch Folders and Batch Pages here after Separation.


  1. If we click on the Batch object in the node tree...
  2. We can click on the "Viewer" tab to see the "Batch Viewer".
  3. Here we can see the contents of the Batch.


  1. At the top level is the Batch itself.
  2. Here we have the Batch Pages in the Batch.
  3. Here we can see the Batch and Batch Pages as objects in the node tree.


  1. Through the process of separation, Batch Pages will be separated into document folders.
  2. These Batch Pages are at the Scope of Page
  3. Here we can see the hierarchy of Batch Folders and Batch Pages within the Batch in the node tree.

Folder Levels

When scanning paper into Grooper, the Batch Pages come in one at a time and there is no differentiation between one document or another. As part of Grooper's workflow, Batch Pages are normally separated into Batch Folders (each folder containing one complete document) so that Grooper knows where one document begins and ends.

A Batch can be as simple as a series of Batch Pages. A Batch may also consist of a complex hierarchy of Batch Folders.

For certain activities, it is important to tell Grooper which Folder Level the Activity needs to be executed on.

  • The Scope of Batch refers to the top most Batch Folder. All Batch Folders and Batch Pages exist within this main Batch Folder. While never referred to as "Level 0" anywhere in Grooper, considering 0 indexing, it may be easy to think of it as such.
  • The first set of Batch Folders under the main Batch Folder is considered Folder Level 1.
  • A Batch Folder that is a child of a Batch Folder at Folder Level 1 is considered at Folder Level 2. A Batch Folder that is a child of a Batch Folder at Folder Level 2 is considered at Folder Level 3, etc.
  • A Batch Page is always considered to be at the Scope of Page.
    • Sometimes you will have Batch Pages inside Batch Folders at different Folder Levels in the Scope of the Batch, but you always want to run certain activities on all Bath Pages. You would set those activities to a Scope of Page.

For example, OCR text is obtained from images by running a Recognize Activity at the Scope of Page. Document classification is done by running a Classify Activity at the Scope of Folder. Export is an example of an Activity that could possibly be run at either a Scope of Batch or Folder.




Production vs Test Batches

Batches exist in two environments:

  • "Production"
    • Stored in the "Batches > Production" branch of the Grooper node tree.
    • The Batch is contained in a folder according to the Batch Process being applied to the Batch.
  • "Test"
    • Stored in the "Batches > Test" branch of the Grooper node tree.
  1. In the image below you can see a Batch within the "Production" folder.
  2. A Batch is also seen existing within the "Test" folder.


So, what are the differences between a "Test" and "Production" Batch?

  • "Test Batches": These are only visible to Grooper Design users. They are used to test extraction and Batch Process steps being designed. These Batches are not exposed to Activity Processing services.
  • "Production Batches": These Batches are visible from the "Batches" page and. Production Batches are "visible" to Activity Processing services and are actively run through a Batch Process that has previously been designed and published.

Both "Test" and "Production" Batches can be created and processed from the Grooper Design page by Design users. However, typically, production Batches are created and processed using the "Batches" page. This also means that different users that are part of different Review Queues can affect Batch workflow.

Test Batches, however, will only be seen by "Design" users.

  1. This is the "Design" page icon
  2. This is the "Batches" page icon

How To

Creating a Test Batch

Creating a Test Batch is relatively simple. First, you must create an empty Batch. Then you can just drag and drop the files from your computer into the Batch.

  1. To add a Test Batch, right-click on the "Test" folder in the node tree.
  2. Hover over "Add" and then click on "Batch..."


  1. In the "Add" dialog box give your Batch a name.
  2. Click "EXECUTE" to create the Batch.


  1. Select the newly created Batch.
  2. Select the "Viewer" tab.
  3. Now you can see that we have an empty Batch. All you need to do now is to drag and drop a file from your computer to this area and your file(s) will be added to Grooper.


  1. A PDF file has been "drag-and-dropped" onto the Batch Folder of the Batch, thus creating a Batch Folder with the PDF as an attachment.

Creating a Production Batch

There are two ways to create a Production Batch in Grooper:

  1. Scanned content: Scanned documents are brought into Grooper from the "Batches" page. For more information on scanning documents into Grooper, see our Desktop Scanning in Grooper article.
  2. Imported content: Importing digital content into Grooper happens in the "Imports" Page. An article detailing how to import Batches via the "Imports" page will be coming soon.