Barcode Document Separation with ILINX Capture

While exploring different document separation techniques I discovered that bar code separation may cause the document to be split multiple times.   I scanned in a single document that had 334 pages and for some reason it split the document multiple times.  There were no other barcodes except one Patch Type T separator at the beginning of the document.

After looking over the settings on the Barcode QSX module inside the ILINX Capture Server Manager I noticed that the Patch Type T document separator and the 3 of 9 barcode separator were enabled.  Please see picture below…

ILINX Capture Barcode OSX Module

One of the challenges with setting up barcode separation with both Patch Type T document separator and the 3 of 9 barcode separator is that every time the recognition engine comes across a 3 of 9 barcode it will separate the document automatically regardless if you want it to or not . Unfortunately the software can get tripped up on its own logic and every time the recognition engine comes across a 3 of 9 barcode it will separate the document automatically.  ILINX Capture’s recognition engine still separates by the Patch Type T Patch Code as well as every 3 of 9 barcode. This can give unexpected results with the number of documents that are automatically generated.  To fix the above example I removed the bar code separation because it was not needed. As you can see in the following example…

ILINX Capture Barcode Settings

However, in some cases this may not meet a client’s needs and different approach to document separation is needed. The best practice for multiple document separation is when using Patch Type T Patch separator pages and 3 of 9 barcode separation you need to add a prefix for each type of document you want to separate.

Here is a good example:

A client may want to separate documents by what’s in the barcode itself, such as capturing the word “ILINX” in the barcode for a document type of “Application” and the word “Invoice” in the barcode for a document type of “Invoice”.  To do this you need to add a prefix value with a document type see.

As you can see ILINX Capture has the ability to be customized to fit your needs no matter how basic and/or how complicated the requirements are. The main concept here is ILINX Capture is a very powerful tool and needs to be configure properly to get want you need out of it. The above example is only a small scratch on the surface on what this tool can actually do.

However, in some cases this may not meet a client’s needs and different approach to document separation is needed. The best practice for multiple document separation is when using Patch Type T Patch separator pages and 3 of 9 barcode separation you need to add a prefix for each type of document you want to separate.

A client may want to separate documents by what’s in the barcode itself, such as capturing the word “ILINX” in the barcode for a document type of “Application” and the word “Invoice” in the barcode for a document type of “Invoice”. To do this you need to add a prefix value with a document type see.

ILINX Capture Prefix Settings

As you can see ILINX Capture has the ability to be customized to fit your needs no matter how basic and/or how complicated the requirements are. The main concept here is ILINX Capture is a very powerful tool and needs to be configure properly to get want you need out of it. The above example is only a small scratch on the surface on what this tool can actually do.

John Hart
ImageSource Inc.