Adding Recurrence for Timings Settings of Objects

Request related to Revision of Access to Timings Settings of Objects

1 Initial Problem

In the timing area of an object, in this case in reference to a context, it is possible to set a start and end date and time. However, the possibility of creating a repetitive time frame is missing.
Example: I want to make the use of a context and / or a course available only on certain days of the week, during working hours. Or just on weekends.

2 Conceptual Summary

In sessions, it is possible to set a Recurrences so to repeat the same event periodically. The same settings should be available for other objects such as contexts and courses.

3 User Interface Modifications

3.1 List of Affected Views

The views to modify are:

• Availability-section in Form in first Settings-subtab
• "Availability"-Action opened via Action-Menu in List GUI

3.2 User Interface Details

Both the views above should contain the possibility to set a Recurrence, as it already happens in Sessions:

This should take users' time zones into account. If it is not already provided in ILIAS (for example for sessions), then I will need to add another Feature Request.

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 Privacy Information

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Truppa, Ilario [ilario.truppa] - OC Open Consulting srl
• 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.}

8 Funding

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

• OC Open Consulting srl

9 Discussion

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