Bookshelf Home | Contents | Index | PDF |
Siebel Data Quality Administration Guide > Data Quality Concepts > Identification of Candidate RecordsThe way in which candidate records are identified differs for the Oracle Data Quality Matching Server and the Universal Connector as described in the following topics. Identification of Candidate Records with the Oracle Data Quality Matching ServerWhen using the Oracle Data Quality Matching Server for data matching, identification of candidate records is irrelevant as match candidate acquisition takes place within the Oracle Data Quality Matching Server. Identification of Candidate Records with the Universal ConnectorData quality queries the database for candidate records by using a Dedup Query Expression parameter specific to the current Business Component. A Dedup Query Expression is used rather than the related Dedup Token Expression, for the following reason: If a user does not specify a value for any of the fields that compose the Dedup Token Expression, then the token is constructed with an underscore (_) instead of a value in the part of the expression that corresponds to that field. If the token were to be used in a query, the effect would be for the query to seek records that had NULL values in corresponding fields. In contrast, the Dedup Query Expression replaces each underscore in the Dedup Token Expression with a '?' wildcard character that matches any single character, leading to the desired query results. You can customize both the Dedup Token Expression and the Dedup Query Expression parameters through the Third Party Administration view. The configuration of these expressions must be consistent with the internal matching logic of the vendor, which is different for each vendor. For optimal results therefore, change these values only after consulting the relevant vendor. If you change the expressions, you must regenerate match keys. See Table 1 for examples about how the default expressions can differ for different business components. The maximum number of candidate records that are sent to the third-party software at one time is determined by the value of the following vendor parameters in the Third Party Administration view:
NOTE: Information in this topic does not apply if using the Oracle Data Quality Matching Server for data matching as match candidate acquisition takes place within the Oracle Data Quality Matching Server. |
Siebel Data Quality Administration Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |