2023:Overrides (UI Element) - Revision history

Randallkinard at 15:03, 22 November 2024

2024-11-22T15:03:18Z

← Older revision		Revision as of 10:03, 22 November 2024
Line 76:		Line 76:

	A simpler, perhaps more common, example of where '''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 '''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 '''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 '''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.

	~~== Glossary ==~~
	~~<u><big>'''Batch'''</big></u>: {{#lst:Glossary\|Batch}}~~

	~~<u><big>'''Content Model'''</big></u>: {{#lst:Glossary\|Content Model}}~~

	~~<u><big>'''Content Type'''</big></u>: {{#lst:Glossary\|Content Type}}~~

	~~<u><big>'''Data Element'''</big></u>: {{#lst:Glossary\|Data Element}}~~

	~~<u><big>'''Data Field'''</big></u>: {{#lst:Glossary\|Data Field}}~~

	~~<u><big>'''Data Model'''</big></u>: {{#lst:Glossary\|Data Model}}~~

	~~<u><big>'''Document Type'''</big></u>: {{#lst:Glossary\|Document Type}}~~

	~~<u><big>'''Extract'''</big></u>: {{#lst:Glossary\|Extract}}~~

	~~<u><big>'''Labeled OMR'''</big></u>: {{#lst:Glossary\|Labeled OMR}}~~

	~~<u><big>'''Labeled Value'''</big></u>: {{#lst:Glossary\|Labeled Value}}~~

	~~<u><big>'''Overrides'''</big></u>: {{#lst:Glossary\|Overrides}}~~

	~~<u><big>'''Project'''</big></u>: {{#lst:Glossary\|Project}}~~

	~~<u><big>'''Review'''</big></u>: {{#lst:Glossary\|Review}}~~

	~~<u><big>'''UI Element'''</big></u>: {{#lst:Glossary\|UI Element}}~~

Randallkinard at 15:14, 27 August 2024

2024-08-27T15:14:53Z

@@ Line 25: / Line 25: @@
 * [[Media:2023_Wiki_Overrides_Batch.zip]]
 |}
 == About ==
@@ Line 105: / Line 76: @@
 A simpler, perhaps more common, example of where '''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 '''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.

Randallkinard at 16:45, 10 May 2024

2024-05-10T16:45:58Z

@@ Line 25: / Line 25: @@
 * [[Media:2023_Wiki_Overrides_Batch.zip]]
 |}
 == About ==
 '''Grooper''' solutions can range from simple scan and archive processes to extremely complex solutions. '''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.

Randallkinard at 18:35, 29 April 2024

2024-04-29T18:35:35Z

← Older revision		Revision as of 13:35, 29 April 2024
Line 3:		Line 3:
	[[File:2023_Overrides_01_About_01.png\|thumb\|This is a snippet of in '''Design''' showing the '''Overrides''' tab.]]		[[File:2023_Overrides_01_About_01.png\|thumb\|This is a snippet of in '''Design''' showing the '''Overrides''' tab.]]

	<blockquote ~~style="font-size~~:~~14pt">~~		<blockquote>{{#lst:Glossary\|Overrides}}</blockquote>
	~~'''~~Overrides~~''' is a tab provided to allow overriding of default properties set to a '''Data Element'''.~~
	</blockquote>

	{\| class="fyi-box"		{\| class="fyi-box"

Randallkinard: Randallkinard moved page 2023:Overrides (Concept) to 2023:Overrides (UI Element) without leaving a redirect

2024-04-23T17:51:38Z

Randallkinard moved page 2023:Overrides (Concept) to 2023:Overrides (UI Element) without leaving a redirect

← Older revision	Revision as of 12:51, 23 April 2024
(No difference)

Randallkinard: Randallkinard moved page 2023:Overrides to 2023:Overrides (Concept) without leaving a redirect: new naming convention

2024-04-16T21:00:47Z

Randallkinard moved page 2023:Overrides to 2023:Overrides (Concept) without leaving a redirect: new naming convention

← Older revision	Revision as of 16:00, 16 April 2024
(No difference)

Dgreenwood at 14:09, 27 March 2024

2024-03-27T14:09:15Z

← Older revision		Revision as of 09:09, 27 March 2024
Line 16:		Line 16:
	Prior to version 2023, "Overrides" were referred to as "Data Element Overrides". If you see older documentation referring to "Data Element Overrides", you may assume it is talking about "Overrides".		Prior to version 2023, "Overrides" were referred to as "Data Element Overrides". If you see older documentation referring to "Data Element Overrides", you may assume it is talking about "Overrides".
	\|}		\|}

	~~== About ==~~

	{\|class="download-box"		{\|class="download-box"
Line 29:		Line 27:
	* [[Media:2023_Wiki_Overrides_Batch.zip]]		* [[Media:2023_Wiki_Overrides_Batch.zip]]
	\|}		\|}
			== About ==

	'''Grooper''' solutions can range from simple scan and archive processes to extremely complex solutions. '''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.		'''Grooper''' solutions can range from simple scan and archive processes to extremely complex solutions. '''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.

Randallkinard: updated ZIP files, removed tables and tabs // via Wikitext Extension for VSCode

2024-03-08T20:49:18Z

updated ZIP files, removed tables and tabs // via Wikitext Extension for VSCode

Show changes

Dgreenwood at 13:39, 12 January 2024

2024-01-12T13:39:13Z

← Older revision		Revision as of 08:39, 12 January 2024
Line 19:		Line 19:
	==About==		==About==

	{\|~~cellpadding~~="~~10" cellspacing="5~~"		{\|class="download-box"
	\|-		\|
	~~\|style="font-size:14pt; color:#f89420; border: 2px solid #f89420; width:40px"\|~~[[File:Asset 22@4x.png]]		[[File:Asset 22@4x.png]]
	~~\|style="border: 2px solid #f89420"~~\|		\|
	You may download and import the file(s) below into your own Grooper environment (version 2023). There is a '''Batch''' with the example document(s) discussed in this tutorial, as well as a '''Project''' configured according to its instructions.		You may download and import the file(s) below into your own Grooper environment (version 2023). There is a '''Batch''' with the example document(s) discussed in this tutorial, as well as a '''Project''' configured according to its instructions.
	<br>		<br>

Dgreenwood: Dgreenwood moved page Overrides - 2023 to 2023:Overrides without leaving a redirect

2023-12-22T22:33:32Z

Dgreenwood moved page Overrides - 2023 to 2023:Overrides without leaving a redirect

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

← Older revision		Revision as of 10:03, 22 November 2024
Line 76:		Line 76:

	A simpler, perhaps more common, example of where '''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 '''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 '''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 '''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.

	~~== Glossary ==~~
	~~<u><big>'''Batch'''</big></u>: {{#lst:Glossary\|Batch}}~~

	~~<u><big>'''Content Model'''</big></u>: {{#lst:Glossary\|Content Model}}~~

	~~<u><big>'''Content Type'''</big></u>: {{#lst:Glossary\|Content Type}}~~

	~~<u><big>'''Data Element'''</big></u>: {{#lst:Glossary\|Data Element}}~~

	~~<u><big>'''Data Field'''</big></u>: {{#lst:Glossary\|Data Field}}~~

	~~<u><big>'''Data Model'''</big></u>: {{#lst:Glossary\|Data Model}}~~

	~~<u><big>'''Document Type'''</big></u>: {{#lst:Glossary\|Document Type}}~~

	~~<u><big>'''Extract'''</big></u>: {{#lst:Glossary\|Extract}}~~

	~~<u><big>'''Labeled OMR'''</big></u>: {{#lst:Glossary\|Labeled OMR}}~~

	~~<u><big>'''Labeled Value'''</big></u>: {{#lst:Glossary\|Labeled Value}}~~

	~~<u><big>'''Overrides'''</big></u>: {{#lst:Glossary\|Overrides}}~~

	~~<u><big>'''Project'''</big></u>: {{#lst:Glossary\|Project}}~~

	~~<u><big>'''Review'''</big></u>: {{#lst:Glossary\|Review}}~~

	~~<u><big>'''UI Element'''</big></u>: {{#lst:Glossary\|UI Element}}~~