Share

submit to reddit

About Lowell Fryman, CBIP-CDMP

Lowell is responsible for directing thought leadership and advisory services in the Customer Success practice of Collibra. He has been a practitioner in the data management industry for three decades and is recognized as a leader in data governance, analytics and data quality having hands-on experience with implementations across most industries. Lowell is a co-author of the book “Business Metadata; Capturing Enterprise Knowledge”. Lowell is a past adjunct professor at Daniels College of Business, Denver University, a past President and current VP of Education for DAMA-I Rocky Mountain Chapter (RMC), a DAMA-I Charter member and member of the Data Governance Professionals Organization. He is also an author and reviewer on the DAMA-I Data Management Book of Knowledge (DMBOK). He focuses on practical data governance practices and has trained thousands of professionals in data governance, data warehousing, data management and data quality techniques. You can read his Data Governance Blogs at https://www.collibra.com/blog/,

  • Jeff

    What are the recommended parts of the Business Glossary? Obviously Business Term and Business Definition. What about natural keys or identifiers?
    Here’s the thing I’m running into… We have some business entities that have some (undocumented) natural identifiers. But the physical tables either don’t include the natural identifiers, or don’t make them part of the primary key. You can’t tell if two rows are duplicates or really separate items. So, it’s hard to compare entity instances across systems and hard to set a standard for data quality.
    Do you recommend including natural keys / identifiers in the Business Glossary? Or is that something too technical that you should hide from the business users?

Top