Import or Export Grooper Objects: Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
| Line 95: | Line 95: | ||
[[File:Import-and-Export-Grooper-Objects-08.png]] | [[File:Import-and-Export-Grooper-Objects-08.png]] | ||
|} | |} | ||
</tab> | </tab> | ||
<tab name="Exporting Objects with References" style="margin:20px"> | <tab name="Exporting Objects with References" style="margin:20px"> | ||
=== Exporting Objects with References === | |||
Grooper makes use of references in a variety of different ways. '''Data Fields''' often reference '''Data Type''' extractors to populate fields in a '''Data Model'''. A '''Recognize''' step in a '''Batch Process''' will reference an '''OCR Profile'''. References are a fantastic way to get reusability out of the objects you create and configure. | |||
When you export an object referencing an external object (one that is in a different location in the Node Tree) by default, Grooper will ''also'' include that object in zip file export. However, depending on your situation, you may want to export the referenced object or you may not. | |||
{|cellpadding=10 cellspacing=5 | |||
|valign=top style="width:40%"| | |||
# For this example, we will export the '''Content Model''' named "Sample Content Model - Cow App". | |||
Note, the "Docket Number" '''Data Field''' uses a ''Read Zone'' extractor in order to populate the field. The ''Read Zone'' extractor allows you to (among other things) anchor a rectangular zone from a text label on the document. Any text falling within that zone will be extracted as the '''Data Field's''' result. The ''Read Zone'' extractor also allows you to optionally re-process the text's OCR result with the '''''OCR Profile''''' property. | |||
#<li value=2> Here, the '''''OCR Profile''''' property references the '''OCR Profile''' named "Tesseract Cell OCR" in the '''OCR Profiles''' folder of the '''Global Resources''' folder. | |||
| | |||
[[File:Import-and-Export-Grooper-Objects-09.png]] | |||
|- | |||
|valign=top style="width:40%"| | |||
# We're starting this export by right clicking the "Sample Content Model - Cow App" '''Content Model'''. | |||
#* One of its child objects (the "Docket Number" '''Data Field''') contains a reference to an external object (the "Tesseract Cell OCR" '''OCR Profile''') | |||
# Select "Share" and "Export to Zip Archive..." | |||
# Note the '''''Items to Export''''' property lists Sample Content Model - Cow App ''+ 1 reference''. This indicates that external '''OCR Profile''' is already included in this export! | |||
# You can verify or change this by pressing the ellipsis button at the end of the property. | |||
| | |||
[[File:Import-and-Export-Grooper-Objects-10.png]] | |||
|- | |||
|valign=top style="width:40%"| | |||
Notice in the "References to Include" window the referenced '''OCR Profile''' named "Teseract Cell OCR" is included in this list of items. This window will list all referenced objects of the object (or objects) you have selected for export. | |||
By default the box next to these references is checked, indicating it will be included in the export. However, if you wish to exclude a referenced object from the export, simply uncheck the box next to the listed object. | |||
| | |||
[[File:Import-and-Export-Grooper-Objects-11.png]] | |||
|} | |||
</tab> | </tab> | ||
</tabs> | </tabs> | ||
Revision as of 09:41, 25 September 2020
How can you share Grooper objects, like Content Models, Batch Processes, Batches and more, with other Grooper users?
About
Grooper allows you to export Grooper objects from a Grooper Repository as a zip archive file. You can then bring in those objects into a Grooper Repository (such as one you are not connected to) by importing the zip file.
The process is straightforward, but there are a few things to watch out for.
How To
Export Grooper Objects to a Zip File
Exporting a Single Object
|
For this example, we have an IP Profile batch named "Sample IP Profile - Layout Data" that we want to export from this Grooper repository and import it into another.
|
|
|
The following window will appear.
|
|
|
You will then return to the previous window.
|
|
|
You can find the zip file wherever you chose to save it. |
Exporting Multiple Objects
|
You can also easily export multiple objects to a single zip archive. For example, what if we wanted to export the "Sample IP Profile - Layout Data" IP Profile as well as this Batch named "Sample Batch"? |
|
|
The starting point is much like an export of a single object.
|
|
|
This will bring up a window allowing you to select multiple objects in your Node Tree.
|
|
|
Exporting Objects with References
Grooper makes use of references in a variety of different ways. Data Fields often reference Data Type extractors to populate fields in a Data Model. A Recognize step in a Batch Process will reference an OCR Profile. References are a fantastic way to get reusability out of the objects you create and configure.
When you export an object referencing an external object (one that is in a different location in the Node Tree) by default, Grooper will also include that object in zip file export. However, depending on your situation, you may want to export the referenced object or you may not.
Note, the "Docket Number" Data Field uses a Read Zone extractor in order to populate the field. The Read Zone extractor allows you to (among other things) anchor a rectangular zone from a text label on the document. Any text falling within that zone will be extracted as the Data Field's result. The Read Zone extractor also allows you to optionally re-process the text's OCR result with the OCR Profile property.
|
|
|
|
|
Notice in the "References to Include" window the referenced OCR Profile named "Teseract Cell OCR" is included in this list of items. This window will list all referenced objects of the object (or objects) you have selected for export. By default the box next to these references is checked, indicating it will be included in the export. However, if you wish to exclude a referenced object from the export, simply uncheck the box next to the listed object. |










