We’ve managed to complete the all the integration from our current systems (Celcat and Sits),  so we now have a completed view of the student time table and changes.

From that we’ve been able to create a messaging table which so far stores messages on time table changes. Based on this messaging table we’ve created a draft RSS feed and an email broker using database mail in SQL Server 2005.

We’re currently investigating the quality of the data we get from our current systems.

Sits in particular could potentially hold a great deal of useful data on the students current channels of contact; like university email, personal email and mobile telephone number. This could speed up the registration process and remove any “I’ve already given them this once” feelings the students might have.

Also, hopefully, we’ll be able to extract which modules the student is currently on and send them the correct time table changes / module updates from sits.

We’re also currently meeting with other university staff members with knowledge on our room allocation system – Celcat. Less is known within the team about Celcat at this stage.

We’re starting to look at the scope of the project, the technological challenges and the data requirements involved.  Today we had a meeting with Paul Sharples who has been developing a widget server to discuss the possibility of using it in the project. 

Authentication
Our discussion brought up a number of issues.  A key concern was how to authenticate student users requesting information from within different applications, devices or widgets.  One idea that came up was the concept of generating a key per student which would represent the course, modules and module occurrences they are studying but not their identity.  This could be provided to the student who could then use it to return information specific to them whilst keeping it separate from their personal identity.

We also discussed whether widgets are the right way to go for all strands of information delivery within the project.  In some cases simpler RSS might be sufficient and usable by more platforms.

The Only Connect project at the University of Bolton is one of 6 small-scale pilot projects that have been funded to support institutions in their responses to to emergent technologies.

Other pilot projects are in progress at Staffordshire University, University of Cambridge, Kingston College,  Ravensbourne College of Design and Communication and Manchester Metropolitan University.  A full list of projects with summaries and accompanying links can be found at the JISC site.

Today I attended a brief introductory meeting with the project leaders and the JISC support team at the JISC Innovation Forum 2008, held at Keele University.  Project leaders outlined their projects and agreed to organise an event for development teams to meet and exchange ideas/experiences later in the year.

Mark Stubbs from the REACh project at Manchester Metropolitan University was present and expressed interest in identifying opportunities for collaboration.