Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgradation Results Case #81

Open
gauravjain2 opened this issue Jan 25, 2021 · 13 comments
Open

Upgradation Results Case #81

gauravjain2 opened this issue Jan 25, 2021 · 13 comments

Comments

@gauravjain2
Copy link

This doesn't properly take case of students who got upgraded in overall result.

Let's Say Student 'A' did B.Tech in ECE in 1st and 2nd Sem and then got upgraded to CSE in 3rd Sem. Then, in this case, the website is showing overall percentage counting from sem 3 onwards and not counting the sem 1 and 2 result.

Issue you will face is that enrollment number of student changes after upgrading but the result for earlier semester is carried forward.

@ankushgarg1998
Copy link
Owner

Right. I don't know how you're listening in on my conversation with @eshaan7 😂 but you're raising the same issues.

I've had this problem since day one. Was trying to ignore it for as long as possible 😛
The issue here is that exactly what you pointed out in the last statement.

@ankushgarg1998
Copy link
Owner

Just the fact that we do not have any publicly available mapping of connecting enrollment numbers, makes this problem theoretically impossible to solve.

@ankushgarg1998
Copy link
Owner

The only way out of this is an option that allows a user to enter both his enrollment numbers, and shows him his individual collated result.

As discussed in #43

@eshaan7
Copy link

eshaan7 commented Jan 25, 2021

The only way out of this is an option that allows a user to enter both his enrollment numbers, and shows him his individual collated result.

As discussed in #43

Yep. Often the best solution is: no overengineering :D.

@divyansh000915
Copy link

I am one of USICT (Formerly USIT, consider changing college name too) students upgraded (intra college) (2022 batch) in 2019 (after 1st year)

Here's the list of upgraded students of my batch, Older Roll Nos. can be found below, For New Roll Nos., you may try searching in the new branch with the student's name, phone no. or like a pool of comparisons or some other way. Another idea (for USICT UPGRADATION cases) is to check for missing student records in the 3rd sem (4th sem preferably) lists and compare with other branch records for that semseter [Just giving a clue]
http://ipu.ac.in/Pubinfo2019/upgrade040919.PDF

@gauravjain2
Copy link
Author

gauravjain2 commented Jan 25, 2021

Just the fact that we do not have any publicly available mapping of connecting enrollment numbers, makes this problem theoretically impossible to solve.

About the public mapping
Each year university releases such mapping on the website.

Here is an example from session 2018-19 Revised Enroll No

But that's a scanned copy and I don't think it can be directly parsed
And would take up a lot of manual work, though.

@ankushgarg1998
Copy link
Owner

Wow 😂
I guess we've established I know very little about my own university. I had no clue this info was publicly available.

Having said that, that's about 200 manual entries. Not scalable at all.

@ankushgarg1998
Copy link
Owner

Unless some Cybersecurity guy helps me hack the actual PDFs/Excel sheets from IPU. 🌚
Nudge Nudge @eshaan7

@ankushgarg1998
Copy link
Owner

ankushgarg1998 commented Jan 25, 2021

I am one of USICT (Formerly USIT, consider changing college name too) students upgraded (intra college) (2022 batch) in 2019 (after 1st year)

Here's the list of upgraded students of my batch, Older Roll Nos. can be found below, For New Roll Nos., you may try searching in the new branch with the student's name, phone no. or like a pool of comparisons or some other way. Another idea (for USICT UPGRADATION cases) is to check for missing student records in the 3rd sem (4th sem preferably) lists and compare with other branch records for that semseter [Just giving a clue]
http://ipu.ac.in/Pubinfo2019/upgrade040919.PDF

@divyansh000915 Thanks for bringing this up. I've given the solution you're suggesting, a fair amount of thought.

Let's say I set-up a system to match enrollment numbers with only 1st 2nd sem result and corresponding 3-8th sem result. Let's say I even add an admission year consistency check over the same "name" check too.
This is not enough to conclude that these two can be joined (without any conflicts).

There could always be two students with the same full name migrating in the same year.

Student A with name "Raj" migrating from EEE to CSE.
Student B with name "Raj" migrating from ECE to CSE.

We'll not be able to programmatically determine (given the data we have), which one's which.

@eshaan7
Copy link

eshaan7 commented Jan 25, 2021

Having said that, that's about 200 manual entries. Not scalable at all.

So about 200~ and that too each year!

Unless some Cybersecurity guy helps me hack the actual PDFs/Excel sheets from IPU. 🌚

I stick to the original solution ref. xD
One thing to make it easier for such students would be an URL pattern like this perhaps:

https://www.ipuranklist.com/migration-student/<roll_no_1>/<roll_no_2>

@ankushgarg1998
Copy link
Owner

So about 200~ and that too each year!
🤯

I stick to the original solution ref. xD
😆

One thing to make it easier for such students would be an URL pattern like this perhaps:
🔥

@ankushgarg1998
Copy link
Owner

#43 is resolved now.

For all the migration and upgradation students:
https://www.ipuranklist.com/upgradation-student

Go Nuts!

@ankushgarg1998
Copy link
Owner

ankushgarg1998 commented Aug 21, 2023

RECENT FINDING

There's something called "Student ID". It remains the same across multiple enrollment numbers of a student for the following cases:

  • Changing branch (Upgradation)
  • Changing college (Migration)

This problem of linking two enrollment numbers might actually be solvable!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants