How 424137-ship-it/college-event-management-system works
HarshaX is a college event and community platform. Students browse events, register for QR passes, attend with verified check-in, and access certificates; organizers create events and manage attendance, budgets, and galleries, while administrators govern users and event approvals. The React client calls a Django REST API backed by MySQL. The graph preserves documented capabilities, but several backend and frontend modules were not sampled; their internal call paths are omitted where the evidence does not establish them.
Main entry points: api.js API client · events/views.py Event API · models.py Registration and passes · reports/views.py Analytics and reports
Components 22
Web client
- App routing
frontend/src/App.jsx - Auth context
frontend/src/context/AuthContext.jsx - API client
frontend/src/services/api.js - Event experience
frontend/src/pages/EventDetails/EventDetails.jsx - Student dashboard
frontend/src/pages/dashboards/StudentDashboard.jsx - Organizer console
frontend/src/pages/dashboards/OrganizerDashboard.jsx - Admin console
frontend/src/pages/dashboards/AdminDashboard.jsx
Identity and governance
- Accounts and roles
backend/accounts/models.py - Account API
backend/accounts/views.py
Events and participation
- Event API
backend/events/views.py - Event catalog
backend/events/models.py - Registration and passes
backend/registrations/models.py - Registration API
backend/registrations/views.py - QR attendance
backend/attendance/views.py - Certificates
backend/certificates/views.py
Organizer operations
- Clubs and communities
backend/clubs/views.py - Budgets and expenses
backend/budgets/views.py - Event gallery
backend/gallery/views.py
Platform services
- Notifications
backend/notifications/views.py - Analytics and reports
backend/reports/views.py - MySQL database
Other components
- Campus users
Connections 32
- Campus users → App routing: use
README.md - App routing → Event experience: routes to
frontend/src/App.jsx - App routing → Organizer console: routes to
frontend/src/App.jsx - App routing → Admin console: routes to
frontend/src/App.jsx - Auth context → API client: calls auth API
frontend/src/context/AuthContext.jsx - Event experience → API client: calls API
frontend/src/pages/EventDetails/EventDetails.jsx - Organizer console → API client: calls API
frontend/src/pages/dashboards/OrganizerDashboard.jsx - Student dashboard → API client: calls API
- Admin console → API client: calls API
- API client → Account API: REST requests
README.md - API client → Event API: REST requests
README.md - Event API → Event catalog: reads and writes
backend/events/views.py - Event API → Registration and passes: queries
backend/events/views.py - Event API → Notifications: creates
backend/events/views.py - Registration API → Registration and passes: reads and writes
backend/registrations/views.py - Registration API → Notifications: creates
backend/registrations/views.py - QR attendance → Registration and passes: verifies passes
backend/attendance/views.py - QR attendance → Event catalog: checks event
backend/attendance/views.py - Certificates → Registration and passes: checks participation
backend/certificates/views.py - Analytics and reports → Event catalog: aggregates
backend/reports/views.py - Analytics and reports → Registration and passes: aggregates
backend/reports/views.py - Analytics and reports → QR attendance: aggregates
backend/reports/views.py - Account API → Accounts and roles: uses account data
- Event API → MySQL database: persists event data
README.md - Registration API → MySQL database: persists registrations
README.md - QR attendance → MySQL database: persists check-ins
README.md - Certificates → MySQL database: stores credentials
README.md - Clubs and communities → MySQL database: stores communities
README.md - Budgets and expenses → MySQL database: stores budgets
README.md - Event gallery → MySQL database: stores gallery data
README.md - Notifications → MySQL database: stores notifications
- Analytics and reports → MySQL database: queries metrics
README.md