Manual anchoring is only enabled for pages that include
an anchor field with the variable Required=1 and
where the anchor field's position in the runtime page data file is
undefined or set to 0,0,0,0.
Unidentified pages (pages of type Other)
typically do not have a runtime page data file. So you must first
assign a page type. When you assign a page type, AIndex creates a
page data file and sets all of the fields to 0,0,0,0.
If the page type you assign has an anchor field with Required=1,
AIndex enables manual anchoring.
AIndex checks document integrity
when you submit the batch. So your documents and pages must be structured
correctly. Additionally, you need to have appropriate Done
Page Statuses, Validation Statuses, Done
Field Statuses, and Ignored Field Statuses values
in the task's .set.xml file (see Configuring the VeriFine client). You do this task later when you update
the TravelDocs application to use AIndex (see Updating ManualPageID).
To identify or register a page by using manual anchoring:
-
In the AIndex batch tree view pane, select the page that
requires identification or manual registration.
-
If the page is unidentified, use the drop-down lists to
set the document type and page type. Depending on the position of
the page within the batch, you might need to select the Start
Doc option before you can set the document type.
-
If manual anchoring is enabled for the page type that you
selected, Datacap displays
a message that you must set the anchor position. Click OK to
close the message box.
-
Click Anchors in the batch tree
view pane.
-
If the page is unidentified, Datacap displays thumbnails
of all fingerprints with a required anchor (Required=1).
You are asked to double-click the matching fingerprint. Click OK to
close the message box and then double-click the matching fingerprint.
Datacap reads
the position of the anchor object for the fingerprint that you selected
from the document hierarchy, and floats a red version of the anchor
image over the current page image.
-
Use the mouse to align the anchor object with the page
image.
-
When you complete the batch, Datacap writes the anchor
position to the runtime page data file and writes the offset values
to the runtime batch hierarchy.
The following table
provides an example.
| Runtime page data file |
Runtime batch hierarchy file |
<P id="appdevguide_TM000006">
<F id="appdevguide_Vendor_Logo">
<V n="TYPE">Vendor_Logo</V>
<V n="Position">221,229,608,332</V>
<V n="STATUS">-1</V>
</F>
etc.
|
<P id="appdevguide_TM000006">
<V n="IMAGEFILE">tm000006.tif</V>
<V n="TYPE">Air_Ticket</V>
<V n="STATUS">0</V>
<V n="Image_Offset">-45,-29</V>
<V n="TemplateID">562</V>
etc.
|