Test & Assessment: Pseudonymization of names for «manual scoring» view

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

The approach refers to the module "Test & Assessment". Text-based answers of online tests in the test & assessment module cannot be scored pseudonymously so far. For an unbiased scoring of student answers a pseudonymized presentation of results for the correctors would be desirable. Currently, results can only be evaluated in a completely anonymized manner, making them untraceable for the correctors afterwards.

2 Conceptual Summary

In the correctors view for text-based answers, it should be possible to have the names of the participants presented pseudonymized . This could be implemented as follows:

• When starting the manual correction of a test, the list of participants names should be presented pseudonymized in randomized order. Pseudonymization of names should be activated by default but can be deactivated by the corrector. The students' names should only become visible when the status 'scoring completed' for all participants has been reached - or the corrector deactivates pseudonymization manually. If scores are changed afterwards, the originally pseudonymized grade should be noted.

3 User Interface Modifications

3.1 List of Affected Views

• The correctors "Manual Scoring" view for text based answers in the test & assessment module
  

3.2 User Interface Details

List item "student name" should be presented pseudonymized and in a random order when a text based question is selected for correction.

3.3 New User Interface Concepts

Toggle, checkbox or radiobutton (specific pattern tbd) to activate and deactivate the pseudonymization view. The settings should be available either in the list or above it.

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: Max Wirnsberger / Sigmar Papendick (digitale-lehre@uni-konstanz.de)

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