Feature Wiki

Information about planned and released features

Tabok

Multilingual Container Objects

Lapáttekintés

[Elrejtés]

 

1 Initial Problem

Container objects in ILIAS can have sub items for different target languages. However most properties of courses, groups and folders can't be translated today.

2 Conceptual Summary

We want to develop this feature based on the Feature Request Multilingual Input Element.

2.1 Focus on Container Object Types

In the details below, I will focus on container objects (excluding cross-type functionality like taxonomies, custom metadata or news).
However, comments are welcome on whether this is the most important aspect, actually.

The reason why our ideas are focusing on container objects:
As soon as you can design language-sensitive surfaces for container objects, you can use them to forward users to language-specific objects, that is, by:
  • Making the objects in a course or group invisible via the permission system.
  • Providing internal links to language-specific objects.
This way, we wouldn't need multilinguality for learning modules, tests etc. because an english-language users will only be able to access english-language content.

3 User Interface Modifications

3.1 List of Affected Views

  • Courses
    • crs/view_content/view_content and copg/edit_crs/:
      "Content" view of the course and its edit mode
    • crs/settings/crs_settings:
      "Settings > Course Settings" view (affected fields: Title, Description)
    • crs/info_short/ and crs/settings/crs_info_settings:
      "Info" view of the course and its edit mode (affected fields: those in the "General Information" section, in the "Contact" section)
    • crs/settings/crs_custom_user_fields and crs/join/:
      "Settings > Course Relevant User Data" view [1] and the "Join" screen where course relevant user data are asked for.
      (Affected fields: Name, Value)
    • Courses ("Learning Objectives-Driven" view), additional views:
      • crs/crs_objectives/objectives and crs/crs_objective/create_obj:
        "Learning Objectives > Learning Objectives" and "Describe Learning Objective" views where title for LOs are entered (affected fields: Title, Description)
      • copg/edit_lobj/:
        "Edit Page" view of LO
  • Groups
    • grp/view_content/view_content and copg/edit_grp/:
      "Content" view of the group and its edit mode
    • grp/settings/grp_settings:
      "Settings > Course Settings" view (affected fields: Title, Description)
    • grp/info_short/ and grp/settings/grp_info_settings:
      "Info" view of the group and its edit mode (affected field: Important Information)
    • grp/settings/grp_custom_user_fields and grp/join/:
      "Settings > Group Relevant User Data" view [2] and the "Join" screen where group relevant user data are asked for.
      (Affected fields: Name, Value)
  • Folders
    • fold/view_content/view_content and copg/edit_fold/:
      "Content" view of the group and its edit mode
    • fold/settings/fold_settings:
      "Settings > Course Settings" view (affected fields: Title, Description)

3.2 User Interface Details

see Multilingual Input Element as soon as its concept is ready.

3.3 New User Interface Concepts

-

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 Contact

  • Author of the Request: SIG Language Support
  • 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.}

6 Funding

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

7 Discussion

Suittenpointner, Florian [suittenpointner] 2016: Here is an overview of functionality in repository objects possibly relevant to multilinguality

Analysis of All Objects
In this file, we analyze all repository object types in the following structure:
  • Object Level:
    Text input fields on the level of an entire object:
    • Title/description
    • Other text entries in general settings of objects, like "Course Information", "Introductory Message" in tests/surveys
    • Other Object-Wide Text-Related Functionalities, like "Course Relevant User Data"
    • Other cross-type text-related functionalities, like "Taxonomies", "Custom Metadata" or "News"
  • 1st Sub-Element Level:
    Text input fields on the level of an objects sub-elements:
    • Chapter/page titles in learning modules
    • Assignment titles in exercises
    • Item titles in mediacasts
    • ...
  • 2nd Sub-Element Level:
    • Answers in questions, Feedback texts or Hint titles and texts in tests
    • Field titles and descriptions in data collections
  • Object pages, i.e., the page editor in several interfaces

Kiegel, Colin [kiegel] 2017-02-03: I split this request off of Multilingual Titles and Descriptions for All Object Types + Plugins as a result of the JF Workshop on 2017-01-31 about Multinguality.

Is it sufficient to link Multilingual Input Element for implementation details? We propose to use the newly introduced user interface concept from there.

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

[1] Watch out: in v5.2 there is a wrong screen ID crs/settings/obj_news_settings!
[2] Watch out: in v5.2 there is a wrong screen ID grp/settings/obj_news_settings!

Utoljára szerkesztette: 16. Okt. 2017, 18:09, Suittenpointner, Florian [suittenpointner]