2.90:Data Element Overrides: Difference between revisions
Created page with "<blockquote style="font-size:14pt"> '''Data Element Overrides''' is a tab provided to allow overriding of default properties set to a '''Data Element'''. </blockquote> ==Abou..." |
No edit summary |
||
| Line 9: | Line 9: | ||
{| | {| | ||
| style="padding:25px; vertical-align:top" | | | style="padding:25px; vertical-align:top" | | ||
Following is an example of | Following is an example of how to setup '''Data Element Overrides'''. In this example are three different document formats, all of which are collecting the same data. Format A and B follow a similar enough structure and will not use an override to extract. Format C is different enough that it will override the default extractor to get its data. | ||
|| [[File:data_element_overrides_001.gif]] | || [[File:data_element_overrides_001.gif]] | ||
|} | |} | ||
<tabs style="margin:20px"> | |||
<tab name="Understanding the Forms" style="margin:25px"> | |||
{| | |||
| style="padding:25px; vertical-align:top" | | |||
In the image on the right you can see that Format A and Format B have values that can be captured with simple ''key-value pair'' extractors. In fact, the '''Value Extractor''' '''Data Type''' for the '''Value 1''' '''Data Field''' is simply referencing two different extractors, each in either a horizontal or vertical layout. This one extractor is successfully extracting values for both Format A and Format B, but it fails on Format C because that form is using OMR boxes instead of YES/NO values. | |||
|| [[File:data_element_overrides_002.gif|1000px]] | |||
|} | |||
</tab> | |||
</tabs> | |||
==Version Differences== | |||
Versions prior to '''Grooper 2.9''' had an initial concept version of overrides in the '''Data Element Profiles''' tab located on the '''Content Model''' or '''Document Type'''. These profiles only allowed modification to a limited number of properties on the data element, as opposed to '''Grooper 2.9''' where all properties can be overridden. | |||
===Where Did Zonal Properties Go?=== | |||
All the zonal extraction properties are now set directly on the '''Data Element'''. | |||
Revision as of 16:35, 9 April 2020
Data Element Overrides is a tab provided to allow overriding of default properties set to a Data Element.
About
Grooper solutions can range from simple scan and archive processes to extremely complex solutions. Data Element Overrides allow discrete control of Data Elements on a per Content Type basis. This greatly magnifies Grooper’s inheritance-based architecture and allows for more robust and scalable Data Models. You are no longer required to make copies of Data Elements when you just need to modify a property for an oddball Document Type. This can greatly save time building the solution and reduce complexity by eliminating those copied Data Elements. One can also quickly and easily Test Extraction directly in the Overrides tab. After modifying any of the Data Element properties, you can easily test the results of the modification against a test Batch without leaving the tab.
How To
|
Following is an example of how to setup Data Element Overrides. In this example are three different document formats, all of which are collecting the same data. Format A and B follow a similar enough structure and will not use an override to extract. Format C is different enough that it will override the default extractor to get its data. |
|
|
In the image on the right you can see that Format A and Format B have values that can be captured with simple key-value pair extractors. In fact, the Value Extractor Data Type for the Value 1 Data Field is simply referencing two different extractors, each in either a horizontal or vertical layout. This one extractor is successfully extracting values for both Format A and Format B, but it fails on Format C because that form is using OMR boxes instead of YES/NO values. |
|
Version Differences
Versions prior to Grooper 2.9 had an initial concept version of overrides in the Data Element Profiles tab located on the Content Model or Document Type. These profiles only allowed modification to a limited number of properties on the data element, as opposed to Grooper 2.9 where all properties can be overridden.
Where Did Zonal Properties Go?
All the zonal extraction properties are now set directly on the Data Element.