I am not usually out to promote specific products on this blog, but I have been getting really excited about the latest advancements in the ILINX Product Suite. It is an area that I, among other experienced ECM technologists, have utilized our expertise in creating and refining solutions that can provide real world value for businesses implementing or utilizing ECM solutions. Take a minute to read this quick post and judge for yourself the value that ILINX Products can provide for your organization.
You may be hearing the word ILINX used in Enterprise Content Management circles more and more these days. From the humble beginnings of a simple release script connecting a document capture system to an ECM repository the ILINX Product Suite has grown into a set of powerful, easy to use products that provide quick ROI. There are multiple levels to the ILINX Product Suite ranging from a full blown web client based document capture system (ILINX Capture) or an ECM Repository (ILINX Content Store) to variety of middleware products that can provide time savings and productivity boosting results like ILINX Integrate.
If you are not familiar with all that the Product Suite has to offer, check out the ILINX website for the details and product demos.
Last time we took a look at the Abbyy FlexiCapture product to perform College Transcript processing in a broad overview. This time I would like to start looking at some lower level details of the product that show where FlexiLayouts end and Project Level Document Definitions begin.
Let’s start with some basic definitions. A Layout is used to help the Recognition Engine to identify the document in a batch as belonging to a particular Document Definition. A Layout is also used to help the Recognition Engine to find the locations of the data to extract and place in fields the user can then see and modify if necessary. A Document Definition is used to determine the type of processing to perform on the document, the fields contained in the document and the type of data those fields should have. Continue reading →