Test: General Revision of Manual Scoring within Removing LUI

1 Initial Problem

This FR documents the revise of the ILIAS Test Manual Scoring during the Removing of Legacy-UIComponents-Service and Table project. We need to remove this legacy tables and want to revise also the concept of manual scoring the answers of the participants.
We discussed a concept based on the Sequence Navigation at the SIG EA Meeting in Düsseldorf in autumn 2024 presented by Engländer, Ferdinand [fenglaender] from CaT.

. 

2 Conceptual Summary

We propose to introduce the Sequence Navigation to the Scoring Tab to both "Scoring by Question" and "Scoring by Participant". But with the use of the Squence Navigation we do not need the subtabs. Both options are accessible with the sequence navigation. We remove the use of tables and expand the filtering options.

The Sequence Navigation itself describes how this should work: "The Sequence Navigation is used to move through a series of content segments in a particular order. Segments (or the amount of) may change during navigation, however, they will remain in a consecutive order." We move from either question to question or participant to participant. Also, we compose a view with all questions on one page: then we move from participant to participant. Or all participants on one page, then we move from question to question.

3 User Interface Modifications

3.1 List of Affected Views

This views will be removed:

3.2 User Interface Details

3.2.1 Filter

The new filter will have the following values:

Mockup

3.2.2 Sequence Navigation

The Sequence Navigation will use the "Back" and "Next" buttons to navigate through the segments of questions or participants. The concrete representation of the chunk can be controlled by the view control "Participant oriented" / "Question oriented". A second view control will control if the questions or participants are presented "All" on one page or "One by One".

If "Participant oriented" is chosen, the participant data (name [username], number of the scored test attempt, info "marked as 'scored,'" and the Test ID) is shown beside the view controls (large screens) or below (smaller screens).

If "Question oriented" is chosen, the question title is shown and the question text can be folded out.

Mockup

Participant oriented - All 

If participant-oriented selection is chosen, a button, "Mark as 'Scored Participant'", is presented to set this marking.
Below that, the questions are presented as additional segement. Every question can be graded with a click on a "Grade" button, which opens a modal. 

This setting allows all questions from a single participant to be answered. Clicking on "Next" takes you to the next participant.

Mockup

Participant oriented - One by One

Unlike “All,” this setting displays one question per participant at a time. The scoring per question is done directly on the page. The Markdown editor for the feedback is also displayed. The "Next"-button moves you trough all questions from one participant. Afters that, the first question of the next participant is shown. And so on. The button "Mark as 'Scored Participant'", is also shown.

The status of scoring, points, and feedback has to be saved with the "Save" button before moving on to the next question, according to the rules for the Sequence Navigation.

Mockup

Question oriented - All

If question-oriented selection is chosen, the first sement displays the question title and question itself. Below that, a segment with the answers of a participants are shown. Grading is possible after a button click ("Grade"), which opens a modal. Eachs answer-segment will also show the data of the participant as described above.

Clicking on "Next" will open the next question from this test.

Mockup

Question orented - One by One

Unlike “All,” this view displays one participant per question at a time. The "Next"-button moves you trough all participants, which have answered this question. After that, the next question is shown. And so on.

Mockups

In every view, the segments show who has completed the scoring and when.

Mockups

Modal to Grade

The modal to grade, which opens after the button click, shows on the left side the data of the participant and below that, the answers the participant has entered or selected.

On the right side, the input for the points, the markdown editor for the feedback, and the checkbox for the 'scoring completed' mark are shown.

In the upper right corner, a "Save" and "Close" button are used to either save the inputs and close the modal or close the modal without saving.

Mockup

3.3 New User Interface Concepts

We use the new Sequence Navigation, which is already part of the UI Kitchen Sink.

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

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

4.3 Privacy

No additional personal data are stored with this feature request.

4.4 Security

No changes within security.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers:  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

6 Implementation

Feature has been implemented by CaT: Haagen, Nils [nlz] & Engländer, Ferdinand [fenglaender].

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}

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

6.5 Accessibility Implications