Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Fuzzy Population

Fuzzy Population

If the match/search strategy is Fuzzy, then you must select a
population
, which defines certain characteristics about the records that you are matching.
Data characteristics can vary from country to country. By default,
Informatica MDM Hub
comes with a Demo population, but
Informatica
provides standard populations for each country. If you require another population, contact
Informatica
support. If you chose an exact match/search strategy, then this value is ignored.
Populations perform the following functions for matching:
  • accounts for the inevitable variations and errors that are likely to exist in name, address, and other identification data
    For example, the population for the US has some intelligence about the typical identification numbers used in US data, such as the social security number. Populations also have some intelligence about the distribution of common names. For example, the US population has a relatively high percentage of the surname Smith. But a population for a non-English-speaking country would not have Smith among the common names.
  • specifies how
    Informatica MDM Hub
    builds match tokens
  • specifies how search strategies and match purposes operate on the population of data to be matched

0 COMMENTS

We’d like to hear from you!