NOTES: The stages of processing are included in the base Quick Fields installation, but some of the other features and processes described require add-ons.

Quick Fields 8 includes multiple stages of processing to help you configure your sessions for maximum efficiency. With these new stages, you can avoid repeating the same steps or waiting for time-consuming processes to be completed.

The three stages are Pre-Classification Processing, Page Processing and Storage Processing.

Pre-Classification Processing

Processes configured in this stage run on every page of every document. It is particularly useful with multiple document classes.

Example: The City of Wonderland is processing public works requests that need to be handled quite differently, depending on the type of request. Each request has a code number in the upper right corner designating the request type. They configure the OmniPage Zone OCR process in the Pre-Classification Processing stage to read the code from each page at the beginning of the session. They then create a document class for each type of request and use the new Token Identification process in each document class to analyze the OmniPage Zone OCR tokens and assign the documents to classes accordingly. The session will run much faster than if each document had to go through an OmniPage Zone OCR identification process for every document class until it was assigned.

Page Processing

Processes configured in this stage run on specified pages of documents that have been assigned to a class. This was formerly the only stage of processing in Quick Fields, and was previously known as Image Processing. The name has been changed to reflect the increased support for electronic documents and page text in Quick Fields 8.

Example: B.N. Riche Financial Advisors sorts fund prospectuses, which are published as PDF documents. In Page Processing, they configure Pattern Matching to search the first page of each prospectus for information such as the type of fund and the date of the prospectus, and use tokens generated by the process to populate the folder paths and fields associated with the document.

Storage Processing

Processes in this stage also run on specified pages of documents that have been assigned to a class, but they are applied only when the documents are stored to Laserfiche. This can help you sort and scan documents much faster, since you can apply time-consuming processes such as Optical Character Recognition at scheduled storage times.

Example: The Phoenix Clinic is scanning its patients’ hospital records from paper files. They want to generate text from them so the records can be full-text searchable in Laserfiche, but they do not need the text for any processes in Quick Fields. They configure OmniPage OCR in Storage Processing and schedule storage to take place at 1:00 a.m. when more resources are available.

Strategic thinking about where to place processes in your session can result in much more efficient and productive Quick Fields sessions, so it’s always a good practice to consider the roles of the different phases and the interactions of different processes.

Tags: Quick Fields

Posted on Tuesday, June 16th, 2009 at 9:21 am under Support, UserNews. You can comment on this post.