Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

Transcription

1 IBM Datacap Taskmaster Capture Version Parascript FieldScript for IBM Datacap Taskmaster Capture Guide GC

2

3 IBM Datacap Taskmaster Capture Version Parascript FieldScript for IBM Datacap Taskmaster Capture Guide GC

4 Note Before using this information and the product it supports, read the information in Notices on page 1. This edition applies to version 8, release 0, modification 1 of IBM Datacap Taskmaster (product number 5725-C15) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 1994, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Table of Contents Parascript FieldScript for IBM Datacap Taskmaster Capture V Preparing for installation...3 Downloading Parascript FieldScript for IBM Datacap Taskmaster Capture V Integrating Parascript FieldScript for IBM Datacap Taskmaster Capture V Identifying the computers on which Parascript must be installed... 4 Identifying and shutting down Taskmaster software... 4 Installing Parascript FieldScript for IBM Datacap Taskmaster Capture V Planning your application... 5 Understanding recognition context... 5 Understanding Field Types and properties... 5 Understanding writing style... 6 Understanding dependencies within the application... 6 Performing image preprocessing... 7 Identifying the correct format of input images... 7 Understanding the USPS database... 7 Deciding the location of the USPS database... 8 Viewing the contents of the USPS database... 8 Incorporating an end user database... 8 Understanding vocabularies... 8 Building custom or editing existing vocabulary files... 9 Understanding Dynamic Dictionary actions... 9 Running Parascript recognition in the background... 9 Adding Parascript Actions, Field Types, properties to your application... 9 Parascript actions reference...12 Parascript recognition actions RecognizeFieldsICR_P SetPostalDBPathICR_P Parascript Dynamic Dictionary actions AddWord DeleteWord ImportCSF Copyright IBM Corp. 1994,

6 LoadFromFile NewDictionary SaveToFile Parascript Field Types reference...18 Parascript recognition properties reference Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

7 Parascript FieldScript for IBM Datacap Taskmaster Capture V8.0.1 Parascript FieldScript for IBM Datacap Taskmaster Capture V8.0.1 allows you to incorporate intelligent character recognition (ICR) in your Datacap Studio applications. Parascript FieldScript supports recognition for English language cursive writing (letters are connected), unconstrained handprint without bounds, handprint with bounds such as comb boxes, and machine typefaces. The recognition engine can use the standard vocabularies (lists of expected values) that are included in the installation package, and it also supports the creation and use of custom vocabularies to increase accuracy. When the United States Postal Service (USPS) database is used, recognition accuracy is enhanced for United States (U.S.) postal addresses that contain a zip code. You must install and configure Parascript FieldScript for IBM Datacap Taskmaster in an environment where Taskmaster Fix Pack 2 or later is running. Once the software is installed, you must set up field zones, incorporate the actions, and fine-tune the recognition properties. The various settings and properties associated with the Parascript FieldScript recognition engine are referred to as Parascript properties or ICR/P properties (intelligent character recognition, Parascript engine) to distinguish them from properties associated with the other recognition engines included with Taskmaster. For links to complete information on installing and configuring the appropriate Taskmaster environment, see the IBM Datacap Taskmaster Capture Version publication library page Preparing for installation Before you begin installing Parascript FieldScript for IBM Datacap Taskmaster Capture, ensure that you have: Parascript FieldScript for IBM Datacap Taskmaster Capture installation media Parascript FieldScript Data Disk (contains USPS database) Administrator access to all computers on which Taskmaster software is installed Taskmaster Fix Pack 2 or later installed and running. At a minimum, ensure one of the sample or foundation applications runs correctly, because this makes troubleshooting easier. To determine if your software is the correct version on all Taskmaster workstations and servers, take the following actions: If you are running: Windows XP or Windows 2003 Windows 7 or Windows 2008 Do this: 1. From the Windows Start menu, select Settings, then Control Panel. 2. Double-click Add or Remove Programs. 3. In the Add or Remove Programs window, scroll down to the IBM Datacap Taskmaster Capture entry. 1. From the Windows Start menu, select Control Panel. Copyright IBM Corp. 1994,

8 2. Double-click Program and Features. 3. In the Uninstall or change a program window, scroll down to the IBM Datacap Taskmaster Capture entry. Downloading Parascript FieldScript for IBM Datacap Taskmaster Capture V8.0.1 See the download documents at the following locations for details on how to access the installation media and separate data disk for Parascript FieldScript for IBM Datacap Taskmaster Capture V8.0.1: Parascript FieldScript for IBM Datacap Taskmaster Capture V8.0.1: Integrating Parascript FieldScript for IBM Datacap Taskmaster Capture V8.0.1 Integrating Parascript FieldScript into your IBM Datacap Taskmaster Capture environment starts with identifying the computers on which Parascript must be installed, performing the installation on those computers, and then planning, developing, testing, and deploying the application. Identifying the computers on which Parascript must be installed In general, Parascript FieldScript must be installed on every computer on which Taskmaster recognition tasks are run, and on every computer that is used by developers who work with Taskmaster applications that include the Parascript actions. Depending on how Taskmaster was set up in your system environment and which Taskmaster software components were installed on which computers, you might have to install Parascript on one or more of the following computers: Developer workstations Workstations on which Taskmaster Client is installed and where operators manually run recognition tasks Servers on which Rulerunner (Datacap Rulerunner Quattro Service) is installed and is set up to run recognition tasks Servers on which Taskmaster Client Service is installed and is set up to run recognition tasks Servers that host the application files for applications that use the Parascript FieldScript recognition engine Identifying and shutting down Taskmaster software Before you install Parascript on any computer in your network, you must shut down all the Taskmaster software on all the computers in your network environment. Prior to this shutdown, it is a best practice to make note of the Taskmaster software that is running on each computer so that you know exactly what to restart after you install Parascript. Once you have your list, shut down the Taskmaster software components in the following sequence: 1. Taskmaster Client software for all applications: Taskmaster Client, Taskmaster DotEdit, Taskmaster DotScan, Datacap Studio, Batch Pilot, Taskmaster Web Client, RV2, Fingerprint Maintenance Tool, Taskmaster Flex Manager, NENU Manager, 4 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

9 Taskmaster Application Manager, Datacap Rulerunner Quattro Service, Rulerunner Quattro Manager, Taskmaster Client Service, Taskmaster Client Service Manager 2. Rulerunner Web Service, Taskmaster Web Client Service, Fingerprint Service, Taskmaster Web 3. Taskmaster Server Service and Taskmaster Server Manager Installing Parascript FieldScript for IBM Datacap Taskmaster Capture V8.0.1 You can place the installation package on any network accessible drive. When you run the Setup.exe file in the installation package, the installation process applies the software to the computer from which you run Setup.exe. The default target installation location is C:\Datacap. When your application is recognizing address information, all of the computers on which the Parascript software is installed need to have access to the contents of the data disk. For detailed information about the database, see Understanding the USPS database. 1. Make the installation package available on your network, or insert the Parascript FieldScript CD into the computer's CD/DVD drive. If the installation process does not start automatically, or if the package is on the network, open Windows Explorer, and navigate to and double-click the Setup.exe file. The Parascript FieldScript for IBM Datacap Taskmaster Capture installation program opens. 2. Answer the prompts. 3. Click Finish to complete the installation process. Planning your application There are a number of concepts and design rules that you must take into consideration when planning your application. Understanding recognition context The Field Types and properties you set up in your application define the context within which the Parascript recognition engine works. Context, when defined precisely, restricts and eliminates incorrect recognition results, limits the number of possible correct results, and increases recognition accuracy. For example, when a character could be a zero (0) or a capital O, if the Field Type is set to Numeric, the incorrect result (capital O) is eliminated as a possibility. Well-defined context can also provide the recognition engine with suggested correct results that increase accuracy. For example, if you incorporate a user database that contains a list of your customer names, the recognition results are always names from that customer list. Understanding Field Types and properties Each Field Type that is supported in Taskmaster has one or more mandatory or optional properties available for use. These properties allow you to define the context for each field at a more granular or specific level. If you do not assign a specific Field Type to a field, the Parascript recognition engine processes the field as if it were assigned the AlphaNumeric Field Type. Using Field Types, you can define contexts such as: Full name Date Amount Copyright IBM Corp. 1994,

10 Year Alphabetic date Using the properties associated with a specific Field Type, for example Full name, you can further define the context: Use a particular Writing Style (cursive, machine print, constrained or unconstrained handprint) Use a particular Full name format (First Middle Initial Last or Last First Middle Initial) Use a database that contains a list of all acceptable Full names For detailed information about all of the Field Types that you can use in Taskmaster applications, see Parascript Field Types reference. For information about the available properties and values, see Parascript recognition properties reference. Understanding writing style Writing Style (cursive, machine print, constrained or unconstrained handprint) is one of the most important properties for setting recognition context, and selecting the appropriate style significantly improves recognition accuracy. When a field can contain a mixture of styles, if there is one style that dominates, set the property to the dominant style. Otherwise, set the style to Unconstrained Handprint (the default value). When a field can contain a mix of alphabetic and numeric characters, set the style based on how the alphabetic characters are written. Understanding dependencies within the application There are a number of dependencies that must be considered when you create your application. Fields must be zoned Mandatory properties must be set When using the USPS database for recognition, address-related fields in the Setup DCO must be set up in a particular sequence Rules must run in a particular sequence Actions within rules must run in a particular sequence Zoning fields All of the data that you want to capture must be in fields that are zoned. If any data is in a field that is not zoned, the recognition engine skips the field and the skipped field is logged in the task log. When using the USPS database and capturing and recognizing U.S. postal addresses, each section of the address must be zoned separately so that Parascript can locate and use the zip code to determine the correct results for street address data. Zone a minimum of two separate address fields: one for the street address, the other for citystate-zip (CSZ). Setting mandatory properties Ensure that you set the mandatory properties for the Field Type. For information about which properties are mandatory for which Field Types, see Parascript Field Types reference. 6 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

11 Sequencing fields in the Setup DCO Parascript requires that recognition results for the city-state-zip (CSZ) field must be captured before it can recognize street addresses because it uses the captured zip code to identify the correct street address data. This requirement means that when you set up the fields for a page on the Document hierarchy pane of Datacap Studio, the CSZ field must precede the Street address field. Sequencing rules in the application In general, to ensure accurate recognition, the following processes need to happen in the application before the application calls the RecognizeFieldsICR_P action. Each of these steps must occur in a separate ruleset: 1. Run a scan task to scan the document. 2. Run the Page ID task, fingerprint matching, or another method to identify the document. 3. Run the CreateFields action to create fields for each document type. 4. Assign zones using the ReadZones action. 5. Invoke the SetPostalDatabasePath action to set the path to the database. When you run this action, you do not have to set the Postal Database Path property at the field level. 6. Run the RecognizeFieldsICR_P action. Size of recognition zones The defined zone for a field must be drawn around the entire area where the text can be found in the image. If the zone is too small, the recognition results are not accurate. Setting up checkboxes Parascript recognizes checkboxes when each checkbox is set up as an individual field. On the page in the Document Hierarchy, create the checkbox field as a field, not a subfield. Draw the zone for this field around the single checkbox that is to be recognized. Set the Field Type to Checkbox and set the Ink Drop-out property. Performing image preprocessing Parascript recognizes data on clean images. For best results, your application must remove lines, boxes, combs, smudges, and other noise from the images before it runs the recognition process. Identifying the correct format of input images Parascript recognizes data found on black and white TIFF files. If your input images are not black and white, or the TIFF format is not listed below, your application must convert them to an appropriate format before sending them to the recognition engine. The following are the TIFF input formats that Parascript can process: 1. LZW compression 2. Uncompressed 3. PackBits compression (Macintosh) 4. CCITT Group 3 (lossless) Fax Encoding 5. CCITT Group 4 (lossless) Fax Encoding Understanding the USPS database If you want your application to capture fields that contain U.S. city, state, and zip, or fields that contain street, apartment number, or post office box (PO box) address Copyright IBM Corp. 1994,

12 information, use Field Types of CSZ (City State Zip) or Street address, and the Postal Database Path property. Recognition results are validated against the Parascript database for maximum accuracy. If an address contains an error, such as a misspelled street or city, Parascript automatically corrects the results to match the name appearing in the USPS database. Parascript uses a proprietary version of the USPS database that contains comprehensive U.S. address information. This address information is contained on the data disk that is separate from the Parascript software installation package. The content of the database is refreshed by the USPS periodically and IBM makes the new data available on a regular basis. In accordance with USPS rules, each database is automatically disabled 105 days after the date of issue. Seventy days after the issue date, Parascript writes a warning to the recognition task logs indicating the database will expire. You must ensure you obtain the refreshed data on a regular schedule so that you avoid all issues associated with a disabled database. Deciding the location of the USPS database The database must be in a location that is accessible as read-only to every computer on which Parascript recognition tasks are run, and every computer that is used by developers who work with Taskmaster applications that include the Parascript actions. In addition, every user or service account that runs Parascript recognition tasks must have read-only permissions to the database. These accounts include developers, end users who run recognition tasks manually, as well as Taskmaster Client Service and Datacap Rulerunner Quattro Service accounts. Viewing the contents of the USPS database You can use the Postal Database Viewer tool (C:\Datacap\dcshared\ICRP\AdbManager.exe) to view the contents of the database. Information about the Postal Database Viewer tool can be found in the PostalDatabaseViewer.pdf file that is located in the same folder. Incorporating an end user database When recognizing Full name or Reverse full name Field Types, Parascript can access a custom database that contains all of the correct names. This user database must be a Microsoft Access 97 database and must contain a single table that contains only three columns. The first column must contain first names, the second column must contain middle initials, and the third column must contain last names. The names of the database, table, and columns can be anything you want. The custom database must be in a location that is accessible as read-only to every computer on which Parascript recognition tasks are run and every computer that is used by developers who work with Taskmaster applications that include the Parascript actions. In addition, every user or service account that runs Parascript recognition tasks must have read-only permissions to the custom database. These accounts include developers, end users who run recognition tasks manually, as well as Taskmaster Client Service and Datacap Rulerunner Quattro Service accounts. Understanding vocabularies During recognition, the Parascript engine can use a vocabulary that contains all of the probable values that can be found in the field. Using a vocabulary file can significantly improve recognition accuracy. Vocabulary files are in a Parascript proprietary format that has a.voc extension. These files are also referred to as dictionaries in the embedded action help text. 8 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

13 It is a best practice to use vocabularies whenever possible and for almost all Field Types, you must include all of the words that are reasonable recognition results. When Field Type is set to Alpha, the vocabulary automatically defaults to english.voc. When Field Type is set to Alpha, the words in the vocabulary file are assumed to contain 60% of the words that can appear and the recognition engine can produce a result that is not present in the vocabulary. While a number of vocabulary (.VOC) files are included with the Parascript software, these vocabularies are not automatically associated with the relevant Field Types. When the path to a vocabulary file is provided as a property, the words in the vocabulary file are assumed to contain 100% of the words that can appear and the recognition result is one of the entries in the vocabulary. The recognition engine also uses the vocabulary to normalize the recognition results. For example, if a month name is spelled out on an input image and the field is associated with the included vocabulary that contains the names of months, the recognized results are returned as the standard three or four letter abbreviation for that month. Building custom or editing existing vocabulary files You can use the Vocabulary Manager tool (C:\Datacap\dcshared\ICRP\VocMan.exe) to edit the default vocabularies or to create your own. The first time you start VocMan.exe, right-click and run as Administrator. Subsequent use does not require running as administrator. Information about the Vocabulary Manager tool can be found in the VocabularyManager.pdf file that is located in the same folder. Understanding Dynamic Dictionary actions While Parascript provides standard vocabulary files, and the Vocabulary Manager tool provides you with the ability to create custom vocabulary files, Taskmaster also provides Dynamic Dictionary actions that allow you to create, populate, change, and save vocabulary files while your application is running. Dynamic Dictionary actions manipulate a Parascript vocabulary object that exists in memory until you use the SaveToFile action to write the results to a.voc file on disk. The recognition process does not use the vocabulary object in memory and can only use the contents of.voc files. Each user or service account that runs Parascript recognition tasks that include these Dynamic Dictionary actions must have read-write permissions to the locations where these vocabularies are located. For more information about these dictionary actions, see Parascript actions reference. Running Parascript recognition in the background Taskmaster recognition tasks do not require user intervention and are usually run by automatic processes as background tasks. The Parascript actions are not thread-safe. To run Parascript recognition tasks using Datacap Rulerunner Quattro, configure Rulerunner Quattro to run Parascript recognition tasks on a single thread on each computer or VM. You can configure Taskmaster Client Service to run Parascript recognition tasks. Adding Parascript Actions, Field Types, properties to your application Every Taskmaster application is unique, but you follow the same general procedure for incorporating the Parascript recognition capabilities into an existing application. Before you begin your application development: Copyright IBM Corp. 1994,

14 For information on developing Taskmaster applications, see the Application Development using IBM Datacap Taskmaster Capture document that is available on the IBM Datacap Taskmaster Capture Publications Center: business/linkweb/publications/servlet/pbi.wss?cty=us&fnc=srx&pbl=sc For an explanation of the available actions, see Parascript actions reference. For an explanation of the available Field Types, see Parascript Field Types reference. For an explanation of the available recognition properties, see Parascript recognition properties reference. In general, once the Parascript software is installed and, optionally, the USPS database is available, the high-level steps to incorporate Parascript into your application are: 1. Ensure that Taskmaster Server Service is started. 2. Ensure that your application has been added to the datacap.xml file. 3. Using the Taskmaster Application Manager, ensure that the settings for your application appear correctly. 4. Start up Datacap Studio and open your application. 5. Ensure that all fields are zoned. 6. On the Rulemanager > Actions Library tab, in the Global Actions section, scroll down, and ensure the icr_p library is listed. If it is not listed, Parascript is not installed properly or is not installed on the correct computer. Follow the installation instructions to install Parascript on the correct computers before you continue. 7. On the Rulemanager > Rulesets tab, make changes to or replace the rulesets that contain the actions that set up fields and run recognition. For information about how the application must be constructed, see Understanding dependencies within the application. 8. Click the Sync DCO view with Ruleset view button to expand the Document Hierarchy and ensure that each ruleset is bound to the correct field, page, document, or batch object or objects. 9. Click Save to save the changes to the ruleset. 10. Click the Zones tab to display it. 11. To display the ICR/P properties tab, right-click on the Properties tab, and on the Show tabs menu, select ICR/P. The tab is added to the tabs at the bottom of the Properties tab. 12. Click the ICR/P tab to display it. 13. On the Document Hierarchy tab, click the Lock DCO for editing button. 14. Select the first field that you want Parascript to recognize. 15. On the ICR/P tab, select the appropriate Field Type and properties for the field. 16. Repeat the previous two steps for each field that you want Parascript to recognize. 17. On the Document Hierarchy tab, click Save Changes and click the Unlock DCO button. 18. Test your changes. 10 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

15 19. When the application is ready, on the Rulemanager > Rulesets tab, click Publish ruleset. Copyright IBM Corp. 1994,

16 Parascript actions reference Parascript FieldScript contains a number of actions that can be categorized into two types: Recognition actions Dynamic Dictionary (vocabulary) actions. Parascript FieldScript contains a number of actions that can be categorized into two types: Recognition actions Dynamic Dictionary (vocabulary) actions Parascript recognition actions RecognizeFieldsICR_P The Parascript recognition engine recognizes the contents of the zoned fields that were configured for recognition. Performs recognition on all of the zoned fields and saves the recognition results automatically. Member of namespace: icr_p Syntax: bool RecognizeFieldsICR_P () Parameters: None. Returns: False if the rule containing this action is not applied to a Batch, Document, Page, or Field, or if the specified Parascript recognition engine is unavailable. Otherwise, True. Level: Batch, Document, Page, or Field level. If the action is set at a level above the Field level, Parascript recognizes all underlying Fields contained in the object. Details: The action can be part of a rule that is bound to a Batch, Document, Page, or Field object of the Document Hierarchy. Parascript FieldScript supports recognition for English language cursive writing (letters are connected), unconstrained handprint without bounds, handprint with bounds such as comb boxes, and machine typefaces. The recognition engine can use the standard vocabularies that are included in the installation package, and it also supports the creation and use of custom vocabularies to increase accuracy. When the United States Postal Service (USPS) database is used, recognition accuracy is enhanced for United States (U.S.) postal addresses that contain a zip code. This action uses the recognition properties you set up in Datacap Studio on zoned fields. Open your application in Datacap Studio, click the Zones tab, lock the Document Hierarchy, and click the ICR/P Properties tab to display the properties. For each zoned field, set the Field Type, then select the properties appropriate to that Field Type and the data you expect in the field. In general, to ensure that city, state, zip, and street addresses are properly recognized, the following processes need to happen in the application before the application calls the RecognizeFieldsICR_P action. Each of these steps must occur in a separate ruleset: 12 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

17 1. Run a scan task to scan the document. 2. Run the Page ID task, fingerprint matching, or another method to identify the document. 3. Run the CreateFields action to create fields for each document type. 4. Assign zones using the ReadZones action. 5. If U.S. postal addresses are captured, invoke the SetPostalDatabasePath action at the Page or higher level to set the path to the database. When you run this action, you do not have to set the Postal Database Path property at the field level. 6. Run the RecognizeFieldsICR_P action. Example: SetPostalDBPathICR_P(\\ServerName\ParentDir\icrp\PostalDB) RecognizeFieldsICR_P() SetPostalDBPathICR_P Provides the UNC or local path to the folder containing the Parascript USPS database. Smart parameters are supported. Member of namespace: icr_p Syntax: bool SetPostalDBPathICR_P (StrParam) Parameters: Path to the folder containing the USPS database. Returns: False if the rule containing this action is not applied to a Batch, Document, Page or a Field, or if the specified Parascript recognition engine is unavailable. Otherwise, True. Level: All, but generally used at the Batch level. Details: Sets the path to the folder containing the USPS database used during Parascript (ICR/P) recognition. If you use this action to set the path to the database at the Page or higher level, you do not have to set the Postal Database Path property for each field in Datacap Studio. Example: SetPostalDBPathICR_P(\\ServerName\ParentDir\icrp\PostalDB\) RecognizeFieldsICR_P() Parascript Dynamic Dictionary actions AddWord Adds a word to the vocabulary object in memory. Member of namespace: icr_p Syntax: bool AddWord (StrParam) Copyright IBM Corp. 1994,

18 Parameters: Two parameters to add a set of characters (word), and a weight (or priority value). Smart parameters are supported. 1. The word to add to the vocabulary file. 2. The weight or priority value of the word. Valid values are Returns: False if the word cannot be added to the vocabulary. Can occur when the vocabulary object does not exist. Otherwise, True. Level: Page or Document level. Details: Adds a word to the vocabulary object currently in memory. When either the LoadFromFile or ImportCSF action precedes the AddWord action, the vocabulary object in memory contains words and the AddWord action adds the word to the existing words. When the NewDictionary action precedes the AddWord action, the vocabulary object in memory is empty and the AddWord action adds the word to the empty vocabulary. After you have used AddWord to change the vocabulary object in memory, use the SaveToFile action to save the altered vocabulary object to disk. Example: LoadFromFile(\\ServerName\ParentDir\testvoc.voc) AddWord(ExampleWord,8) SaveToFile(\\ServerName\ParentDir\testvoc.voc) DeleteWord Removes a word from the vocabulary object in memory. Member of namespace: icr_p Syntax: bool DeleteWord (StrParam) Parameters: One parameter that contains the set of characters (word) to be removed from the vocabulary file. Smart parameters are supported. Returns: False if the word cannot be removed from the vocabulary. Can occur when the word or vocabulary object does not exist. Otherwise, True. Level: Page or Document level. Details: Removes a word from the vocabulary object currently in memory. When either the LoadFromFile or ImportCSF action precedes the DeleteWord action, the vocabulary object in memory contains words and the DeleteWord action removes the word from the existing words. After you have used DeleteWord to change the vocabulary object in memory, use the SaveToFile action to save the altered vocabulary object to disk. 14 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

19 Example: LoadFromFile(\\ServerName\ParentDir\testvoc.voc) DeleteWord(ExampleWord) SaveToFile(\\ServerName\ParentDir\testvoc.voc) ImportCSF Imports data from a comma separated text file into the vocabulary object in memory. Member of namespace: icr_p Syntax: bool ImportCSF (StrParam) Parameters: Provides the UNC or local path and file name of the comma separated file to import. Smart parameters are supported. Returns: False if the Parascript object does not exist or the comma separated file is not in the correct format. Otherwise, True. Level: Page or Document level. Details: Imports data from a comma separated file into the vocabulary object in memory. The comma separated file must contain text in the following format: word, priority_value where: word is the word to be added to the vocabulary priority_value (or weight) is a value ranging from Example: NewDictionary ImportCSF(\\ServerName\ParentDir\testtable.csv) SaveToFile(\\ServerName\ParentDir\testtable.voc) LoadFromFile Loads the contents of an existing vocabulary (.VOC) file into the vocabulary object in memory. Member of namespace: icr_p Syntax: bool LoadFromFile (StrParam) Parameters: Provides the UNC or local path and file name of the vocabulary file to load. Returns: False if cannot create the object. Returns false when the vocabulary file has an invalid format or cannot be read. Otherwise, True. Level: Page or Document level. Copyright IBM Corp. 1994,

20 Details: Loads the contents of an existing vocabulary (.VOC) file into the vocabulary object in memory. If the vocabulary object does not exist, this action creates a new one in memory. Example: LoadFromFile(\\ServerName\ParentDir\testvoc.voc) SaveToFile(\\ServerName\ParentDir\testvoctable.voc) NewDictionary When a vocabulary object exists in memory, the NewDictionary action clears it and creates a new, empty Parascript vocabulary object in memory. When a vocabulary object does not exist in memory, the NewDictionary action creates a new, empty vocabulary object. Member of namespace: icr_p Syntax: bool NewDictionary () Parameters: None. Returns: False if the object cannot be created. Otherwise, True. Level: Page or Document level. Details: Creates a new Parascript vocabulary object. Use to clear memory and create a new vocabulary object. Example: NewDictionary() AddWord(ExampleWord,8) SaveToFile(\\ServerName\ParentDir\testvoc.voc) SaveToFile Saves the current Parascript vocabulary object as it exists in memory to a.voc file so that the recognition engine can use it. Member of namespace: icr_p Syntax: bool SaveToFile (StrParam) Parameters: Provides the UNC or local path and file name of the file to which to save the vocabulary object. Returns: False if cannot save the file as specified or if the Parascript vocabulary object does not exist. Otherwise, True. 16 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

21 Level: Page or Document level. Details: Saves the Parascript vocabulary object as it currently exists in memory to disk. If a file with the same name already exists, it is overwritten. If the file does not exist, a new file is created. Example: AddWord(ExampleWord,8) SaveToFile(\\ServerName\ParentDir\testvoc.voc) Copyright IBM Corp. 1994,

22 Parascript Field Types reference The following table contains information about the Field Types that are available for use in a Taskmaster Capture application. IMPORTANT: If you have Parascript FieldScript installed in an IBM Datacap Taskmaster Capture Fix Pack 2 environment, the following explanations contain more accurate and complete information than the text displayed in the Datacap Studio embedded assistance pane on the Properties tab. If you have Parascript FieldScript installed in a Fix Pack 3 or later environment, the Datacap Studio embedded assistance pane on the Properties tab will contain updated information that is more similar to the following explanations. When you create your application, you assign a Field Type to each zoned field, and you select the properties that are appropriate for that Field Type. The combination of Field Type and properties provides the recognition engine with context and distinctive clues that help the engine correctly recognize the data. For information about the available properties and values, see Parascript recognition properties reference. Field Type Age Alpha Definition Supported values Properties Describes a field that contains age data. This Field Type supports a numeric value such as "37" or an alphanumeric string such as "14 years old." Describes a field that contains alphabetic characters. Day, Days, Dys Mo, Month, Months, Mos, Mths, Mth, Month Old, Months Old, Mos Old, Mths Old Week, Weeks, Wk, Wks Year, Years, Years Old, Yr, Yrs, Yrs Old The supported character set includes the letters A to Z (uppercase, lowercase, or mixed case) and the following additional characters: space ' apostrophe - dash, comma. period / slash # pound sign + plus $ dollar sign ( ) parentheses * asterisk " " quotation marks Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary Optional Properties: Character Style, Min/Max Length, Favor Accuracy or Speed, Special Character Set, Template, Vocabulary 18 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

23 Field Type Definition Supported values Properties Alpha Numeric Describes a field that contains a combination of alphabetic and numeric characters. This Field Type combines the attributes of an Alpha Field Type and a Numeric Field Type. Optional Properties: Character Style, Min/Max Length, Favor Accuracy or Speed, Special Character Set, Template, Vocabulary Amount Describes a field that contains a monetary amount. Parascript FieldScript recognizes amounts up to $100, and rejects amounts exceeding $100, The supported character set includes numeric characters and the following additional characters: space, comma. period $ dollar sign Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary Checkbox Describes a field that contains a marked or unmarked check box. Parascript FieldScript accommodates a wide variety of checkbox styles and marks. Ink Dropout can be set to: ON: Indicates ink was removed by the scanner. OFF: Indicates ink was not removed by the scanner. CSZ (City State Zip) Describes City, State, and ZIP code information that occurs in a single field or a series of fields. The ZIP code must consist of at least five digits. Mandatory Property: Postal Database Optional Property: Character Style Recognition results will contain five digits. Copyright IBM Corp. 1994,

24 Field Type Definition Supported values Properties Date alpha Describes a date in which month is indicated by letters or numbers. Permissible year values are The Parascript FieldScript recognition answer is normalized to the format Month DD, YYYY, where Month is the standard three- or fourletter abbreviation of the name of the month. For the best recognition of numeric month data in a date field, use the Date Numeric Field Type. When a two-digit year is processed, if the digits are lower than the Year Threshold (NN), the year is interpreted as 21st century (20NN). If the two digits are higher or equal to the threshold, the year is interpreted as 20th century (19NN). Month DD YY Month DD YYYY MM DD YY MM DD YYYY Optional Properties: Blank Delimited Character Style, Date Format, Favor Accuracy or Speed Date numeric Describes a field that contains a date in numeric format. Permissible year values are The Parascript FieldScript recognition answer takes one of these forms: When the Date Format property is set to American: MM/DD/YYYY or MM/DD/YY When the Date Format property is set to European: DD/MM/YYYY or DD/MM/YY Mandatory Property: Date Format Optional Properties: Character Style, Date Format, Favor Accuracy or Speed Day Describes a field that contains a numeric day value (DD). Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary 20 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

25 Field Type Definition Supported values Properties First name Describes a field that contains a person's first name. The supported character set includes alphabetic characters and the following additional characters: Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary space - dash. period ' apostrophe Full name Describes a field that contains a person's full name in one of two formats. The supported character set includes alphabetic characters and the following additional characters: space - dash. period ' apostrophe Optional Properties: Character Style, Favor Accuracy or Speed, User Database The Full name Field Type also supports abbreviations such as Mr., Mrs., Jr., and Sr. The supported formats are: [First Name] [Middle Initial] [Last Name] [Last Name] [Middle Initial] [First Name] Copyright IBM Corp. 1994,

26 Field Type Definition Supported values Properties Reverse full name Describes a field that contains a person's full name in various formats. The Reverse Full Name Field Type can be used only with the Machine Print Character Style property. The supported character set includes alphabetic characters and the following additional characters: space - dash, comma. period ' apostrophe Mandatory Property: Character Style must be set to Machine Print. Optional Properties: Favor Accuracy or Speed, User Database The Reverse Full Name Field Type also supports abbreviations such as Mr., Mrs., Jr., and Sr. The supported formats are: [Last Name], [First Name] [Middle Initial] [Last Name] [First Name] [Middle Initial] [Last Name], [First Name] [Last Name] [First Name] Last name Describes a field that contains a person's last name. The supported character set includes alphabetic characters and the following additional characters: Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary space - dash. period ' apostrophe 22 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

27 Field Type Definition Supported values Properties Length Describes a field that contains a length measurement expressed in feet, inches, or both. The field zone must not include alphabetic characters. The supported character set includes numeric and the following additional characters: - dash ' apostrophe " quotation marks Mandatory Property: Vocabulary Optional Properties: Character Style, Favor Accuracy or Speed Typical supported formats include: NN' - NN" NN' NN" NN NN NN-NN NN' NN" Measure Describes a field that contains a numeric value and an abbreviation, such as "115 lbs." The supported character set includes letters and numbers and the following additional characters:. period # pound sign The measurement unit (lbs., oz., kg., mm., etc.) must not exceed four characters. Mandatory Property: Vocabulary Optional Properties: Character Style, Favor Accuracy or Speed Middle initial Describes a field that contains a person's middle initial. The supported character set includes alphabetic and the following additional characters: Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary - dash. period Month Describes a field that contains month data expressed as numbers or letters. This Field Type works best with numeric month data. If a set of images contains alphabetic month data, such as "November" instead of "11", you should use the Field Type AlphaNumeric and a custom vocabulary. Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary Copyright IBM Corp. 1994,

28 Field Type Definition Supported values Properties Numeric Describes a field that contains numbers. The supported character set includes the numerals 0-9 and the following additional characters: space ' apostrophe - dash, comma. period / slash # pound sign + plus $ dollar sign ( ) parentheses * asterisk " " quotation marks Optional Properties: Character Style, Min/Max Length, Special Character Set, Favor Accuracy or Speed, Template, Min/Max Value, Vocabulary Phone Describes a field that contains a U.S. area code, a telephone number, or both. Area Code Local Phone Full Phone Optional Properties: Blank Delimited, Character Style, Phone Format, Favor Accuracy or Speed, Vocabulary Social security number Describes a field that contains a U.S. social security number. The supported character set includes the numerals 0-9 and the following additional characters: Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary space - dash. period / slash 24 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

29 Field Type Definition Supported values Properties Street address Describes one or more fields that contain address information. The address information can include a street number, a street name, an apartment or suite number, or a PO Box. Typical supported formats for the Street Address include: A complete address in a single field A street address in one field and an apartment or suite number in another A street number in one field, a street name in another, and an apartment or suite number in another Mandatory Property: Postal Database Optional Property: Character Style Year Describes a field that contains year data. The possible character set includes the numerals 0-9 and an apostrophe ( ). Possible year values are Use for fields that contain a numeric year such as: YY YYYY 'YY Optional Properties: Character Style, Favor Accuracy or Speed, Vocabulary Empty Describes a field that does not contain data. Use this Field Type for fields that are typically empty or when it is important to identify fields that are empty when they are expected to contain data. Copyright IBM Corp. 1994,

30 Parascript recognition properties reference The following properties and values are available for use with Parascript FieldScript in an IBM Datacap Taskmaster Capture environment. IMPORTANT: If you have Parascript FieldScript installed in an IBM Datacap Taskmaster Capture Fix Pack 2 environment, the following explanations contain more accurate and complete information than the text displayed in the Datacap Studio embedded assistance pane on the Properties tab. If you have Parascript FieldScript installed in a Fix Pack 3 or later environment, the Datacap Studio embedded assistance pane on the Properties tab will contain updated information that is more similar to the following explanations. Property Name Description Available values Address Type Alias Blank Delimited Date Format Specifies the type of address that is expected in the field. This property is optional when Field Type is set to Street address. By default, the recognition engine detects the Address Type automatically. NSA: Numbered street address P.O. Box: Post office box RR: Rural route All: All of the above Reserved for future use. Determines whether blanks are used as delimiters. This property is optional when Field Type is set to Phone, Date alpha, or Date numeric. Specifies the date format to use during recognition. The default value of this property is American. When Field Type is set to Date numeric, the following date formats are recognized: American: MM/DD/YYYY or MM/DD/YY European: DD/MM/YYYY or DD/MM/YY When Field Type is set to Date alpha, the recognition engine only recognizes these American date formats: Month DD YY Month DD YYYY MM DD YY MM DD YYYY The permissible values for Year include 1900 to Month is the standard three or four letter abbreviation of the month name. If Year is two digits (YY), the recognition engine uses the Year Threshold property to determine the century. NSA P.O. Box NSA and P.O. Box RR NSA and RR P.O. Box and RR All ON: Blanks are used as delimiters. OFF: Blanks are not used as delimiters. American European 26 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide

31 Property Name Description Available values Date Preference Ink Dropout Field Type Full Name Format Maximum Length Maximum Value Reserved for future use. Indicates whether the border of a checkbox that is printed in dropout ink was removed from the image. This property is optional when Field Type is set to Checkbox. The default value is OFF. Defines the type of data that is expected in the field. The Field Type that you select provides the recognition engine with a context that affects the recognition results. Defines the sequence in which First name, Middle initial, and Last name are expected. This property is required when Field Type is set to Full name. Specifies the maximum number of characters that are allowed in a field. This property is optional when Field Type is set to Alpha, AlphaNumeric, or Numeric. Use in non-vocabulary mode. The default value is 0 (no limit). Specifies the maximum value that is allowed in a numeric field. This property is optional when Field Type is set to Numeric. Use in non-vocabulary mode. The default value is 0 (no limit). ON: Dropout ink was dropped by the scanner. OFF: Dropout ink was not dropped by the scanner. Age Alpha AlphaNumeric Amount Checkbox CSZ Date alpha Date numeric Day Empty First name Full name Last name Length Measure Middle initial Month Numeric Phone Reverse full name Social security number Street address Year First_MI_Last Last_First_MI Copyright IBM Corp. 1994,

32 Property Name Description Available values Minimum Length Minimum Value PhoneFormat Postal Database Path Specifies the minimum number of characters that are allowed in a field. This property is optional when Field Type is set to Alpha, AlphaNumeric, or Numeric. Use in non-vocabulary mode. The default value is 0 (no minimum length). Specifies the minimum value that is allowed in a numeric field. This property is optional when Field Type is set to Numeric. Use in non-vocabulary mode. The default value is 0 (no minimum value). Defines the format of the U.S. telephone number that is expected in the field. This property is optional when Field Type is set to Phone. The default value is Not BlankDelimited. Area Code: Three digit area code, for example 888. Local Phone: Seven digit phone number with hyphen, for example Full Phone: Area code followed by seven digit phone number with hyphen, for example (888) or Provides the UNC path to the folder that contains the Parascript FieldScript USPS database. This property is required when Field Type is set to CSZ or Street Address. No default value is provided. If you use the SetPostalDBPathICR_P action prior to the RecognizeFieldsICR_P action to set this path at the Page or higher level, you do not have to set this property at the Field level. To comply with USPS rules, each version of the database expires 105 days after it is issued. Database versions that are more than 105 days old are not authorized for further use and are disabled. Parascript FieldScript logs a warning 70 days after the database release date that indicates that the database can be used for another 35 days. Area Code Local Phone Full Phone 28 Parascript FieldScript for IBM Datacap Taskmaster Capture Guide