Technical Support for ECM

The Nexus Scoop

It’s been a while since I posted anything new to the ECM support blog.  If you want to know why, see Brandon’s post from a while back- Support: A Day in the Life Of.  I feel his pain!  But there have been some exciting things happening here and you should know about them.

First of all, I got the low-down on Nexus ’11 the other day!  It seems that the goal is to make every year bigger and better then the next.  This year there are some very well-known and engaging speakers (such as Dr. James Brown), break-out sessions held by ECM professionals, deep dives with ECM field specific experts and of course the after-hours social events.  If you have not been to Nexus, you need to register for this event.  If you sign up early, you get a pricing discount!  Tell us if you want to attend!  (The best way to get a hold of us is put in a support ticket and in the description put that you are interested in Nexus.)

On the software front, I have been busy working with development teams on ILINX® products!  Content Store specifically has been really taking off and there are new improvements being added all the time!  The whole goal of ILINX is to provide a simple user experience, while providing a powerful administration interface, all though thin-client technology.  The ILINX Products Suite has everything covered – conversion, workflow, storage and integration.  Tell us if you want a demo – we have great people that know their stuff in the world of Content Management that would love to work with you to see if ILINX is right for you!

Last but not least, I want to thank all the reader’s outside of Washington State.  Thank you for finally sending us some warmer weather – it took ‘til August but summer is finally here as well!  As always, any questions or comments, please call or email me and we will give you an answer!

Mike Peterson
Support Engineer
ImageSource, Inc

August 2, 2011 Posted by | AIIM, Document Conversion, ECM, Electronic Workflow, Green Solutions, ILINX, Integration, Nexus 2011, Support | , , , , , , , , , , , | Leave a Comment

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

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

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

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.

  

January 30, 2010 Posted by | Document Scanners, Document Scanning, ECM, Electronic Workflow, Green Solutions, Help Desk, ILINX, Integration, Uncategorized | , , , , , , , , , , , | 2 Comments

   

Follow

Get every new post delivered to your Inbox.