Measuring The Effectiveness of ICAP

[Joe_Pineda]

This is for OnBase 15!

Hi all,

We are trying to report on how effective ICAP is by determining if a keyword (or a group of keywords) was touched by a human after ICAP.  If so, that would be considered a failure. Then, we would count the failures and divide them by the successes, and get a hit rate. Basically, We're being asked to help with a 'hit report' which the customer has defined as the rate of success/failure related to the intervention of the AP staff in having to correct keywords on documents that have gone through ICAP.

Our challenges are as follows.

1. We would like to know what tables in the database have relevant ICAP information.

2. What table and column would tell us if a human updated a keyword?  We think the system assigns a 'keyword created/modified date' (like xx/xx/1964), and if it was updated by a human during indexing, that date would be something other than xx/xx/1964. We found a table called aisuspectkeys that has a column called reviewtime. Would this be the right table/column to determine if a keyword was touched by a human? (date is different from 1964-01-01.

Any help is welcome and appreciated.

[Joe_Lane]

Hi Joe,

1. Here are the related ICAP database tables:

hsi.aikeywordmap
hsi.aitags
hsi.aiitemtypetags
hsi.ailayouts
hsi.ailayoutidentifiers
hsi.aiitemtypestats
hsi.aitagstats
hsi.aitablestats
hsi.aierpsystems
hsi.aisuspectkeys
hsi.queuexaierpsystems

2. The following information should prove useful in your reporting:

1. hsi.aisuspectkeys - The suspectvalue column represents the suspect level for each keyword that ICAP indexes on a document.
   0 - Confident Value
   1 - Suspect based on OCR Confidence
   2 - Suspect based on Tag or Value Location Confidence
   4 - Suspect based on the use of tag pool tags instead of learned tags
   8 - Suspect based on the core rejecting the value as a valid keyword
2. hsi.scanninglog - Batches which are automatically processed by ICAP will not log a row for the Awaiting Index queue since the batch does not go to the Awaiting Index queue.
3. hsi.transactionxlog - With the "Log Keyword Modifications" Scan Queue setting enabled, this table will log a Delete Keyword and Add Keyword event when a user updates a keyword value that was indexed during ICAP processing.

The Database Reporting Guide also provides information you may find helpful when writing your custom report.

Since queries against these tables have the potential to negatively impact performance, we recommend that SQL statements should only be edited or written by a certified database administrator. Queries that are not written with the index schemas and data distributions in mind can become long-running queries that consume substantial database server resources and adversely affect the performance of the entire system.

Regards,

Joe Lane
Tech Support
Hyland