Main Page: Difference between revisions

From Grooper Wiki
No edit summary
No edit summary
(13 intermediate revisions by the same user not shown)
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:box_cmis_binding_000.png|256px|right|thumb|link=Box (CMIS Binding)]]
<blockquote style="font-size:14pt">
[[Data Context]]
</blockquote>
 
Data without context is meaningless.  Context is critical to understanding and modeling the relationships between pieces of information on a document.  Without context, it’s impossible to distinguish one data element from another.  Context helps us understand what data refers to or “means”. 


<blockquote style="font-size:14pt">[[Box (CMIS Binding)]]</blockquote>
This allows us to build an extraction logic using '''[[Data Type]]''' and '''[[Field Class]]''' extractors in order to build and populate a '''[[Data Model]]'''. 


Secure collaboration with anyone, anywhere, on any device, now connected to Grooper.  Integration with '''[https://www.box.com/home Box]''' cloud content management system in '''Grooper''' leverages the '''[[CMIS+]]''' architecture to allow you to take full advantage of this powerful '''[https://en.wikipedia.org/wiki/Content_management_system Content Management System]'''.
There are three fundamental data context relationships:


This [[CMIS Binding]] provides connectivity to the Box environment for for a variety of powerful data integration purposes. This allows you to import documents and their associated metadata from Box as well as export Grooper processed documents and their extracted index data to Box as their endpoint, as well as taking advantage of our new [[CMIS Lookup]] functionality to validate and populate fields using metadata directly from a Box.com source.
* '''Syntactic''' - Context given by the syntax of data.
* '''Semantic''' - Context given by the lexical content associated with the data.
* '''Spatial''' - Context given by where the data exists on the page, in relationship with other data.


For more information on how to set up a connection between Grooper and a Box.com account, visit the full article [[Box (CMIS Binding)|here]]
Using the context these relationships provide allows us to understand how to target data with extractors.
|
|
Grooper re-envisioned how to connect to CMIS sources and other storage platforms in version 2.72Prior to this version, Grooper users connected to various storage systems through a variety of Import and Export ProvidersIn version 2.72, we created a unified framework to connect to data sources with our [[CMIS+]] Architecture!
You can now manually manipulate the confidence of an extraction result.  The '''''[[Confidence Multiplier and Output Confidence]]''''' properties of '''[[Data Type]]''' and '''[[Data Format]]''' extractors allow you to change the confidence score of extraction results.  No longer are you forced to accept the score Grooper providesThese properties give you more control when it comes to what confidence a result ''should'' be.
 
This allows you to prioritize certain results over others.  You can create a kind of "fall back" or "safety net" result by using this propertyYou can even ''increase'' the confidence of an extractor's result, allowing you to give more weight to a fuzzy extractor's result over a non-fuzzy one, for example.


This new architecture allows for easier integration of CMIS systems with Grooper, as well as exposing non-CMIS sources, such as the Windows file system and Microsoft Outlook inboxes, as if they were CMIS sources.  This provided a more standardized import/export workflow across a variety of storage systems, increased ability to map document metadata on import and export, better ability to search, query and filter document repositories, and faster integration of new content management systems, such as the new [[Box (CMIS Binding)|Box.com]] integration.
For more information visit, the [[Confidence Multiplier and Output Confidence]] article.
|}
|}


Line 111: Line 119:
* [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:02, 23 September 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.90 Reference Documentation


Featured Articles Did you know?

Data Context

Data without context is meaningless. Context is critical to understanding and modeling the relationships between pieces of information on a document. Without context, it’s impossible to distinguish one data element from another. Context helps us understand what data refers to or “means”.

This allows us to build an extraction logic using Data Type and Field Class extractors in order to build and populate a Data Model.

There are three fundamental data context relationships:

  • Syntactic - Context given by the syntax of data.
  • Semantic - Context given by the lexical content associated with the data.
  • Spatial - Context given by where the data exists on the page, in relationship with other data.

Using the context these relationships provide allows us to understand how to target data with extractors.

You can now manually manipulate the confidence of an extraction result. The Confidence Multiplier and Output Confidence properties of Data Type and Data Format extractors allow you to change the confidence score of extraction results. No longer are you forced to accept the score Grooper provides. These properties give you more control when it comes to what confidence a result should be.

This allows you to prioritize certain results over others. You can create a kind of "fall back" or "safety net" result by using this property. You can even increase the confidence of an extractor's result, allowing you to give more weight to a fuzzy extractor's result over a non-fuzzy one, for example.

For more information visit, the Confidence Multiplier and Output Confidence article.

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