|
|
| Line 1: |
Line 1: |
| <onlyinclude>
| | #REDIRECT[[Batch - 2023]] |
| <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.
| |
| # 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'''
| |
| </onlyinclude>
| |
| | |
| == About ==
| |
| | |
| There are three components to a batch:
| |
| | |
| # The [[Batch]] itself
| |
| # [[Batch Folder]]s
| |
| # [[Batch Page]]s
| |
| | |
| 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.
| |
| | |
| | |
| {|cellpadding="10" cellspacing="5" style="margin:auto"
| |
| |-valign="top"
| |
| |style="width:33%"|At the top level is the '''[[Batch]]''', named here "Simple 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.
| |
| |-
| |
| |[[image:1572881419282-110.png|center|300px]]||[[image:1572881490382-273.png|center|300px]]||[[image:1572881745304-100.png|center|300px]]
| |
| |}
| |
| | |
| | |
| 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.
| |
| | |
| 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.
| |
| | |
| 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.
| |
| | |
| | |
| === Production vs Test Batches ===
| |
| | |
| '''Batches''' exist in two environments:
| |
| | |
| * '''Production'''
| |
| ** Stored in the '''Batches > Production''' branch of the Grooper node tree.
| |
| * '''Test'''
| |
| ** Stored in the '''Batches > Test''' branch of the Grooper node tree.
| |
| | |
| Test '''Batches''' are only visible to Grooper Design users. Production '''Batches''' are visible to all users who have appropriate access rights.
| |
| * Typically, production '''Batches''' are created and processed using the "/Grooper/Batches" page.
| |
| ** However, be aware, production '''Batches''' can be created and processed both from the "/Grooper/Design" page and the "/Grooper/Batches" page, meaning multiple users at multiple access levels can affect '''Batch''' workflow.
| |
| * Test '''Batches''', however, will only be seen by "Design" users.
| |
| | |
| [[Category:Articles]]
| |
| [[Category:Stub]]
| |
