CONSISTENT NAMING AND CODING STANDARDS
When designing rules in Informatica Data Quality, the developers and data stewards will see the same rules. Therefore, it is important to develop consistent naming and coding standards. For example, both the data steward and the developer will understand what “rule_” means while not everyone will understand what “mplt_” means. Therefore, mapplets should be named rule_ if they are used in both the Analyst and Developer tools.
It is a best practice to include anchors and descriptions in DQ mappings for faster modifications, readability and comprehension. Any metadata changes to a source or target object in a mapping (e.g. a new column) can quickly be made if anchor transformations exist immediately following the source object and immediately preceding the target object. These
can simply be pass-through transformations. All objects should also have descriptions. The description will be displayed in the Analyst tool and can be useful to data stewards for understanding the data anomalies when viewing profiles. This can also help remind the data steward what rule was applied and whether or not it needs to be updated.
PARTNER WITH US
Do you have a current Data Quality initiative? How is your Data Quality project progressing? We’d like to hear from you. Take a few minutes to send us an email and let us know about your project. If you’d like further assistance with your current project, feel free to contact us directly. We’d be happy to talk with you and develop a proposal around your project.
If you’d like more tips & tricks regarding Informatica Data Quality, download our eBook: SIX DESIGN TIPS IN INFORMATICA DATA QUALITY.