Copy-along Membership Limitations

1 Initial Problem

Application scenario:
In a course, there are groups underlying a ML, so course members can only join one of those groups.
In many scenarios, this allows a controlled way of users allocating themselves to groups (besides MLs, also maximum member numbers and registration deadlines are an important means of control).
Not at the least, groups arising like this can be used to form teams in exercise objects.

Problem:
By now (ILIAS version 6), membership limitations (MLs) on groups aren't copied along when you copy a course.
After copying the entire course, the copied groups aren't part of any ML.
You need to rearrange the MLs which is quite a hustle and will overstrain many users.

2 Conceptual Summary

When copying a course, ML of its groups are copied along, i.e., the copied groups are part of a copied ML.
As this way many MLs with the same name would occur, I suggest those MLs to be renamed like "[original name] - [ref_id of copied course]".
Users may rename the MLs.

3 User Interface Modifications

3.1 List of Affected Views

(none)

3.2 User Interface Details

(none)

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 Privacy Information

(none)

6 Security Implications

(none)

7 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]
• 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

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}

Approval

Approved at {date} by {user}.