Show Advanced KnowledgeHide Advanced Knowledge

Membership Limitations for Sessions

1 Requirements

It is possible to join Sessions but by now (v5.1.x), you cannot prevent users from joining all Sessions of a Course (or Group).
Often, however, you want people to join one Session out of several ones available in the Course (or Group).

So, it would be helpful to have membership limitations for Sessions, like they’re available for Courses and Groups.

Notifications should be send for all relevant events:

• Participation to session is confirmed
• User is placed on waiting list (including currernt postion on waiting list)
• Removement from waiting list (rejected by tutor)

Independent from the "limitation settings" user are allowed to place themself on waiting list for a session, even if they registered fro another session. However their registration request is handled with lower priority than the the request of users who are not registered for another session.
Administrators always have the possibility to register users manually, independent from the limitation settings.

The presentation of the "Member-Tab" reuse the member administration currently implemented in courses and groups.
The member table will introduce the following filters:

• Members of next upper context (course group in path)
• Registered users
• Participated users

2 Additional Information

• Idea / concept: Suittenpointner, Florian [suittenpointner], Meyer, Stefan [smeyer]
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

Zenzen, Enrico [ezenzen], 04 AUG 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

4 Implementation

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