Feature Wiki
Tabs
«Manage Members» in Organisation
Page Overview
[Hide]- This request is a part of a number of features for Better Support for Vocational Training
- A Feature Workshop was held on this request on August, 17th 2020 In the workshop some requests were made that are not dealt with in this Feature but were already adressed in other articles:
- Improved Request Membership Screen allows for making the message 'required'.
- There seems to be a need for superiors enrolling employees in courses without the help of course admins
- The number of denied requests of a user should be on record as laid out in the enrolment log of a user as described in Membership History
- A plugin-slot would be much appreciated.
- Neuer Reiter "Join Request" in Staff wird angezeigt, wenn
- für Benutzer der eigenen Orgunit Position Manage Member
- für alle Benutzer RBAC Manage Member
- In diesem Reiter kann man Wartelisten bearbeiten
- Mitglied bekommt eine Mail, Kursadmin bekommt eine Mail, Task erstellen
- Angabe des Kurses in der Tablle im Mock-up fehlt.
- die Tabelle der Warteliste soll gefiltert werden oder nicht, wie im Kurs
- Die Tabelle ist die selbe wie im Kurs. Sie wird um die Spalte "Kurs" erweitert, welche im Kurs nicht angezeigt wird.
- "Mail versenden" aktion läuft über die Membership GUI Die Membership GUI wird refactored, sie Abhängigkeiten zu den Objekttypen (Gruppe, Kursm Sitzung, Studienprogramm) werden verringert
- Membership Service konfigurieren, z.B. Member Gallery deaktivieren
- Neuer Reiter "Join Request" in Staff wird angezeigt, wenn
- für Benutzer der eigenen Orgunit Position Manage Member
- für alle Benutzer RBAC Manage Member
- In diesem Reiter kann man Wartelisten bearbeiten
- Mitglied bekommt eine Mail, Kursadmin bekommt eine Mail, Task erstellen
- Angabe des Kurses in der Tablle im Mock-up fehlt.
- die Tabelle der Warteliste soll gefiltert werden oder nicht, wie im Kurs
- Die Tabelle ist die selbe wie im Kurs. Sie wird um die Spalte "Kurs" erweitert, welche im Kurs nicht angezeigt wird.
- "Mail versenden" aktion läuft über die Membership GUI Die Membership GUI wird refactored, sie Abhängigkeiten zu den Objekttypen (Gruppe, Kursm Sitzung, Studienprogramm) werden verringert
- Membership Service konfigurieren, z.B. Member Gallery deaktivieren
1 Initial Problem
Oftentimes in vocational training taking part in a course actually lies not in the sole discretion of the prospektive learner nor can the course's administrator decide. The decision about taking part in a course lies with the learner's superior or HR. This need for approval is currently not reflected in ILIAS.
2 Conceptual Summary
Activate "Additional Approval" in global Administration
- In Organisational Units in the Administration if Positions in Courses are activated, administrators can activate that a new option is offered for "Request Membership".
- This is mirrored in Administration > Courses with an "Edit Settings" Link
- In Course > Settings a sub-option is offered for the request to be sent to the superior to be signed off first.
- If activated the "Request Membership"-Message is sent to Superior instead of to Course Administrator.
- Superior gets the "Request Membership"-Message per Mail.
- Superior is presented with the Request in Staff > Enrolments on top of the table.
- Superiors can decide upon the request. They can send a message to the employee to communicate their decision.
3 User Interface Modifications
3.1 List of Affected Views
- Administrations > Organisational Units > Settings
- Administrations > Course > Settings
- Course > Settings
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: Tödt, Alexandra [atoedt]
- 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
Bromberger, Norbert [bromberger] May 10, 2019.
I support this idea. From my experience, with this extension, more than 80% of customer requirements can be covered in the direction of booking processes.
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}.
Last edited: 2. Aug 2024, 16:16, Elagamy, Ahmed [Ahmed]