Make 'Allowed Values' for Properties translatable

[lfcastel]

Would it be possible to have property values that are translatable? Very convenient for multi-language countries.

[atomczak]

You mean the description of the value? The description can be translated, and the value needs to be the same in the model, otherwise it's no longer the same data.

[lfcastel]

You mean the description of the value? The description can be translated, and the value needs to be the same in the model, otherwise it's no longer the same data.

I mean the value here. The thing is we have a code (acronym) which is actually what the user has to put. Then there's the full name and description. We use the code because in a multilingual country it is the easiest. But both name and description in our case wouldbe used in applications in different languages, but not as values

[atomczak]

So user, regardless of language, puts the same value in the model, right? Why can't you just translate the description? Can you give an example?

[araccaine]

Maybe I misunderstand this issue completely, but isn't value already stated as Translatable in the JSON documentation?

Code is a unique identification of the value (max 20 characters). It is required and, in most cases is the same as the value. It is needed to enable translations of Values or their Descriptions.

Using the code as identifier allows then to translate value. @lfcastel's example also totally makes sense to me: The Form of the document can be named differently in different languages, and the code allows us to pick the right value regardless of language. In the example above, Bill of Quantities could be Mengenliste in German. This translation is not obvious: A user would have to search for Bill... to get Mengenliste. This would make navigating the bSDD really inconvenient.

---

Not sure if related, but in this presentation (page 7), name is shown as translatable whereas code is used for identification. In the JSON documentation, the example is a little bit contradictory:

Here name is the "Ifc-name" IsExternal and code is some arbitrary code ifc-99088-01. In the presentation, code represents the uniqe "IFC-name" and name is the "human-friendly name".

[lfcastel]

So user, regardless of language, puts the same value in the model, right? Why can't you just translate the description? Can you give an example?

Yes because in a country with 2 official languages and people of both native languages working on the same project, we need a neutral value which is on our case would be English, more precise the English acronym. So if somebody uploads a bill of quantities on a CDE, our national convention says he/she should use BQ as one of the metadatafields. Depending on the user language this should the description 'bill of quantities' should then be displayed in Dutch or French.

I'd say it's comparable to having a ISO standard that has a code 19650-2, a name 'Information management using building information modelling - part 2: delivery phase of the assets' and a description.. both the name and the description should be translatable, but not the code.

as @araccaine mentions it is apparently translatable, but I always check the documentation so i wonder why i commented this, maybe the docs have been updated or the docs are not alligned with the import engine...

I think that i'm using the code as a value here, maybe it's not the right way to do it. So i say that Form can have different values (see the list) and every value has a code, value and description. But i don't see any alternative..