2.90:OCR Reader (Result Post Processor) - Revision history

Dgreenwood at 16:05, 5 August 2025

2025-08-05T16:05:37Z

← Older revision		Revision as of 11:05, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{\|cellpadding=10 cellspacing=5 style="margin:12px"		{\|cellpadding=10 cellspacing=5 style="margin:12px"
	\|-		\|-

2024-01-02T18:37:20Z

← Older revision	Revision as of 13:37, 2 January 2024
(No difference)

2024-01-02T18:34:59Z

← Older revision		Revision as of 13:34, 2 January 2024
Line 295:		Line 295:

	There are no major differences to report from version 2.72 to 2.90.		There are no major differences to report from version 2.72 to 2.90.

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

2024-01-02T18:34:34Z

← Older revision	Revision as of 13:34, 2 January 2024
(No difference)

2023-09-25T18:09:28Z

← Older revision		Revision as of 13:09, 25 September 2023
Line 5:		Line 5:
	'''LEGACY TECHNOLOGY DETECTED!!'''		'''LEGACY TECHNOLOGY DETECTED!!'''

	The OCR 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.		The '''''OCR 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 [[Read Zone]] extractor type to accomplish the same end goal.		Now, it is more likely you would use the [[Read Zone]] extractor type to accomplish the same end goal.

2023-09-25T18:06:22Z

← Older revision		Revision as of 13:06, 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 OCR 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 [[Read Zone]] extractor type to accomplish the same end goal.
			\|}


	[[image:ocr reader2.png\|frame\|The OCR Reader post processor selected on a Data Type's property panel.]]		[[image:ocr reader2.png\|frame\|The OCR Reader post processor selected on a Data Type's property panel.]]

2022-12-12T18:00:32Z

← Older revision		Revision as of 13:00, 12 December 2022
Line 283:		Line 283:

	There are no major differences to report from version 2.72 to 2.90.		There are no major differences to report from version 2.72 to 2.90.

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

2020-10-26T13:26:23Z

← Older revision		Revision as of 08:26, 26 October 2020
Line 78:		Line 78:

	== How To ==		== How To ==

			If you would like to follow along with this tutorial, you may download the zip file below and import it into your Grooper Repository. This file contains a batch with the documents used in this tutorial and configured Grooper assets.

			*[[media:OCR Reader (2.90).zip]]

	<tabs style="margin:20px">		<tabs style="margin:20px">

2020-10-23T19:51:27Z

← Older revision		Revision as of 14:51, 23 October 2020
Line 273:		Line 273:
	</tab>		</tab>
	</tabs>		</tabs>

			== Version Differences ==

			The ''OCR Reader'' result processor is a new configurable property available to '''Data Types''' as of version 2.72. Prior to version 2.72, the capability of reprocessing OCR on a region of a document was available by configuring a Data Element Profile in a '''Document Type''' object. ''OCR Reader'' provides a much simpler configuration to obtain the same result. Furthermore, since the result is returned to a '''Data Type''', the result can be used any time a '''Data Type''' extractor is used in Grooper, not just to populate a '''Data Field''' in a '''Data Model'''.

			There are no major differences to report from version 2.72 to 2.90.

2020-10-23T19:45:26Z

How To

@@ Line 222: / Line 222: @@
 [[File:Ocr-reader-how-to-12.png]]
 |}
 </tab>
 </tabs>