A data team’s success hinges on its leader’s soft skills but, this is easy to lose sight of given the backlog of technical work. These two tips, earned from experience, can help new managers keep a focus on the fuzzy but important work of managing across teams.
In part 2 of Mark's conversation with Chad Sanderson about the Semantic Data Warehouse, they discuss the importance of semantically defining entities and new roles for contracts and the data catalog.
In this first part of Mark's discussion with Chad Sanford, they focus on "semantics," how it should be defined, and how the Semantic Data Warehouse fits with the modern data stack
One of the early questions that data engineering teams pose when implementing a catalog is: should we make the catalog responsible for gathering metadata from data systems ("pull"), or task data systems with reporting metadata to the catalog ("push")? And, what are the consequences of using one approach over the other? Learn how to ingest metadata into your catalog and which method to choose.
Why is data discovery important? What is the role for data discovery in data mesh? Who's responsible for making data discoverable? Learn the answers to these questions (and more!) — summarized from a recent panel discussion on Data Discovery in Data Mesh.
It’s time for the data catalog to evolve. Catalogs already have access to rich, cross-sectional views of your data ecosystem. The next frontier is to repurpose this information for operational use by integrating your catalog into your CICD pipeline.