When source data is unclean, the platform offers several baseline means of improving it during load. System Import transform map scripts allow field values to be cleansed, reformatted or conditionally mapped as import set rows are transformed into target records, so inconsistent names, codes or formats can be corrected in flight. The IntegrationHub ETL capability provides data preparation transforms before data is mapped to target classes and attributes, which supports normalization of structured source data. Field normalization rules and the normalization plugin standardize values such as names and units so that equivalent entries are represented consistently.
A system definition fix scripts module is not a data cleansing facility; fix scripts perform one-time upgrade or data corrections and are not a configured pipeline for incoming data. The Service Graph Connector is a packaged integration for bringing configuration data from a specific source into the CMDB. It is a source-specific connector, not a general mechanism for cleansing customer-supplied data.
Implementers should therefore choose the least complex tool that addresses the defect, applying transform scripts for targeted fixes and normalization for broad standardization. Cleansing before the load is preferable to repairing records afterward, because duplicate third parties produce unreliable rollup scoring.
[Reference: Study Guide – Core Configuration: Data Import, Transformation and Normalization.]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit