Add pdf export option for downloading submission within an assignment

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

After having submitted a portfolio within an assignment one can only download a copy of the submitted portfolio as zip file (i.e. html file). However, experience shows that students feel more comfortable with a pdf file on their local machine.

2 Conceptual Summary

We suggest to add a "Print to PDF" function besides the zip/html download functionality. So, the user can choose whether he/she wants to download the submitted portfolio as zip file or save it as a pdf file.

3 3 User Interface Modifications

3.1 List of Affected Views

• Button "Download Submission" in slate after submission of portfolio within an assignment (no matter if deadline for submission has already been exceeded or not)

3.2 User Interface Details

The additional "Print to PDF" function could for example be realized by a button in the portfolio content view:

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: Weitz, Melanie [mweitz]
• Maintainer: Killing, Alexander [alex]
• 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}.