Hebrew Definitions

The Field Name (v23) identification analysis definition is now deprecated and will be removed in a future release of the QKB.

The Field Name identification analysis definition has been replaced with a copy of the Field Name (v23) definition which takes advantage of updated processing. If you changed your jobs to use the Field Name (v23) definition it is suggested that you change them back.

The Field Name (v23) identification analysis definition is now deprecated and will be removed in a future release of the QKB.

The Field Name identification analysis definition has been replaced with a copy of the Field Name (v23) definition which takes advantage of updated processing. If you changed your jobs to use the Field Name (v23) definition it is suggested that you change them back.

Note: The results listed above reflect the default match sensitivity (85).

A date with DMY format will match with the date with MDY format.

This definition generates one or more match codes for each input string. The number of match codes generated for an input string depends on the content of the string. Each match code represents a combination of different parts of the input string; this enables two strings to be matched even when some parts of one or both of the strings differ. See the examples above for an illustration of clusters that can be produced using match codes generated by this definition.

Note that a consequence of generating multiple match codes is that a record can be placed in more than one cluster by a subsequent clustering operation. Therefore, special attention should be given to the entity resolution process when using this definition.

Generation of multiple match codes is achieved through the use of token-combination rules in the match definition. Each match code generated by the definition is associated with one token-combination rule. There is a weight assigned to each rule; each rule's weight is used to calculate a score that is assigned to the match code that is generated by that rule. The score for a match code is equal to the weight of the rule used to generate the match code times the sensitivity that is selected when the definition is executed.

When a record is clustered, the score for the record’s match code represents the confidence with which we can assert that the record belongs in the cluster. Note that when different rules lead to identical clustering results, the scores of the match codes generated by the different rules can be aggregated using the Cluster Aggregation node in a Data Job. The Cluster Aggregation node allows several different methods for aggregating match code scores, such as minimum, maximum, or mean across instances of a record, or minimum, maximum, or mean across all records in a cluster. For information on the Cluster Aggregation node, refer to the documentation provided with the DataFlux Data Management Studio installation.

Note: The results listed above reflect the default match sensitivity (85).

A date with MDY format will match with the date with DMY format.

This definition generates one or more match codes for each input string. The number of match codes generated for an input string depends on the content of the string. Each match code represents a combination of different parts of the input string; this enables two strings to be matched even when some parts of one or both of the strings differ. See the examples above for an illustration of clusters that may be produced using match codes generated by this definition.

Note that a consequence of generating multiple match codes is that a record can be placed in more than one cluster by a subsequent clustering operation. Therefore, special attention should be given to the entity resolution process when using this definition.

Generation of multiple match codes is achieved through the use of token-combination rules in the match definition. Each match code generated by the definition is associated with one token-combination rule. There is a weight assigned to each rule; each rule's weight is used to calculate a score that is assigned to the match code that is generated by that rule. The score for a match code is equal to the weight of the rule used to generate the match code times the sensitivity that is selected when the definition is executed.

When a record is clustered, the score for the record’s match code represents the confidence with which we can assert that the record belongs in the cluster. Note that when different rules lead to identical clustering results, the scores of the match codes generated by the different rules can be aggregated using the Cluster Aggregation node in a Data Job. The Cluster Aggregation node allows several different methods for aggregating match code scores, such as minimum, maximum, or mean across instances of a record, or minimum, maximum, or mean across all records in a cluster. For information on the Cluster Aggregation node, refer to the documentation provided with the DataFlux Data Management Studio installation.

Note: The results listed above reflect the default match sensitivity (85).

Note: The results listed above reflect the default match sensitivity (85).

Parse definitions named with the Global keyword use a set of output tokens that is consistent across every locale. Results obtained from these definitions can be stored in the same database fields as the results obtained from definitions of the same name in other locales.

Parse definitions named with the Global keyword use a set of output tokens that is consistent across every locale. Results obtained from these definitions can be stored in the same database fields as the results obtained from definitions of the same name in other locales.