New task: Requests for membership

1 Initial Problem

Request for membership is a popular registration procedure for courses and groups. But if you are responsible for several courses and groups and you have busy times, some requests stay on the list untouched for unnecessary long time. This is frustrating for all.

2 Conceptual Summary

A new task shall be implemented that points all users who are responsible for registration requests (checkbox 'Notification' set) to open requests. The task should be implemented for all object types that support the registration setting "Request membership" (e.g. course, group) as well as for the user registration procedure "Registration with approval" (ILIAS auth).

2.1 Request for Membership

• Prerequisites for creating task entry:
  • Registration procedure is set to "Request membership" in course / group
  • At least for one user the checkbox "Notification" is toggled in "Members » Edit Participants"
• Presentation of task in Task List (see also below):
  • Task title: "Request for Membership" (Link)
    • Clicking on task title redirects to tab "Members" of related course / group
  • Course / group title
  • Number of users
• Presentation of task in PD widget Task List:
  • (Level 3) "Request for Membership" in {course / group title}, number of users

No implementation of level 1 and 2 necessary due to Abandon Levels of Details and Movability of Side Blocks on PD

2.2 User System Registration (ILIAS auth)

• Prerequisites for creating task entry:
  • Registration type in "Administration » Authentication and Registration" is set to "Registration with approval"
  • At least one user name is added to input "Notifications" on "ILIAS-Auth / Self-Registration » Registration Settings".
• Presentation of task in Task List (see also below):
  • Task title: "Request for Access to ILIAS"
    • Clicking on task title redirects to edit form of related user account in "Administration » User Management" (e.g.: https://test54.ilias.de/goto.php?target=usrf_114187&client_id=test54)
  • User name
  • Date of request
• Presentation of task in PD widget Task List:
  • (Level 3) "Request for Access to ILIAS" and "User name"

No implementation of level 1 and 2 necessary due to Abandon Levels of Details and Movability of Side Blocks on PD

3 User Interface Modifications

3.1 List of Affected Views

• Personal Workspace » Task (according to Default Configuration of Main Bar Items (ILIAS 6))

3.2 User Interface Details

3.3 New User Interface Concepts

none

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: Kunkel, Matthias [mkunkel]
• Maintainer: Meyer, Stefan [smeyer]
• 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

Killing, Alexander [alex], 2 Apr 2019: I changed the maintainer to Meyer, Stefan [smeyer] since the task service only provides an interface. The membership service will be responsible to implement this task.

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