Data Element Overrides
Data Element Overrides is a tab provided to allow overriding of default properties set to a Data Element.
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
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.
|!||Some of the tabs in this tutorial are longer than the others. Please scroll to the bottom of each step's tab before going to the step.|
Understanding the Forms
Setting up the Override
Testing the Results
It is worth noting that one could have accomplished the above by simply making another extractor and set it up for OMR, then have the Value Extractor Data Types for each Data Field simply reference a third element. Overrides would not be necessary in that case. This example, however, sufficed to provide something to show. As with many things in Grooper there isn't always a right or wrong way. There is perhaps a best practice, and in this case, making the third extractor would be the better thing to do.
A simpler, perhaps more common, example of where Data Element Overrides very much come in handy is with the visibility of Data Elements. One of the properties of a Data Element is the Visible property which is default True. Imagine a Data Model that has five Data Fields, and the Content Model has 3 Document Types. Document1 uses Data Fields 1-3, Document2 uses Data Fields 2-4, and Document3 uses Data Fields 3-5. In Data Review you want to simplify the job for the person reviewing, so you do not want them to concern themselves with fields that are not relevant. To accomplish this you could use Data Element Overrides on each of the aforementioned hypothetical Document Types and set the Visible property to False on all the fields you don't need. This would keep only relevant Data Fields visibile upon review.
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.