Main Page: Difference between revisions

From Grooper Wiki
No edit summary
No edit summary
(20 intermediate revisions by 2 users not shown)
Line 14: Line 14:
|[https://grooper.bisok.com/Documentation/2.90/Main/HTML5/index.htm#t=Start_Page.htm 2.90 Reference Documentation]
|[https://grooper.bisok.com/Documentation/2.90/Main/HTML5/index.htm#t=Start_Page.htm 2.90 Reference Documentation]
|}
|}
{|cellpadding="15" cellspacing="10"
{|cellpadding="15" cellspacing="10"
|-style="background-color:#36b0a7; color:white; font-size:16pt"
|-style="background-color:#36b0a7; color:white; font-size:16pt"
Line 21: Line 19:
|-style="background-color:#d8f3f1" valign="top"
|-style="background-color:#d8f3f1" valign="top"
|
|
[[image:1560961400530-989.png|frame|The Infer Grid Extract Method's property panel]]
[[File:label-sets-badge-3.png|link=Labeling Behavior|thumb|200px]]
<blockquote style="font-size:14pt">
<blockquote style="font-size:14pt">
''[[Infer Grid]]''
'''[[Labeling Behavior|Label Sets]]'''
</blockquote>
</blockquote>


''Infer Grid'' is one of three [[Table Extraction]] methods to extract data from tables on documents.  It uses the positional location of row and column headers to interpret where a tabular grid would be around each value in a table and extract values from each cell in the interpreted grid.
"Label Sets" refers to a variety of document classification and extraction capabilities made possible through the ''Labeling Behavior''.  The ''Labeling Behavior'' is a '''Content Type''' '''''Behavior''''' designed to collect and utilize a document's field labels in a variety of ways.  This includes functionality for classification and data extraction.
 


This method extracts information by inferring a grid from the row and column header positions.  This is done by assigning an '''''X Axis Extractor''''' to match the column headers and, a '''''Y Axis Extractor''''' to match row headers.  A grid is created from the header positions extracted from the two extractors. 
The ''Labeling Behavior'' functionality allows Grooper users to quickly onboard new '''Document Types''' for structured and semi-structured forms, utilizing labels as a thumbprint for classification and data extraction purposes.  Once the ''Labeling Behavior'' is enabled, labels are identified and collected using the "Labels" tab of '''Document Types'''. These "Label Sets" can then be used for the following purposes:


Furthermore, if table line positions can be obtained from a Line Detection or Line Removal '''IP Command''', only the '''''X Axis Extractor''''' is needed.  In these cases, the '''''X Axis Extractor''''' can be used to find the column header labels, and the grid will be created using the table lines in the documents [[Layout Data]]. The raw text data obtained from the '''[[Recognize]]''' activity will populate each cell of the grid according to where it is on the page.
* Document classification - Using the ''Labelset-Based'' '''''Classification Method'''''
* Field based data extraction - Primarily using the ''Labeled Value'' '''''Extractor Type'''''
* Tabular data extraction - Primarily using a '''Data Table''' object's ''Tabular Layout'' '''''Extract Method'''''
* Sectional data extraction - Primarily using a '''Data Section''' object's ''Transaction Detection'' '''''Extract Method'''''
|
|
The earliest examples of OCR (Optical Character Recognition) can be traced back to the  1870s.  Early OCR devices were actually invented to aid the blind.  This included "text-to-speech" devices that would scan black print and produce sounds a blind person could interpret, as well as "text-to-tactile" machines which would convert luminous sensations into tactile sensations.  Machines such as these would allow a blind person to read printed text not yet converted to Braille.
The earliest examples of OCR (Optical Character Recognition) can be traced back to the  1870s.  Early OCR devices were actually invented to aid the blind.  This included "text-to-speech" devices that would scan black print and produce sounds a blind person could interpret, as well as "text-to-tactile" machines which would convert luminous sensations into tactile sensations.  Machines such as these would allow a blind person to read printed text not yet converted to Braille.
Line 42: Line 44:
{|cellpadding="15" cellspacing="10"
{|cellpadding="15" cellspacing="10"
|-style="background-color:#f89420; color:white; font-size:16pt"
|-style="background-color:#f89420; color:white; font-size:16pt"
|style="width:50%"|'''New in 2.9'''||'''Featured Use Case'''
|style="width:50%"|'''New in Version 2021'''||'''Featured Use Case'''
|-style="background-color:#fde6cb" valign="top"
|-style="background-color:#fde6cb" valign="top"
|
|
{|cellpadding=5 cellspacing=2 style="margin:auto"
[[File:Grooper-2021-round.png|thumb|200px|link=https://wiki.grooper.com/index.php?title=What%27s_New_in_Grooper_2021|Welcome to Grooper 2021!]]
!colspan="4" style="padding: 25px" | <blockquote style="font-size:14pt">Welcome to '''Grooper 2.9'''!<br/>Below you will find helpful links to all the articles about the new/changed functionality in this version of '''Grooper'''.</blockquote>
== Welcome to Grooper 2021! ==
 
Grooper version 2021 is here! There's a slew of new features, "under-the-hood" architecture improvements, and simplified redesigns to make this version both easiest to use and provide the most accurate capture capabilities to date.
 
<br clear=all>
 
New feature improvements include:
 
{|cellpadding=5 cellspacing=10
|style="border-style: solid; border-color:#616364"|
[[File:behaviors-badge-3.png|link=Behaviors]]
|valign=top|
* [[Behaviors]]
** This new set of features centralizes the '''Content Model''' as the logical hub of document processing, allowing for new functionality and expanding and simplifying set up of existing functionality.
|-
|-
|[[Image:Compile_stats_02.png|center|200px|link=Compile Stats]]
|style="border-style: solid; border-color:#616364"|
|[[Image:Microsoft_office_integration_000.png|center|200px|link=Microsoft Office Integration]]
[[File:label-sets-badge-3.png|link=Labeling Behavior]]
|[[Image:document_viewer_00.png|center|150px|link=Document Viewer]]
|valign=top|
|[[Image:Separation_and_review_18.png|center|175px|link=Separation and Separation Review]]
* [[Labeling Behavior|Label Sets]]
** A new way of document classification and extraction using labels.
|-
|-
|style="text-align:center"|'''[[Compile Stats]]'''
|style="border-style: solid; border-color:#616364"|
|style="text-align:center"|'''[[Microsoft Office Integration]]'''
[[File:smart-pdf-badge-3.png|link=PDF Data Mapping]]
|style="text-align:center"|'''[[Document Viewer]]'''
|valign=top|
|style="text-align:center"|'''[[Separation and Separation Review]]'''
* [[PDF Data Mapping|Smart PDFs]]
** New PDF generation functionality (via the ''PDF Data Mapping'' '''''Behavior'''''), including embedding extracted data directly to PDF files.
|-
|-
|[[Image:data_review_00.png|center|200px|link=Data Review]]
|style="border-style: solid; border-color:#616364"|
|[[Image:Weighted_rules_00.png|center|200px|link=Confidence Multiplier]]
[[File:rules-engine-badge-3.png|link=Data Rule]]
|[[Image:Data_element_overrides_000.png|center|150px|link=Data Element Overrides]]
|valign=top|
|[[Image:Database_export_002.png|center|200px|link=Database Export]]
* [[Data Rule|Rules Engine]]
** The '''Data Rule''' is a new object designed for hierarchical conditional validation and calculation of '''Data Elements''' in a '''Data Model'''.  This "Rules Engine" drives complex data validation and calculations never before possible in Grooper.
|-
|-
|style="text-align:center"|'''[[Data Review]]'''
|style="border-style: solid; border-color:#616364"|
|style="text-align:center"|'''[[Confidence Multiplier]]'''
[[File:api-badge-3.png]]
|style="text-align:center"|'''[[Data Element Overrides]]'''
|valign=top|
|style="text-align:center"|'''[[Database Export]]'''
* Document Ingestion API
** Integration of a new RESTful document ingestion API provides the ability to create and populate batches, and the ability to monitor the status of batch processes, and retrieve results.
|-
|-
|[[Image:Cmis_lookup_002.png|center|200px|link=CMIS Lookup]]
|style="border-style: solid; border-color:#616364"|
|[[Image:Content_type_filter_000.png|center|100px|link=Content Type Filter]]
[[File:Value-reader-badge-3.png|link=Value Reader]]
|[[Image:Output_extractor_key_000.png|center|200px|link=Output Extractor Key]]
|valign=top|
|[[Image:box_cmis_binding_000.png|center|200px|link=Box (CMIS Binding)]]
* [[Value Reader]]
|-
** A new data extraction object, designed to centralize all of Grooper's extraction functionality into a single object, including its pattern-based, OMR, and zonal types of extraction.
|style="text-align:center"|'''[[CMIS Lookup]]'''
|style="text-align:center"|'''[[Content Type Filter]]'''
|style="text-align:center"|'''[[Output Extractor Key]]'''
|style="text-align:center"|'''[[Box (CMIS Binding)]]'''
|-
|colspan="4"|[[Image:Linq_to_grooper_objects_001.png|center|200px|link=LINQ to Grooper Objects]]
|-
|colspan="4" style="text-align:center"|'''[[LINQ to Grooper Objects]]'''
|}
|}
For more information on these and other improvements, visit the [[What's New in Grooper 2021]] article.


|
|
Line 124: Line 137:
* [https://www.bisok.com/grooper-data-integration-platform/ Grooper.com]
* [https://www.bisok.com/grooper-data-integration-platform/ Grooper.com]
|style="width:25%"|
|style="width:25%"|
* [https://grooper.bisok.com/Documentation/21.0/index.htm#t=Start_Page.htm 2021 Reference and SDK Documentation]
* [https://grooper.bisok.com/Documentation/2.90/Main/HTML5/index.htm#t=Start_Page.htm 2.90 Reference Documentation]
* [http://grooper.bisok.com/Documentation/2.80/Main/HTML5/index.htm#t=Start_Page.htm 2.80 Reference Documentation]
* [http://grooper.bisok.com/Documentation/2.80/Main/HTML5/index.htm#t=Start_Page.htm 2.80 Reference Documentation]
* [http://grooper.bisok.com/Documentation/2.80/SDK/HTML5/index.htm#t=Developer_Reference.htm 2.80 SDK Documentation]
* [http://grooper.bisok.com/Documentation/2.80/SDK/HTML5/index.htm#t=Developer_Reference.htm 2.80 SDK Documentation]
* [https://grooper.bisok.com/Documentation/2.90/Main/HTML5/index.htm#t=Start_Page.htm 2.90 Reference Documentation]
|style="width:25%"|
|style="width:25%"|
* [https://blog.bisok.com/webinars Webinars and Video]
* [https://blog.bisok.com/webinars Webinars and Video]

Revision as of 10:09, 23 September 2021

Getting Started

Grooper was built from the ground up by BIS, a company with 35 years of continuous experience developing and delivering new technology. Grooper is an intelligent document processing and digital data integration solution that empowers organizations to extract meaningful information from paper/electronic documents and other forms of unstructured data.

The platform combines patented and sophisticated image processing, capture technology, machine learning, natural language processing, and optical character recognition to enrich and embed human comprehension into data. By tackling tough challenges that other systems cannot resolve, Grooper has become the foundation for many industry-first solutions in healthcare, financial services, oil and gas, education, and government.

Getting Started
Install and Setup
2.90 Reference Documentation
Featured Articles Did you know?

Label Sets

"Label Sets" refers to a variety of document classification and extraction capabilities made possible through the Labeling Behavior. The Labeling Behavior is a Content Type Behavior designed to collect and utilize a document's field labels in a variety of ways. This includes functionality for classification and data extraction.


The Labeling Behavior functionality allows Grooper users to quickly onboard new Document Types for structured and semi-structured forms, utilizing labels as a thumbprint for classification and data extraction purposes. Once the Labeling Behavior is enabled, labels are identified and collected using the "Labels" tab of Document Types. These "Label Sets" can then be used for the following purposes:

  • Document classification - Using the Labelset-Based Classification Method
  • Field based data extraction - Primarily using the Labeled Value Extractor Type
  • Tabular data extraction - Primarily using a Data Table object's Tabular Layout Extract Method
  • Sectional data extraction - Primarily using a Data Section object's Transaction Detection Extract Method

The earliest examples of OCR (Optical Character Recognition) can be traced back to the 1870s. Early OCR devices were actually invented to aid the blind. This included "text-to-speech" devices that would scan black print and produce sounds a blind person could interpret, as well as "text-to-tactile" machines which would convert luminous sensations into tactile sensations. Machines such as these would allow a blind person to read printed text not yet converted to Braille.

The first business to install an OCR reader was the magazine Reader's Digest in 1954. The company used it to convert typewritten sales reports into machine readable punch cards.

It would not be until 1974 that OCR starts to form as we imagine it now with Ray Kurzweil's development of the first "omni-font" OCR software, capable of reading text of virtually any font.


New in Version 2021 Featured Use Case
Welcome to Grooper 2021!

Welcome to Grooper 2021!

Grooper version 2021 is here! There's a slew of new features, "under-the-hood" architecture improvements, and simplified redesigns to make this version both easiest to use and provide the most accurate capture capabilities to date.


New feature improvements include:

  • Behaviors
    • This new set of features centralizes the Content Model as the logical hub of document processing, allowing for new functionality and expanding and simplifying set up of existing functionality.

  • Label Sets
    • A new way of document classification and extraction using labels.

  • Smart PDFs
    • New PDF generation functionality (via the PDF Data Mapping Behavior), including embedding extracted data directly to PDF files.

  • Rules Engine
    • The Data Rule is a new object designed for hierarchical conditional validation and calculation of Data Elements in a Data Model. This "Rules Engine" drives complex data validation and calculations never before possible in Grooper.

  • Document Ingestion API
    • Integration of a new RESTful document ingestion API provides the ability to create and populate batches, and the ability to monitor the status of batch processes, and retrieve results.

  • Value Reader
    • A new data extraction object, designed to centralize all of Grooper's extraction functionality into a single object, including its pattern-based, OMR, and zonal types of extraction.

For more information on these and other improvements, visit the What's New in Grooper 2021 article.

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.

Feedback

Feedback

We value your feedback!

Help us improve our product by leaving us a review on Gartner.com.

Click the image to the left to submit a review.


Other Resources