How Persistent Proctor Works
Persistent Proctor Diagram
Persistent Proctor Background
Persistent Proctor Components
There are two components that comprise Persistent Proctor regardless of the version being used:
- A test-taker component where registration/enrollment occurs and exams are proctored
- A faculty dashboard where proctored sessions can be reviewed
There are three versions of Persistent Proctor:
- Learning Management System (LMS) Integrated – allows basic test-taker data along with course and exam information to flow into Persistent Proctor. This aids the instructor by not having to enter information into two systems.
- Stand-Alone Persistent Proctor is used by those who do not have a Learning Management System or who do not wish to have integration. We provide the means by which required information can be entered directly into Persistent Proctor
- API – allows for tight integration with user-based systems.
The aforementioned integration occurs in two ways:
- The first is LTI integration which stands for Learning Tools Interoperability, which allows us to run within the environment of the Learning Management System.
- The second is via Web services or Rest API, which allows us to pull data from the LMS about courses, exams, enrollments, and so forth.
Steps Toward Using Persistent Proctor
Test-takers start by accessing Persistent Proctor via their LMS, if present, or via a link provided by Biomids otherwise.
The first time in, test-takers enroll using biometric facial recognition.
Enrollment uses basic identification data. In the case of an integrated LMS, data elements automatically flow from the LMS into Persistent Proctor, such as name and email address in addition to the course and exam information. In the Stand-Alone version, the information would be manually entered into Persistent Proctor.
Test-takers then use a webcam to capture several facial images and an image of a photo ID.
Once the enrollment is completed, all future access to the proctoring system is granted by way of facial recognition authentication, allowing test-takers access to the proctoring system, to their courses, and to their exams.
Note that reenrollment is allowed but captured on the dashboard. In addition, a message with the details of such is sent to the administrator.
While testing is in progress, Persistent Proctor accomplishes several things. The first is called persistent authentication, which uses facial recognition to make sure that, during testing, the person in front of the camera who’s taking the exam is the one who is supposed to be there. This authentication takes place every 30 seconds, which is also customizable.
There are three anomalies that can occur during this persistent authentication:
- First, the camera may find no one present.
- Secondly, the camera may find more than one individual present.
- Thirdly the camera may find that the person in front of the camera is not the person who enrolled.
In all these cases, the anomalies are uploaded to the dashboard and made available for the faculty member to review.
In addition to the Persistent Authentication, we create a video of everything seen by the camera. The camera is actually capturing an image every three seconds and that is assembled into a video. That is done to save space but still provide an effective surveillance tool.
We also keep track of any website visits during the session (if allowed).
Finally, we do a screen capture of everything that transpires on the screen during the session. This is accomplished by capturing an image every few seconds with those images being assembled into a video.
All of this is being done in the background while the test-taker is taking the exam. Once the Proctor session is completed, all of this information is accumulated and uploaded to the server and made available on the faculty dashboard. We do this at the end of the session so as not to interfere with the test-taker who’s taking the exam. We want to be as unobtrusive as possible.
The Persistent Proctor Dashboard consolidates all the information about test-takers and any proctoring sessions they have completed. All the captured videos, proctoring sessions, and anomalies are presented to the administrator in one location for review and processing. Thumbnails are provided for any anomalies that occur, allowing the administrator to “jump” directly to the point in the associated video where the anomalies occurred.
By default, sessions arrive in a Pending state. These can be changed to Approved, Under Review, and Disapproved by the administrator and archived if desired.
Persistent Proctor can also automatically change the status of sessions based on the administrator setting up defaults for allowable numbers of anomalies.
For more information or to see a demo of Persistent Proctor please click here.