Disable Multi language support for Custom Metadata Fields

1 Initial Problem

With the feature Multi language support for Custom Metadata it is possible to configure the internationalisation on custom metadata record level. If enabled the presenation of metadata text fields will offer a text input field for each enabled language.  For some types of text fields (e.g. "Name of Presenter") this is not desired and the configuration of translated field names would be sufficient.

2 Conceptual Summary

If more than one language is enabled for custom meta data records, a new configuration option is available for fields of type "Text", which allows the de/activation multi lingual text field values. The default of this option is "Enabled".

3 User Interface Modifications

3.1 List of Affected Views

• Administration of metadata fields (type text)
• Presenation of metadata fields of type text in "Edit-Mode"

3.2 User Interface Details

3.3 New User Interface Concepts

none

3.4 Accessibility Implications

none

4 Technical Information

No special technical information

5 Privacy

6 Security

No security issues.

7 Contact

• Author of the Request: Meyer, Stefan [smeyer]
  
• Maintainer: Meyer, Stefan [smeyer]
• Implementation of the feature is done by: Meyer, Stefan [smeyer]

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

Kunkel, Matthias [mkunkel], 09 OCT 2023 : Just a question to understand the request properly: in chap. 2 is written that disabling this setting disables multilanguage entries. But the byline of the screenshot mentions that in this case an entry can only be made in the user language _or_ the default (installation) language. But what happens if the user language is not the default language? Wouldn't be the correct explanation that no translation of a language entry is possible (no matter of the user or system language)? The input is used for all enabled languages.

Meyer, Stefan [smeyer], 12 OC 2023: The byline should be improved. This request should support untranslatable field values like e.g. the name of a person. In this case it does make sense to show multiple text  fields for every translation.

Potter, Chris [ChrisPotter] As this option has a byline, I think we could keep the label short? How about 'Multilingualism' instead of 'Multilingual Field Values'? An alternative suggestion for the byline (assuming I have understood the fuctionality correctly) would be something like: "Allow multilingual field versions for this data field. Deactivating this option is recommended for texts that do not need translating, such as personal names." (?)

JourFixe, ILIAS [jourfixe], 16 OCT 2023: We highly appreciate this suggestion and accept the feature for ILIAS 9.

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Screenshots

Settings in Administration

Presentation of Metadata Tab of Object

Test Cases

Test cases completed at 2023-10-26 by Spirou, Ilias [ispirou]

• 63601 : Diactivate Multi language support for specific Custom Metadata Field 

Approval

Approved at 2023-10-27 by Mix, Eva [emix].