Equal Folder Structure in Submissions Download and Feedback Upload

1 Initial Problem

In Exercises, you can download all submissions made by participants, receiving a zip archive with a folder for each participant.
On the other hand, you can upload feedback files to all participants and, to that purpose, download an empty folder structure in a zip archive.

Unfortunately, you cannot use the zip archive received while downloading submissions in order to upload feedbacks, and that's because the folder structure for uploading feedbacks is featuring an additional folder level on top (which doesn't exist in the zip archive received while downloading submissions).

This should be eliminated as the entire feature complex looses a lot of usefulness this way:
Trainers are using it when they are going to enter a situation without or with poor or expensive internet connection, like travelling in a regional train. They should be able to check the participants' submissions and put their feedback right into the same folder or even into the submission file itself. With internet connection available again, they should be able to just zip the material and upload it.
In the way it's like now, trainers need to download the correct folder structure and sort their feedback files correctly from the originally received folder structure into the other one, or they have to insert a folder level above the existing ones.

2 Conceptual Summary

The folder structure should be the same in both downloading submissions and uploading feedbacks.

3 User Interface Modifications

No screen involved.

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 Contact

• Author of the Request: {Please add your name.}
• 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.}

6 Funding

Originally, I reported this as a usability bug (https://ilias.de/mantis/view.php?id=20597).
If any possible, I'd suggest this for the community's streamlining efforts.

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

• …

7 Discussion

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