2.90:Data Element Overrides - Revision history

Dgreenwood at 16:00, 5 August 2025

2025-08-05T16:00:41Z

← Older revision		Revision as of 11:00, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}

Dgreenwood: Dgreenwood moved page Data Element Overrides - 2.90 to 2.90:Data Element Overrides

2023-12-22T22:27:52Z

Dgreenwood moved page Data Element Overrides - 2.90 to 2.90:Data Element Overrides

← Older revision	Revision as of 17:27, 22 December 2023
(No difference)

Dgreenwood at 22:27, 22 December 2023

2023-12-22T22:27:34Z

← Older revision		Revision as of 17:27, 22 December 2023
Line 1:		Line 1:
			{{AutoVersion}}

	[[File:Data element overrides 000.png\|thumb\|350px\|This is a snippet of the '''Grooper Design Studio UI''' showing the '''Data Element Overrides''' tab.]]		[[File:Data element overrides 000.png\|thumb\|350px\|This is a snippet of the '''Grooper Design Studio UI''' showing the '''Data Element Overrides''' tab.]]

Line 103:		Line 105:
	===Where Did Zonal Properties Go?===		===Where Did Zonal Properties Go?===
	All the zonal extraction properties are now set directly on the '''Data Element'''.		All the zonal extraction properties are now set directly on the '''Data Element'''.

	~~[[Category:Articles]]~~
	~~[[Category:Version 2.90]]~~

Randallkinard: Randallkinard moved page Data Element Overrides to Data Element Overrides - 2.90

2023-11-09T16:34:30Z

Randallkinard moved page Data Element Overrides to Data Element Overrides - 2.90

← Older revision	Revision as of 11:34, 9 November 2023
(No difference)

Dgreenwood at 20:17, 9 December 2022

2022-12-09T20:17:44Z

← Older revision		Revision as of 15:17, 9 December 2022
Line 103:		Line 103:
	===Where Did Zonal Properties Go?===		===Where Did Zonal Properties Go?===
	All the zonal extraction properties are now set directly on the '''Data Element'''.		All the zonal extraction properties are now set directly on the '''Data Element'''.

			[[Category:Articles]]
			[[Category:Version 2.90]]

Randallkinard at 17:52, 5 November 2020

2020-11-05T17:52:21Z

← Older revision		Revision as of 12:52, 5 November 2020
Line 77:		Line 77:
	The following is a use case that heavily leverages '''Data Element Overrides'''.		The following is a use case that heavily leverages '''Data Element Overrides'''.

	Our '''Grooper A.C.E. Training Tier II and III''' members can click [~~about~~:~~blank~~ here and login to Grooper xChange] to view a video series covering the build of this awesome model.		Our '''Grooper A.C.E. Training Tier II and III''' members can click [https://xchange.grooper.com here and login to Grooper xChange] to view a video series covering the build of this awesome model.

	The three images below are examples of three different '''Document Types''' in the Revenue Statements model. Notice how different their formats are. As a result, the techniques used for extracting their information is quite different.		The three images below are examples of three different '''Document Types''' in the Revenue Statements model. Notice how different their formats are. As a result, the techniques used for extracting their information is quite different.

Randallkinard at 17:51, 5 November 2020

2020-11-05T17:51:30Z

@@ Line 4: / Line 4: @@
 '''Data Element Overrides''' is a tab provided to allow overriding of default properties set to a '''Data Element'''.
 </blockquote>
+</p><br/>
 A completed '''Content Model''' and accompanying '''Batch''' for what will be built can be found '''[[Media:Data Element Overrides.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''
@@ Line 62: / Line 62: @@
 . Click '''Test Extraction'''<br/>
 *Rinse and repeat for the other documents. Document Format C will now successfully extract due to the overrides.
+<p/><br/>
 It's important to note that because the '''Data Element Overrides''' are applied to a '''Content Type''' a document must be properly classified in order for the '''Data Model''' to know that overrides would be used for extraction for that document. You may be able to successfully test results from the '''Data Element Overrides''' interface without a classified document, but doing so on the '''Data Model''' will result in no extraction.
 || [[File:data_element_overrides_004.gif]]
@@ Line 70: / Line 70: @@
 <br/>
 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.
+{|
 ==Version Differences==

Dgreenwood at 14:51, 14 August 2020

2020-08-14T14:51:34Z

← Older revision		Revision as of 09:51, 14 August 2020
Line 62:		Line 62:
	3. Click '''Test Extraction'''<br/>		3. Click '''Test Extraction'''<br/>
	*Rinse and repeat for the other documents. Document Format C will now successfully extract due to the overrides.		*Rinse and repeat for the other documents. Document Format C will now successfully extract due to the overrides.
	~~<p/><br/>~~
	It's important to note that because the '''Data Element Overrides''' are applied to a '''Content Type''' a document must be properly classified in order for the '''Data Model''' to know that overrides would be used for extraction for that document. You may be able to successfully test results from the '''Data Element Overrides''' interface without a classified document, but doing so on the '''Data Model''' will result in no extraction.		It's important to note that because the '''Data Element Overrides''' are applied to a '''Content Type''' a document must be properly classified in order for the '''Data Model''' to know that overrides would be used for extraction for that document. You may be able to successfully test results from the '''Data Element Overrides''' interface without a classified document, but doing so on the '''Data Model''' will result in no extraction.
	\|\| [[File:data_element_overrides_004.gif]]		\|\| [[File:data_element_overrides_004.gif]]
Line 70:		Line 70:
	<br/>		<br/>
	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.		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.
	~~</p>~~
	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.		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.

Dgreenwood at 14:49, 14 August 2020

2020-08-14T14:49:17Z

← Older revision		Revision as of 09:49, 14 August 2020
Line 4:		Line 4:
	'''Data Element Overrides''' is a tab provided to allow overriding of default properties set to a '''Data Element'''.		'''Data Element Overrides''' is a tab provided to allow overriding of default properties set to a '''Data Element'''.
	</blockquote>		</blockquote>
	~~</p><br/>~~
	A completed '''Content Model''' and accompanying '''Batch''' for what will be built can be found '''[[Media:Data Element Overrides.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''		A completed '''Content Model''' and accompanying '''Batch''' for what will be built can be found '''[[Media:Data Element Overrides.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''

Randallkinard at 20:56, 8 June 2020

2020-06-08T20:56:48Z

← Older revision		Revision as of 15:56, 8 June 2020
Line 43:		Line 43:
	3. Select a '''Data Element''' you want to set overrides for, in this case a '''Data Field'''.		3. Select a '''Data Element''' you want to set overrides for, in this case a '''Data Field'''.
	*Note that '''Data Elements''' that have had properties overridden will be underlined.		*Note that '''Data Elements''' that have had properties overridden will be underlined.
	\|\| [[File:data_element_overrides_003a.png~~\|1000px~~]]		\|\| [[File:data_element_overrides_003a.png]]
	\|-		\|-
	\| style="padding:25px; width:35%" \|		\| style="padding:25px; width:35%" \|
Line 50:		Line 50:
	*In this example the properties were adjusted to allow for the reading of the OMR box, as opposed to the default setup which leveraged two different ''key-value pair'' extractors.<br/>		*In this example the properties were adjusted to allow for the reading of the OMR box, as opposed to the default setup which leveraged two different ''key-value pair'' extractors.<br/>
	6. Click the '''Test Extraction''' button to see the results.		6. Click the '''Test Extraction''' button to see the results.
	\|\| [[File:data_element_overrides_003b.png~~\|1000px~~]]		\|\| [[File:data_element_overrides_003b.png]]
	\|}		\|}
	</tab>		</tab>