Export List of Submissions with Download all Sumbissions

1 Initial Problem

The Exercise is often used for exams or other submissions, where the information about the submissions are important. All Submissions of one Assignment can be downloaded via the button 'Download all Submissions'. This function is the easy way to download and access all submitted files. In addition the ZIP-file can be used to archive the whole Assignment.

Problem: The main information (name, username, date/time of submission) can't be exported/downloaded and are not part of the 'Download all Submissions'.

2 Conceptual Summary

The function of the 'Download all Submissions' shall be extended: At the first folder of the created ZIP-file there should be an Excel-file with all relevant information about the submissions, which have been downloaded. Those are:

• Name
• Login (Username)
• Submitted on
• Deadline (if applicable Individual Deadline)
• Grace Period (if applicable)

3 User Interface Modifications

3.1 List of Affected Views

No Views are affected, only the ZIP-file is to be changed.

3.2 User Interface Details

Example for the Excel-file, which will be created with the 'Download all Submissions':

3.3 New User Interface Concepts

No new User Interface Concepts needed.

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

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}

Privacy

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

Approval

Approved at {date} by {user}.