2.80:OMR Reader (Result Processor) - Revision history

Dgreenwood: Dgreenwood moved page 2.80:OMR Reader (Result Post Processor) to 2.80:OMR Reader (Result Processor) without leaving a redirect

2025-08-05T15:41:50Z

Dgreenwood moved page 2.80:OMR Reader (Result Post Processor) to 2.80:OMR Reader (Result Processor) without leaving a redirect

← Older revision	Revision as of 10:41, 5 August 2025
(No difference)

Dgreenwood at 15:41, 5 August 2025

2025-08-05T15:41:13Z

← Older revision		Revision as of 10:41, 5 August 2025
Line 233:		Line 233:
	== Version Differences ==		== Version Differences ==

	Prior to version 2.80, this functionality would been performed using the "Data Element Profiles" tab of a '''Document Type''' and drawing "OMR Zones" around the checkboxes to read their check states. Grooper has moved away from "Data Element Profiles" in favor of configuring the functionality directly on Data Elements in a Data Model, using '''''Value Extractors''''' such as ''Labeled OMR'' or a '''Data Type''' using the ''OMR Reader'' ~~result post processor~~.		Prior to version 2.80, this functionality would been performed using the "Data Element Profiles" tab of a '''Document Type''' and drawing "OMR Zones" around the checkboxes to read their check states. Grooper has moved away from "Data Element Profiles" in favor of configuring the functionality directly on Data Elements in a Data Model, using '''''Value Extractors''''' such as ''Labeled OMR'' or a '''Data Type''' using the ''OMR Reader'' Result Processor.

	Furthermore, ''OMR Reader'' gives OMR functionality to '''Data Type''' extractors where "Data Element Profiles" could ''only'' be configured to return OMR labels directly to a '''Data Model'''. '''Data Types''' can be used for any number of purposes in Grooper, not just for populating a '''Data Model'''. For example, an ''OMR Reader'' configured '''Data Type''' could be used to classify a '''Document Type'''. This functionality would not be possible prior to version 2.80.		Furthermore, ''OMR Reader'' gives OMR functionality to '''Data Type''' extractors where "Data Element Profiles" could ''only'' be configured to return OMR labels directly to a '''Data Model'''. '''Data Types''' can be used for any number of purposes in Grooper, not just for populating a '''Data Model'''. For example, an ''OMR Reader'' configured '''Data Type''' could be used to classify a '''Document Type'''. This functionality would not be possible prior to version 2.80.

Dgreenwood at 15:10, 5 August 2025

2025-08-05T15:10:54Z

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

Dgreenwood at 15:02, 22 December 2023

2023-12-22T15:02:55Z

← Older revision		Revision as of 10:02, 22 December 2023
Line 242:		Line 242:

	[[Category:Articles]]		[[Category:Articles]]
	~~[[Category:Version 2.80]]~~

Dgreenwood: Dgreenwood moved page OMR Reader (Result Post Processor) - 2.80 to 2.80:OMR Reader (Result Post Processor)

2023-12-22T14:57:13Z

Dgreenwood moved page OMR Reader (Result Post Processor) - 2.80 to 2.80:OMR Reader (Result Post Processor)

← Older revision	Revision as of 09:57, 22 December 2023
(No difference)

Dgreenwood at 14:56, 22 December 2023

2023-12-22T14:56:53Z

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

	{\|cellpadding=10 cellspacing=5 style="margin:12px"		{\|cellpadding=10 cellspacing=5 style="margin:12px"
	\|-		\|-

Dgreenwood: /* See Also */

2023-12-22T14:47:37Z

Dgreenwood at 18:09, 25 September 2023

2023-09-25T18:09:49Z

← Older revision		Revision as of 13:09, 25 September 2023
Line 1:		Line 1:
			{\|cellpadding=10 cellspacing=5 style="margin:12px"
			\|-
			\|style="font-size:200%; background-color:#662d91; color:white; width:28px; text-align:center"\|'''‼'''
			\|style="border: 4px solid #662d91"\|
			'''LEGACY TECHNOLOGY DETECTED!!'''

			The '''''OMR Reader''''' post processor is still configurable for '''Data Type''' extractors in Grooper. However, this is a largely outdated way of doing things as of version 2021.

			Now, it is more likely you would use the [[Labeled OMR]] extractor type to accomplish the same end goal.
			\|}

	[[image:omr reader.png\|frame\|The OMR Reader post processor selected on a Data Type's property panel.]]		[[image:omr reader.png\|frame\|The OMR Reader post processor selected on a Data Type's property panel.]]

Dgreenwood at 18:02, 12 December 2022

2022-12-12T18:02:32Z

← Older revision		Revision as of 13:02, 12 December 2022
Line 227:		Line 227:
	* [[Labeled OMR]]		* [[Labeled OMR]]
	* [[Anchored OMR]]		* [[Anchored OMR]]

			[[Category:Articles]]
			[[Category:Version 2.80]]

Dgreenwood: Dgreenwood moved page OMR Reader (Result Post Processor) to OMR Reader (Result Post Processor) - 2.80: To be consistent with current naming conventions

2022-12-12T18:02:09Z

Dgreenwood moved page OMR Reader (Result Post Processor) to OMR Reader (Result Post Processor) - 2.80: To be consistent with current naming conventions

← Older revision	Revision as of 13:02, 12 December 2022
(No difference)

← Older revision		Revision as of 09:47, 22 December 2023
Line 237:		Line 237:

	* [[Labeled OMR]]		* [[Labeled OMR]]
	* [[Anchored OMR]]		* [[2.80:Anchored OMR]]

	[[Category:Articles]]		[[Category:Articles]]
	[[Category:Version 2.80]]		[[Category:Version 2.80]]