Add Test PRIVACY.md

[slowe47]

Hi @selyesa,

this PR is our proposal for the Test PRIVACY.md to the state code of ILIAS 11.

Please have a look at it.

Thanks a lot & best regards
Simon

[slowe47]

Hi @selyesa & @atoedt,

with my last change I have replaced "user" by "account" and added some more purposes for storing/exporting personal data. I did not add the path at the different sections, because all sections and section titels are already based on tabs and subtabs of the Administration or Test.

Best regards
Simon

[selyesa]

Could you provide a summary table like the one in Learning Sequence?

[slowe47]

Do you mean only for the Log Data (marked lines) or for the whole component?

[selyesa]

See here as an example: https://github.com/ILIAS-eLearning/ILIAS/blob/trunk/components/ILIAS/LearningSequence/PRIVACY.md

[slowe47]

Yes, I know what you mean, but do you want this table for the whole Test component or only for the Log Data? I have this question, because you created this comment at the lines for the Log Data.

In general I can try to provide a summary as table, but I think at the Test component there is a few more data and the configuration is more complex. We will have to check if there is enough time for that left.

[atoedt]

Please include some information about the concept of test attempts, the range of meaning of test taking and the respective required depth of logging.

The test implements several important concepts:

• Participants are accounts that take the test. Participants might take a test without logging into the platform as the user Anonymous. Participants might take a test set to "Results without names". Participants might take a test set to "IP- Range" allowing only participants with a device in that range starting the test, addionally their IP might be logged.
• Questions are created in Test Questions Pools or Tests, always drag along the full name of author to allow for quality assurance and topical clarification. Opening a question, providing answers and authorising an answer, scores by participants is stored within Tests and in Test Question Pools.
• Tests comprise questions and are administered to participants. A participant working through a test is an Attempt at taking it. Attempts may be limited and a test can be set so that named participants can use their answers from previous attempts or delete them. Each attempt is stored and scored separately. For didactical considerations a Waiting Time between attempts can be set as required. Participants are presented with their own results according to the settings of the test.
• Permissions in Tests allow configuring what a account administering the test can do: an account with "Edit Settings" can make changes to test settings, several settings cannot be changed after the test has started specifically the privacy settings. "Score anonymously" allows for blinded manual scoring. "Test Results" provides access to the test results of participants. "View History" provides access to a very detailed log of interactions of accounts with the test.

Typical Purposes of Tests
Some test offer participants rehearsing subject matter by interacting with questions. Some tests are intended to measure the mastery of subject matter of participants and might serve as a precondition for starting the next object. High stakes exams require heightened control over the identity of the participant. Exam View activated and Show Name of Participant is activated, too.

Logging of Tests that Might be Challenged in Courts
At times high stakes exams are contested in courts. Courts have required a detailed log of interactions with the test and its respective individual questions. The History service provides this information on creating and editing of the questions (Test administration Interaction) as well as participants interaction with the questions (Participant Interaction).
High stakes exams are recommended to be administered on a dedicated exam platform, separate from the instructional platform, where everyday learning takes place. Taking exams on a separate platform allows for preparing a court-proof environment, however it makes shuttling test results between platforms necessary.

[selyesa]

Maybe more general, like this:

Logging of Test Interactions
The History service may log interactions related to the creation, administration, and participation in tests. This includes actions performed when creating or editing questions (test administration interaction) as well as participants’ interactions with questions (participant interaction).
Tests may be administered on a dedicated examination platform that is separate from the instructional platform used for everyday learning activities. In such scenarios, transferring test results between platforms may be required.

[slowe47]

Within the next commit I have added a short section about the usage of the test component. From my point of view, the PRIVACY.md is not the document for explanations about the functionality of the test.

At https://github.com/ILIAS-eLearning/ILIAS/blob/trunk/docs/development/how-to-write-a-privacy.md it explicit says, that terms as 'Participants' should be avoided. Therefore I have removed those and only used the permissions of the component.

Because a general information about the component is surely useful, I do not want to end the discussion at this point - from my point of view it should be continued at another place.

[slowe47]

Hi @selyesa & @atoedt,

thanks a lot for your feedback and your improvement approaches.

With my last commit I have worked through the whole feedback in github and the discussions at our meeting. I hope to have found a good solution between the different approaches, so that the document in general is a bit more compromised, but also has a structure.

I did not remove all tabs as sections, because from my point of view sometimes they are needed for having a bit of strutcture, but I have grouped a lot of sub-sections together, which were very short.

At the most of the sections there are no more lists but text, only where a lot of fields are relevant I would like to leave the lists as they are in order to have a structured overview of the fields.

In any section the path to the described tab is mentioned.

Additionally I have linked all integrated components (if there is no PRIVACY.md just the component is linked) and just left a description, if something particularly is needed to be documented for the Test component.

I would appreciate merging this version of the PRIVACY.md, except if we want to add a summary as discussed at #discussion_r3223870713. I propose to discuss the integration of general functionality documentation and configuration recommendations of those complex components at another place.

Best regards
Simon