Feature Wiki
Tabs
Bulk Actions for Exercise Assignments
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 2.1 RFC 2119
- 2.2 Requirements
- 3 User Interface Modifications
- 4 Technical Information
- 5 Privacy
- 6 Security
- 7 Contact
- 8 Funding
- 9 Discussion
- 10 Implementation
1 Initial Problem
Since ILIAS 6 assignments in exercises can be randomly assigned to participants: Randomized Assignments. In this mode all assignments will typically have the same schedule to avoid putting some students at a disadvantage. During a semester tutors will sometimes need to update the schedule for all random assignments. Currently this can only be done per assignment which quickly becomes tedious.
2 Conceptual Summary
2.1 RFC 2119
In order to provide a clear understanding of the importance/relevance of a requirement we use the following keywords as described in RFC 2119:
- MUST, MUST NOT
- REQUIRED
- SHALL, SHALL NOT
- SHOULD, SHOULD NOT
- RECOMMENDED
- MAY
- OPTIONAL
2.2 Requirements
An option to set the schedule for marked assignments is added to the bulk action of the assignments table. A schedule set this way is applied to all selected assignments.
3 User Interface Modifications
3.1 List of Affected Views
- Exercise / Assignments / Edit
3.2 User Interface Details
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
No additional / new data required for this request.
6 Security
No implications.
7 Contact
- Author of the Request: Sesterhenn, Fabian [sesterhenn]
- 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.}
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}.
Last edited: 11. Apr 2022, 11:00, Sesterhenn, Fabian [sesterhenn]