Custom Metadata: Smart(er) date fields

1 Initial Problem

ILIAS right now only offers to types of date fields (in custom metadata), “date” and ”date and time”. But where course for example are created via CampusConnect from the campus management system or in courses sharing scenarios via ECS it is often more interesting to know eg. the weekday a course will take place.

2 Conceptual Summary

We propose to make date and date/time fields “configurably smarter” so that they can be “filled” with a date or date/time (perhaps from an ISO date string via CampusConnect) and configured to show the weekday (eg. Monday) and/or even and interval (every (second) Monday (at 8:00)).

3 User Interface Modifications

3.1 List of Affected Views

Tbd with help of the maintainer.

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: Bogen, Christian [bogen]
• 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}.