How does your organization handle acronyms with multiple meanings and/or across multiple business areas?
This is a multi-part discussion. I wanted to get some discussion around duplicated assets across domains.
How does your organization handle situations where an acronym has two different meanings in two different glossaries? For example, one team’s glossary defines AA as “Alcoholics Anonymous,” and another defines AA as “Association of Astronauts.” How does your organization’s Collibra team handle this? Do they do anything at all?
And what if two glossaries define an acronym the exact same way? Does your organization allow duplicate objects with the same definition across domains? Do you leave them alone? Do you combine them in any way?
With these duplicates, when a user types “AA” in the search box, they will see up to 3 assets called “AA” in the top results area and there’s no indication of the context of those assets in that pane. The user must either open all 3 of the asset pages, or use the Business Glossary filter page to filter on Acronyms with the name “AA” across all glossaries instead of using the global search field.
mirellehgf disuja
·2 years agohey I think we can do this=We maintain a centralized glossary or acronym database that defines all acronyms and their meanings across different business areas; We provide context when using acronyms, specifying the business area or application to avoid confusion; We standardize acronyms wherever possible, assigning unique abbreviations to avoid overlap.
Grzegorz Ręgałek
·5 years ago · EditedThank you @arthur.burkhardt . Got it now. Actually if you restrict it to single domain, collibra does not allow user to create it elsewhere (assuming one domain with specified type is created).
Grzegorz
Grzegorz Ręgałek
·5 years ago · Edited@arthur.burkhardt
Please advise how to restrict a domain for specific assets. When creating a domain or new domain type in settings panel there is no place to say which assets can be created in that domain. So, like asked by Gunnar, if I wanted to have just Acronyms allowed in “Acronyms Glossary”, how can I restrict it? If I’m not wrong, within Glossary I can create Business terms and all child assets of BT.
About those audit checks, is there OOB workflow/plug in that runs this check?
Many thanks.
Grzegorz Ręgałek
arthurburkhardt
·5 years ago · EditedIn the asset type assignment, you can restrict the domain types where acronyms can be created. So you can have one single domain allowing acronym assets, which will enforce consistency.
And you can make a regular check that no one creates an Acronym domain anywhere else on a regular basis.
There is no OOTB workflow that does this, I’m afraid.
Former User
OP6 years ago · EditedI see it that the Acronym exists as a breadcrumb only - the definitions and important metadata resides on the Business Term. Therefore a user will search for “AA” and that will be related to Alcoholics Anonymous, Anti Aircraft and Automobile Association. They will then go to the Business Term that fits the context they require.
Acronyms are therefore quite empty and only exist to lead a user to the Business Term.
arthurburkhardt
·6 years ago · EditedIt depends what your governance model is: decentralized, federated or centralized?
In a decentralized model, users would only have access to their LOB community and you would probably use the [acronym]–is acronym for–>[Business Term] construct… Even if there are 12 definitions of the same acronym, they would only be able to see their community => They would only see 1 acronym.
In a federated model, you would have a process to rationalize vocabulary across business lines.If you need to capture the context in which an acronym is used, you would probably use a complex relation then, that would capture which acronym is used in which context => This can lead to significant additional complexity, so make sure this is actually valuable.
In a centralized model, you shouldn’t have multiple definitions.
noor
·5 years ago · EditedHi Arthur,
Regarding your statement " Even if there are 12 definitions of the same acronym,…"
Is it a possible scenario? can you please explain with an example…
As per the example from Benjamin,
"
“AA” and that will be related to Alcoholics Anonymous, Anti Aircraft and Automobile Association
"
Though the acronym is same it actually represents a different term.
arthurburkhardt
·5 years ago · EditedJust the example you gave is perfect.
One acronym:
AAMultiple definitions:
Alcoholics AnonymousAnti AircraftAutomobile Associationnoor
·5 years ago · Editedthank you, got it…
Gunnar Matthies
·5 years ago · Edited@arthur.burkhardt would that mean that ideally all acronyms are managed in one (enterprise) glossary to avoid duplicate acronym assets?
Does anyone know if it is possible in the DGC to restrict users from creating acronym assets in certain glossaries?
Many thanks in advance
arthurburkhardt
·5 years ago · EditedYou can restrict asset creation to a certain extent through domain types.
And you can have audits to check you don’t have duplicates.
Gunnar Matthies
·5 years ago · EditedThank you Arthur