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: Glossary

Configuring Match Settings for Non-US Populations

Configuring Match Settings for Non-US Populations

If the MDM Hub implementation uses a non-US population, configure the population set and enable encoding for match processing. A population set encapsulates intelligence about name, address, and other identification information that is typical for a particular population. For more information about population sets, see Population Sets.
The MDM Hub includes a
demo.ysp
file and a
<population>.ysp
file. The
demo.ysp
file contains a population for demonstration purposes only and must not be used for actual match rules. In your MDM Hub implementation, use the
<population>.ysp
population file for which you purchased a license. If you do not have a population file, contact Informatica Global Customer Support to get a population file that is appropriate for your implementation.
Decide on a population set based on the following considerations:
  • If the data is exclusively from one country and Informatica provides a population set for that country, then use that population.
  • If the data is mostly from one country with small amounts of mixed data from one or more countries, use the majority population.
  • If the data is from different countries with large amounts of mixed data, consider whether it is meaningful to match across such a disparate set of data. If so, then use the
    international
    population.
For more information about enabling a match population, see the
Multidomain MDM Installation Guide
.

0 COMMENTS

We’d like to hear from you!