Feature Wiki
Tabs
Changed Language Entries for ILIAS 12
Page Overview
[Hide]- 1 Components and Language Entries
- 1.1 Updates to the English Language File
- 1.1.1 News
- 1.1.2 Test and Assessment
- 1.2 Updates to the German Language File
- 1.2.1 News
- 1.3 Changes due to Gendermainstreaming of German Language File
- 1.3.1 ...
- 1.1 Updates to the English Language File
- 2 Process Information
- 2.1 Involved Authorities
- 2.2 Contact
- 2.3 Funding
- 3 Discussion
- 4 Implementation
- 4.1 Description and Screenshots
- 4.2 Test Cases
- 4.3 Privacy
- 4.4 Approval
1 Components and Language Entries
1.1 Updates to the English Language File
1.1.1 News
The language entries for news have been given a general overhaul, correcting grammar and typos, and unifying style, case and terminology across the ILIAS English language files.
This round of improvements to the news language entries was kicked off by the 'Einstellungsreiter-Gruppe' - I based my work on their excellent groundwork.
Notifications" → "daily news roundup: In Course and Groups, users are able to subscribe to an e-mail that collects the news created by Courses or Groups. Previously, to subscribe to this mail, users had to 'Activate Notifications'. This was misleading, as they receive no internal mail, pop-ups or other immediate 'notification'. Therefore all references to notifications in this context have been replaced by 'daily news roundup', a term which more accurately reflects the actual functionality.
Info lines rewritten from "what it does" to "what the user gets": The info lines have been rewritten where necessary in line with the general style of the other Objects that have had their language entries re-worked. The old texts were written from the system's perspective (instruction + caveat), the new ones from the reader's (what is this?, what's in it?, where do I go?, what's the risk?). The info lines are meant to help users who are feeling a little overwhelmed by ILIAS and provide the information they need. Therefore, across the English language info lines in ILIAS, we have been moving away from info lines that read like memory aids for the developers and towards info lines that describe what the user gets if they select an option. There were many examples of this in News, for example:
- Old: "Activates News Timeline Tab"
- New: "Make a 'Timeline' tab visible, in which your news items will be listed. Members will then be able to subscribe to a 'daily news roundup' e-mail."
1.1.2 Test and Assessment
Test and Assessment is such a huge component of ILIAS that it has been necessary to tackle it in phases. In the first phase (for ILIAS 11) we looked mainly at the Object's settings. For this second phase we have focussed on the question types themselves, covering both what question creators see and what end users see.
Questions and question creation reworked: Lots of changes here. Please refer to the spreadsheet below for all changes. Examples include:
- Label corrections: "Use Text Answers" / "Use Picture Answers" (ordering questions, replacing "terms"), "Answer Elements" as the section heading, etc.
- Neutral, de-editorialised, rule-stating texts: for example, the Kprim half-point rule now simply states when points are awarded ("Points are awarded if three out of four statements are answered correctly", replacing the old "It has proven sensible to..." editorial-style text), and the wrong-selection field says what to enter ("Enter the negative point score, e.g. -1, -2, etc." instead of "Enter points for words not included in the marked errors").
- Improved info lines: label-paraphrases turned into actual explanations - what the setting does, who uses it, and what happens as a result. Example: the scoring adjustments info line now describes what can actually be done when the option is selected (deleting answer options, marking alternative cloze answers correct). Also removed redundant/incorrect information from info lines.
- Added a brand new info line for Ordering Questions (Vertical) to explain the rather confusing path to editing nested answers.
Scoring and scoring filter: We will look at scoring in more detail in phase 3, but felt that the filter in the Scoring tab needed immediate work. Changes include:
- Terminology unification: "Scoring Finalised"
One consistent term for the completed-scoring state, replacing the previous mix ("Scoring Completed", "Marked as 'scored'", "Show finalized gradings"). The scoring view's filter labels now also distinguish the two levels explicitly: "Questions Scored" and "Users Scored". Filter options rewritten as actions: "Show only users set to 'Scoring Finalised'" / "Hide users set to 'Scoring Finalised'". - Missing entries restored: Entries in the manual scoring workflow: setting and removing a user's 'Scoring Finalised' status (EN + DE)
- Improved info lines: e.g. for enter_enough_positive_points - The maximum points attainable needs to be greater than 0! Please make sure that the sum of all positive and negative points is a positive number.
1.2 Updates to the German Language File
1.2.1 News
Updates to German entries for news in line with English changes listed above.
1.3 Changes due to Gendermainstreaming of German Language File
1.3.1 ...
2 Process Information
2.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: {Please add related profile link of this person}
- Authority to Sign off Code Changes: {Please add related profile link of this person}
If this request is related to multiple components, please list both authorities for all related components.
2.2 Contact
Person to be contacted in case of questions about the feature or for funding offers: {Please add related profile link of this person}
2.3 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'.
3 Discussion
4 Implementation
Feature has been implemented by {Please add related profile link of this person}
4.1 Description and Screenshots
{ Description of the final implementation and the changed behaviour in the related components. Please add screenshots to visualise the changes if possible. }
4.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
4.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
4.4 Approval
Approved at {date} by {user}.
Last edited: Yesterday, 14:19, Potter, Chris [ChrisPotter]