Multilingual Glossary

1 Initial Problem

The handling of multilinguality in glossaries is very different from learning modules. In glossaries an additional term has to be added.
This should be streamlined.

2 Conceptual Summary

Handling the multilinguality handling in the glossary is changed to be streamlined with the multilinguality handling in the learning module:

1. The multilinguality is made explicit and becomes a sub-tab in the settings tab.
2. Instead of additing an additional term in a different language the original terms will be actually translated.
3. The editing view of the term.

3 User Interface Modifications

3.1 List of Affected Views

• Settings-tab of glossary

3.2 User Interface Details

Settings-Tab

Multilingual Terms

Multilingual Definitions

3.3 New User Interface Concepts

None.

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 Information

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ 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. }

7 Contact

• Author of the Request: {Please add your name.}
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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.

• …

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}.