The portal rejected 'PHYSICS' because it expected 'Physics' — case-sensitivity bug
🎓 Debarghya Ghosh, 20, Baranagar, North Kolkata. Jadavpur University B.Sc Physics, 87% in WBCHSE Class 12 Science. Father: private school teacher. Mother: housewife. Family income well below ₹2.5 lakh threshold. He ticked every box. SVMCM portal rejected him. The reason: "Institution enrollment data mismatch."
🚨 The problem
Jadavpur University's administrative system stored department codes in all capitals for backend consistency. When the system auto-populated enrollment data for the SVMCM portal, it submitted 'PHYSICS'. The portal's validation function was case-sensitive — it expected title case 'Physics'. A system designed to prevent fraud (detecting when actual enrollment didn't match submitted data) had created a deadlock instead. Neither the university nor Debarghya knew what was wrong.
🚀 How GabFORGE helped
An AI system (and Debarghya's IT-professional cousin) diagnosed a technical bug:
- 🔍 Identified case-sensitivity. Explained that the portal's validation function was checking exact string match, not just content. Department names in all caps would fail.
- 💬 Named the fix. Ask the university to resubmit with 'Physics' in title case. Most university systems allow corrections within application windows.
- 📞 Found the BDO income certificate shortcut. Explained that West Bengal requires government-issued income certificates (not employer letters) — free through Block Development Officer, 10–15 days, takes one office visit.
Drafted email to Jadavpur University scholarship cell on May 9. University resubmitted with corrected capitalization by May 12. Portal accepted within 6 hours ✅. Visited South Dumdum BDO office May 15 with required documents. Income certificate collected May 25. Submitted to SVMCM + simultaneously filed West Bengal OBC scholarship. Both approved May 28 ✅. Combined support: ₹1,000/month (SVMCM) + ₹666/month (OBC) = ₹20,000/year.
🇮🇳 Why this matters
Portal architecture details — capitalization rules, field validation, data-type constraints — are invisible to students but absolute in enforcement. A bug in the university's data submission process created a barrier that looked like a student error. An IT professional's eye and a clear correction email translated the barrier into a quick fix. Most students would reapply the next year, losing one year of scholarship. Debarghya got both scholarships within two months because someone explained the system fault, not the student fault.
The long version has the case-sensitivity bug explained technically, the BDO income certificate process, Arjun's technical insight, and the moment both scholarships approved.