Main Page: Difference between revisions

From Grooper Wiki
No edit summary
No edit summary
(42 intermediate revisions by 2 users not shown)
Line 4: Line 4:
|-style="background-color:#fde6cb" valign="top"
|-style="background-color:#fde6cb" valign="top"
|rowspan="3" style="width:75%"|
|rowspan="3" style="width:75%"|
Grooper is a software application that helps organizations innovate workflows by integrating difficult data.
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.


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.
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.


|[https://xchange.grooper.com/discussion/57/read-me-getting-started Getting Started]
|[https://xchange.grooper.com/discussion/57/read-me-getting-started Getting Started]
Line 12: Line 12:
|[[Install and Setup]]
|[[Install and Setup]]
|-style="background-color:#fde6cb" valign="top"
|-style="background-color:#fde6cb" valign="top"
|[http://grooper.bisok.com/Documentation/2.80/Main/HTML5/index.htm#t=Start_Page.htm 2.80 Reference Documentation]
|[https://grooper.bisok.com/Documentation/2.90/Main/HTML5/index.htm#t=Start_Page.htm 2.90 Reference Documentation]
|}
|}


Line 21: Line 21:
|-style="background-color:#d8f3f1" valign="top"
|-style="background-color:#d8f3f1" valign="top"
|
|
[[Image:Database_export_002.png|center|200px|link=Database Export]]
[[File:Table-extraction-simple-table.png|thumb|300px|Data in an Excel spreadsheet is an example of tabular data.]]
<blockquote style="font-size:14pt">
<blockquote style="font-size:14pt">
'''[[Database Export]]'''
[[Table Extraction]]
</blockquote>
</blockquote>


The most important goal of '''Grooper''' is to deliver accurate data to line of business systems that allow the information to be integrated into impactful business decisioning. [https://en.wikipedia.org/wiki/Table_(information) Tables] in [https://en.wikipedia.org/wiki/Database databases] remain, to this day, one of the main vessels by which this information is stored. '''Grooper's''' '''Database Export''' activity is the mechanism by which this delivery is performed. '''Database Export''' uses a configured '''[[Data Connection]]''' to establish a link to ('''[https://en.wikipedia.org/wiki/Microsoft_SQL_Server Microsoft SQL Server]''' or '''[https://en.wikipedia.org/wiki/Open_Database_Connectivity ODBC-compliant]''') tables in a database and intelligently populate said tables.<br/>
Table Extraction refers to Grooper's functionality to extract data from cells in tables. This is accomplished by configuring the '''[[Data Table]]''' '''''[[Data Element]]''''' in a '''[[Data Model]]'''.


Database export is the chief delivery device for "collection" elements. These are '''[[Data Element|Data Elements]]''' for which there will be a collection, or "set", of values. Examples of these are '''Data Columns''' found within '''[[Data Table|Data Tables]]''', or '''[[Data Field|Data Fields]]''' located in '''[[Data Section|Data Sections]]''' with the '''''Scope''''' property set to ''MultiInstance''.
Tables are one of the most common ways data is organized on documents.  Human beings have been writing information into tables before they started writing literature, even before paper was invented. There are examples of tables carved onto the walls of Egyptian temples! They are excellent structures for representing a lot of information with various characteristics in common in a relatively small space (or an Egyptian temple sized space).  However, targeting the data inside them presents its own set of challenges. A table’s structure can range from simple and straightforward to more complex (even confounding).  Different organizations may organize the same data differently, creating different tables for what, essentially, is the same data.


Two ''key distinctions'' about '''Grooper's''' '''Database Export''' activity are its ability to take full advantage of its sophisticated hierarchical data modeling to flatten complex/inherited data structures, and the ease of delivery to multiple tables at once.
In Grooper, tabular data can be extracted to '''Data Table''' objects using the ''[[Row Match (Table Extract Method)|Row Match]]'', ''[[Header-Value (Table Extract Method)|Header-Value]]'', or ''[[Infer Grid (Table Extract Method)|Infer Grid]]'' table extraction methods.
|
|
You can talk to us!
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.


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?
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.


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.
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.
|}
|}


{|cellpadding="15" cellspacing="10"
{|cellpadding="15" cellspacing="10"
Line 100: Line 101:


[https://www.bisok.com/case-studies/electronic-data-discovery-case-study/ You can access the full case study clicking this link].
[https://www.bisok.com/case-studies/electronic-data-discovery-case-study/ You can access the full case study clicking this link].
|}
==== <span style="color:white">Feedback</span> ====
{|cellpadding="15" cellspacing="10" width="100%"
|-style="background-color:#36b0a7; color:white; font-size:16pt"
|colspan=2|'''Feedback'''
|-style="background-color:#d8f3f1" valign="center"
|style="width:25%"|
[[File:Gartner pi.jpg|link=https://www.gartner.com/reviews/market/data-and-analytics-others/vendor/bis/product/grooper]]
|
<span style="font-size:14pt">We value your feedback!<br><br>Help us improve our product by leaving us a review on [https://www.gartner.com/reviews/market/data-and-analytics-others/vendor/bis/product/grooper Gartner.com].<br><br>Click the image to the left to submit a review.</span>
|}
|}


Line 114: Line 126:
* [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 12:19, 22 February 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?
Data in an Excel spreadsheet is an example of tabular data.

Table Extraction

Table Extraction refers to Grooper's functionality to extract data from cells in tables. This is accomplished by configuring the Data Table Data Element in a Data Model.

Tables are one of the most common ways data is organized on documents. Human beings have been writing information into tables before they started writing literature, even before paper was invented. There are examples of tables carved onto the walls of Egyptian temples! They are excellent structures for representing a lot of information with various characteristics in common in a relatively small space (or an Egyptian temple sized space). However, targeting the data inside them presents its own set of challenges. A table’s structure can range from simple and straightforward to more complex (even confounding). Different organizations may organize the same data differently, creating different tables for what, essentially, is the same data.

In Grooper, tabular data can be extracted to Data Table objects using the Row Match, Header-Value, or Infer Grid table extraction methods.

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 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.

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