2021:Export (Activity): Difference between revisions

From Grooper Wiki
Created page with "<blockquote style="font-size:125%"> The '''Export''' activity exports processed document content to an external storage platform. </blockquote> '''Export''' is an '''Unattend..."
 
No edit summary
Line 9: Line 9:
== About ==
== About ==


So you've ingested some documents into a '''Batch'''.  You've recognized their text with the '''Recognize''' activity, either through OCR or extracting their native embedded text.  You've classified these documents, assigning the '''Batch Folders''' a '''Document Type''' from a '''Content Model''' during the '''Classify''' activity.  You've collected the data you want from these documents during the '''Extract''' activity.  Now what?
So you've ingested some documents into a '''Batch'''.  You've obtained their full text data with the '''Recognize''' activity, either through OCR or extracting their native embedded text.  You've classified these documents, assigning the '''Batch Folders''' a '''Document Type''' from a '''Content Model''' during the '''Classify''' activity.  You've collected the data you want from these documents during the '''Extract''' activity.  Now what?


You need to get these documents and that data out of Grooper!
You need to get these documents and that data out of Grooper!


Enter the '''Export''' activity.
Enter the '''Export''' activity.

Revision as of 12:56, 21 September 2021

The Export activity exports processed document content to an external storage platform.

Export is an Unattended Activity, typically added as of of the last steps (if not the last step) of a Batch Process. It allows Grooper users to deliver processed Batch content to an external system. Whether exporting Batch Folders as PDF files to a Windows folder, exporting extracted Data Model fields to a SQL database, exporting to a content management system, or some combination of multiple exports to multiple systems, the Export activity handles how document Batch Folders in a Batch ultimately leave Grooper after they have been classified and had their data extracted.

How documents are exported (what gets exported, where they go, and what format the exported content takes) is all controlled by Export Behaviors. Export Behaviors can be configured locally, configured as part of the Export activity's property configuration, or can be configured for a particular Content Type, by configuring the Behaviors property of a Content Model and/or its descendant Content Categories or Document Types.

About

So you've ingested some documents into a Batch. You've obtained their full text data with the Recognize activity, either through OCR or extracting their native embedded text. You've classified these documents, assigning the Batch Folders a Document Type from a Content Model during the Classify activity. You've collected the data you want from these documents during the Extract activity. Now what?

You need to get these documents and that data out of Grooper!

Enter the Export activity.