What's New in Grooper 2021: Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
| Line 5: | Line 5: | ||
=== Introducing... Behaviors! === | === Introducing... Behaviors! === | ||
'''''[[Behaviors]]''''' are a new set of features designed to centralize the '''Content Model''' as the main hub controlling various aspects of document processing. ''''Behaviors'''' are born of the idea that consolidating the the flow of data to the objects most relevant to its collection and delivery makes for a more streamlined and effective Grooper experience. | '''''[[Behaviors]]''''' are a new set of features designed to centralize the '''Content Model''' as the main hub controlling various aspects of document processing. '''''Behaviors''''' are born of the idea that consolidating the the flow of document data to the objects most relevant to its collection and delivery makes for a more streamlined and effective Grooper experience. | ||
This allows a '''Content Model''' (and its component '''Content Types''') to wrest control from various other disparate '''Activities''', centralizing command of how documents and their data are modeled and what happens to that data once collected. The result is more focused control about how data is imported, collected, and exported by a '''Content Model'''. In other words, how it "behaves". | This allows a '''Content Model''' (and its component '''Content Types''') to wrest control from various other disparate '''Activities''', centralizing command of how documents and their data are modeled and what happens to that data once collected. The result is more focused control about how document data is imported, organized, collected, and exported by a '''Content Model'''. In other words, how it "behaves". | ||
The following Behavior Types are introduced in 2021: | The following Behavior Types are introduced in 2021: | ||
| Line 14: | Line 14: | ||
* '''''Export Behavior''''' | * '''''Export Behavior''''' | ||
* '''''Labeling Behavior''''' | * '''''Labeling Behavior''''' | ||
* '''''PDF Data | * '''''PDF Data Mapping''''' | ||
* '''''Text Rendering''''' | * '''''Text Rendering''''' | ||
=== Introducing... Label Sets! | === Introducing... Label Sets! === | ||
** [[Labeling Behavior]] | ** [[Labeling Behavior]] | ||
=== Introducing... PDF Data Mapping! === | |||
* [[PDF Generate Behavior]] | * [[PDF Generate Behavior]] | ||
=== Introducing... Data Rules! === | === Introducing... Data Rules! === | ||
| Line 68: | Line 50: | ||
** [[Transaction Detection]] | ** [[Transaction Detection]] | ||
** [[Nested Table]] | ** [[Nested Table]] | ||
=== Changes to Document Export and Database Export === | |||
==== Goodbye Document Export and Database Export. Hello Export! ==== | |||
In 2021, we heavily reworked Grooper's document and data export functionality, to improve the process and allow for new functionality. As part of this process, we unified '''Document Export''' and '''Database Export''' into a single '''Activity''': '''Export''' | |||
'''Export''' is now the single '''Activity''' driving all export operations in Grooper. Whether exporting PDFs to a content management system, exporting data to a database, or any content to any external storage platform, '''Export''' is your way to go. | |||
==== Goodbye CMIS Content Types. Hello Import and Export Behaviors! ==== | |||
One big change to how things were done before 2021 is how data is mapped according to its '''Data Model''' structure to or from an external storage platform upon document import or export. Previously, these mappings were configured using the CMIS Content Type objects, created as children of a CMIS Connection. | |||
In 2021, the '''CMIS Connection''' object purely serves the function of integrating Grooper with an external storage platform. Import and export mappings are defined using '''''Import''' or '''''Export Behaviors'''''. This removes some unnecessary object bloat around the '''CMIS Connection''' object and lets the '''Content Model''' and '''Document Types''' drive their associated '''Data Model''' mappings. | |||
Import and Export Behaviors are configurable via: | |||
* The '''Export''' '''Activity''' | |||
* '''Content Models''' or '''Document Types''' | |||
=== Install and Setup Changes === | === Install and Setup Changes === | ||
Revision as of 10:27, 30 August 2021
Welcome to Grooper 2021!
Introducing... Behaviors!
Behaviors are a new set of features designed to centralize the Content Model as the main hub controlling various aspects of document processing. Behaviors are born of the idea that consolidating the the flow of document data to the objects most relevant to its collection and delivery makes for a more streamlined and effective Grooper experience.
This allows a Content Model (and its component Content Types) to wrest control from various other disparate Activities, centralizing command of how documents and their data are modeled and what happens to that data once collected. The result is more focused control about how document data is imported, organized, collected, and exported by a Content Model. In other words, how it "behaves".
The following Behavior Types are introduced in 2021:
- Import Behavior
- Export Behavior
- Labeling Behavior
- PDF Data Mapping
- Text Rendering
Introducing... Label Sets!
Introducing... PDF Data Mapping!
Introducing... Data Rules!
- Data Rule
- Apply Rules and Convert Data activity types
Introducing... API!
Data Extraction Improvements
- Value Reader
- Including new/changed Extractor Types!
- Vertical Wrap for easier stacked label matching.
- Constrained Wrap for easier pattern matching for data constrained in a box (think table cells).
- New and improved Table Extraction methods
- Tabular Layout
- Delimited Extract
- Fixed Width
- Fluid Layout
- New Data Section Methods
Changes to Document Export and Database Export
Goodbye Document Export and Database Export. Hello Export!
In 2021, we heavily reworked Grooper's document and data export functionality, to improve the process and allow for new functionality. As part of this process, we unified Document Export and Database Export into a single Activity: Export
Export is now the single Activity driving all export operations in Grooper. Whether exporting PDFs to a content management system, exporting data to a database, or any content to any external storage platform, Export is your way to go.
Goodbye CMIS Content Types. Hello Import and Export Behaviors!
One big change to how things were done before 2021 is how data is mapped according to its Data Model structure to or from an external storage platform upon document import or export. Previously, these mappings were configured using the CMIS Content Type objects, created as children of a CMIS Connection.
In 2021, the CMIS Connection object purely serves the function of integrating Grooper with an external storage platform. Import and export mappings are defined using Import or Export Behaviors. This removes some unnecessary object bloat around the CMIS Connection object and lets the Content Model and Document Types drive their associated Data Model mappings.
Import and Export Behaviors are configurable via:
- The Export Activity
- Content Models or Document Types
Install and Setup Changes
- Changes to Grooper Config
- Changes to Install and Setup - 2021
- Including changes to Grooper Repository creation and connection.
- Licensing changes
Miscellaneous
- Changes to Content Action
- Document Viewer improvements
- Text file improvements