Show Advanced KnowledgeHide Advanced Knowledge

Membership Limitation

1 Initial Problem

it is corruently not possible to create a membership limitation rule which allow users to join n out of m courses / groups, but only 1 out of n. We have some scenarios in which users can freely choose 3 groups to join out of a set of 45 groups.

2 Conceptual Summary

The feature should be more flexible. It should be possible that users select not only 1 of n groups, but also x of n groups. The current workflow for creating a membership limitation should be improved and made easier to understand. Similar to other complex workflows in ILIAS, this process should be realised as a multi-step-wizard-workflow.

1. Hit "Membership Limitations" to start the workflow
2. Create a new limitation (see below for editing an existing one)
3. Enter a name for the limitation, maybe also a description and save
4. Assign one or more courses / groups to this limitation (instead of a list of all courses / groups it is better to show at first only the objects at the node of current object. Usually, other courses or groups which are part of such a membership limitation are in the same category as the one you are editing)
5. Save the settings.

ad 2: Instead of creating a new limitation, one might want to change an existing one. In this case the wizard is continuing with step 3.

1. Hit "Membership Limitations" to start the workflow
2. Create a new limitation (see below for editing an existing one)
3. Enter a name for the limitation, maybe also a description and save
4. Assign one or more courses / groups to this limitation (instead of a list of all courses / groups it is better to show at first only the objects at the node of current object. Usually, other courses or groups which are part of such a membership limitation are in the same category as the one you are editing)
5. Save the settings.

 
ad 2: Instead of creating a new limitation, one might want to change an existing one. In this case the wizard is continuing with step 3.

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

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

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Kunkel, Matthias [mkunkel], Glaubitz, Marko [mglaubitz]
• Maintainer: Meyer, Stefan [smeyer]
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

AK, MK 12 Dec 2011: We highly appreciate the idea.

JF 2012-09-03: Feature postponed to 4.4 due to missing time / beta deadline.

MW 25 Jun 2015: We thought this feature had already been implemented, but unfortunately not. Why is it listed as implemented in 4.4? This feature is really a good idea and some of our teachers already asked for the possibility that users can select x out of n groups/courses instead of 1.

Kunkel, Matthias [mkunkel], Jan 05, 2016: This feature has not been implemented yet. Facing Miriam's posting it looks as if there is still an interest in this feature. Therefore I suggest it for 5.2. But funding is needed to implement the feature.

Zenzen, Enrico [ezenzen], 03 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.

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

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.