Feature Wiki

Information about planned and released features

Tabs

Launcher for Courses and Groups

Page Overview

[Hide]

As background information for this request please consult MOOC-like Look.

1 Initial Problem 

For Courses and Groups the «Info»-tab cannot be switched off.

For Courses and Groups the «Join»-tabis a normal form. This form requires users to provide input and take in some important information before actually starting the interaction with the course content. Having the buttons above the form will fail for the same reason as in the survey bug for Success Criterion 2.4.3 Focus Order. 

«Join» tab

2 Conceptual Summary

«Info»-tab 

  • The «Info»-tab can be switched off in the Settings-tab of respective course or group.
  • If the «Info»-tab is switched off, then no "Info"-Action is not displayed on the outside.
«Join»-tab 
  • The «Join»-tab gets its own permantent link.
  • The «Join»-tab uses a new type of form ensuring the buttons are only displayed at the bottom of the form.

3 User Interface Modifications

3.1 List of Affected Views

  • Course > Settings-tab 
  • Course > Join-tab 
  • Group > Settings-tab 
  • Group > Join-tab 

3.2 User Interface Details

Course and Group settings should be dealt with the same fashion
Entrance Form, Join might even be a primary button

3.3 New User Interface Concepts

UI Component > Input > Container > Form > Entrance Form (new)

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

6 Funding

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

  • …

7 Discussion

Seiler, Yvonne [yvseiler], 16th november 2017: Thanks for this feature request. I like the possibility to show a join page instead of the info page to unregistered users. But I have some problems to understand the labeling of the "Info tab" options:

  1. Always show 'Info' tab: 'Info' will be displayed as tab and action.
  2. 'Info' tab is shown to unregistered users: Tab and action are labelled 'Join' and are displayed only to users that are not yet members. Members will not be presented with this tab.
Option titles
The option titles seems very close to me. I do not get the real difference between both options.

Does the first option (1.) means, that there is no change in the actual behaviour: So everyone sees this info page and there is a separate "Join" tab?
And does the second option (2.) means, that info tab in general is hidden and only unregistered members see this "info" tab but it's now called "Join"?

Suggestions
If yes, perhaps it should be called something like
  1. # Show 'Info' tab
  2. # Disable 'Info' tab for members
Or
  1. # Show to all members and unregistered users
  2. # Show only to unregistered users
Or
  1. # Show 'Info' tab to every user.
  2. # Show 'Join' tab to unregistered users.
Bylines
The bylines describes some "action", but I do not get which action will be addressed in this case.

What action will be called "Info" in the first option (1.)? Or do you mean, the "Join" action would be displayed on the "Info" tab?
For second option (2.) perhaps we could call it "Tab and selfregistration action are labelled...." or something like this.

Tödt, Alexandra [atoedt] 2021-05-20 : Kunkel, Matthias [mkunkel] has volunteered to prepare the Kitchensink for the Entrance Form.

Kergomard, Stephan [skergomard], 2021 Mai 25: Thank you very much for this request. Just one question for clarification, as the print-screens might suggest otherweise: In case you are not a member of the course yet then join-Tab will be shown in the left most position and, if activated, the info-tab in the second. No other tabs will be shown, right? And: I would propose to get rid of the Join-Tab when one is already a member of the Course.

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: 25. Jul 2023, 13:59, Tödt, Alexandra [atoedt]