Refactor Session Participant Class & consistent with course and group

This feature request is a part of the Calendar Revision III.

Relationship to Set Registered Attribute for Registration Procedure No Registration Necessary exists

1 Initial Problem

Courses, groups as well as meetings offer the possibility to register or join. They have similar effects, but there are differences in both the interface and the technical background that need not be.

The session settings in the "Registration Settings" section should be adjusted to match the settings of courses and groups.

2 Conceptual Summary

For the sake of user-friendliness, settings that already have the same title should have the same effects and be called the same. Then a learned pattern (e.g. course) can be easily applied to new places (here session).

2.1 Requirements

For Session Settings "Registration Settings" there should be some adaptations:

1. Add a "No Self-enrolment" option
2. Give as similar titles as possible
3. Adapt the sorting

2.2 New Option "No Self-enrolment"

Only administrators or interfaces has the possibility to registrate users as "Session Participants".

3 User Interface Modifications

3.1 List of Affected Views

• Session > Settings
• Session > Info
• Session > Participants
• Session > Permissions?

3.2 User Interface Details

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: Seiler, Yvonne [yvseiler] (Universität Bern)
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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.

• Universität Bern

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