A transfer readiness checker for Cerritos College students applying to UC engineering and computer science majors. Enter the courses you've taken (or plan to take), pick a target major, and see which ASSIST.org articulation requirements you've met and what's still missing, plus a full Cal-GETC general education breakdown.
| Layer | Tech |
|---|---|
| Frontend | React 19, TypeScript, Tailwind CSS, Vite |
| Backend | Node.js, Express 5 (JavaScript, ESM) |
| Database | MongoDB (mongodb driver) |
| Scraper | Python 3, requests, pymongo |
The database is a MongoDB(subject to change) instance with three collections: majors, articulations (each embedding its course groups and courses), and cerritos_catalog. The scraper writes the data and the app reads it.
Both sides read the same two variables:
MONGO_URI: the connection string. The scraper defaults tomongodb://localhost:27017; the backend has no default.DB_NAME: the database name. The scraper defaults toassist; the backend has no default.
Point both at the same MongoDB with the same DB_NAME and you're set. Note that only the scraper falls back to defaults, so set both variables explicitly for the backend (in backend/.env for local dev, or the host's environment in deployment).
Install Python dependencies and populate the database from ASSIST.org:
pip install -r scraper/requirements.txt
python scraper/scrape_assist.pyThis connects to MongoDB (defaulting to mongodb://localhost:27017, database assist) and fills it. The indexes are created automatically, so there's nothing to provision beyond a running MongoDB server.
The scraper targets the 2025-2026 academic year, pulling all engineering/CS articulation agreements between Cerritos College (ID 104) and UCI, UCLA, UCSD, and Berkeley.
To point at a different MongoDB instance (e.g. MongoDB Atlas), set MONGO_URI:
MONGO_URI="mongodb+srv://user:pass@cluster.example.mongodb.net" python scraper/scrape_assist.pyTo scrape a single university instead of all four:
python scraper/scrape_assist.py --university UCLA
# choices: UCI, UCLA, UCSD, BerkeleyTo look up ASSIST.org institution IDs:
python scraper/scrape_assist.py --list-institutionsScraper modules
| File | Responsibility |
|---|---|
scrape_assist.py |
CLI entry point: argument parsing and top-level orchestration |
config.py |
Constants: institution IDs, academic year, MongoDB connection, request headers |
api.py |
HTTP session, XSRF auth, all ASSIST.org API calls |
db.py |
Schema creation and all database insert/upsert functions |
scraper.py |
Per-university scrape loop |
The backend and frontend are separate npm packages. Install and run each in its own terminal.
API on port 3001:
cd backend && npm install && npm run devVite dev server on port 5173:
cd frontend && npm install && npm run devThe backend's npm run dev loads backend/.env automatically, so put MONGO_URI and DB_NAME there.
There's no Vite proxy, so the frontend reaches the API through VITE_API_URL. Create frontend/.env and point it at the backend:
VITE_API_URL=http://localhost:3001Then open http://localhost:5173 in your browser.
The app runs as three pieces: the frontend on Netlify, the backend on Render, and the data in MongoDB Atlas. Each one points at the next.
Backend (Render)
- Root directory:
backend - Build command:
npm install - Start command:
npm start - Environment variables:
MONGO_URI= your Atlas connection stringDB_NAME= your database name (e.g.assist)CORS_ORIGIN= your Netlify site URL, so the browser is allowed to call the API
Render provides PORT automatically; the server reads it and listens on 0.0.0.0. If you leave CORS_ORIGIN unset the API allows any origin, which is fine for testing but you'll want it locked to your Netlify URL in production.
Frontend (Netlify)
- Base directory:
frontend - Build command:
npm run build - Publish directory:
dist - Environment variable:
VITE_API_URL= your Render backend URL (set at build time)
Data (MongoDB Atlas)
Run the scraper once against the cluster to fill it:
MONGO_URI="<atlas-connection-string>" python scraper/scrape_assist.pyKeep the database named assist, since that's what the backend expects. Re-run the scraper anytime to refresh the data.
If the database is empty the app still boots, but the majors list stays empty until the scraper has run.
Transfer Readiness: select a UC major, then the app posts your course list to /api/check-readiness. The server joins your courses against the articulation data (including former course identifiers) and returns which UC requirements are satisfied, which are missing, and which have no articulation path.
Cal-GETC: posts your course list to /api/check-calgetc. The server looks up each course's Cal-GETC areas from the catalog and checks all 11 areas, including the Area 4 cross-discipline rule.