DRAP: Draft Ranking Automated Processor

Welcome to DRAP: the Draft Ranking Automated Processor for the University of the Philippines Diliman - Department of Computer Science's yearly draft of research lab assignments. In a nutshell, this web application automates the mechanics of the draft:

1. All participating students register for the draft by providing their full name, email, student number, and lab rankings (ordered by preference) to the draft administrators.
2. The regular draft process begins. For each round in the draft:
   1. Draft administrators notify (typically via email) the lab heads about all of the students that have chosen their respective research lab as the first choice.
   2. Each lab selects a subset (i.e., possibly none, some, or all) of these first-choice students to accept them into the lab. After this point, the selected students are considered to be "drafted" and are thus no longer part of the next rounds.
   3. The next round begins when all of the labs have submitted their preferences. This time around, the second-choice preferences of the remaining students are evaluated (and so on).
3. Should there be students remaining by the end of the regular draft process, the lottery round begins.
4. Before the randomization stage, draft administrators first negotiate with participating labs (that have remaining slots) to check if any of the labs would like to accept some of the remaining students immediately.
5. After manual negotiation and intervention, the remaining students are shuffled and assigned to participating labs in a round-robin fashion.
6. The draft concludes when all registered participants have been assigned to a lab.

Development

The main web application is powered by SvelteKit. Data persistence is backed by PostgreSQL.

Docker Environment Variables

For local development, we use a Docker Compose to build an image of PostgreSQL with the required extensions. See the Dockerfile for more details.

As the image builds on top of the official postgres image, the following environment variables (stored in a .env file at the project root) will be relevant to the image initialization.

See more initialization variables here. In most cases, however, the default values are fine with some standard password like "password". There is no need to overthink it as the instance should only be local for development.

Server Environment Variables

At runtime, the server requires the following environment variables to be present.

Setting up the Codebase

# Install dependencies.
pnpm install

# Check formatting.
pnpm fmt # prettier

# Apply formatting auto-fix.
pnpm fmt:fix # prettier --write .

Linting the Codebase

# Check linting rules.
pnpm lint:eslint
pnpm lint:svelte

# Perform all lints in parallel.
pnpm lint

Running the Development Server

# Run the Vite dev server for SvelteKit.
pnpm dev

# Run the Vite preview server for SvelteKit.
pnpm preview

Building the Applications

# Build the main web application (SvelteKit).
pnpm build
node --env-file=.env build/index.js

Acknowledgements

The DRAP project, licensed under the GNU Affero General Public License v3, was originally developed by Sebastian Luis S. Ortiz and Victor Edwin E. Reyes as a service project under the UP Center for Student Innovations. The DRAP logo and banner were originally designed and created by Angelica Julianne A. Raborar.