Feature Wiki
Tabs
Move (sub-)settings for additional features to new subtab
Page Overview
[Hide]1 Initial Problem
Disclaimer: This affects both courses and groups. I will henceforth only speak of courses, but the feature should be implemented for both objects.
The settings in the section "additional featuers" in courses offers greate possibilities and are essetial for many sceanrios in the day to day e-learning life at universities - just think of the news functionalities, the calendar, "mail to members", ...
While some settings are simply a chechbox that switches the feature on and off, other settings require a configuration workflow or additional steps for the feature to work at all (news, bagdes, competences, ...). In the current implementation it is possible to switch more than one of these features on (or toggle) in one go, since all checkboxes are localted on the same page otgether with all other course settings.
Therefore, necessary second steps like (1) "Activate News" -> (2) Activate News Block and/or Timline -> (3) Configure Behaviour of Block / Timeline are not possible. Course admins need to see either the very subtle new subtab "news settings" or the new tab (bagdes).
We should find a better solution which makes auch secondary configurations steps better accessible and easier to handle.
2 Conceptual Summary
The (additional) course settings should be reorganised in such a way, that all settings from the section "additional features" are moved to a new subtab "Settings" --> "Additional Features".
The new subtab should be designed in such a way, that configuration workflows or "second steps" are easier to see and change than it is realised now. Therefore a table should be introduced that works like the table in "Administration" - "Plugins" providing:
- the current Infotext as a description in a column
- a (new) "Status" message for each setting and an "Action" menu button (default: either "activated" or "deactivated", possible more telling info)
- an "Action" menu button with the the options "Activate"/"Deactivate", for some settings "Configure"
In order to make the change of UI easier for experienced users, the space on the "Course settings" page beneath the last section could then be used to s´display the status of the options together with a "Got to settings page" link, just like it is done numerous times in the administration (e.g. course administration)
Here is an exmple with an easy and a more complex option:
Feature | Description | Status | Actions |
Calendar | The ‘Calendar’ block will be displayed inside the ‘Content’ tab. | activated / deactivated | [Actions]v |
News | Activate the news block and/or timeline view. |
| [Actions]v |
Here is the complete table (work in progress :))
Feature | Description | Status | Actions |
Calendar | The ‘Calendar’ block will be displayed inside the ‘Content’ tab. | activated / deactivated | [Actions]v |
News | Activate the news block and/or timeline view. |
| [Actions]v |
Custom Metadata | If activated metadata can be configured. | activated / deactivated | [Actions]v |
Tag Cloud | The ‘Tag Cloud’ block will be displayed inside the ‘Content’ tab. | activated / deactivated | [Actions]v |
Default Object Rating | Rating is activated by default for new files, learning modules and wikis. | activated / deactivated | [Actions]v |
3 User Interface Modifications
3.1 List of Affected Views
{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}
3.2 User Interface Details
![](./data/docu/mobs/mm_60526/Bildschirmfoto_2018-04-27_um_09.57.48.png?il_wac_token=72cf6cd5b0fb3620e800808eed55108c5981ab57&il_wac_ttl=5&il_wac_ts=1725752804)
{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.}
![](./data/docu/mobs/mm_60527/Bildschirmfoto_2018-04-27_um_09.59.48.png?il_wac_token=72cf6cd5b0fb3620e800808eed55108c5981ab57&il_wac_ttl=5&il_wac_ts=1725752804)
3.3 New User Interface Concepts
{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}
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: Glaubitz, Marko [mglaubitz], Universität Freiburg
- 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
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}.
Last edited: 29. Nov 2021, 11:30, Glaubitz, Marko [mglaubitz]