July 2016 to August 2016
e:Vision implementation of student online enrolment
I helped the team implement a new student portal for completing enrolment as well as viewing previously completed courses. I had four distinct roles:
Enrolment Summary Page
- Creation of new summary page, showing courses previously enrolled and courses pending enrolment.
- Re-engineering of process to locate available interview slots during a specific period of time.
- Creation of administrative process to handle the printing and delivery of student ID cards.
- Resolution of minor issues, bug-fixing, testing and escalation.
The summary page had two components:
- Table showing list of courses pending enrolment. A button provides a link to a task allowing completion of each enrolment.
- Table showing historic list of courses where student has previously enrolled or withdrawn.
In both cases, clicking on the course title would open a dialogue box listing details about that particular course.
The work described above required the creation of new CPGs, CONs, COPs and role groups (RGDs). Additionally, new SLPs and RQHs were created to output the current and previous academic years based on both the current date and the corresponding entries in AYR.
Process rewritten (mainly using SQL) to list appointment slots available and provide the means to book a place on a specific slot.
Student ID Cards
This was a TKT-based process, created for university administrative staff, that performed the following functions:
- List all newly enrolled students who have submitted a photo for their ID card that has subsequently been approved.
- List all newly enrolled students where their ID card is pending collection / delivery.
- Provide means to filter list of students based on course start date and whether student is on or off-site.
- 'Post' button to flag when single ID card has been posted.
- 'Print' button to flag batch of students as having had ID card printed.
- 'Collect' button to flag batch of students as having had ID card collected in person.
Additionally, several RQH / RQI records were created retrieve and update batches of students.
Editing of HTS / CSS / JS files following 9.1.0 upgrade
Following the upgrade to 9.1.0, I was responsible for editing HTS, CSS and JS files to ensure e:Vision was following BCU branding guidelines, whilst incorporating critical Tribal updates.
This project was a delicate balancing act between three potentially conflicting areas:
- Maintaining BCU legacy code and existing functionality
- Re-styling all pages to ensure compliance with BCU branding guidelines
- Implementation of as many Tribal updates as possible, especially related to responsive design
Changes to HTS files were deliberately kept to a minimum, keeping to the latest Tribal versions were possible. New BCU style sheet was created to ensure brand compliance. A new jQuery script was implemented in order to resolve any remaining issues that could not be resolved by styling alone.
Begun in June 2016
Responsible for fixing various issues encountered since go-live implementation, as well as implementation of âwish listâ developments.
Curriculum Manager is a large and complex implementation of process manager, allowing support staff to create a new programme of study with the necessary means of supporting documentation and approval processes, all implemented via e-Vision.
I was responsible for tackling a long list of issues with the existing live implementation of Curriculum Manager as well as implementing a series of new developments required and also some items from a 'wish list' of desired functionality. Changes made:
- Completely re-engineered validation process to report on missing form fields on-the-fly. jQuery would disable the 'submit' button until all mandatory fields had been populated. User notified of all missing mandatory fields.
- Created new process to ascertain percentage complete for each section within a programme and only allow submission once all mandatory fields had been entered. A progress bar for each section is displayed on a summary page to provide a quick overview for the entire programme.
- Fixed issue with two academic year drop-down menus, ensuring one would auto-populate whenever the other was changed.
- Resolved issue with creation of C-blocks (i.e. course blocks spanning across an academic year boundary); identified data error in AYR table.
- Created page element to report on document(s) uploaded (i.e. when submitting supporting evidence).
- Created RQH / RQI and jQuery scripts to auto-populate school and department drop-downs based on selected faculty.
- Resolved several issues related to form data not being written back to PMOD screen.
Not quite a full-blown project, a mini project is a significant piece of work scoped, tested and implemented using normal software development methodology. A mini project will typically be an improvement to a business process, introducing efficiencies and reducing complexity where possible.
Resolution of issues with e:Vision clearing implementation
At the time, BCU was one of only a handful of institutions using the new Tribal e:Vision clearing component, XCLR. I was responsible for assisting the team with both new developments and fixes to existing issues. Time-frames were very tight on account of the imminent beginning of clearing. Changes made:
- Created custom dialogue pop-up, to alert user when no courses were selected (and thereby disabling the âsubmitâ button).
- Implemented new 'submit' button and hid existing Tribal 'submit' button, using jQuery to trigger legacy button only under specific circumstances (e.g. user selected one or more courses).
- Various re-styling done, to ensure BCU branding compliance.
- jQuery used to replace default Tribal headings with BCU-styled headings.