... | ... | @@ -67,101 +67,31 @@ The folder level provides configuration options that apply at the folder level, |
|
|
- deadline that applies for all assignments within the folder
|
|
|
- grade calculation options (set weights of individual assignments within this folder, criteria to pass)
|
|
|
|
|
|
### Deadlines and Assignment Visibility
|
|
|
#### Publish/Hide assignments
|
|
|
For assignments under construction, or assignments to become available at a later moment, you can hide an assignment (default for just created assignments), and/or limit the time window for which the assignment should be available to students.
|
|
|
To hide/publish assignments
|
|
|
- use the `Actions` menu at the top.
|
|
|
<img src="uploads/3c8a603a6abf482b7716cd7c08b53083/hide-assignment.png" width="500px" />
|
|
|
- hide or publish the assignment from the menu. Folders will also have recursive options
|
|
|
- when hidden, it gets reflected in the indicator icons at (1)
|
|
|
|
|
|
|
|
|
#### Set time window for availability
|
|
|
If an assignment should only become available after, until or during a specified time frame, the dates can be configured in the `Edit Assignment` view:
|
|
|
<img src="uploads/71e9056655d5f9aef54f8148470f3c63/set-time-window.png" height="250px" />
|
|
|
|
|
|
#### Deadlines
|
|
|
Assignment deadlines apply to all students and are typically set at the folder level. Students can edit their submission until the deadline passes. Individual students can also be assigned a personal deadline extension (e.g. due to illness or dyslexia), or a general deadline extension (optionally with a linearly increasing grade penalty) can be set for an assignment.
|
|
|
For assignment deadlines,
|
|
|
- open `Edit Assignment`, and browse to the `Dates/Exam Access` tab like in the [picture above](#set-time-window-for-availability)
|
|
|
- set the deadline, and optionally a deadline extension (with penalty).
|
|
|
<img src="uploads/40405238b73c03cb5f936bb1644592f3/set-deadline.png" width="500px" />
|
|
|
|
|
|
To give a student an **individual deadline extension**
|
|
|
- open the `Submissions` page for the assignment for which deadline should be overridden
|
|
|
<img src="uploads/b0bd51c0132b94abcb334bc87514236f/nav-submission-info.png" width="500px" />
|
|
|
- use the filters to search for the student's name
|
|
|
- open submission info dialog, and hit administer
|
|
|
<img src="uploads/92dec9e5bef4a4213cd9e4c02306237b/submission-info.png" height="250px" />
|
|
|
- enter a personal deadline
|
|
|
<img src="uploads/87e647108b0df553cc00db5861a24663/personal-deadline.png" height="250px" />
|
|
|
|
|
|
## Workflow Examination in WebLab
|
|
|
### Assignment deadlines and Visibility
|
|
|
This content is available at [Assignment Visibility and Deadlines](WebLab/Assignment-Visibility-and-Deadlines).
|
|
|
|
|
|
## Examination in WebLab
|
|
|
When WebLab is used as platform for examination, the typical workflow entails:
|
|
|
|
|
|
- (Registering your exam as usual, with WebLab selected as platform for your digital exam)
|
|
|
- ([Add your course to WebLab](#add-your-course-to-weblab))
|
|
|
- **Create the exam content**
|
|
|
- Create an exam folder (see [folders](#organizing-assignments-in-folders)) e.g. `Exams/Final Exam` (assuming there will also be a Resit later on)
|
|
|
- Make sure it is _hidden_ (not published)
|
|
|
- Make sure it is not set to _public_ (not published)
|
|
|
- Create or import the exam assignments
|
|
|
- **Test the exam content**
|
|
|
- Check the exam for issues, also by others, by using the `Hybrid Student Mode` (todo)
|
|
|
- Check the exam for issues and/or let other course staff review it, by using the `Hybrid Student Mode` (todo)
|
|
|
- **Provide practice exam(s) for students**, so they know what to expect and get familiar with WebLab, especially when it was not used during the course.
|
|
|
- **When the exam schedule is final**:
|
|
|
- Set the `visible-from` date to the start (typically 9.00, 13.30 or 18:30)
|
|
|
- Set the `visible-from` date to the start (typically 9.00, 13.30 or 18:30).
|
|
|
- Set `deadline` to start + duration. It's common to add one minute extra for the deadline (e.g. 12.01), and set the `Due date` (i.e. the advised date to finish, non-functional) to the round value (e.g. 12.00).
|
|
|
- Do _not_ set `visible-until`, unless you really want the exam to be hidden after it ends. In that case make sure that it is set after the very last personal deadline extension for students with extra time.
|
|
|
- Communicate to students that they should enrol for the course on WebLab. (verify that enrolment is open at the course settings)
|
|
|
- **Set up Exam Tickets**
|
|
|
- Enable exam tickets from the `Dates/Exam tickets` tab, and open its manage page
|
|
|
<img src="uploads/0429d362ae52023c8ef92ae53ddef1c6/enable-exam-tickets.png" height="250px" />
|
|
|
- Generate the tickets:
|
|
|
<img src="uploads/b82ec730043b41b5fa0fedccac3c533f/generate-tickets.png" height="250px" />
|
|
|
- Configure the desired access and restriction options (see [Exam Ticket Options](#exams-in-weblab-using-exam-tickets))
|
|
|
- [Enable and configure exam tickets](WebLab/Exam Tickets)
|
|
|
- **Exam Logistics / Communication**
|
|
|
- Make sure the WebLab team [gets informed](contact) (todo) about the upcoming exam. At least one member should review the exam settings and be present during the exam. Communication in preparation of, and during the exam is often done in form of a channel on Mattermost/Slack/... with relevant course staff.
|
|
|
|
|
|
### Exams in WebLab using Exam Tickets
|
|
|
In addition to the visibility and deadline settings, WebLab provides facilities for examination using Exam Tickets. Exam tickets allow students to work on their exam in restrictive exam mode. The restrictions may very per exam, and are configurable.
|
|
|
When Exam Tickets are enabled, students need to explicitly start their exam submission by hitting `Register & Start Exam`:
|
|
|
<img src="uploads/995783213fa016953e25c04568110a17/start-exam.png" width="500px" />
|
|
|
|
|
|
When started, a student's WebLab account will be in exam mode and the student is only allowed to work on the exam from the browse session from which he/she started. In case the student logs in from another browser (tab) or device, he/she won't be able to continue from the new session, except when the student's exam ticket gets reset. A ticket can be reset by the course staff (i.e. it requires student to contact course staff), or by the student itself when tickets are set to be *reusable*. Also, the student will receive a warning message in case there is a change in network connection detected. This gets logged and course staff can view this information from the registrations page.
|
|
|
|
|
|
#### Enable Exam Tickets
|
|
|
|
|
|
- Open `Edit Assignment`
|
|
|
- Browse to the `Dates/Exam tickets` tab
|
|
|
- Enable exam tickets and click save
|
|
|
<img src="uploads/2886f493e2beddde155a0b92173a9d57/enable-exam-tickets.png" height="250px" />
|
|
|
- Open the `Manage exam keys` from the same `Dates/Exam tickets` tab
|
|
|
- Generate the tickets without key requirement (or with key requirement for on-campus exams):
|
|
|
<img src="uploads/b82ec730043b41b5fa0fedccac3c533f/generate-tickets.png" height="250px" />
|
|
|
|
|
|
#### Exam Tickets Settings - Restricted Exam Mode (open vs closed book)
|
|
|
The `Restricted Exam Mode` controls whether students are allowed to view course content other than the exam assignments during the exam. When enabled (for closed-book exam), students can only access the exam assignment after they've started the exam. Note that this access restriction is most effective in an already controlled environment, like with on-campus exams (campus pc's load an environment with internet connection limited to WebLab, invigilators walking around). The access restriction only applies to the student's account from the moment they started the exam mode and it's outside WebLab's control to check that students have old browser tabs open, browse the internet, or use another (friend's) WebLab account to access the information on WebLab that's not part of the exam.
|
|
|
|
|
|
#### Exam Tickets - One time vs Reusable ticket
|
|
|
One-time tickets restrict students to finish their exam from one and the same browse session from which they started the exam. If, for whatever reason, the student needs to start a new browse session in WebLab (e.g. laptop died/computer restarted during the exam), only course staff will be able to reset the student's ticket in order to let him/her continue from another device/session:
|
|
|
<img src="uploads/a148188d3dc29dc9b950ddf999b5b337/continue-exam-one-time-ticket.png" width="500px" />
|
|
|
|
|
|
With reusable tickets, students may switch device/log in from other browser (tab) and continue their exam submission from there:
|
|
|
<img src="uploads/075296bd9e9d36398636720bf76747f5/continue-exam-reusable-ticket.png" width="500px" />
|
|
|
|
|
|
When tickets are set to be reusable, it reduces communication overhead and administration by the student and course staff in case of a device switch or (browser) restart. However, it becomes easier to work on a single exam submission from different locations. Still, only one session can access the exam submission at a time, and changes in network location or browser session get logged in the registration overview that is available to course staff.
|
|
|
|
|
|
#### Exam Tickets - Protected Exam Access
|
|
|
To prevent students from sharing access to their exam submissions with others, a security layer can be added in form of a personal exam key or password.
|
|
|
|
|
|
**Personal Exam Keys** are useful for on-campus exams. The personal key gets distributed with the student on paper, just before the exam starts (i.e. after the student entered the exam room). This key will only work for the student associated with this key, and tickets should be configured to be valid one-time. Whenever a student switches to another computer, course staff should generate a new exam key in order for the student to continue (i.e. this ensures that not someone else starting to work on the student's exam). Course staff can generate the key-forms from the exam ticket page and include any other information on these form next to the the personal exam key and student name/student number/netid. The key forms can be generated for all students in the course, or a list of student ids can be entered for which to generate the key forms for.
|
|
|
|
|
|
**Password Protection** is used in a proctored setup with RPNow. The password is not shared with the students, but will be configured at the RPNow side by the WebLab administrators. The RPNow Secure Browser, which students need to use for the exam, will insert the password at the start-page of the Exam, without exposing it. This ensures that the students only access the exam using the proctored environment, which facilitates the authentication/student id/room/surveillance checks.
|
|
|
|
|
|
**No keys/password** - For remote exams that are not proctored, neither of these protections will add to the prevention of exam access sharing. Passwords/personal keys can easily be shared over any communication channel and it only adds administrative overhead in preparation/during the exam.
|
|
|
|
|
|
#### Exam Tickets - Allow students to leave exam mode
|
|
|
Exam mode will be active until the exam ticket gets deactivated for a student. This is done by the course staff after the exam, or by the students themselves when set to allow this. When Restricted Exam Mode is enabled (for closed-book exam) exams, only course staff should be allowed to deactivate the tickets. Students can otherwise temporarily leave exam mode to check non-exam content on WebLab and re-join to continue their exam.
|
|
|
|
|
|
### Fraud preventing assignment facilities
|
|
|
Exam content can organized with fraud prevention in mind by using (a combination of) facilities provided in WebLab. These include:
|
... | ... | |