Thursday, 2 February 2017

Curriculum coverage

For the past year and a half I have been thinking about a solution to help us make sure that we deliver a balanced timetable for our students. Being the timetabler also helps to push that challenge.
At HPSS we want to develop the ideas of a Personalised LearnPath

Personalised LearnPath

The Learning Coach works with students to identify passions and link their interests and needs to their learning. Learners negotiate their LearnPath (personalised learning programme) with their Coach to ensure that what they are learning is relevant to them. The Coach supports and guides students to set and meet challenging learning goals.

We have a great system in place already to gather this information together when developing the module booklets, it is the next stage of the process. The part in hubs and selections for students that I want to develop. Looking at a students selections and trying to make sure that they have selected everything that you want, some of it is relied that it has been done correctly and the instructions followed by the student.

As timetablers we hope that this has been done correctly, checking 240 foundation students timetables takes a fair bit of trust. 
One of the teachers at the school developed a way to do this in Google sheets last year, but there is a fair bit of modification to get it going. I did wonder at the time whether I could get something similar working on the web, but I kept putting it on the back burner. 

paper checker
Ready for this year, I thought about what I had to do today and spotted some time, next thing I was in phpmyadmin developing a database to hold the requirements for our q2 programme, a quick copy of the structure and I had the q1 programme in as well. Next came entering all the codes of our modules, something simple to do with sql statements.

Then using my php template, I had all the students name listed. Now to develop a quick check programme against their selection and all the learning areas to see if the module name existed. Add a number to the counter, and display. 
Surprisingly I checked everything by running form the data exported from KAMAR and I had it working within an hour of starting.

Next I created the foundation years check and tested it from the data collected by one of my new hub students, eek, will have to go back over the requirements with this as it failed to meet the coverage.

Suddenly, this brought a new issue, why do we check at the end of the process, why not develop something that could check before the information is entered, to save any issues that may come up before they happen. A quick verification from some of the staff in the staffroom and away to develop the prototype. This will continue to develop as we go through the year that it will pull the information straight from the database, at the moment all dropdown boxes are entered manually. However it does check the selections against the database tables for learning area module names.

This is the start of the showing of what a student will have covered for a year. 
At present the student fills this in through a google sheet document. I would like them to see coverage throughout the year through a google chart API and webpage so that they can share this quickly and easily when doing reflections and check in's. How do we make learning visible?

No comments: