Feature Wiki
Tabs
Test: Pseudonymization of Names for Manual Scoring
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
Please note, that an old version of this article, which was outdated, was deleted on 09 APR 2025. Please refer to the history, to view this old article again.
1 Initial Problem
The pseudonymized correction of exam questions increases the objectivity and fairness of student performance assessments, reduces bias and protects the students' identities. Previously, the test could only be used to carry out completely anonymous tests for formative self-assessment scenarios. The anonymous test cannot be used to carry out summative examinations to score academic performance, as the anonymized results cannot be assigned to students by the examiners.
2 Conceptual Summary
The test is to be extended so that test results can be corrected in a pseudonymized manner. In the process of an exam, various actors are usually involved who take care of the organization and creation of exams as well as the correction of exams. To fulfill the requirements of these conditions, we propose the following changes:
- We add a new RBAC right to the test: Score Pseudonymously. The Title within HTML will be: "User can score pseudonymous participants". Users with this right will see the (renamed) Tab "Scoring" and there only the Test IDs of the participants.
- Users with the "Score"-right can score, nothing else. (Right to see everything is: "Edit Settings").
- Users with more rights will see the full data as today.
- Organisational Units: Users have right through superior status over staff and additional RBAC right "Score Pseudonymously" see results etc. from their staff within the test as today and all other users only with Test ID in the scoring tab.
- In existing tests the right are set to deactivated.
3 User Interface Modifications
3.1 List of Affected Views
- Test > Permissions: New right "Score Pseudonymously". By activating the "Score Pseudonymously"-right, the "Scoring" Tab is shown for this role and the personal data is removed and only Test ID of the participants is shown
- Test > Scoring: Tab will be renamed from Manual Scoring to Scoring - Column Test-ID will be added
3.2 User Interface Details
See also the Mockups above. Another Feature Request exists, that proposes the general revision of the scoring, but within this request, we will work with mockups based on ILIAS 10.
- Scoring by Question and Scoring by Participant Tables are only showing the Test ID for users with only "Score Pseudonymously" right. Users with higher-quality rights will see, like today, the personal data of the participants AND the Test ID.
Mockup Tab Scoring with all rights within the test object
Mockup Scoring by Participant Table only with Test IDAlso within the scoring modal, only the Test ID is shown, if one only have the right "Score Pseudonymously":
Analogously, "Scoring by Particpant" and right "Score Pseudonymously":
3.3 New User Interface Concepts
No new UI Concepts are used for this proposal.
3.4 Accessibility Implications
We only use existing elements, so we therefore, we are not assuming any unknown problems.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Strassner, Denis [dstrassner]
- Authority to Sign off Code Changes: Joußen, Thomas [tjoussen] & Kergomard, Stephan [skergomard]
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
This Feature Request is maybe affected by another Feature Request. But not dependent.
4.3 Privacy
No new user data will be saved though this proposal. But great new scenarios are possible.
4.4 Security
no changes
4.5 Contact
Person to be contacted in case of questions about the feature or for funding offers: Gerl , Stefanie [stefanie.gerl] & Strassner, Denis [dstrassner]
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
5 Discussion
Kunkel, Matthias [mkunkel], 22 APR 2025: I see the need to support pseudonymized tests and I am sure it is a good feature for ILIAS. But I am not convinced of the suggested way to realise this by adding a permission for a very specific scenario. Let me explain:
I see pseudonymizing participants as a specific property of a test in ILIAS. It is mainly needed in e-exams (or other types of summative assessments) where the answers of test participants are scored and the correctors should not know the participant's identity in order to remain impartial.
But if we consider a test with pseudonymized participants as a specific type of test, I would expect a distinct setting for realising this scenario – and not an implicit permission.
And why should we support two kinds of (manual) scoring within one test – one where correctors see only pseudonymized participants due to the given permission 'Score Pseudonymously" and one where correctors see clear names because they have "Edit Settings" permission? I would assume that pseudonymization is affected to all persons who have access to the (manual) scoring of participants.
Why don't we introduce a new permission "Score manually" that is required to get access to the "Scoring" tab and allow to change given points. This permission is independent from "Edit Settings" (so Edit Settings no longer gives access to the Scoring tab). When upgrading ILIAS, a migration script can set these permissions in all existing tests for roles with 'Edit Settings'.
If this permission is given in combination with a setting 'Pseudonymized Scoring', all test participants appear with pseudonym and an objective and fair assessment of the test is ensured.
A combination of a setting with a permission makes it much clearer to users what happens within such a configured test.
6 Implementation
Feature has been implemented by {Please add related profile link of this person}
6.1 Description and Screenshots
{ Description of the final implementation and screenshots if possible. }
6.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
6.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
6.4 Approval
Approved at {date} by {user}.
Last edited: 22. Apr 2025, 15:16, Kunkel, Matthias [mkunkel]