At my organization, we’re learning to use Purview for data governance. For example, we’ve started to use the Data Map to get assets from our data warehouse, and enrich those assets with additional metadata in Purview. Nice!

Now, I’d also like to create our org’s conceptual data model in Purview, somehow. That is, (a) our real-world objects, independent of any systems/data, each with a name and a definition/description; plus (b) the relationships between these objects, each with the cardinality and description. And I’d like for all our our end users to be able to read the conceptual data model, in Purview.

But how? I am reading lots of Purview documentation in Microsoft Learn, and it seems there could be several possible solutions. But it’s not clear to me that any one of these solutions is the right fit, for this use case. Has anyone done this in Purview? Any recommendations? Should our conceptual data model be created in Purview…

…as Glossary Terms? (Can these have relationships with each other?)…in the Metamodel? (Maybe with custom asset types? I know I can create relationships, here—that’s key.)…as Critical Data Elements? (Can these have relationships with each other? This could be nice because then I could relate objects in the conceptual model to actual data points in the data warehouse.)…as something else?

​At my organization, we’re learning to use Purview for data governance. For example, we’ve started to use the Data Map to get assets from our data warehouse, and enrich those assets with additional metadata in Purview. Nice! Now, I’d also like to create our org’s conceptual data model in Purview, somehow. That is, (a) our real-world objects, independent of any systems/data, each with a name and a definition/description; plus (b) the relationships between these objects, each with the cardinality and description. And I’d like for all our our end users to be able to read the conceptual data model, in Purview. But how? I am reading lots of Purview documentation in Microsoft Learn, and it seems there could be several possible solutions. But it’s not clear to me that any one of these solutions is the right fit, for this use case. Has anyone done this in Purview? Any recommendations? Should our conceptual data model be created in Purview… …as Glossary Terms? (Can these have relationships with each other?)…in the Metamodel? (Maybe with custom asset types? I know I can create relationships, here—that’s key.)…as Critical Data Elements? (Can these have relationships with each other? This could be nice because then I could relate objects in the conceptual model to actual data points in the data warehouse.)…as something else?  Read More

​