Selection fields translation

Question

Hey, community!

While Collibra is a great tool for managing multi-language enterprises, there is one specific area that seems to need improvements.
That’s about Custom fields of type Selection and Multi-Selection. We can define set of values but no option to create translations “out-of-the-box”.

What are your best practises for solving that?

gustavaagesen · Answer

The feature was requested for this in Ideation 5 years ago… It seems not to be a priority. https://productresources.collibra.com/ideation-platform/?id=DGCPLAT-I-62

gustavaagesen · Answer

Hi @bineesh.babu.collibra.com and @ruslan.ahmetzyanov.

We have previously started adding custom assets in our own locale, and at the same time create asset names in Norwegian.

The elephant in the room, as I see it, is translating asset types, relations, and attributes as a whole.

We have now a situation where we have started using the language file for what it is worth. But multi-language support is only achieved when OOTB-assets can be translated so that the users can move between languages and get consistency.

Further we see that the OOTB-workflows should be implemented using language settings. Either as declared variables in top of the files, or as separate resource files.

Bineesh Babu · Answer

Hello @ruslan.ahmetzyanov , Yes thats current Limitation. option are :- create attribute in two language or use Code Values and related asset to these Code Values (which are in different language) Thanks Bineesh

1	Grant Rollerson SUNCORP CORPORATE SERVICES PTY LTD
2	Tom Friesen Algonquin College
3	SB S Benson Plus3 IT
4	S stefan_busch
5	Brian Lloyd USA TODAY Co.
6	D daverichard