How define and document a value from an attribute?
Hi,
I would like to find a way of documenting/give a definition for each values of an attribute.
As an example, for an attribute called ‘Priority’ there are 5 values available ‘Blocking, Critical, Urgent, Normal, Minor’. For each value I would like to give a definition explaining what needs to be understood for each of the value.
Is there a way somebody already did that ? And what is the best practice in this case?
Thank you
Pauline FOUQUAT
Posted 3 years ago · Edited 1 year ago·Last reply 3 years ago
7 comments
arthurburkhardt
·3 years ago · EditedFYI, we’ve done something a little similar to expose the collibra metamodel into a glossary and define what each component means. It’s so much easier to give a link to stakeholder when we need to remind them of the definition of what “data set” or “report” is.
Pauline FOUQUAT
OP3 years ago · EditedThanks a lot again Arthur for your quick reply and advice.
We’ll try and do that, and see how it fits our users’ need.
Pauline FOUQUAT
OP3 years ago · EditedThanks Arthur for sharing your thoughts on this topic.
I have added my vote to your ideation !
I will try and manage the workaround you suggested.
Thank you
arthurburkhardt
·3 years ago · EditedThis is not possible technically, but there are workarounds.
I have the same need as you and proposed a “turbocharged” component, that could combine a multi-value selection attribute + an asset (to which you can provide a definition): Ideation: Give superpowers to tags, selection attributes and relations! - Product Q&A - the Data Citizens community (collibra.com)
In the meantime, here are some workaround ideas:
arthurburkhardt
·3 years ago · EditedThis is not possible technically, but there are workarounds.
I have the same need as you and proposed a “turbocharged” component, that could combine a multi-value selection attribute + an asset (to which you can provide a definition): Ideation: Give superpowers to tags, selection attributes and relations! - Product Q&A - the Data Citizens community (collibra.com)
In the meantime, here are some workaround ideas:
Pauline FOUQUAT
OP3 years ago · EditedHi again Arthur, hope you’re doing well ?
I come back on this topic, as I tried the workaround suggested by created a dedicated glossary and inside this glossary for an existing attribute with multi values, I created a BT for the attribute (Priority) and BATT for each of the values that compose the attribute (Blocking, Critical, Minor, Normal, Urgent).
For each of these BATT I completed a definition.
But then how do you manage to link the assets that are in the ‘Collibra Glossary’ and the existing attribute used already? Or is this link not possible to manage so far?
Is the only ‘link’ within the workflow where you suggest to add the description of the newly created BATT?
Or am I misunderstanding something?
Thanks in advance
arthurburkhardt
·3 years ago · EditedThat looks good!

Indeed, there are no way to link it.
A few thoughts to ensure consistency: