Fuse tables «Consultation Hours Appointments» and «Bookings»

1 Initial Problem

A usability test in Novermber 2023 produced the finding that the tables "Consultation Hours Appointments" and "Bookings" are

• hard to find
• hard to operate 
• arranged in wrong order

2 Conceptual Summary

• The tables "Consultation Hours Appointments" and "Bookings" are presented in one single table. 
• The secondary panels in the Consultation Hours Appointments "Calendar" and "Calendar Selection" are no longer dispalyed. All available slots and all booked appointments are displayed. The selection via the secondary panels is discontinued. The view control ensures the number of entries is managable.  
• Another View Control ist offered to allow for looking only at booked or open slots.  
• If multiple Appointments per slot are possible. One row is created per person and slot. 
• Open Appointment slots have the Action "Edit Slot", "Assign Users" and "Delete Slot". 
• Booked Appointment slots have the Action "Delete Booking" and "Cancel Booking". 

3 User Interface Modifications

3.1 List of Affected Views

• Personal Workspace > Calendar > Consultation Hours 

3.2 User Interface Details

3.3 New User Interface Concepts

No new elements are used. 

3.4 Accessibility Implications

Since this feature only uses KS elements, we expect no accessibility issues.

4 Technical Information

None.

5 Privacy

No additional personal data is stored compared to today. Today the user data of participant, consulting hour manager and consulting hour owner are stored. 

6 Security

We do not foresee any security relevant changes.

7 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• Maintainer: Killing, Alexander [alex]
• 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.

• …

9 Discussion

JourFixe, ILIAS [jourfixe], 22 JAN 2024: Suggestion is highly appreciated and feature scheduled for ILIAS 10.

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}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.