Introducing the Export functionality of the ExaminationProtocol

1 Initial Problem

The ExaminationProtocol does not yet offer the option to export ExaminationProtocols. As a prerequisite to the interface to the TestArchiveCreator (TAC; https://docu.ilias.de/goto_docu_wiki_wpage_8009_1357.html) we would like to add the opportunity to implement an export.

2 Conceptual Summary

The ExaminationProtocol is supposed to offer a subtab called "Export" which allows the user to create an .html export of the examinationprotocol. This export is supposed to be listed in a table with its corresponding export date and export size just like the export of tests or the test archive creator.

The export of the examinationprotocol is supposed to contain all data that is collected by the examinationprotocol. The downloaded file is a .html file which is called according to the following scheme: examprotocol_<obj-id>_<timestamp>.html

The export will contain the following (here german named) columns: Startzeit des Ereignisses, Endzeit des Ereignisses, Studenten, Matrikelnummer, Ereignis, Beschreibung, Prüfungsraum, Name der verantwortlichen Aufsichtsperson, zuletzt editiert am, zuletzt editiert von, Zeitstempel der Erstellung des Ereignisses, Erstellt von.

When implementing the Interface to the TestArchiveCreator for Exports the examinationprotocol is supposed to create a new export as soon as someone clicks on the "create" button of the TestArchiveCreator.

TODO:

• Column name/matriculationnumber/login (25.01.24: "<lastname>, <firstname> (<matriculation number> [login])". if empty then a place holder is added such as "--" This all is put in one column which is called students/Studierende
• finalizing (in workshop)
• pdf-Export mockups

3 User Interface Modifications

3.1 List of Affected Views

Screenshot 1. The table which shows the different exports from the exam event protocol subtab "Export".

Screenshot 2. The export file of the examinationprotocol. This export file is supposed to contain all data that is saved by the examinationprotocol. Please also add the column "matriculation number" which is not shown in the mockup (which is 12 columns in total).

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

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