Had some of the results back from the evaluation at the Sled workshop and a number of people have mentioned about the left hand menu being too ‘close’ to looking like learning design and so being a bit confusing. I can see exactly where they are coming from as I agree, but the problem I have is what to do about it.
The current men system is set up as it is because the LD spec allows titles to be places at virtually all levels, eg activity structure, activities, items etc (made more complicated again by the ability to nest all these items), so different LD authors may decide to place the titles at different places. For example author A might decide to use the title tag within the item, author B might use the title tag within the activity and author C might decide to use a mixture.
This then makes it very difficult for the player to know which ones should be displayed (any blank titles or missing title elements are just ignored by the player anyway) – especially if the author has been ‘thorough’ and completed all the title tags for each element. The only way around that I can see is just letting the player display say the activity structure and item titles and them everything else is ignored, but then authors who have completed more might get confused as to why it’s not getting displayed.
Anyway, if you have any bright ideas as to how this could be resolved then please let me know!
I attended the recent Unfold CoP meeting in Glasgow which was very useful – all the presentations etc are available via the Unfold project website. The most useful parts for me were….
- We (well actually Patrick & Diane) ran a workshop on our Sled player, which seemed to go well, though we had a few problems with the responsiveness of our Sled demo site (more about that later!!)
- I presented some of the work I’ve been doing with the integration of external services into LD, eg how we did the QTI integration and the problems we had in using the same methodology to integrate ePortfolio.
- James Dalziel’s presentation on the updates they’ve been working on for LAMS, and the new release that is due out soon, with the ability to be able to write your own tools to plug into the LAMS interface. Would like to get chance to explore and have a look at what they’ve done in more detail
- Scott Wilson’s presentation which gave much more detail on the tools integration method used by LAMS – I think it’s a really good start at being able to connect up different service providers, but it’s not quite a ”plug and play” type of methodology just yet !
- Mark Barrett-Baxendale’s presentation on their real life use of learning design on actual students at Liverpool Hope University – where they are making use of CopperCore engine and the Sled player
One thing that did come up were some performance issues that we’ve not been able to resolve yet and we’re not yet sure of the actual cause, if it’s the Sled player, CopperCore engine or something else. When we were running the workshop we found that having 15 or more people connecting to our demo system at the same time slowed the system down to a crawl – making it almost unusable. I thought that this may be due to the fact that it’s just running on a desktop machine and we’re only using the default database, rather than upgrading to MSSQL or PostgreSQL and that upgrading the database or putting it on a bigger machine would solve the problem. However , when Mark presented their work at Liverpool Hope Uni, they are also having performance problems if they have a whole class of students accessing the system at the same time. There, they already have upgraded the database to PostgreSQL and are running it on a ‘proper’ server.
So, I’m not sure where the problem lies, whether its the Sled player, or CopperCore, but to help try and track down the problem I’m going to find a load testing tool and run it against an installation of Sled and the CopperCore player on one of our servers and see what happens. Finding what the problem is will probably be the easy part though – going to be more difficult to figure out what to do about it!
After I’ve spent a bit of time looking at this performance stuff, I’ll then get back to what I’m meant to be doing for the JISC toolkit and demonstrator projects as I still have quite a few bits to finish off for these, and need todecide what the priorities are for the last couple of weeks.
Have been away quite a lot for the past few weeks – hence why I’ve not been keeping this up to date. I attended the latest Unfold CoP meeting in Glasgow a week or so ago which seemed to go well, I’ve put more about this in my LD blog, so have a look there!
I’ve just been back in the office for a day now, so just catching up on things. On 10th Oct we released our new IET website; the actual design hasn’t changed (well, only a little) but we have:
- Created the site content from scratch – there were 100’s (or 1000’s) of old, unmaintained, out of date pages on the old site, so in starting afresh we have removed all of these. They are still available on backup if we do need to restore any sections/pages for any reason, but we hope we’ve got the main content areas covered
- Moved to a clustered servers – so the website should be much more robust. Though we have had some intermittent problems with one or other of the cluster servers becoming unresponsive overnight. I think we’ve got this fixed now – might have been due to one of the server timeout settings not being set, so if a long running page was hit (or caused an infinite loop) the server didn’t automatically terminate the request after a certain amount of time.
- Changed the publishing system for the site – now all IET staff can edit the site via their web browser (a bit like a wiki) and everynoe has access to edit any of the pages. Previously people needed to use Dreamweaver or other web editing software to actually go and edit files – and also have access to the files. This meant that updates to the site often didn’t get done because of the hassle invovled in finding the right person who has access etc etc. We’re not sure yet that this will definitely solve the problem – but it does mean there is no excuse if someone spots a typo or incorrect email address etc for them not to just go and update the page themselves. It also means we can track more easily pages which haven’t been updated in a certain length of time – I think we should be aiming for ensuring pages get updated at least every 6 months – or at least reviewed even if nothing actually needs to be changed.
The next thing I’ve got to work on is getting the LD JISC projects finished off and what should be the priorities to get done, and also some work finishing off bits on the new IET site.
I’m just now beginning to install the ePET tool, so that I can explore what web services functionality it has and how I may be able to link this up to the Sled player. There seems to be a few bits and pieces to get installed (mysql, zope etc) in order to get ePET running, but I’ll log here any problems that I come across.