user is able to select the membership approver

1 Initial Problem

Scenario: a course is available for a larger group (>5000) of people.
Some of them are defined as tutor for this course.
Its important, that there is only one course for all of these users.

Each tutor is responsible for a small group of learners. Each learner should only get approved for course membership by his responsible tutor.

These responsibilties are not represented and independent from the organizational herarchy in org-units.
Only the learner / tutor are knowing their mutual assignment.

There is no possibilty for the learner to select his responsible tutor for approving his membership proposal.

2 Conceptual Summary

There should be a new option for membership-process:

() join directly
( ) join with Course Password
( ) Request Membership
(O) Request Membership from user (user select)
( ) No Self-enrollment


When this option is active, and the learner gains access, he will be asked to select which tutor/administrator of the course should approve his membership request . After clicking "Request membership" the membership proposal is only sent to the selected tutor/admin.

3 User Interface Modifications

3.1 List of Affected Views

• Course Settings
• Course Registration Screen

3.2 User Interface Details

modified:

• Course Settings
• Course Registration

3.3 New User Interface Concepts

n/a

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: Hesse, Joel [Joel_Hesse]
• 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.

• ...

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