Study Programme: Bulk Change of Required Points

1 Initial Problem

Study Programmes allow to define "Individual Plans" for assignments.
Often, a substantial subset of assignments is supposed to have the same "individual" plan, e.g., with onboarding programmes in companies:
There are 100 new employees who have to work through the onboarding programme but 30 of them have a job profile that doesn't require an entire branch of the programme.

You can very well declare this branch "irrelevant" for those 30 new employees, however, you still need to change the points required from them in the overall programme.
Example:

• Overall programme requires 100 points.
• Five branches exist delivering subsets of those 100 points, e.g., 20, 30, 40, 10 and 10 (where both of the latter ones are exchangeable as you can complete the overall programme by the other branches and one of those latter ones).
• The first branch (20 points) is irrelevant for the abovementioned subset of assignments, so they cannot achieve those 20 points.
  So, you need to reduce the required points of the overall programme to 80 for them.

By now (v9), this can only be done for each single assignments separately.

2 Conceptual Summary

A new bulk action "Change Required Points" is introduced.
Having selected assignments and started the action's workflow, a field is presented that allows to state the new number of reuired points in the programme node currently edited.

3 User Interface Modifications

3.1 List of Affected Views

• "Edit Assignments" view in the "Assignments" tab
• new intermediate view for stating the number of required points

3.2 User Interface Details

• "Edit Assignments" view in the "Assignments" tab:
  Additional menu option "Change Required Points"
• New intermediate view for stating the number of required points:
  • Field "Required Points" (input type "number") is presented.
  • Field accepts value > 0 and denies saving with a warning in case other values are selected or entered.

3.3 New User Interface Concepts

none

3.4 Accessibility Implications

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

none

6 Security

none

7 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]
• Maintainer: Klees, Richard [rklees]
• Implementation of the feature is done by: Klees, Richard [rklees]

8 Funding

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

• CaT Concepts and Training GmbH

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}

Privacy

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

Approval

Approved at {date} by {user}.