User manual BUSINESS OBJECTS DATA SERVICES 3.0 REFERENCE GUIDE

[. . . ] Data Services Reference Guide BusinessObjects Data Services XI 3. 0 (12. 0. 0) Copyright © 2008 Business Objects. patents, which may cover products that are offered and licensed by Business Objects: 5, 555, 403; 5, 857, 205; 6, 289, 352; 6, 247, 008; 6, 490, 593; 6, 578, 027; 6, 831, 668; 6, 768, 986; 6, 772, 409; 6, 882, 998; 7, 139, 766; 7, 299, 419; 7, 194, 465; 7, 222, 130; 7, 181, 440 and 7, 181, 435. Business Objects and the Business Objects logo, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Desktop Intelligence, Inxight, the Inxight Logo, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let there be light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. All other names mentioned herein may be trademarks of their respective owners. [. . . ] Both fields blank operation Ignore: This criteria is ignored in the comparison process, and its contribution to the weighted score is proportionally distributed among the remaining criteria, therefore negating any impact the contribution score may have had. Specifies the similarity score if both of the fields are blank and Both fields blank operation is set to Eval. Type a value from 1 to 100, depending on the matching method you use. Both fields blank score 546 Data Services Reference Guide Transforms Descriptions of transforms 5 Option Description Specifies whether the match score should be adjusted for any transposed characters encountered. Yes: The transform deducts half as many points for transposed characters as it deducts for other non-matching characters. For example: Comparison: Smith--Simth Check for transposed characters Finding: characters 2 and 3 are transposed Percentage alike: 90% No: The transform handles transposed characters the same way it handles any non-matching characters. For example: Comparison: Smith--Simth Finding: characters 2 and 3 are transposed Percentage alike: 80% Data Services Reference Guide 547 5 Transforms Descriptions of transforms Option Description Specifies how to handle fields where more than one word commonly exists. Field: If you choose Field, the transform compares the entire field's data as a single string. This algorithm is more efficient and should be used in fields that typically have just one word, like a first name field. Compare algorithm Word: If you choose Word, the transform first parses the data into words and then compares the words. This algorithm is less efficient than the Field algorithm, but will do a better job comparing data that typically has more than one word in it, such as firm data. Specifies the contribution value, when you use the weighted or the combination scoring method. Contribution to weighted score If no single criteria decides a match or nomatch, the contribution score is calculated by multiplying the similarity score by the contribution value. Type a value between 0 and 100. 548 Data Services Reference Guide Transforms Descriptions of transforms 5 Option Description Specifies whether to include diacritical characters in the matching process. Be aware of the following: · · This option is valid for all match engine options. If you are processing Japanese data, for example, you may have some Latin1 data mixed in. In these cases you will be able to convert diacritical characters. Yes: Converts diacritical characters to the Convert diacritical characclosest English ASCII equivalent for matching ters purposes. No: Preserves diacritical characters in the matching process, treating ä and a as not identical characters. Note: This option works on the mapped input field used in this and other criteria. If you set this option to something different than how it is set in another criteria using this same field, it will override that setting. Before setting this option, be sure that there are no other criteria using this same field. Data Services Reference Guide 549 5 Transforms Descriptions of transforms Option Description Specifies whether numbers represented as text (one, two, three) should be converted to numbers. If you choose Yes, they will be in cardinal (one > 1) or ordinal (first > 1st) format. Be aware that this option is valid for all match engines except the Other_Non_Latin1 engine. No: Leaves any numerical text intact. Note: This option works on the mapped input field used in this and other criteria. [. . . ] It is required only at the end of rule definition and at the end of each action line. : Colon ; Semicolon Related Topics · Designer Guide: Data Cleanse, classifications Action section of a parsing rule After you define the components that the Data Cleanse transform should look for when parsing, you must tell the application what to do with it when it finds a match for that rule. In other words, you must tell the Data Cleanse transform what action it needs to perform. These actions are performed both for the main parsed item and the subcomponents that make up the main item. The example and table below explain the pieces that make up the action section of a parsing rule. options = begin: end; action = PERSON : D; PERSON = 1 : PRENAME PERSON = 1 : FAMILY_NAME1 PERSON = 1 : NAME_CONNECTOR PERSON = 2 : PRENAME PERSON = 2 : GIVEN_NAME1 PERSON = 2 : GIVEN_NAME2 PERSON = 2 : FAMILY_NAME1 end_action : : : : : : : 1; 2; 3; 4; 5; 6; 7; 1198 Data Services Reference Guide Data Quality Appendix Data Cleanse reference 13 Component Description and example Options line Specifies your parsing preferences. [. . . ]