Main Page: Difference between revisions

From Grooper Wiki
No edit summary
No edit summary
Line 21: Line 21:
|-style="background-color:#d8f3f1" valign="top"
|-style="background-color:#d8f3f1" valign="top"
|
|
[[File:separation_and_review_14.png|right|500px|link=Separation and Separation Review|This is an example of the '''Separation Review''' '''Attended Client''' interface.]]
<blockquote style="font-size:14pt">
<blockquote style="font-size:14pt">
'''[[Separation and Separation Review]]'''
'''[[Expressions Cookbook]] and [[LINQ to Grooper Objects]]'''
</blockquote>
</blockquote>
This week, we feature ''two'' articles contributed by BIS team member, Brian Godwin!  These articles pertain to the wide world of '''''Expressions''''' in Grooper.  Expressions are snippets of .NET code, allowing Grooper to do various things outside its "normal" parameters. This includes calculating or validating extracted Data Field values in a Data Model, applying conditional execution of a Batch Process or IP Profile, and more!


'''Grooper''' uses various approaches and '''[https://en.wikipedia.org/wiki/Algorithm algorithms]''' to determine the classification of a page or folder. The settings on a '''[[Content Model]]''' and '''[[Document Type]]''' add to the complexities for separating pages into documents. Grooper Version 2.9 builds on the '''''Separation''''' settings found on '''Document Types''', including the ability to adjust the '''''Training Scope''''' and configure a '''''Secondary Page Extractor'''''.
Expressions take the high configuration of Grooper one step ''even'' further. However, many users don't know where to begin when it comes to writing them. Brain has collected some common examples into our [[Expressions Cookbook]] article.  But we're not stopping there!  This article will serve as a central location for anyone to add expression examples as well.


Adjusting the '''Training Scope''' provides benefits to the accuracy and performance of '''ESP Auto Separation''' by focusing what is important when it comes time to separate and classify ''Unstructured'' paginated documents. For example, the ''Normal'' mode will create a single '''FormType''' and divide trained examples into "First", "Middle" and "Last" pagesFrom individual document to individual document, often the most meaningful features composing them are found on the first and last pages, and there can be more variance on the pages in between. This is different from the previous approach, which created individual '''FormTypes''' for each trained example, each with their own "Page X of X" '''PageType''' objects. This unifies all trained examples into a single '''FormType''', making the training and classification of these documents ultimately simpler and more efficient.  The ''FirstLast'' mode assumes meaningful features for classification are ''only'' found on the first and last pages, with the middle pages containing no information needed to make a separation or classification decision.  With this mode enabled, ''only'' trained examples of the first and last page and their associated features will be saved.  This can improve processing time by removing all the features in the middle pages for consideration.  The ''FirstOnly'' mode narrows this scope even further by only storing features from the first page of trained documents.
In version 2.9 we increased our expressions functionality further with LINQ (Language Integrated Query) integrationThe unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, LINQ nets the same result while being more concise, readable, and overall, more user-friendly.


Furthermore, ESP Auto Separation ''removes'' but does not ''eliminate'' a lot of the manual work to separate and classify documents. Separation Review is a new review module designed to make the manual work quick and easy.
For more information on LINQ, visit the full article [[LINQ to Grooper Objects|here]]
 
For more information on Separation and Separation Review, visit the full article [[Separation and Separation Review|here]]
|
|
The '''Separation Review''' module was added to improve review of complicated document sets separated and classified by '''ESP Auto Separation'''.  Because this Separation Provider separates using page based classification, it can be important to how it made the decision to separate or not separate a document on a page by page basis.  The '''Classify Review''' module presents the reviewer with pages already placed in document folders, and it can be cumbersome to review the page by page separation viewing documents already placed in folders.
You can talk to us!


Enter '''Separation Review'''. This review module is modeled off our '''ESP Auto Separation Tester''' which Grooper Architects use to test the separation and classification of documents, using '''ESP Separation'''. This viewer gives you a much broader look at the individual pages, allowing an easier (and ultimately quicker and more efficient) view of the separation logic applied to the batch.
Do you have an idea for an article? Have you noticed something missing from one already in the wiki? Do you have other comments or feedback about the wiki?


There are further quality of life improvements for the '''Separation Review''' module, making the process of reviewing documents separated and classified by '''ESP Auto Separation''' simpler, faster, and more satisfying.
If so, check out the [https://xchange.grooper.com/categories/documentation-requests Documentation Requests] section of Grooper x Change.  This is your way to communicate with our documentation team.  Please, let us know how we can continue to improve our wiki.
|}
|}



Revision as of 09:37, 3 August 2020

Getting Started

Grooper is a software application that helps organizations innovate workflows by integrating difficult data.

Grooper empowers rapid innovation for organizations processing and integrating large quantities of difficult data. Created by a team of courageous developers frustrated by limitations in existing solutions, Grooper is an intelligent document and digital data integration platform. Grooper combines patented and sophisticated image processing, capture technology, machine learning, and natural language processing. Grooper – intelligent document processing; limitless, template-free data integration.

Getting Started
Install and Setup
2.80 Reference Documentation


Featured Articles Did you know?

Expressions Cookbook and LINQ to Grooper Objects

This week, we feature two articles contributed by BIS team member, Brian Godwin! These articles pertain to the wide world of Expressions in Grooper. Expressions are snippets of .NET code, allowing Grooper to do various things outside its "normal" parameters. This includes calculating or validating extracted Data Field values in a Data Model, applying conditional execution of a Batch Process or IP Profile, and more!

Expressions take the high configuration of Grooper one step even further. However, many users don't know where to begin when it comes to writing them. Brain has collected some common examples into our Expressions Cookbook article. But we're not stopping there! This article will serve as a central location for anyone to add expression examples as well.

In version 2.9 we increased our expressions functionality further with LINQ (Language Integrated Query) integration. The unfortunate truth is that writing expressions tends to be even more complicated than writing complete code in the form of scripts or applications. Basically, writing an expression is no different than writing a script, except for the fact that all the conditions, logic and output needs to squeeze into one “line” of code. When applicable, LINQ nets the same result while being more concise, readable, and overall, more user-friendly.

For more information on LINQ, visit the full article here

You can talk to us!

Do you have an idea for an article? Have you noticed something missing from one already in the wiki? Do you have other comments or feedback about the wiki?

If so, check out the Documentation Requests section of Grooper x Change. This is your way to communicate with our documentation team. Please, let us know how we can continue to improve our wiki.

New in 2.9 Featured Use Case

Welcome to Grooper 2.9!
Below you will find helpful links to all the articles about the new/changed functionality in this version of Grooper.

Compile Stats Microsoft Office Integration Document Viewer Separation and Separation Review
Data Review Confidence Multiplier Data Element Overrides Database Export
CMIS Lookup Content Type Filter Output Extractor Key Box (CMIS Binding)
LINQ to Grooper Objects

They’re Saving Over 5,000 Hours Every Year in Data Discovery and Processing


American Airlines Credit Union has transformed their data workflows, quickly saving thousands of hours in electronic data discovery , resulting in much greater efficiency and improved member services.

Discover how they:

  • Quickly found 40,000 specific files among one billion
  • Easily integrated with data silos and content management systems when no other solution would
  • Have cut their mortgage processing time in half (and they process mortgages for 47 branch offices!)
  • Learn from the document and electronic data discovery experts at BIS!

You can access the full case study clicking this link.


Other Resources