The University Problem: The NSTP

The University Problem: The NSTP #Solving the ISO Attendance Problem: ●​ The Mobile Clock-In: When students arrive at the barangay for street sweeping, they open your mobile app. The app checks their phone's GPS. If they are within the 500-meter "Geofence" of the assigned barangay, the "Clock In" button unlocks. ●​ The Backend Magic: Your Python backend (using FastAPI or Django) records the exact timestamp and coordinates into the AWS RDS database. ●​ The ISO Generator: At the end of the day, the NSTP Coordinator logs into the Web Dashboard and clicks "Generate ISO Attendance." Your Python backend uses a library like openpyxl or ReportLab to inject the day's data into the exact Excel/PDF template your university requires (complete with the university logo and headers). ●​ The Result: The coordinator simply prints the perfectly typed, auto-calculated sheet, and the students just sign beside their pre-printed names. It is 100% accurate and ISO-ready. #Solving the Google Drive Nightmare ●​ Structured Uploads: During the activity, students use the app to take their required "Action Photos" and type a short caption (e.g., "Planted 5 mahogany seedlings in Brgy. San Juan"). ●​ Cloud Storage: The photos are automatically compressed by the app and securely uploaded to your AWS S3 Bucket. The database links that specific photo directly to the student's ID number. ●​ Auto-Compiled Narrative Reports: When the semester ends, the student doesn't need to manually create a Word document. They just press "Generate Narrative Report" on the app. The Python backend pulls their total hours, all their captions, and all their photos, and automatically renders a clean, formatted PDF document. The coordinator can view all 500 reports directly on the Web Dashboard without requesting a single Google Drive access link. # The Security & Anti-Cheat Features ●​ Device Binding: A student's account is tied to their physical phone's MAC address or device ID. They cannot ask their classmate to log in for them on a different phone. ●​ GPS Anti-Spoofing: You can integrate basic checks in the mobile app to detect if the student is using a "Fake GPS" app (mock locations). ●​ Live Selfie Metadata: When they clock in, the required selfie is stamped with a non-editable time and GPS coordinate watermark before it hits AWS. The Updated Workflow: "Weekly Milestones to Final Compilation" Phase 1: The Weekly "Post-Deployment" Report Instead of a Google Drive folder, your mobile app acts as the student's weekly logbook. ●​ The Trigger: After the student clocks out of their NSTP location using the GPS geofence, their app dashboard updates: "Week 1 Deployment Complete. Weekly Report Unlocked." ●​ The Input: Before the week ends, the student must open the app and fill out the structured form for just that week (Tasks done, challenges, 2-3 action photos uploaded to AWS S3). #siguro for the inputs na kelangan sa report pede dpt ma edit ng admin kung ano kelangan sa report so hindi dpt hard coded yung mga hihingin sa report ●​ The Submission: They click "Submit Weekly Report." The database locks that specific week's entry so the student cannot secretly edit it later. Phase 2: The Coordinator's "Weekly Approval Queue" This is where you solve the coordinator's headache. ●​ The coordinator logs into the Web Dashboard and sees an organized notification: "You have 45 Pending Weekly Reports for Week 1." ●​ They don't have to download anything. They click a student's name, and the text and photos load instantly on the screen. ●​ The Action Buttons: The coordinator clicks either "Approve" or "Needs Revision". ●​ If they click "Needs Revision," they type a quick comment (e.g., "Your reflection is too short, and your photos are blurry"). The Python backend instantly sends an SMS or push notification to the student to fix it. Phase 3: The Grand Finale (The Magic Button) Because the coordinator has been approving these reports week by week, the end of the semester is entirely stress-free. ●​ The Magic Button: The student logs into the system and clicks "Generate Final NSTP Portfolio." ●​ The Python Compiler: Your backend script queries the database and fetches only the weekly reports that have a status of "Approved". ●​ It stitches them all together into one massive, beautifully formatted, ISO-compliant PDF. ○​ Page 1: Official University Cover Page ○​ Page 2: Total Hours Summary & E-Signatures ○​ Pages 3-4: Week 1 Narrative & Photos ○​ Pages 5-6: Week 2 Narrative & Photos... and so on. ●​ The coordinator receives the final compiled file, perfectly formatted, with zero Google Drive links involved. Attendance part 1. The Student Interface (Mobile App) The student's mobile app must be lightweight and heavily rely on location services. The goal here is "No Geofence, No Clock-In." ●​ Screen 1: The Deployment Dashboard ○​ When the student logs in, they see a "card" showing their assigned NSTP activity for the day (e.g., Street Sweeping at Brgy. San Juan). ○​ It displays the required time (e.g., 8:00 AM - 12:00 PM) and a mini Google Map showing a circle (the geofenced radius) around the Barangay Hall. ●​ Screen 2: The Smart Clock-In Screen ○​ At the bottom of the screen is a massive "CLOCK IN" button. ○​ The Lock: If the student's phone GPS detects they are at home or at McDonald's (outside the 500-meter radius of the barangay), the button is grayed out and says "Move closer to the deployment site to clock in." ○​ The Unlock: Once they physically step inside the radius, the button turns green. ●​ Screen 3: Proof of Life (Selfie Verification) ○​ When they tap the green "Clock In" button, the app opens the front camera. ○​ They take a live selfie with the barangay background. They cannot upload an old photo from their gallery. ○​ The system watermarks the photo with the exact Date, Time, and GPS Coordinates, then sends it to your AWS S3 bucket. ●​ Screen 4: Active Timer #maganda sana to kaso ang naiisip ko ay kelangan bukas lagi data tapos dpt maging low lang kain sa data tapos pero maganda ○​ The screen shifts to an active state: "Currently Deployed: 2 Hours 15 Mins." * When their shift is done, they press "Clock Out," which triggers the exact same geofence and selfie check to prove they didn't leave early. 💡 The Tech Flex (For Your Panel): > You can explain to your panelists that your Python backend calculates the distance between the student and the barangay using the Haversine formula. This mathematical formula calculates the shortest distance over the earth's surface: $d = 2r \arcsin\left(\sqrt{\sin^2\left(\frac{\varphi_2 - \varphi_1}{2}\right) + \cos(\varphi_1) \cos(\varphi_2) \sin^2\left(\frac{\lambda_2 \lambda_1}{2}\right)}\right)$ (Where $\varphi$ is latitude, $\lambda$ is longitude, and $r$ is the Earth's radius). If $d$ is greater than 500 meters, your backend throws an error and rejects the attendance! #dko alam to kung pano to pero parang kelangan natin siguro ma pin point yung mismong range ng baragy katulad nung kay ser ual na project yung sa farms 💻 2. The Coordinator Interface (Web Dashboard) The coordinator does not need a mobile app; they need a wide-screen command center. Their interface focuses on macro-management, live monitoring, and generating those critical ISO documents. ●​ Screen 1: The Live Deployment Map (The "Command Center") ○​ On a Saturday morning (when NSTP usually happens), the coordinator opens this screen. ○​ They see a large map of Malvar/Batangas. There are green dots flashing on the map representing students who have successfully clocked in at their respective barangays. ○​ On the right sidebar, there is a live tally: "Brgy. San Juan: 45/50 students present. Brgy. Luta Norte: 50/50 students present." This lets the coordinator know instantly if a group is understaffed. ●​ Screen 2: The Attendance Roster & Anomaly Checker ○​ This is a clean, searchable data table. The coordinator can filter by Course, Section, Barangay, or Date. ○​ Anomaly Flags: The system automatically highlights rows in red if there is a problem. For example: ■​ Flag: "Student clocked in, but GPS accuracy was poor." ■​ Flag: "Student took a selfie, but facial recognition couldn't detect a face" (if you want to add a basic AWS Rekognition API later). ○​ The coordinator can click any student's name to see the exact time they logged in and view their watermarked selfie. ●​ Screen 3: The ISO Export Module ○​ This is where you solve the ISO hardcopy problem. ○​ The coordinator selects a section (e.g., BSIT 3-A), selects a date, and clicks "Generate Official Attendance Sheet." ○​ The screen gives them a preview of the perfectly formatted PDF/Excel file, complete with the university header, document control codes (e.g., ISO-NSTP-004), printed student names, computer-verified time-in/time-out, and a blank column for the students to affix their physical wet signatures later.