Metadata for Appointments

1 Initial Problem

Unlike other objects, Appointments are not supporting custom metadata. There are, however, relevant meta-information concerning calendar entries in real live, i.e. types of appointments such as phone call, appraisal or vacation, that we would like to have in a machine readable form.

There are certainly way more (and specific) usecases for metadata at appointments; this is why we would like the metadata to be customizable.

2 Conceptual Summary

In the adminstration section for metadata you can add custom metadata sets and assign them to objects. We suggest the extension of the object list by "Appointments".

On creating / modifying an appointment, metadata fields should be available in the form.

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

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: Nils Haagen, CaT Concepts and Training GmbH (Haagen, Nils [nlz])
• Maintainer: Stefan Meyer, Leifos GmbH (Meyer, Stefan [smeyer])
• 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}.