The following
buttons are available at the bottom of this window:
The
string
substitution table substitutes
Search Text with
Replacement Text in the document and in the
database. It is used to normalize the results of the text search.
This font is
commonly used when standard character shapes are required to scan numbers and
for recognizing text without bar codes. Examples of where this font is used
include bank checks, passports, labels, and postal mail.
This font is used for
Magnetic Ink Character Recognition (MICR) and is primarily used for check
processing in the banking industry. Since special ink is used to print the MICR
characters, they can be recognized by a MICR reader with high reliability, even
if the characters are written over or obscured in any way. This font is also
easily readable by humans.
The
Hierarchy view is available only for test sets or benchmark sets when the
default document subset is selected. If any other document subset is selected,
the
Hierarchy View
toolbar setting is not available.
Simple
fields are the most common type of field. These fields typically contain a
single piece of information extracted from a document during processing.
Table
fields contain many pieces of extracted data from a document. Each cell in the
table contains extracted data, but instead of configuring each cell separately
using
simple fields, a table field in partnership
with a
table model and a locator, does this
automatically.
If
there are any unsaved changes to your document sets, you are prompted to save
or discard these changes before you are able to move or copy any documents.
This ensures that you do not inadvertently overwrite any modifications that you
want to keep.
If this
validation method is in a sequence of validation methods, it is not fired if
the previous validation method fails.
Select this
setting to allow an empty field to be valid. If this setting is not selected,
and a field is empty, it is marked as invalid.
To test the
settings, enter some sample input text and click
Format
. The sample text is formatted per the settings and displayed in the
output field. If the sample cannot be formatted per the settings, a warning or
error message is displayed.
This group has
the following settings:
This group has the
following setting:
Select a
reference document and four other sample documents with the following
characteristics:
-
All sample documents should have the same layout and represent the
same form.
The following examples cannot be considered the same form:
-
A multi page image of the same form but with a different page
order.
-
A US letter sized document that is printed on legal paper and
significantly shrunk as a result.
-
A small document such as an ID card that is scanned in large
format and not always in the same location of the large image.
-
A faxed document that has been faxed multiple times and has
shrunk as a result.
-
All sample documents should have the same page count.
-
All sample documents should have the same orientation.
-
All sample documents should have the same horizontal and vertical
resolution.
-
The layout of the document and its fields are easily
distinguishable.
-
There is no noise, punch holes, or marks on the documents.
-
The documents are not skewed or stretched in any way.
-
If forms contain hand written text, ensure that the text does not
fall outside the space available for each field.
-
The document contains typical values and any check boxes are clearly
marked.
This is
available only for projects created using the Classification Group template.
By default,
all of the above columns are displayed in the
Open Batch window for all user modules. You can
configure which columns are hidden by editing
ACConfig.xml file. This file is located in your
Tungsten Capture
installation. For more information on this configuration file, refer to
the
Tungsten Capture
Installation Guide.
To
optimize zone recognition, one or more pages with individual zones are bundled
together and sent to
Tungsten Clarity. A
volume license is consumed for each page in the bundle.
The following
buttons are available at the bottom of this window:
Related
topics:
The
confidence levels on the Field Settings for a field populated by an
Advanced Zone Locator subfield are ignored, and
that field is populated with a value from the
Advanced Zone Locator regardless of the specified
thresholds.