I ran into an interesting challenge with a customer and thought it might be something of interest to others. The challenge was in creating a way to have an entire batch of documents go through Advanced Capture processing and be returned to the input software, in this case ILINX Capture, as a single batch upon export.
I have implemented numerous Advanced Capture solutions over the years and have identified a number of sticking points that are easily overcome, but can also be a real pain. I would classify an Advanced Capture solution as any document capture implementation that is more than a standard heads-up indexing or very basic zonal OCR of fixed forms based on X and Y coordinates. That definition leaves a lot of room for what could be designated as an ‘advanced capture solution’, but I think it fits. Once you move out of the realm of basic capture, you start to encounter a lot of the same problems. There is one problem I seem to encounter every time we implement a solution.
From time to time I receive questions about large file uploads with ILINX Capture. ILINX Capture can upload files of any size. The limitation is within Internet Information Services(IIS) and or the amount of memory installed in the web server. This is not only true for ILINX Capture, but and ASP or ASP.Net application.
The feature set in ILINX Capture is vast and it can be a drag reviewing and interpreting feature lists in software documentation. Those of you not familiar with ILINX Capture can visit the following website.www.ilinxcapture.com, or feel free to leave a comment and we can provide additional information and/or a hands-on demonstration. In short, ILINX Capture is a web based capture platform that excels in distributed capture and custom capture workflow environments. It is scalable to work on a single workstation or it can be extended to an enterprise wide global standard for capture in your organization.
I wanted to use this post to touch on a couple of the features that I see being used more and more in ILINX Capture. These features became part of the product based on customer feedback, industry direction, and internal vision for the product. All of the following features can be added to any point in your process flow map, so it provides not only the functionality but also the flexibility to adapt to the business needs of current processes in place today.
- 2D Barcode Support – This feature adds the ability to read metadata, classify and separate documents, and provide quality control checks through the recognition of 2D barcodes. Through a GUI the user has the ability to parse the barcode data and map it to fields, separate and identify the type of document, and validate that the number of pages in the document match what was captured through the scanning or electronic import process.
I recently was asked to help with a client’s KTM (Kofax Transformation Modules) project, because they were not pleased with the percentages of valid and/or correct extraction fields. My first question was, “Are you using subclasses?” The answer was, “No.” Subclassifying your top forms is an easy way to greatly improve your extraction results.
What I mean by that is instead of trying to use a single locator to find data from all of your documents with a “one size fits all” approach, you can use subclasses to first classify the document and then tune your locators specific to that form to look in a precise location for the information. For example, let’s say you need to find a “Case Number” off of all of your forms. Some forms might have the word “Case Number” above the text you need to extract. Others might have the word “Number” to the left of the data. Another might not have any text around the data to key off of at all. It’s difficult to add enough rules in one locator to catch all the possible scenarios. Furthermore, there are times when adding rules to help find data on one form will actually give you negative results from another. Subclasses can help by allowing you to create a specific locator to zero in on the information that you are looking for. Continue reading