Main Page: Difference between revisions

From Grooper Wiki
No edit summary
No edit summary
(2 intermediate revisions by the same user not shown)
Line 22: Line 22:
|
|
<blockquote style="font-size:14pt">
<blockquote style="font-size:14pt">
'''[[Database Export]]'''
[[Data Context]]
</blockquote>
</blockquote>
[[Image:Database_export_002.png|right|300px|link=Database Export]]


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


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


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



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