Update user-docu
|
@ -11,7 +11,7 @@ meeting rooms, instruct connected SEB clients to join a certain meeting room. SE
|
|||
allowing connected SEB clients to receive audio and video as well as enabling chat functionality.
|
||||
|
||||
.. note::
|
||||
This feature is still in a prototype state and not all functionality meight work as expected. Basically the meeting features
|
||||
This feature is still in a prototype state and not all functionality might work as expected. Basically the meeting features
|
||||
are given or restricted by the meeting service that is used and the API and GUI that is given by that meeting service client
|
||||
|
||||
To be able to use the integrated live proctoring feature with SEB and SEB Server you need an external meeting service that can be used by the SEB Server to automatically create meetings.
|
||||
|
@ -35,7 +35,29 @@ the external meeting service. SEB Server will then try to connect to the meeting
|
|||
Within the "Collecting Room Size" field you can define the number of maximal participants that shall be collected within one proctoring room. SEB Server will automatically
|
||||
create these collecting rooms while SEB clients are connecting to the running exam in the monitoring view.
|
||||
|
||||
After you have all the settings set, use "OK" to confirm the settings. SEB Server will then try to connect to the meeting service with the given settings and check the access.
|
||||
.. note::
|
||||
If you choose Zoom as your proctoring service and you also want to conduct your exam with Mac and/or iOS SEB Clients you will also need a Zoom SDK-Key and -Secret since SEB Mac/iOS uses Zoom SDK for proctoring integration.
|
||||
|
||||
Scroll down the Proctoring Settings window to see more settings for SEB Server based proctoring features:
|
||||
|
||||
.. image:: images/exam/proctoringSettings2.png
|
||||
:align: center
|
||||
:target: https://raw.githubusercontent.com/SafeExamBrowser/seb-server/master/docs/images/exam/proctoringSettings2.png
|
||||
|
||||
- Use Zoom App-Client: Enable this setting to use a Zoom App/Desktop client for the origin proctoring room. This needs an existing Zoom Desktop App installation on the proctor's desktop.
|
||||
- Broadcasting Feature: Enable this to see the broadcasting features buttons in the opened proctoring windows. E.g. "Enable/Disable Audio" and "Enable/Disable Video" buttons.
|
||||
- Chat Feature: Enable this to see the "Enable/Disable Chat" feature buttons in the opened proctoring windows.
|
||||
- One to One Room: Enable this to see the One to One Room feature button during an exam monitoring within a SEB Client detail view
|
||||
- Town-Hall Room: Enable this to see the Town-Hall Room feature button in the exam monitoring view
|
||||
|
||||
To read more about this proctoring features, please have a look at `Exam Monitoring <https://seb-server.readthedocs.io/en/latest/monitoring.html#live-proctoring>`_.
|
||||
|
||||
After you have all the settings done, use "OK" to confirm the settings. SEB Server will then try to connect to the meeting service with the given settings and check the access.
|
||||
|
||||
.. note::
|
||||
Once a proctoring service is integrated for an exam, it is currently not possible to switch it to another service anymore.
|
||||
This is because different services needs different meeting reference data on SEB Server and there is no conversion supported.
|
||||
In the future we will make it possible to at least delete a already existing proctoring setup and to start from scratch.
|
||||
|
||||
The SEB client settings for proctoring can be found in the "Exam Configuration" "SEB Settings". There is a new tab with the name "Proctoring" where all SEB settings for proctoring are available.
|
||||
These settings are directly used by a SEB client that supports the proctoring feature. SEB will initialize with this settings when connecting to SEB Server and also will use this settings as default settings during an exam.
|
||||
|
@ -45,10 +67,10 @@ These settings are directly used by a SEB client that supports the proctoring fe
|
|||
:target: https://raw.githubusercontent.com/SafeExamBrowser/seb-server/master/docs/images/exam/proctoringSEBSettings.png
|
||||
|
||||
Since SEB Server version 1.2 there is also an Zoom service section that let you define the default SEB settings for a Zoom proctoring setup.
|
||||
Please be aware that not all of the settings are functioning yet. Please refer to the the settings tooltip to get a actual description of
|
||||
Please be aware that not all of the settings are functioning yet. Please refer to the the settings tool-tip to get a actual description of
|
||||
a particular SEB feature setting
|
||||
|
||||
**Jitsi Meet***
|
||||
**Jitsi Meet**
|
||||
|
||||
To setup and configure a Jitsi Meet service for testing you can refer to the `Docker installation documentation <https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker>`_
|
||||
|
||||
|
|
Before Width: | Height: | Size: 66 KiB After Width: | Height: | Size: 51 KiB |
BIN
docs/images/exam/proctoringSettings2.png
Normal file
After Width: | Height: | Size: 67 KiB |
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 69 KiB |
Before Width: | Height: | Size: 94 KiB After Width: | Height: | Size: 78 KiB |
|
@ -21,9 +21,9 @@ exam administrator of your institution to get help and check if you are correctl
|
|||
To monitor an exam either double-click on the list entry of the exam or select the list entry and use the "Monitoring" action form the
|
||||
right action pane to navigate into the main page of exam monitoring.
|
||||
|
||||
On the the main page of exam monitoring you find a list of all SEB client connections that has been connected to the exam since the
|
||||
exam is running. There are some filter switches on the right action pane that may hide some canceled and/or closed SEB connections but
|
||||
you should see at least all active connections instantly.
|
||||
On the the main page of exam monitoring you find a heat-map list of all SEB client connections that are connected to the exam since the
|
||||
exam is running. There are state filter switches on the right action pane that allows to show/hide SEB client connection of specified states.
|
||||
As default you should see at least all active connections instantly.
|
||||
|
||||
.. image:: images/monitoring/examMonitoring.png
|
||||
:align: center
|
||||
|
@ -33,12 +33,32 @@ The list is automatically sorted in the way that SEB connections with incidents
|
|||
"User Name or Session" identifier criteria. The general SEB client connection attributes are:
|
||||
|
||||
- **User Name or Session** The user account or user session identifier sent by the LMS to the SEB client and from SEB client to the SEB Server. This identifier may vary depending on the LMS that is involved. For Open edX it is the user account identifier (username).
|
||||
- **IP Address** The IP address of the device the connected SEB client is running.
|
||||
- **Status** The status of the SEB client connection.
|
||||
- **Connection Info** The IP address of the device the connected SEB client is running plus some additional information about the operating system and the SEB version.
|
||||
- **Status** The status of the SEB client connection.
|
||||
|
||||
This general attributes are followed by the indicator attributes of all indicator defined by the exam. The column name of an indicator is
|
||||
the name of the indicator defines in the exam and the cell shows the measured value of the indicator for each SEB client connection and
|
||||
the cell is tinted in the color of the reached threshold also defined for each indicator on the exam.
|
||||
The following SEB connection states are defined:
|
||||
|
||||
- **Connection Requested** This state appears from when a SEB client contacted to SEB Server the first time until the SEB client has finished up the hand-shake protocol with the SEB Server and the student has logged into the LMS.
|
||||
- **Active** This state appears after successful hand-shake and login into LMS and stays as long as the SEB connection is available and not closed or terminated
|
||||
- **Missing** This state appears when a SEB connection is currently in active state but has missing ping (last ping last longer then the highest ping threshold of the ping indicator).
|
||||
- **Closed** This state marks a closed SEB connection that was once active.
|
||||
- **Canceled** This state marks a SEB connection that has been canceled.
|
||||
|
||||
This general connection attributes are followed by the indicator attributes of all indicator defined by the exam. The column name of an indicator is
|
||||
the name of the indicator defined in the exam. The cell shows the measured value of the indicator for each SEB client connection and
|
||||
the cell is tinted in the color of the reached threshold also defined for each indicator on the exam administration.
|
||||
|
||||
**Search**
|
||||
|
||||
Since the monitoring heat-map list is automatically sorted and cannot be filtered except on connection status, there is a search feature to find a
|
||||
particular connection or a set of connections. To search connection on a running exam, please use the "Search" action from the right action pane.
|
||||
A search pop-pup will appear with all connection is a usual list with the possibility to filter and sort the entires.
|
||||
Double-click on an entry to go to the detail view of the specified SEB client connection.
|
||||
|
||||
.. image:: images/monitoring/search.png
|
||||
:align: center
|
||||
:target: https://raw.githubusercontent.com/SafeExamBrowser/seb-server/master/docs/images/monitoring/search.png
|
||||
|
||||
|
||||
**Instructions**
|
||||
|
||||
|
@ -51,16 +71,20 @@ with usual list (multi)selection by holding Ctrl or Shift key plus right mouse c
|
|||
|
||||
**Filter**
|
||||
|
||||
There are some filter to hide/show SEB client connection of in particular states. These are located in the right action pane has the name of the
|
||||
filter action that will be performed on click and the name of the effected connection status. With this actions you are able to toggle between
|
||||
There are connection state filter to hide/show SEB client connection in particular states. These are located in the right action pane hand has the name of the
|
||||
filter action that will be performed on click (hide/show) and the name of the affected connection status. With this actions you are able to toggle between
|
||||
hide and show SEB client connection of a particular state.
|
||||
|
||||
- **Show/Hide Closed** Use this to show or hide all SEB client connections that are currently in the "Closed" state.
|
||||
- **Show/Hide Requested** Use this to show or hide all SEB client connections that are currently in the "Requested" state and are not responding anymore.
|
||||
- **Show/Hide Active** Use this to hide SEB client connections in active state that has no incident and are not missing. If this filter is enabled and an active SEB connection gets an incident or is marked as missing it suddenly appears in the list. So no incidences are accidentally hidden. This feature is best used for exams with a lot of participants to keep a good overview.
|
||||
- **Show/Hide Closed** Use this to show or hide all SEB client connections that are currently in the "Closed" state.
|
||||
- **Show/Hide Canceled** Use this to show or hide all SEB client connections that are currently in the "Canceled" state.
|
||||
|
||||
Since SEB Server version 1.3 each filter also shows the current number of connection in the particular state. Now one has an overview of how many connections
|
||||
are there for an exam and in witch state.
|
||||
|
||||
.. note::
|
||||
When a certain state filter is set to hide and a particular SEB client connection switches into that state, it will automatically be hiding from the list.
|
||||
When a certain state filter is set to hide and a particular SEB client connection switches into that state, it will automatically disappear from the list.
|
||||
|
||||
Detailed View
|
||||
-------------
|
||||
|
@ -84,11 +108,11 @@ Live Proctoring
|
|||
---------------
|
||||
|
||||
.. note::
|
||||
This feature is still in a prototype state and not all functionality meight work as expected. Basically the meeting features
|
||||
This feature is still in a prototype state and not all functionality might work as expected. Basically the meeting features
|
||||
are given or restricted by the meeting service that is used and the API and GUI that is given by that meeting service client
|
||||
|
||||
|
||||
**Collecting Rooms**
|
||||
**Proctoring (Collecting) Rooms**
|
||||
|
||||
When the exam live proctoring feature is enabled for the running exam (see :ref:`sebProctoringSettings-label`), SEB Server will automatically create and collect
|
||||
connected SEB clients into so called collecting rooms. The size of this collecting rooms can be defined within the proctoring settings in the exam.
|
||||
|
@ -107,14 +131,17 @@ load the detailed monitoring view of that participant.
|
|||
A collecting room, once created will live as long as the exam is running and not has been deleted. When the exam ends or is been deleted,
|
||||
the collecting room will automatically get deleted on the SEB Server's persistent storage as well as on the meeting service side if needed.
|
||||
|
||||
**Town-hall Feature**
|
||||
**Town-Hall Feature**
|
||||
|
||||
Beside the usual collecting room, there is a town-hall room feature. By using the "Open Townhall" action from the right action pane, SEB Server enforce all SEB clients that
|
||||
are in collecting rooms as well as new connecting SEB clients to leave their current meeting and join the town-hall meeting for as long as the town-hall is active.
|
||||
Within the town-hall a proctor has the same features as in the collecting room but can connect to all participants at the same time.
|
||||
When the town-hall is closed all connected SEB clients are enforced to leave the town-room and go back to its collecting room meetings again.
|
||||
|
||||
.. note::
|
||||
This feature is only available if it is enabled within the exam proctoring settings in the exam administration.
|
||||
|
||||
**Single Room Feature**
|
||||
**Single Room or One-to-One Room Feature**
|
||||
|
||||
Another live proctoring feature can be found in the detailed monitoring view of one particular SEB client connection. The single room features allows a proctor to connect to a single
|
||||
participant and being able to view or communication with just this one participant. You can initiate this single room connection by using the "Single Room Proctoring" action on
|
||||
|
@ -126,6 +153,9 @@ When the single room is closed the connected SEB clients is enforced to leave th
|
|||
:align: center
|
||||
:target: https://raw.githubusercontent.com/SafeExamBrowser/seb-server/master/docs/images/monitoring/proctoringClient.png
|
||||
|
||||
.. note::
|
||||
This feature is only available if it is enabled within the exam proctoring settings in the exam administration.
|
||||
|
||||
**Boradcast Features**
|
||||
|
||||
Within a live proctoring window a proctor can use the enabled features of the integrated meeting service. And is able to communicate with the SEB clients by using one
|
||||
|
@ -142,6 +172,17 @@ A Student as well as a proctor is then able to use all the features of the meeti
|
|||
:align: center
|
||||
:target: https://raw.githubusercontent.com/SafeExamBrowser/seb-server/master/docs/images/monitoring/proctoringWindow.png
|
||||
|
||||
.. note::
|
||||
Each of this features is only available if it is enabled within the exam proctoring settings in the exam administration.
|
||||
|
||||
**Known Issues with Live Proctoring**
|
||||
|
||||
- Within the Zoom service it often happens that a participant appear twice in a room or meeting. This is probably caused by SEB clients rejoining the meetings while rooms or feature settings are changed.
|
||||
- In Zoom it is not possible to fully control a participant microphone. Therefore it may happen that participant can hear each other even if no proctor is in the meeting.
|
||||
- Within Jitsi Meet service when a proctor leaves the room it currently happens that a random participant became host/moderator since it is not possible in Jitsi Meet to have a meeting without host. We try to mitigate the problem with the `moderator plugin <https://github.com/nvonahsen/jitsi-token-moderation-plugin>`_ or `Jitsi Meet SaS <https://jaas.8x8.vc/#/>`_
|
||||
- In both services while broadcasting, it is not guaranteed that a student always see the proctor. Usually the meeting service shows or pins the participant that is currently speaking automatically.
|
||||
|
||||
|
||||
|
||||
All SEB Client Logs
|
||||
-------------------
|
||||
|
@ -166,19 +207,20 @@ action form the right action pane to open up a pop-up containing all related inf
|
|||
Currently there is no export functionality to export all interessting SEB client logs to a CSV table for example. But such a feature will probably come
|
||||
with a next version of SEB Server.
|
||||
|
||||
**Export filtered client logs**
|
||||
|
||||
To export all currently filtered client logs in CSV format, please use the "Export CSV" action form the right action pane. SEB Server will then convert and download
|
||||
all client logs for you. This might take some time if there are a lot of logs to export.
|
||||
|
||||
.. note::
|
||||
Please avoid exporting of huge log files while one or more performance intensive exam are running to not stress the service unnecessarily.
|
||||
|
||||
**Delete filtered client logs**
|
||||
|
||||
To delete all currently filtered client logs, please use the "Delete Logs" action form the right action pane.
|
||||
|
||||
.. note::
|
||||
On deletion, all available logs will permanantly be deleted from the persistent storage. So please make sure you want to delete all
|
||||
On deletion, all available logs will permanently be deleted from the persistent storage. So please make sure you want to delete all
|
||||
logs that are currently displayed in the list before deleting.
|
||||
|
||||
|
||||
**Known Issues**
|
||||
|
||||
- Within the Zoom service it often happens that a participant appear twice in a room or meeting. This is probably caused by SEB clients rejoining the meetings while rooms or feature settings are changed.
|
||||
- In Zoom it is not possible to fully control a participant microphone. Therefore it may happen that participant can hear each other even if no proctor is in the meeting.
|
||||
- Within Jitsi Meet service when a proctor leaves the room it currently happens that a random participant became host/moderator since it is not possible in Jitsi Meet to have a meeting without host. We try to mitigate the problem with the `moderator plugin <https://github.com/nvonahsen/jitsi-token-moderation-plugin>`_ or `Jitsi Meet SaS <https://jaas.8x8.vc/#/>`_
|
||||
- In both services while broadcasting, it is not guaranteed that a student always see the proctor. Usually the meeting service shows or pins the participant that is currently speaking automatically.
|
||||
|
|
@ -326,6 +326,24 @@ public class ExamProctoringSettings {
|
|||
|
||||
return () -> formHandle;
|
||||
}
|
||||
|
||||
// TODO
|
||||
// private void procServiceSelection(final Form form) {
|
||||
// final ProctoringServerType proctoringServerType = ProctoringServerType
|
||||
// .valueOf(form.getFieldValue(ProctoringServiceSettings.ATTR_SERVER_TYPE));
|
||||
// switch (proctoringServerType) {
|
||||
// case ZOOM: {
|
||||
// form.setFieldVisible(true, ProctoringServiceSettings.ATTR_SDK_KEY);
|
||||
// form.setFieldVisible(true, ProctoringServiceSettings.ATTR_SDK_SECRET);
|
||||
// break;
|
||||
// }
|
||||
// default: {
|
||||
// form.setFieldVisible(false, ProctoringServiceSettings.ATTR_SDK_KEY);
|
||||
// form.setFieldVisible(false, ProctoringServiceSettings.ATTR_SDK_SECRET);
|
||||
// }
|
||||
// }
|
||||
// }
|
||||
|
||||
}
|
||||
|
||||
}
|
||||
|
|
|
@ -663,7 +663,7 @@ sebserver.exam.delete.report.list.empty=No dependencies will be deleted.
|
|||
sebserver.exam.proctoring.actions.open=Proctoring Settings
|
||||
sebserver.exam.proctoring.form.title=Exam Proctoring Settings
|
||||
sebserver.exam.proctoring.form.info.title=Remote Proctoring
|
||||
sebserver.exam.proctoring.form.info=This allows you to integrate a supported external proctoring service.
|
||||
sebserver.exam.proctoring.form.info=This allows to integrate a supported external proctoring service.<br/>To integrate Jitsi Meet, JWT based authentication must be enabled.<br/>To integrate Zoom a Zoom higher-plan account is needed and also JWT based authentication.
|
||||
sebserver.exam.proctoring.form.enabled=Proctoring enabled
|
||||
sebserver.exam.proctoring.form.enabled.tooltip=Indicates whether the exam proctoring feature is enabled for this exam or not.
|
||||
sebserver.exam.proctoring.form.type=Type
|
||||
|
|