The Search Progress Tracker provides a central, accessible location for OSU hiring committees to track candidates through the hiring process. The committee's Search Chair has the ability to create and modify all information related to the position they're hiring for. Once they've filled out this information, the interviewing process can begin. For each interview round (eg Resume Review, Phone interview, etc) everyone on the committee can submit their notes about each candidate and score them for how well they meet each qualification for the position. Once a final decision has been made for a candidate, the Search Chair can update their status based on options provided by OSU HR.
Initial Development: Summer 2023 - (Development still ongoing)
Contributors
- Nate Baird ([email protected])
- Travis Hudson ([email protected])
Deployment URL: https://eecs.engineering.oregonstate.edu/education/hiring
The following resources provide information about how to develop the website locally and the workflow for pushing changes to the staging area and subsequently deploying them to production.
Not yet implemented on this site
In addition, create a pre-commit hook that will ensure file permissions are set correctly before you commit
code. To do this, copy the scripts/pre-commit.sh
file and save it as pre-commit
in your local .git/hooks
directory. Also ensure it is executable.
cp scripts/pre-commit.sh .git/hooks/pre-commit
chmod a+x .git/hooks/pre-commit
There should be an INI file located in the private files for this site (not in the repository) with the following contents:
host =
user =
password =
db_name =
Please see the Server Documentation for details on the server configuration of the site.
Please see the Structure Documentation for a detailed structural overview of this site.
Users
- Can submit feedback as they review candidates with their committees.
- Can create new positions to review with their committees.
- Can modify positions (qualifications, rounds, and candidates) that they are the Search Chair for.
- In the future, may recieve additional permissions based on their role.
Admins
- Must approve each position before the Search Chair can fill out information or upload files.
- Can edit any position.
- Can take on the role of any user to diagnose issues (with heavy tracking).
- Can grant other users admin functionality.
Authentication data is located in a database.ini
file outside this repository. The Tekbots Web Dev Team's shared
Google Drive contains documentation on the internal structure of database tables used in this site.
Database Name: eecs_tekbots
Server Name: engr-db Groups
Within pages/login.php
, the auth/[authenticator].php
script is executed on login button click.
Login credentials required to interface with the authenticator are:
- redirect_uri
- client_id
- client_secret
Each authenticator will provide different user info configurations but will have sufficient data needed to create a
new user. All new users are defaulted as Students and are re-directed to pages/login.php
with a new portal section.
Users must contact an administrator of this application in order to be given the access level of admin.
Session variables are used to persist user data throughout the course of a user's active session. The instantiation of these variables occur in the following workflow:
- The user visits the
pages/login.php
page. - The user selects a login authentication type (EX: Google, Microsoft).
- After successful authentication, the following session variables are instantiated and can be used in PHP throughout the entire application:
$_SESSION['userID']
: This variable is a string of numbers.$_SESSION['userAccessLevel']
: This variable is a string that can be either:- "User"
- "Admin"
$_SESSION['newUser']
: This variable is a boolean (either true or false).