Manage Instruction Files in assignments

1 Initial Problem

Creating and editing an assignment are different as far as the use of instruction files is concerned: When creating an assignment, files can be stored in the form in section Work Instructions. These are then stored in a separate tab "Instruction Files".
If an existing assignment is edited, these instruction files can no longer be uploaded/edited directly in the form in section Work Instructions, as was the case when the assignment was created. The users only find their way to the new tab "Instruction Files" late.

The aim is to make it possible to manage files directly from the form, where work instructions have already been stored when creating the form.

2 Conceptual Summary

The KS element File Field Input is to be used in the form to upload Work Instruction Files.

As before, the files are saved and displayed directly in the "Instruction Files" tab. In the form in the "Work Instruction" area, the File Input field remains, even if one or more files have already been stored.

An additional link indicates that files are already available. If you click on this link, you will be directed to the tab "Instruction Files".

3 User Interface Modifications

3.1 List of Affected Views

• Exercise > Assignments > Button "Add Assignment" > New Assignment > Section "Work instructions"
• Exercise > Assignments > Actions "Edit" > Edit Assignment > Section "Work instructions"

3.2 User Interface Details

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: Seiler, Yvonne [yvseiler] (Universität Bern)
• 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.

• Universität Bern

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