Feature Wiki

Information about planned and released features

Tabs

Offer Multilingualism for Course, Group and Category Links

1 Initial Problem

After creating an object link whose reference object has multilingual titles (e.g. English and German), the title of the new object is always displayed in the default language only. Regardless of whether I as a user have selected English or German as the language.

On the following screenshot one can see that the default language is English and the user has set German as the language. The reference object is correctly displayed in German, but the object link is in English.

Furthermore one can see that the description is NOT displayed (only in tile view). In list view the description is displayed correctly and even in the correct user language (what can cause an english title with a german description in this case).

2 Conceptual Summary

The object links should always be displayed in the user's selected language if the reference object has a corresponding translation. Otherwise, the default language is used.

3 User Interface Modifications

3.1 List of Affected Views

  • repositories

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

None

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

{ Personal data that will need to be stored or processed to implement this feature have to be listed here. For each date give a short explanation why it is necessary to use that date. }

4.4 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  Seibt, Alina [alina.seibt]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

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

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.

Last edited: 14. Jan 2025, 12:10, Seibt, Alina [alina.seibt]