Forum Discussion
Data Product Owner and Contacts should be separate fields
The intent of the single owner is to provide a simpler accountability method for everything in Purview. Ensuring that the owner is on every concept and the different levels and types of ownership will help to segment their expertise. We are adding custom attributes in the coming months (MS-Purview-Data-Governance-Roadmap-detailed.pdf) which will enable adding additional custom roles and names for those that should be contacted for specific questions. As we look to enhance the collaboration features within Purview we can look to provide specific roles based on how they would interact with others and the concepts they are a part of in the catalog.
While I appreciate the reply, I stand my ground. Data Product Owner and Contact should not have this one on one relationship.