7.5

l A Capture field is setup for ICR in a PlanetPress Design document.
l The document is sent to PlanetPress Production
l The Capture Field Generator is used to produce one or more print-outs using this document.
l The physical sheets are written on using an Anoto Digital Pen
l The pen is docked and the data is sent to PlanetPress Production
l The pen data goes through the Capture Field Processor, where the Capture Field ink is sent through the ICRengine.
l The captured ICRdata is retrieved with the document using the Get Capture Document task.
l Conditions are applied if necessary with the Capture Condition task.
ICR, just like OCR, has its limitations. Please refer to the PlanetPress Capture ICR Best Practices page for more infor-
mation.
Terminology and Definitions
In regards to our ICRtechnology specifically, the following terminology applies:
l ICR:"Intelligent Character Recognition", or the engine that will read the pen data and attempt to recognize the text
written using the pen itself. The ICRengine uses the path of the pen, its movement speed as well as the overall shape
of each character to determine which character was written.
l ICRValue:The alpha, numeric or alphanumeric value that was determined by the ICRengine.
l ICRConfidence:Apercentage value that the ICRengine gives to any specific value, when comparing the pen data with
it's character database.
l ICRResemblance:Apercentage value that defines how closely the value resembles the "average"character shape.
Both the Confidence and Resemblance can be used together to make an informed decision on the contents received by
ICR.
PlanetPress Capture ICR Best Practices
The latest version of PlanetPress Suite (7.5) now gives PlanetPress Capture the capability of doing the Intelligent Character
Recognition (ICR). However, this technology comes with certain limitations. A successful integration of ICR within a business
requires the application of best practices by all parties involved: Form designer, Workflow designer and User.
The present document gives a list of recommended best practices. Each of these guidelines aim at maximizing the likelihood
that the characters are recognized; and minimize the risk of errors due to an incorrect analysis.
You will find the following information, when applicable, for each best practice:
l Target: The targeted audience. There are 3 possibilities: Form designer, Workflow designer and User.
l What: A brief description of the best practice. This could include an explanation of the concepts that are addressed.
l Why: A brief explanation of the reasoning behind the relevance of this guideline.
l How: How to apply this best practice.
This section describes a list of the best practices to implement. They are listed in no particular order of importance. Pay atten-
tion to the targeted audience to know if this rule applies to you.
1- Using the most restrictive mask
l Target: Form designer
l What: In the Options Capture tab of a Capture object, the mask type indicates the type of character to be recognized.
There are 3 possible selections: numeric, alphabet and alphanumeric. The alphabetic mask type allows you to select
the letter case.
Special Workflow Types