Ever try to put something together without reading the instructions? We’ve all done it, and then we had to pull the thing apart and read the instructions to figure out where we went wrong before putting it back together. Metadata is a piece of the overall instruction set of a BI effort, part of the circuitry of your Data Warehouse environment. Let me explain.
Simply put, Metadata is data about data. Usually, it doesn’t mean much—unless you have to describe something. But someone who accesses, develops, or maintains data needs to know exactly what he’s looking at. In his book, The Data Warehouse Toolkit (2nd edition), modern Data Warehousing founder Ralph Kimball defines metadata as “all the information that defines and describes the structures, operations, and contents of the DW/BI system.” Kimball describes three types:
Whether it’s in the cloud or on-premise, the location of your metadata doesn’t matter. Metadata is a critical aspect of the business intelligence effort when building a data warehouse or data mart. A well-written metadata dictionary becomes the inventory list that catalogs what data is to be stored. BI looks at this data in a manner opposite to transactional applications. In transactional applications, you know what you’re going to populate and create code to align to that data. In contrast, BI looks at what the business user needs to report on, and drives back to get that data. So it’s critical we understand how and what data they need to do their job. Remember, data that doesn’t exist—or is improperly formatted—is still needed. Spreadsheets get created and become an ever-present stop gap that is difficult to get rid of, if at all possible.
Here’s a common scenario: ever had difficulty getting two individuals, managers, or organizations to agree on how something is defined? Unless this definition is in writing and agreed-upon, ambiguity or conflicting definitions quickly become critical issues for development, data maintenance, data quality, and reporting (i.e. a hit to your budget). In addition to being a BI project building block as part of the design phase, a well-written metadata dictionary becomes a source for input into your Data Governance process to referee data conflicts and confusion. Without it, the amount of rework, bad data, and loss of user confidence (especially in a large effort) is staggering.
Is your organization lacking a Data Warehouse or BI environment? If you do any type of reporting at all, you need a clear definition set in writing to describe your terms and the calculations you’re reporting on—which you can then use to better scale your business. If you’d like some help building your Data Warehouse or BI environment, check out our reach out. We’d love to get you started.
Business Intelligence Architect
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.