Last time we explored consumption and usability as an alternative approach to data governance. In that framework, data stewards can measure the quality of the data and alert users about potential risks of using the results, but are prevented from changing the data. In this post we can look at
Author
David Loshin (@davidloshin) on naming conventions for naming things.
David Loshin (@davidloshin) on using analytics to pinpoint your best customers.
David Loshin (@davidloshin) offers a new approach to addressing customer classification.
Data expert David Loshin (@davidloshin) delves into value pricing and customer analytics.
David Loshin (@davidloshin) discusses the importance of social media analytics.
Last time we began to look at the opportunity for integrating a newly developed master data repository with existing business applications supported by a data warehouse. That meant understanding the requirements for integration and verifying that those requirements are met.
David Loshin explains how to integrate MDM with your data warehouse.
David Loshin discusses master data model requirements.
David Loshin explains the technical requirements for MDM/DW integration.
David Loshin's latest blog post: "Balancing Performance Measures for Data Accessibility using Data Federation."
David Loshin's latest blog post: "Monitoring for Event Patterns."
David Loshin on analyzing sequences of events.
Read David Loshin's latest blog post: Understanding Sequences of Events.
Data governance as an MDM program planning task, part 2.
Does data governance make a difference? See what @davidloshin has to say.
Read David Loshin's latest blog post: "Innovation in Creating Information Products."