Sessions relative to course period

1 Initial Problem

Currently, in the settings of a session you can set the start/end date with start/end time. The period of a session is always fixed. If for example the course period changes the date of a session remains unchanged. This means that in a course with many sessions the administrator has to change the date for each session.

2 Conceptual Summary

It would be helpful, if in addition to the fixed date, the settings would include the option “relative to course period”. This option should be optional. Selecting this option course period can change and the sessions adjust automatically. The field "event day" indicates if this session relates e.g. to the first (1) or second (2) day of course period.

Note: In contrast to the mockup above the "Wiederholungen" option will not be available for the "relative option". It will become a suboption of the "fixed date" option.

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

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

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: {scarlino} CaT Concepts and Training GmbH
  
• 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}.