Contest Check-in

Table of contents

  1. Contestant Check-in
    1. Managing Contestant Check-in
      1. Swipe Check-in
    2. Check-in Process
      1. Failure: Case 1
      2. Failire: Case 2
  2. Volunteer Check-in
    1. Completing Check-in

Navbar check-in
Figure 1. Check-in links available in contest volunteer navbars.

Contestant Check-in

The Contestant Check-in interface is used to perform contestant check-in on contest day, and consists of a simple form that refreshes after each user checks in. When logged in as a volunteer, a link to the interface is accessible from the user’s dropdown menu located in site’s navigation bar. The page may be accessed directly by navigating to <site_url>/checkin/.

Managing Contestant Check-in

Contestant check-in is best managed by using several laptops as check-in stations. At each station, a volunteer will log in and navigate to the Contestant Check-in interface. The volunteer should then monitor the station as contestants use the laptop to complete the check-in process.

Check-in Interface Access

The Contestant Check-in interface is accessible only by contest volunteers.

Swipe Check-in

Contestants have the option of completing the check-in process by swiping their FSUCard at a check-in station. Contestants who add the last 8 digits of their FSUCard number to the the FSU Number section of their account profile may utilize this check-in method.

To enable swipe check-in support at a check-in station, simply attach a USB swipe card reader to the station’s computer. Many operating systems will automatically install the drivers required to recognize and operate the card reader as an input device.

Check-in Process

The following diagram summarizes a contestant’s interaction with the check-in interface.

---
title: Contestant Check-in Flow
---
graph TD
    A[<small>Initial Prompt</small><br>Are you a member of a registered team?]-->|Yes| B{<small>Check-in Form</small><br>Enter credentials}
	A-->|No| C{<small>Walk-in Form</small><br>Select Division}

    B-->|Swipe FSUCard<br>** OR **<br>Enter email address| D((Submission<br>Accepted?))
    C-->|Lower| B
    C-->|Upper| B

    D-->|Yes| E(Check-in Success Notification)
    D-->|No| F(Check-in Failed Notification)

    E--> G[/<small>DOMjudge credentials</small><br><small>delivered via email</small>\]

    F-->|Bad Credentials| I{<small>Correct entry</small><br>}
    I-->|Retry| B

    F-->|All Walk-in teams assigned| J>Fail Case 1]

    F-->|Not on a team| K>Fail Case 2]

Failure: Case 1

In the event that a user attempts to check in as a Walk-in contestant and all Walk-in teams have been assigned, they will receive an error notification that no Walk-in teams are available. Unfortunately, additional walk-in teams cannot be created in this scenario. The contestant will need to find and join a registered team or an already assigned walk-in team with an open spot.

Failire: Case 2

In the event a contestant selects ‘Yes’ at the registered teams prompt despite not being on a team and then provides a valid FSUCard swipe or email address entry, then they will receive a notification that they are not on a registered team. The contestant will either need to find and join a registered team with an open spot, or check in as a walk-in contestant.

Volunteer Check-in

The Volunteer Check-in interface is used to perform contest check-in by those who are Docents, Proctors, Question Writers, or Contest Organizers. The interface consists of a simple form which refreshes after each user checks in. When logged in as a volunteer, a link to the interface is accessible from the a user’s dropdown menu located in site’s navigation bar. The page may be accessed directly by navigating to <site_url>/checkin/volunteer/.

Completing Check-in

On or after Contest Day, the Contest Organizers will provide each volunteer who fulfills the participation requirements with a passphase used to complete the check-in process. A volunteer must enter their username and the passphrase into the check-in form to successfuly record their participation.

---
title: Volunteer Check-in Flow
---
graph TD
    A[<small>Check-in Form</small><br>Enter username and passphrase]--> B((Submission<br>Accepted?))
    B-->|Yes| C[/Participation recorded\]
	B-->|No| D{<small>Correct entry</small><br>}
    D-->|Retry| A