Main Page: Difference between revisions

From Grooper Wiki
No edit summary
No edit summary
(10 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 22: Line 22:
|
|
<blockquote style="font-size:14pt">
<blockquote style="font-size:14pt">
'''[[Expressions Cookbook]] and [[LINQ to Grooper Objects]]'''
[[Data Context]]
</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!


Expressions take the high configuration of Grooper one step ''even'' furtherHowever, many users don't know where to begin when it comes to writing themBrain has collected some common examples into our [[Expressions Cookbook]] articleBut we're not stopping there!  This article will serve as a central location for anyone to add expression examples as well.
Data without context is meaningless.  Context is critical to understanding and modeling the relationships between pieces of information on a documentWithout context, it’s impossible to distinguish one data element from anotherContext helps us understand what data refers to or “means”.   


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.
This allows us to build an extraction logic using '''[[Data Type]]''' and '''[[Field Class]]''' extractors in order to build and populate a '''[[Data Model]]'''.


For more information on LINQ, visit the full article [[LINQ to Grooper Objects|here]]
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 talk to us!
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.


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


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.
For more information visit, the [[Confidence Multiplier and Output Confidence]] article.
|}
|}


Line 114: 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