Content Preview: rss
440 days ago
I like to address how critical a good rule engine is a master data repository and how important it is that it supports an extended workflow. Take the example where customers can add themselves over the net, and immediately place orders. A strict and well designed GUI with wizards will of course bring you far, with shrewd functionality surrounding the critical business keys, but marketing will most certainly limit these checks in fearing of that too many rules and checks will take away users. So in the instance where we actually do give a heck regarding issues such as double accounts, false information etc. we would set up a workflow to verify these new data. A workflow which stretches from a repository aided workflow controlled by well defined business rules, over a workflow platform and into a manual workflow strictly governed. Scanning every input will flood any data stewards into giving in and worse of all not give enough care to his data responsibility. Smooth ...
501 days ago
News just in… Microsoft has purchased Zoomix, a data quality software vendor. This is truly interesting while Zoomix will contribute with the missing data improvement layer to the Microsoft Sql server data Platform. By this expanding Microsoft already ongoing MDM effort (stratature/bulldog/+EDM) I found it intriguing reading Kirks Haseldens blog on the Data Profiling abilities efforts in SQL Server 2008. It seems that SSIS and SQL server is going to bridge Microsoft’s effort to integrate Zoomix and +EDM, I find it fair to say this is really interesting news, seen in a MDM perspective. Guldmann
543 days ago
When venturing into any data quality program, is data profiling an essential cornerstone to turn. It provides a wealth of information about the data that you have. A master data repository must hold functionality to automatically identify data quality issues in a more than one way. Common for needed profiling plug-in is the requirement to drill trough to the very entries causing the anomalies, and the very same data must facilitate KPI reports over the same. Basic statistics, frequencies, selectability, data patterns, ranges and outliers. Through patterning the content of the attributes the possibility to detect a vararity of condition emerges. Say Postal code is mostly created with two chars indicating the country, followed by a space and then 4 numeric chars indicating the postal area, consider the mount of information deriving from patterning of this information. e.g. Attribute Entry Pattern DK 8000 XX[_]9999 DK 9000 XX[_]9999 ...
546 days ago
It’s not often this old rat is moved emotionally by a singer, but this is the most beautiful song I've ever heard. I've been back to this site at least 100 times to listen and watch Josh sing this song. Even though I don't understand much Italian, it doesn't make any difference. He makes the hair stand up on my neck every time I listen to it. http://www.youtube.com/watch?v=nKDkXOOHG34
556 days ago
Master Data repository should provide a validation framework to check the consistency of your master data. When looking into identify master data duplicates in a MDM repository, it is important that it support some basic functionality. Beyond its ability to merge specific master data records into a central repository a repository must be able to provide means to detect doublets through a fully parametric search. This resulting into a overview over the degree of similarity between different records. The Identifying plug-in must operate fully automatically, yet the merging conclusion can only be taken by the steward. The automated matching is based on matching rules, and these rules are bundled into matching strategies. According to a matching strategy, a probability score is calculated ranking the probability that specific records are duplicates. The steward can then compare potential duplicates and merge any records in the entities ...
