• last updated 7 hours ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix typo

Fix the case of the last comment

Improve performance of delete operation

Behavior reform:

now commenting an artifact won't be considered as "OK". To flag an artifact as "OK" or "for review", one has to explicitly click on the green and red buttons.

  1. … 2 more files in changeset.
Implement buttons to set all artifacts for a user as ok or not ok

  1. … 6 more files in changeset.
file review-all.tcl was initially added on branch oacs-5-10.

Notify new revisions on a proctoring artifact on the object's websocket, in a way that the users list, already designed to refresh in case on messages, will display new information when the revision is proceeding

Store the string "false", not the boolean false

Normalize the way the flag is represented in the JSON

Significant improvements on the proctoring display UI to help the review process of proctored artifacts:

- user can flag artifacts as OK or to be reviewed

- user can add and delete comments on the single artifacts

- user can filter artifacts by "verified/not verified" "flagged/not flagged" and "all". A counter is displayed showing how many over the total number are being displayed

- interface will update as before when new pictures come in from an ongoing exam

- interface has been designed "mobile first" and with minimal, mostly graphical dependencies, to Bootstrap

  1. … 6 more files in changeset.
file review.tcl was initially added on branch oacs-5-10.

Port the downstream only websocket enpoint

  1. … 2 more files in changeset.
file websocket.tcl was initially added on branch oacs-5-10.

file websocket.adp was initially added on branch oacs-5-10.

Provide a showcase example of proctoring: admins will see the UI to examine results, regular users will start a proctored session

might be extended in the future

file display.adp was initially added on branch oacs-5-10.

file proctored-index.adp was initially added on branch oacs-5-10.

file index.tcl was initially added on branch oacs-5-10.

file index.adp was initially added on branch oacs-5-10.

file display.tcl was initially added on branch oacs-5-10.

Introduce a data model for "proctoring artifacts", aka the pictures

and audios, which so far have only lived as files in the filesystem

named after a convention

The new datamodel allows to quickly and reliably retrieve the pictures

collected by proctoring and also provides for a technical space, in

form of a JSON metadata column, to store additional information coming

from e.g. postprocessing phases.

The idea is to use this feature to provide reviewing tools of proctoring results and allow for flexile downstream postprocessing.

The file naming convention has not been changed for the time being, so this would be

retro-compatible. However, integrators should start relying on the new

data model to retrieve pictures.

  1. … 8 more files in changeset.
Trap errors happening when taking the picture, potentially dependent on the specific hardware/sowftware setup of the user, and abort the session in this case

added support for optionally turning off proctoring recodings

This options is useful e.g. for e.g. mock exams to avoid privacy issues.

  1. … 8 more files in changeset.
improve spelling

  1. … 1 more file in changeset.
Now that the proctoring display UI has been ported, notify by default new proctoring events via websockets

  1. … 1 more file in changeset.
Do not handle 400 responses in any special way: cases found in practice were always the result of a client-side timeout

Hide timing information from the user

Streamline proctoring upload:

- do not hardcode a timeout, requests will either complete or eventually fail

- use a single event handler at the end of the request to decide if and how to reschedule the upload. This prevents the possibility that the same error event triggers multiple uploads via different handlers

- improve documentation

Make sure that in case of errors that are also detected as timeouts, we do not reschedule the failed picture twice

Address a problem encountered already with proctoring uploads: in cases that count both as timeouts and errors, the rescheduling of the request would happen twice. If the condition persists, the number of requests can grow out of control