Show Advanced KnowledgeHide Advanced Knowledge

Support of OrgUnits in Tests

1 Initial Problem

Tests should support organisational units for better distinguishing between participants that relate to different departments/faculties/institutions sharing the same courses and therefor also the same test objects. The following use cases are currently not possible:

1. Admin / Tutor can only see test results of those users that belongs to the own org unit (e.g. Tutor from Dep. A sees just test results of learners from Dep. A).
2. Admin / Tutor can only manage test participants that belong to the own org unit.
3. Admin / Tutor can access learning progress only for members of his/her org unit .

Nearly the same considerations as in Support of OrgUnits in courses and groups apply to test settings. The support described there should be extended to test-objects (and potentially to exercise- objects too).

2 Conceptual Summary

When test objects are used in scenarios where different institutions are involved, an important aspect of running the test is to grant access to participants and their data only for tutors of the same institution. All data of participants and the participants themself needs to be hidden for tutors of other institutions.

Within the workflow of running a test there are different use cases that might be done by different actors within the different institutions. The following permissions will be offered for org unit positions:

2.1 View Learning Progress

When access to the learning progress tab is granted due to the org unit position permission View Learning Progress the tab offers the learning progress information for other users only for that users, that relate to the own org unit. The integration behaves the same like known from the integration to e.g. the course object.

2.2 Access to Test Results

The org unit position permission Access Results offers access to the test results of test participants within the results tab. But only those participants are shown, that relate to the own org unit. Additionally access to the statistics tab is granted. But all statistical information is calculated based on only that participants that relate to the own org unit.

2.3 Score Participants

With the org unit permission Score Participants access to the manual scoring tab is granted. Only those participants will be available for scoring that relate to the own org unit. Both ways of manual scoring will be supported (score by participants and score by question).

2.4 Manage Participants

The org unit position permission Manage Participants grants access to fucntionality in the test object at different places.

Participants Test Results

Access to the functionality of removing test results for other test participants within the test results tab is granted. Only the results of those participants that relate to the own org unit can be removed.

Manually Selected Participants

When the test setting Manually Selected Participants is enabled each participant needs to be added to the test by hand. The dashboard tab is available for this purpose and provides the opportunity to add users of the own org unit as participant to the test. Also removing is possible, but again only for the own org unit related users.

Extra Time Feature

When the test is limited in time and can be taken by participants only once, the dashboard tab is available and provides the ability to give extra time to participants that are just running the test. This is possible only for those participants that relate to the own org unit.

3 User Interface Modifications

3.1 List of Affected Views

Screens that are affected due to filtered data:

• Test -> Results -> All Participants
• Test -> Dashboard -> Manually Selected Participants
• Test -> Dashboard -> Extra Time
• Test -> Manual Scoring
• Test -> Statistics
• Test -> Learning Progress

Screens that are affected with new permission:

• Test -> Permission -> Position

3.2 User Interface Details

3.3 New User Interface Concepts

none

4 Technical Information

In general the integeration of an org unit supprt requires an implementation within the test module only. Since additional position permissions are required, some small changes needs to be done within the org unit service. The test maintainer will provide a PR to the org unit maintainer.

The folling org unit position permissions will be added:

• view_learning_progress (reused) - View Learning Progress
• access_results (reused) - Access Results
• score_participants (newly introduced) - Score Participants
• manage_participants (newly introduced) - Manage Participants

5 Contact

• Idea / concept: Kunkel, Matthias [mkunkel], Jackisch, Ingo [jackisch]
• Maintainer: Heyser, Björn [bheyser], Schmid, Fabian [fschmid]
• closely reated to Support of OrgUnits in courses and groups
• Implementation of the feature is done by: Heyser, Björn [bheyser]
• Testcases by: Heyser, Björn [bheyser]

6 Funding

Interest in funding:

• DHBW

7 Discussion

JourFixe, ILIAS [jourfixe], 13 AUG 2018 : We highly appreciate this suggestion and schedule it for 5.4. Please consider also the related SOAP methods (removeTestResults, getTestResults, getTestUserData) and make them OU-sensitive.

2018-10-26, Jackisch, Ingo [jackisch]: To ensure a consistent behaviour of ILIAS, Test, surveys (ond other Position-enabled Objects) should warn teh user when deleting ohter users from the test or when removing test results (etc.). A description of these warnigns is given in: Support of Positions in Surveys

8 Implementation

The integration of this feature has been done according to the descriptions above. A new subtab Orgunit-Specific Permissions has been added to the Permissions tab. This new subtab shows the existing Org Unit Positions and there respective permissions. Globally set permissions can be overwritten per test object.

Note: In addition to the orgunit-specific permissions a user needs to have Visible and Read access within the regular RBAC permissions.

8.1 View Learning Progress of Subordinate Users

This orgunit-specific permission grants access to the Learning Progress tab, but the access to participants is restricted to that participants, that relates to the own orgunit. So the learning progress can be reported for subordinated users only.

8.2 Access Results of Subordinated Users

This orgunit-specific permission grants access to the Results tab as well as to the Statistic tab. The Results tab is again limited to the participants that relates to the own org unit, when access is granted by the orgunit-specific permission. For any statistic the involved participant data is also limited to that participants.

8.3 Score Subordinated Participants

This orgunit-specific permission grants access to the Manual Scoring tab. The Manual Scoring tab is of course limited to the participants that relates to the own org unit, when access is granted by the orgunit-specific permission. Participants of other org units remains hidden.

8.4 Manage Subordinated Participants

This orgunit-specific permission grants access to the Dashboard tab as well as to the Results tab.

Within the Dashboard tab all participants that relates to the own org unit can be added or removed as manually selected participants if the test is configured to be taken by manually selected participants only. Also the extra time can be granted there.

The Results tab offers the functionality to remove existing test results for all participants, that relates to the own org unit.

Test Cases

Test cases completed at 20. August 2018 by Heyser, Björn [bheyser]

• C24645 : Lernfortschritt untergeordneter Benutzer einsehen
• C24646 : Zugriff auf Ergebnisse untergeordneter Benutzer
• C24647 : Untergeordnete Teilnehmer bewerten
• C24648 : Untergeordnete Teilnehmer verwalten: Durchläufe Schließen
• C24656 : Untergeordnete Teilnehmer verwalten: Testergebnisse löschen
• C24657 : Untergeordnete Teilnehmer verwalten: Ausgewählte Teilnehmer und Zeitverlängerung

Approval

Approved at 2018-10-26 by Jackisch, Ingo [jackisch].

...