Messaging groups in a booking pool

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

Within the ILIAS item: booking pool, you have different slots and different people registering for those slots, forming sort of "groups". Except for copying the User ID in the messaging area of ILIAS, there is (as fasr as I know) no convenient way to message the people that registered for let's say the first slot.

2 Conceptual Summary

One can mark the people withing the booking pool that have booked a certain slot. There you can choose in the drop-down menu, to either cancel the reservation/booking or to delete it completely.
It would be nice, to also be able to choose "message" as additional option in that drop-down menu.

3 User Interface Modifications

3.1 List of Affected Views

• there is only one view, that is affected. The view within the booking pool, when you click on reservations:

3.2 User Interface Details

--> the dropdown element "message" should be added. It should interact with the messaging in ILIAS in a way, that when people are selected and that new option chosen, that the screen changes into the one for creating a message, with the previsouly selected people being automatically placed in the "To" section.

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

3.4 Accessibility Implications

--

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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

ILIAS User ID & Username --> needed because of the switch from booking to messaging

{ 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

--

{ 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: {Müller, Tobias [Tobias246810],Tobias Müller, E-Mail: tobias.mueller@rfh-koeln.de}
• Maintainer: {1st Maintainer: Meyer, Stefan [smeyer], 2nd Maintainer: akill}
• 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

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