Shared Calendar Permissions information

1 Initial Problem

When opening a calendar there is no information about permissions.

Users can be confused, when located in a calendar view (month, week...) they want to create an event but the current calendar is not listed in de dropdown. This is happening because they have only read permissions for this calendar.
If they do not see that in the dropdown they will create this event in the "Personal Calendar" not in the current calendar.

The situation could be worst if user "A" shares with read-only permission the calendar "Personal Appointments" with user B. User "B" visits user "A" "Personal Appointments" and click on one of the (+) icons to create an event. The dropdown will show the option "Personal Appointments". He saves the event but can not see it in the current calendar.
He does not see the new event because it was created in user B "Personal Appointments" calendar not in the current calendar from user "A"

2 Conceptual Summary

Option 1: Hide all the create event options for the calendar because is read only.

Option 2: Indicate somewhere that the calendar is read only. (info message)

Option 3: Additionally, provide the name of the owner somewhere in the view.

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:
• Maintainer: 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}.