Master data ownership management
Hi All,
What would be an efficient way to handle master data ownership management in Collibra?
e.g. a description of a set of assets is managed in another application and is imported in Collibra and one of the asset descriptions contains a typo. How does one know that this data is managed in Collibra - and it can be updated in Collibra - or that we need to do the alteration in the source application?
In a master data management application data would be ‘greyed out’ (not manageable) when it is not managed in the application itself. What is best practice in Collibra to manage this? One could add a note in the info field of an attribute, but the granularity is not great, because attributes can be used in other assets(types) as well.
Thanks!
Tom
tomkuppens1
Posted 4 years ago · Edited 1 year ago·Last reply 4 years ago
3 comments
arthurburkhardt
·4 years ago · EditedIndeed the granularity is not great and there are at this time no functionality to support this use case, so you have to rely on process exclusively.
You can vote on some similar ideas on the ideation board:
In the meantime, it is possible to discourage users to edit such fields, through:
The last option, you can create a workflow designed to check the metamodel on a regular basis for changes to read-only attributes from users that are not approved. It’s a bit retroactive but can ensure the eventual consistency of the catalog.
arthurburkhardt
·4 years ago · EditedIndeed the granularity is not great and there are at this time no functionality to support this use case, so you have to rely on process exclusively.
You can vote on some similar ideas on the ideation board:
In the meantime, it is possible to discourage users to edit such fields, through:
The last option, you can create a workflow designed to check the metamodel on a regular basis for changes to read-only attributes from users that are not approved. It’s a bit retroactive but can ensure the eventual consistency of the catalog.
tomkuppens1
OP4 years ago · EditedThanks for the insights Arthur. Tom