Main Page: Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
Line 21: | Line 21: | ||
|-style="background-color:#d8f3f1" valign="top" | |-style="background-color:#d8f3f1" valign="top" | ||
| | | | ||
<blockquote style="font-size:14pt"> | |||
'''[[Database Export]]''' | |||
</blockquote> | |||
[[File:Database_export_002.png|thumb]] | |||
Database Export is one of the main ways to '''[[Five Phases of Grooper|Deliver]]''' data '''[[Five Phases of Grooper|Collected]]''' in Grooper. | |||
A completed '''[[Content Model]]''' and accompanying '''[[Batch]]''' for what will be built can be found '''[[Media:Database Export.zip|here]]'''. It is not required to download to understand this article, but can be helpful because it can be used to follow along with the content of this article. ''This file was exported from and meant for use in Grooper 2.9'' | |||
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.</p> | |||
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. | |||
For more information on Database Export, visit the full wiki artcile [[Database Export|here]]. | |||
| | | | ||
[[Database Lookup]]s changed in version 2.80. Prior to Version 2.80, database lookups were performed on individual Data Fields in a Data Model, using simple field mappings. | [[Database Lookup]]s changed in version 2.80. Prior to Version 2.80, database lookups were performed on individual Data Fields in a Data Model, using simple field mappings. | ||
Line 86: | Line 87: | ||
| | | | ||
[[File:Olers-insurance-document-capture-service-case-study-grooper.jpg|thumb]] | |||
<blockquote style="font-size:14pt"> | <blockquote style="font-size:14pt"> | ||
'''Empowering Faster and Safer Services for Thousands of Public Servants''' | |||
</blockquote> | </blockquote> | ||
With over 100 years of public servant records on disks or paper files, the Oklahoma Law Enforcement Retirement System needed a new modern system to protect private information and streamline daily workflows. | |||
In 1947, Oklahoma Senate Bill 125 created a Death, Disability and Retirement | |||
Fund for Department of Public Safety members. In 1980, a new bill | |||
established the Oklahoma Law Enforcement Retirement System (OLERS) | |||
which continued the previous plan and expanded upon it to include | |||
* | members of other law enforcement agencies. | ||
* | |||
* | Currently, OLERS provides retirement funds to 11 different statewide law | ||
* | enforcement agencies. | ||
Key Outcomes: | |||
*Saving Hundreds of Hours Annually with Modern Document Management | |||
*Monthly Capture Service Provides Additional Time Savings | |||
*Many Layers of Personal InformationProtection | |||
*Redaction of At-Risk Data | |||
[https://www.bisok.com/case-studies/ | [https://www.bisok.com/case-studies/empowering-faster-and-safer-services-for-thousands-of-public-servants/ You can access the full case study clicking this link]. | ||
|} | |} | ||
Revision as of 10:47, 11 May 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.80 Reference Documentation |
Featured Articles | Did you know? |
Database Export is one of the main ways to Deliver data Collected in Grooper. A completed Content Model and accompanying Batch for what will be built can be found here. It is not required to download to understand this article, but can be helpful because it can be used to follow along with the content of this article. This file was exported from and meant for use in Grooper 2.9 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. Tables in 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 (Microsoft SQL Server or ODBC-compliant) tables in a database and intelligently populate said tables.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. For more information on Database Export, visit the full wiki artcile here. |
Database Lookups changed in version 2.80. Prior to Version 2.80, database lookups were performed on individual Data Fields in a Data Model, using simple field mappings. Now, lookups are configured on a Data Model, Data Section or Data Table’s properties, using SQL queries. Other improvements include:
Visit the Database Lookup article for more information. |
New in 2.9 | Featured Use Case | ||||||||||||||||||||||||||||
|
In 1947, Oklahoma Senate Bill 125 created a Death, Disability and Retirement Fund for Department of Public Safety members. In 1980, a new bill established the Oklahoma Law Enforcement Retirement System (OLERS) which continued the previous plan and expanded upon it to include members of other law enforcement agencies. Currently, OLERS provides retirement funds to 11 different statewide law enforcement agencies. Key Outcomes:
|
Other Resources | |||
|