System Overview

Trust, Governance & Campus Resource Architecture

ResourceBridge bridges the divide between specialized, underutilized college assets and students who need verified access for academic research, capstones, and creative production.

The Campus Resource Problem

Higher education institutions invest heavily in specialized laboratories, 4K production cameras, robotics gear, high-performance computing clusters, and audio engineering facilities.

However, departmental silos often keep these resources locked behind administrative boundaries. Studies indicate that up to 70% of specialized college equipment sits idle outside scheduled class hours, while students and cross-disciplinary teams lack clear channels to request and utilize them safely.

The Four Pillars of Trust

  • 1. Verified Campus Membership: Every user holds an authenticated identity (Student, Manager, or Administrator) with strict role segregation.
  • 2. Departmental Oversight: Lab custodians inspect booking requests, verify required safety training, and make transparent approval or rejection decisions.
  • 3. Handover & Return Condition Reports: Formal inspection records at checkout and return ensure equipment condition is systematically tracked and accountable.
  • 4. Conflict Prevention & Audit Trail: Concurrency locking and automated overlap detection prevent double-bookings, backed by an immutable event timeline.

Technical Architecture & Implementation

ResourceBridge is engineered with a clean, conventional Python/Flask architecture that balances security, performance, and maintainability without unnecessary third-party bloat.

Backend Architecture

  • Framework: Python 3 + Flask (Application Factory pattern)
  • ORM & Database: Flask-SQLAlchemy with SQLite database
  • Authentication: Flask-Login session management
  • Security: Werkzeug PBKDF2 password hashing & CSRF protection

Data Models & Lifecycle

  • User: Roles (Student, Manager, Admin), verification flags
  • Resource: Equipment & Space categorization, safety requisites
  • Booking: State machine (Pending, Approved, Checked In, Returned, Rejected, Cancelled)
  • ConditionReport & Incident: Initial checkout notes, return condition, manager resolution
  • AuditLog: Timestamped action history and state transitions

Security & Concurrency

  • Concurrency Guard: Thread-safe approval locking and refresh-check preventing double-bookings
  • Safe Redirects: Strict RFC-compliant URL validation against Open Redirect attacks
  • Access Boundaries: Strict role decorators preventing unauthorized cross-department access
  • Security Headers: X-Content-Type-Options, X-Frame-Options, Content-Security-Policy

Frontend Design System

  • Rendering: Jinja2 templates with semantic HTML5 elements
  • Styling: Restrained, high-contrast custom CSS with institutional design tokens
  • Interactivity: Vanilla JavaScript (zero bulky frontend frameworks)
  • Accessibility: Visible focus indicators, accessible contrast, mobile-responsive tables

Engineering Milestones Completed

Stage 1

Core Foundation & RBAC

Secure User model, PBKDF2 hashing, session security, role boundaries, and demo persona seeder.

Stage 2

Inventory & Discovery

Resource cataloguing, multi-parameter search/filters, safety prerequisites, and owner inventory management.

Stage 3

Booking Lifecycle

Reservation requests, date/time validation, manager review queue, approval/rejection reasons, conflict detection.

Stage 4

Handover, Returns & Incidents

Check-in condition reports, return inspection logging, incident tracking, and audit event timeline.

Stage 5

Code Quality & Defect Repair

Comprehensive codebase review, query optimization, role-specific metrics, and accessibility fixes.

Stage 6

Security Hardening

CSRF defense, safe redirect enforcement, custom error handlers, and process-level concurrency locking.

Stage 7

Integration & Concurrency QA

Multi-threaded race condition tests, open redirect verification, 64-test regression baseline established.

Stage 8

Frontend Redesign & Submission

Calm, professional UI redesign, repository hygiene audit, deployment readiness, and documentation package.