MGIT PYQ Hub — Editor View

Paper audit • Extraction checks • Source links

Back to Website

Editor Access

This page audits how each question paper was parsed. All questions and papers are already public on the main site, so the password only keeps these check tools together.

Cancel

Question Bank Audit

Every question on the site is traced back to a real paper in the Drive folder. This view shows that trail paper by paper.

Data from pyq-data.js Drive links verified
0 Questions in Bank After merging repeated questions
0 Unique Papers Duplicates removed by paper code
0 Papers to Recheck Fewer than 12 questions parsed
0 Non-III-Sem Papers Kept, and labelled with their printed semester

Subject-Wise Inventory

0 Subjects
Subject Full Name Papers on Drive Questions in Bank Units Covered Drive Folder

Paper-by-Paper Audit

0 Papers

A full MGIT paper normally yields 10 Part-A sub-questions and 4–5 Part-B questions. A lower count usually means the scan was hard to read, not that the paper was short.

Subject Paper Printed Sem Questions Parsed Status Source

Distribution & Recurrence

Questions by Year

Questions by Part

Repeat Frequency

Incoming Contributions

Students send papers and notes straight to WhatsApp from the website, and each one is opened, checked against the printed header, and added here by hand. Nothing is published automatically, and nothing is stored in this browser.

Open Contribution Chat Open the Drive Folder

Where the Data Comes From

Google Drive Repository

Root: SEM 3 folder, shared read-only.

Each question card links to its own source PDF page.

Open Drive Folder
Source Repository

The extractor, this page, and the question bank all live in one repo.

Repo: Amaanuddin-Ahmed/CSE-III-sem

Open GitHub
AI Answers

Handled by the serverless function /api/gemini, so the key never reaches the browser.

Checking AI availability...

Test on the Website