Multi-Language Titles and Options for UDF

1 Initial Problem

UDF ("Custom Fields") can be selected for display in many tables (e.g., Learning Progress).
By now (v8), their titles cannot be differentiated according to user language.
The same applies to options of those UDF offering selection menues instead of text fields.

So, institutions with multilingual target groups can only either combine all translations in one field (thus making the titles or options very long) or offer redundant UDF for different languages (thus loosing the ability to sort or filter across languages).

2 Conceptual Summary

UDF can be equipped with language-dependent titles, and, if they are of the "Selection List (Single Choice)" type also with language-dependent selection options.

3 User Interface Modifications

3.1 List of Affected Views

• usrf/settings/user_defined_fields -> Edit (existing field)

3.2 User Interface Details

The UI component introduced with Multi language support for Custom Metadata could be applied to UDF, too, provided that the user navigation is changed in some way:

• Clicking "Edit" for a UDF opens a view in which the tabs of the "User Management" administration area have disappeared and only two tabs "Settings" and "Multilingualism" are displayed, together with a link "Custom Fields" at the beginning of the tab bar.

  

• Opening the "Multilingualism" tab, the same view appears like in the solution for Multi language support for Custom Metadata:

  • As soon as more than one language has been activated, the UI component is displayed in the "Settings" tab that allows to switch between language variants.
  • Clicking "Custom Fields" takes you back to the list of UDF.

  

3.3 New User Interface Concepts

(none)

3.4 Accessibility Implications

(?)

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

(none)

6 Security

(none)

7 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]
• Maintainer: Meyer, Stefan [smeyer]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

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

• Torsten Thoms, SIEBENPLUS GmbH

9 Discussion

10 Implementation

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

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.