Reviewing the runtime batch files

After you run the batch through the workflow, you can review the runtime batch files to ensure that they were processed correctly.

To review the runtime batch files:

1. Open the most recent batches folder of the TravelDocs application.
2. Open the file PageID.xml and scroll till end of the file to view the details for the last page.

   <P id="TM000015">
   		<V n="IMAGEFILE">tm000015.tif</V>
   		<V n="ScanSrcPath">c:\datacap\traveldocs\images\offsetairticket.tif</V>
   		<V n="RecogStatus">0</V>
   		<V n="LC_Confidence">0.4774427</V>       <--Confidence level from fingerprint matching
   		<V n="LC_Image_Offset">-24,0</V>
   		<V n="LC_TemplateID">569</V>             <--Closest matching fingerprint
   		<V n="Fingerprint Created">No</V>
   		<V n="Confidence">0.4774427</V>
   		<V n="TemplateID">566</V>                <--Matching fingerprint based on pattern matching
   		<V n="PatternConfidence">10</V>          <--Confidence level from pattern matching
   		<V n="Image_Offset">-100,-100</V>        <--Offset relative to fingerprint 566
   		<V n="MatchType">GeometricPattern</V>    <--Page identified using geometric pattern matching
   		<V n="DATAFILE">tm000015.xml</V>
   </P>

   In this example, the closest matching fingerprint is fingerprint 569, one of the hotel pages. But the confidence level is only 0.477, which is not enough for a match. This result caused the FindFingerprint action to fail.

   After the FindFingerprint action failed, Datacap ran the Identify using Text Match function. However, this function failed because the Airline #2 ticket does not include the word "Car." Datacap then ran the Identify using Pattern Match function and found an exact match with the fingerprint 566, the original Airline #2 fingerprint. The match is exact because the vendor logo, not the data, is identical on both pages. Open the export text file (C:\TravelDocs\export\batch_id.txt). You can see that Datacap located all of the data fields by using the offsets that it calculated during pattern matching and recognized the data successfully.

   ,U Airline #2,Newark, NJ (EWR),Dayton, OH (DAY),MON JAN 10, 2011,
   Dayton, OH (DAY),Newark, NJ (EWR),THUR JAN 13, 2011,360.56,33.23,393.79