Nigerian Army University Biu Student Attendance

Nigerian Army University Biu Student Attendance is an attendance experience designed for university classes. This repository contains an interactive, browser-local MVP prototype and the first Supabase/Postgres schema for a server-verified MVP.

Important: prototype, not an official attendance system. The current screens persist demo data in one browser. They do not authenticate users, share session state across phones, call Supabase, or create tamper-resistant attendance records. Client-side time, GPS, device IDs, and browser storage can all be changed. Do not use this prototype to determine examination eligibility. Connect the authenticated server workflow described below before collecting real student data.

What works in the prototype

• Lecturer overview, session list, student roster, attendance-risk report, and CSV downloads.
• Create sessions with course, date/time, venue, coordinates, and a 10–2,000 m radius.
• Generate a QR link, copy it, close a session, and rotate its token. Rotation replaces the previous token.
• Student check-in with ordered token/session, time-window, GPS accuracy, radius, enrolment, duplicate, and device checks.
• Browser geolocation with readable permission/accuracy failures, plus an explicitly labelled simulated-location helper for local demonstrations.
• Responsive mobile layouts, app-style bottom navigation, installable PWA support, keyboard-dismissable dialogs, reduced-motion support, high-contrast status labels, and light/dark themes.
• NAUB seal on the left, Army insignia on the right, and a full-cover NAUB campus-photo background with dashboard photo accents; the palette uses olive, field green, khaki, warm sand, and gold.
• Separate student, lecturer, and admin demo sign-in flows. The app starts on the sign-in portal, student sign-in uses normalized matriculation number plus password, and accepted sample credentials open the role-specific dashboard. The static preview is browser-only and does not create secure authenticated sessions or enforce production roles; student registration does not save production profiles.
• Browser support does not expose a device MAC address. The preview does not fingerprint devices or treat an IP address, browser identifier, or Tracking ID as secure device authentication.
• The demo contact directory provides call links and a local message composer for interface testing; it does not deliver messages between users. Production contact details and messaging must come from the authenticated university directory and a server-side notification service.
• Sample courses and student roster are included as non-production fixtures in the UI.
• Lecturer demo users can publish, reschedule, cancel, and start attendance for class schedules. Student demo users see enrolled-course schedules and deduplicated schedule notifications; browser storage and polling keep the preview synchronized across open tabs.
• Administrators can manage faculty-labelled venues, mark rooms unavailable for maintenance, and review current venue bookings. Lecturer booking forms hide inactive or overlapping venues and include faculty, campus, building, type, and capacity details.

Public demo login accounts

Open Student portal in the top bar and select a role. The Use button fills that role's sample credentials; submit the form to open its demo dashboard.

Role	Username / matriculation number	Password
Student · Chiamaka Okafor	190401001	StudentDemo26!
Lecturer · Dr. Amina Yusuf	lecturer.demo	DemoLecturer26!
Admin · NAUB Administrator	admin.demo	DemoAdmin26!

These credentials are deliberately public, hard-coded UI fixtures. Anyone can inspect them, and they provide no authentication, role protection, account persistence, or access to official records. Never reuse them as real credentials.

Apply supabase/attendance_present_migration.sql after the base schema to add normalized matriculation identities and both server timestamps for immediate Present attendance. The SQL provides the atomic authenticated mark_present(session_id) RPC and preserves existing records. When a user signs in through Supabase, the UI calls these procedures through js/naub-data.js; the local demo accounts keep using browser-local sample data.

Apply supabase/class_schedule_migration.sql after that migration to add lecturer-owned schedules, schedule history, notification de-duplication, schedule-linked sessions and attendance, and the authenticated publish_class_schedule, update_class_schedule, cancel_class_schedule, and start_scheduled_attendance RPCs. The schedule RPCs enforce course ownership and lecturer approval on the server; the UI's local demo controls are not a substitute for these RPCs. When a user signs in through Supabase, the UI calls these procedures through js/naub-data.js; the local demo accounts keep using browser-local sample data.

Apply supabase/venue_booking_migration.sql after the schedule migration to add venues, venue history, faculty/campus-aware schedule venue links, administrator-only venue management RPCs, and transaction-safe overlap checks. It uses a PostgreSQL advisory lock plus a trigger to prevent simultaneous overlapping reservations; cancelled schedules no longer block a venue, while configured venue buffers are respected. When a user signs in through Supabase, the UI calls these procedures through js/naub-data.js; the local demo accounts keep using browser-local sample data.

Apply supabase/lecturer_attendance_migration.sql after the venue migration to add server-authoritative lecturer check-in records and the check_in_lecturer(schedule_id) RPC. It also adds the academic-session profile field used during student registration.

This is the beginning of the README. Read the rest at the original. Read the full README ↗