Table of Contents

Search

  1. Preface
  2. Introduction
  3. Starting Population Override Manager
  4. Purpose Operations
  5. Overriding Frequency Tables
  6. Edit-List Overrides
  7. Rule Definitions
  8. Implementing a Local Population

Population Override Manager

Population Override Manager

Edit-List Processing Overview

Edit-List Processing Overview

Before we look at the various Edit-List Rule types, there are some fundamental Edit-List processing concepts that should be understood.
Prior to being processed against the Edit-List, names and addresses first go through a character "cleaning" phase. In this phase, special characters, delimiters and double spaces are removed. In many cases, accents are also removed. For non-Latin character sets, other rules may apply - check with Informatica Corporation technical support if you have questions about non-Latin character cleaning.
This means, for most Rule Types, do not enter words that contain special characters or delimiters. If it is necessary to define a rule about a word that contains special characters, use the character rule type.
A word may be defined with multiple rule types, provided the words are processed in different Edit- List Processing phases (see the end of this chapter for a description of Edit-List Processing Phases).
Edit-List lookup processing uses exact matching. In other words, for an Edit-List rule to be triggered, the word, number, code or phrase in the name must match exactly the word, number, code or phrase in the Edit-List.
When defining replacement rules, the recommended approach is to replace the shorter word with its longer variation. This is because there is generally more chance of error and variation in the longer word, and as the Edit-List lookup processing uses exact matching, it makes sense to use the word that has the lesser chance of error in the lookup process.
Always, when defining new Edit-List rules, put the effort into making the rules complete. For example, if adding an abbreviation rule for the new word,
UNIVERSITY
, don’t limit your thinking to the most obvious (for example,
UNI
). Ask your end-users, or analyze your data, to see what other variations may be in common user (for example,
VARSITY
,
UNIV
,
UNVSTY
).
If you have discovered a rule which you think should be in the Standard Population, please advise Informatica Corporation who will evaluate its inclusion in the next release.

0 COMMENTS

We’d like to hear from you!