avantifellows / avantifellows/external_data_sources

dakshana_fact_reported_results: only 2025 + only JEE-Main/NEET (no Advanced, no earlier years)

Open
#54 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1
Forks
1
Avg merge
7h 7m
Merged PRs (30d)
32

Description

**Problem.** `dakshana_fact_reported_results` currently holds **only `test_year = 2025`** and **only `exam IN ('JEE Main','NEET')`** (371 rows: 253 JEE-Main across 5 JNV CoEs + 118 NEET at Pune). It has no JEE-**Advanced** results and no 2023/2024 cycles.

**Why it matters.** Dakshana's own published annual reports carry, per JNV CoE, the JEE-Advanced / IIT-seat and NIT-seat splits and multiple prior years — the exact outcome detail analyses need to project centre results. Today that lives only in PDFs, so any per-centre Dakshana outcome analysis has to hand-scrape the ARs.

**Evidence.** AR24/AR23 give e.g. JNV Bengaluru Urban: Class 2024 = 235 took JEE → 206 IIT / 25 NIT; Class 2025 = 76 → 63 IIT / 10 NIT. JNV Pune (NEET): Class 2023/24/25 = 40/50/118. None of the IIT/NIT/MBBS-seat splits or the 2023-24 batches are in the table.

**Open question for the data team.** Can Advanced results and the earlier (2023-24) cycles be ingested into this table (from the same Dakshana source), so it becomes the single machine-readable record instead of the ARs?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the dakshana_fact_reported_results table and its existing ingestion entry point. Review the AR24 and AR23 Dakshana reports for the JEE-Advanced, IIT/NIT-seat, and earlier-cycle records, then verify that the table contains the requested 2023–2025 results and centre-level outcome splits.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.