It’s been a while since my last SystemOne related post. Here are some updates so far:
- An important part of our registration process is the updating of student checklist. We have an online prototype application for this, but I found a very important glitch (several in fact) that makes it unuseable for the web processing. I found out for example that it takes a long time to process a checklist with many entries especially in getting the recommended courses. REGIST is still better for this job. Anyhow, a student who does not update his/her checklist increases the chance for him/her to have problems during preregistration/registration.
- To lessen our problems during registration, the ad hoc registration committee for the university ( OUR, the college secretaries and I) devised the SystemOne Form 1, which was discussed as “SOF 1″ in a report made by the CAS. This quarter-sheet paper enables the student to add recommended courses even if the course is not yet in the proper schedule (ie. plan of study) as long as it is approved by his/her adviser. One drawback for this is, each college secretary had to process this during registration which is really a hassle. Pasaway talaga ang UPLB student. UPLB seniors are especially lax during their last year. The “SOF 1″ should have been used only during the preregistration period.
- I had to create several mini programs to clean up the database once the grades were in. One drawback of the preregistration is: because we assumed that students will pass their current courses, WHICH is really a bad idea but we make do anyway. The programs I created cleans up the recommended courses and slots of people who failed in their subjects.
- AS a result of the above: during the registration, I had students contacting me why they lost some of their slots, apparently they forgot about the “agreement” that you don’t have the right to hold on to your slots if you flunk in your current subjects especially if they are prerequisites. They wanted me to call their college secretaries, even their teachers, to confirm their grades. A usual conversation goes this way:
- Student: Sir ba’t po nawala yung slot ko sa Subject X?
- Me: Did you get an INC/4.0/5.0/U in a subject for the past sem? (esp. prerequisite). [Note some students stop the conversation after this question. ]
- Student: 4.0 po ako pero na remove ko na po noong <date here>. [Note some removal grades were considered especially for subjects whose removal/completion grades were submitted early].
- Me: [I check submitted data]. The grade is not here yet.
- Student: Pero naremove/complete ko na po e, <grade here> po ang grade ko dun.
- Me: I wouldn’t know. [I briefly explain the limits of my responsibility] I only use what data they give me, and what they give me is what I have now. I don’t change grades, because hey, I didn’t give you your grade and second I would need to see proof na pumasa ka nga, hindi yung sinasabi mo lang and that the proof is sent by your college secretary or the teacher. Also, my responsibility is limited to maintaining the system and fixing technical problems. Grade problems are not technical problems.
- Student: Pero sir, kelangan ko yung slot na yun. “Paki”tawag naman po sa college secretary namin to get my grade, etc.. etc.. etc…
- Me: [ Says outloud but not on the chat ] W*F it’s freaking SUNDAY (it was the first sunday of November back then)! [I have been staying in at the office since Friday night - going home for personal sanitation]. I end up saying: “Again that’s not my responsibility. The only advice I can give you is to come here ASAP and see this problem fixed yourself.”
- Student: Not possible, [W*F, e di wag!] I am far away from Los Banos…blah blah…what’s the point of being online…blah blah blah….
- Me: [Sarcastic Mode] Well I already told you what to do. [It was somewhat cruel but I said] May you should not have gotten a 4.0 in the prerequisite.
- Student: [Starting to b*tch up] Blah blah blah…do you know how hard the subject is…. [Magtake ka din kaya ng CMSC subjects]….blah blah blah ang yabang mo naman blah blah blah…..
- Bottom line of this story: You get a INC/4.0/5.0, it doesn’t really end up good for you, so suck it up and live with it.
- I had the chance to look under the hood again and looked up at my former student’s database code, and boy was it messy. I really should see to the other database routines we have used, I cleaned up some and the performance came out better. For example, I simplified and reduced the code for the conflict checking method, initial performance data indicates faster performance ( I have to recompute but 70+% better performance was noted).
- There was this stupid data import error that entirely ignored the T in TTh that is why the system saw TTh classes as only Th classes leading to some conflict errors especially for TTh classes. The error was found to be made by the data importer. Day schedules are denoted using integers which are the integer equivalent of the binary rep of the schedule. For example: 101000 is 40 which means MW, 010100 is 20 which means TTh. TTh classes were imported as 4 (which means Thursday only). This error was detected almost midway into the registration week.
- I created a new and improved classlist printable format.
- I created PHP code to email students daily of their PS Form updates (or no updates) and implemented an email way of finalizing student schedules. Apparently a great number of students do not read my PLEAS in the email. I pleaded that they cannot use email to enlist in courses and yet here is a great number of emails doing just that and I swear I could have replied with all FLAME text.
- I bungled up a print batch leading to double printing of Form 5s (Just one batch) but I am writing this down to TAKE NOTE OF MY oversights.
- Some chap reported that it was possible that a student maybe enlisted in a subject that is not yet recommended for the student by copying a link in the web page and changing details of the link and inputting the link in the address bar of the browser. I tried to replicate what he said but somehow, I cannot find a single random student where that happened to. Unbeknowst to all, the things they see in the links are for crosschecking only. The server remembers what you do and uses those information when doing something at least for the case of enlisting.
- I did not remove students who did not finalize their PS Forms from the classlists. AGain another lesson of good intentions leading to mayhem. I should have done exactly what was supposed to be done.
- On the last day, ONE of the greatest mishaps to an otherwise smooth week, I bungled up a query that messed up some of the classlists ( a great number of them actually) and we had to stay overnight the next day to fix this and delay the printing of the last batch of printing of Form 5s. This caused a problem in the classlist printing, some departments actually complained. I spent all week guarding against possible errors and attacks
- The lesson from the above is: the greatest threat to the system is not some student who thinks he found a way to circumvent the system, nor a hacker — it is me.
After all that here are what we plan to do:
- Change the waitlist system to the following: A student can only be waitlisted to one specific section OR to the so called universal waitlist which will enlist the student to the first available slot that frees up or created.
- I will yet suggest this and I hope my bosses will agree: A “FORFEIT” button. Let me explain this part:
- REGIST distributes slots in its most optimal way it can process.
- It tries to distribute limited number of slots to many students, and tries to give good standing students full load.
- There are still some parts that we need to change in REGIST most especially in the case where students are given over the required load.
- Aside from the above, it tries to give slots to students the best it can.
- HEre is a what we want to happen: I, personally, go for a complaint-free system. Of course when you complain about things like this it usually means you do not understand what the events were that lead you to the current situation.
- Now, 4 students are given 15, 12, 9, 6 units. Now we find out that :you give units to students and they will complain: you give them less than the required because there is no other choice at the moment–THEY COMPLAIN. YOu give them full load — THEY COMPLAIN (i.e. all GE for example because again there is no other choice). YOu give them over load — THEY COMPLAIN ( hell, go cancel! that’s what the SystemOne OCM for right?).
- So with the four students, if any of them want to complain, they click the FORFEIT button. That means they don’t like what is given to them that they did not go through hell to get. What happens is, their slots are redistributed to other students.
- So if say the 9-unit holder presses the button and his slots are useable by the 15-unit holder and 12-unit holder, we get two students who get say 18 units who are now less like to complain, leaving 2 students who will surely complain.
- Notice the difference: before we have 4 complainants, after only 2.
- I hear students are still blaming me for their misfortunes i.e. on their slots. I think I am now exasperated to even argue to the fact that I don’t have anything to do with their getting less than what they want. How out of place is it that I (or “SystemOne” for that matter) get to be blamed when you are #1 in the waitlist and it seems not to be changing. Maintaining and managing a computerized system is really hard that’s for sure. The only fun I get is of course I can be my sarcastic self and call them “misinformed” or the more sarcastic and fun version : “studid”. I am sorry I can’t help myself and not say it.
.