Video/audio conferencing tools in use in the Curriculum Delivery programme

There has been considerable use of video/audio conferencing technologies for synchronous communication and podcasts for content delivery across the programme. The increasing ubiquity of MP3 players and free audio software is increasingly making podcasts a relatively simple way to augment course content.

Conferencing software
*Elluminate: Atleir-D, Escape
*Megameeting: Cowl (trialled, but then moved to skype)
*Skype: Cowl (with conjunction with the mikago plug-in)
*WimbaClassroom: Cowl

Podcasting (creation and delivery)
*Echo360: Cowl
*Quicktime: Middlesex
*Riffly: Cowl
*Wimba voice board: Duckling
*Audacity: Kube
*Garageband: Kube

(most podcasts are available in mp3 format)

More information on the projects can be found by following the specific links in the text.
The projects have all developed resources for staff and students around the integration and use of all the technologies which are being made openly available through the Design Studio.

Online environments in use in the Curriculum Delivery programme

As the curriculum delivery programme is rapidly approaching its end (October 2010) over the next few days I’m going to be publishing a number of posts outlining the technologies in use across the programme. As with other programmes, CETIS has been recording the use of technology in our PROD database.

As I posted previously, over 60 different technologies and standards were investigated and used across the programme. As no technologies or standards were mandated the range of technologies used is not surprising. The programme is really about developing innovative approaches and processes involved towards curriculum delivery which in “this context is meant as shorthand to embrace the many ways in which learners are enabled to achieve the outcomes offered to them by a curriculum. Teaching, learning support, advice and guidance, coaching, mentorship, peer and collaborative learning, feedback and assessment, personal development planning and tutoring, skills development and practice, and enabling access to curriculum resource”
(http://www.jisc.ac.uk/whatwedo/programmes/elearning/curriculumdelivery.aspx)

The most common technology in use is the VLE, with Moodle being the most popular platform – 7 out of the 14 projects are using it. I think this probably reflects the increase in adoption of Moodle across the UK. Despite the technorati debates around the death of the VLE, they are alive and kicking and more importantly as the work of all the projects demonstrate, people are adapting/enhancing them to meet the real needs of students and staff.

The usage is as follows:

*Moodle
eBiolabs, Cowl, Cascade, G4, Integrative Technologies Project, KUBE, Making the New Diploma a Success.

*Blackboard
Duckling, Morse, Making Assessment Count

*webCT
Making the New Diploma a Success (project co-incided with institutional migration to Moodle).

*LearningNet
KLTV

*Studyspace
Kube (project co-incided with institutional migration to Moodle)

A number of project have also been experimenting augmenting course delivery with using social networking environments.

*Facebook
Atelier-D

*Ning
Atelier-D

*Elgg
Morse

Three of the projects (Atelier-D, Duckling, G4) have also been investigating the use of immersive worlds – in particular Second Life. G4 have been continuing the development and use of the Virtual Patient and Open Labyrinth which has been specifically designed for medical education.

Although offering potential for certain educational contexts, there are a number of issues around impact and cost-effectiveness of using such environments. The Duckling project have produced a useful summary of the impact and cost effectiveness of all the technologies they have trialled.

More information on the projects can be found by following the specific links in the text.
The projects have all developed resources for staff and students around the integration and use of all the technologies which are being made openly available through the Design Studio.

Simplifying Learning Design – my response

Scott Wilson has posted his views on the proposed Simple IMS Learning Design 2.0 from Guillaume Durand so I thought I’d just add my tuppence worth.

Like Scott and Durand I’m all in favour of anything that can simplify the current IMS LD spec. However before we go ahead with the technical ins and outs I would really like to ensure that any development is based on real needs – what teachers and learners actually need and what we can really expect our systems to do effectively and efficiently.

So, before we start debating what we keep in/out of scope, I’d really like to see the development of a robust and real set of use-cases. Let’s use those to engage teachers and vendors alike and build tools that do what teachers really need them too. Let’s be realistic about who is actually going to take the time to create a fully fledged UoL to use IMS speak. Not every teacher/ learning designer will or necessarily needs to. Let’s look at what people really want to do and where there is a real gap. We have a wealth of designs now that we can draw on now. What are the key things people need to do but can’t just now, or could be done more effectively by some automatic processes for example grouping, populating classes? And instead of showing the XML, let’s start with what the user wants to do and work backwards from there.

Previewing of LAMS sequences without login

Hurrah! You can now preview LAMS sequences without having to log-in to a LAMS server. One of the most frustrating things when looking for any teaching and learning resources is not being able to preview the resource. This is particularly so when you are searching through more detailed resources such as a course designed in LAMS or a similar learning design system. It’s difficult to get a feel of the course, without actually seeing as the student would.

Previewing sequences was a one of the discussion points at last year’s Design Bash, so it’s great to see that this has been taken forward by James, Ernie and all the team at LAMS.

To see for yourself, the why not have a look a this sequence “Chinese Language – Celebrating Spring Festival“, (author Christine McDonald). As pointed out by the LAMS team in their newsletter this sequence also makes use of the new video recording functionality in LAMS too.

Sharing great ideas – LAMS 2010 Conference and Design Bash

This year’s European LAMS and Learning Design conference will be held on 15 July at the University of Oxford. Following the success of last year’s back to back events, CETIS will be holding a Design Bash on 16th July, again at the University of Oxford

“The focus of 2010 European Conference is “Sharing Great Ideas”. We will look at technologies, applications and approaches that support sharing, collaboration and open access to knowledge and resources. What are the differing implications for individuals and organisations? Importantly, we wanted to capture the experience of those who have used LAMS & Learning Design and share some of the lessons learnt about Open Education in higher education, the K-12 sector, vocational and professional education.”

Submission to the conference is now open and the deadline for papers is 26 March, full details are available from the conference website.

The design bash will again be taking a more informal, hands on approach looking at ways to share systems, designs and design approaches. For more of an insight into the design bash an overview of last year’s event is available here and you can also explore the cloudscape of the day including designs and related resources.

Expert expectations of IMS LD systems – pre-publication report now available

As part of the iCOPER project, an IMS Learning Design Expert Workshop was held at the University of Vienna on November 20 & 21, 2008. The methodology and findings from the workshop have been written up in a paper which will be published (April 2010) in the International Journal of Emerging Technologies (iJET) . A pre-publication version of the report is now available from D-Space.

The report focuses on the outcomes of group working around two key issues – usability and the lifecycle of a unit of learning. The proposed solutions regarding the usability and utility problem were to investigate how teachers’ and learners’ representations of a learning design can be brought together, and to set up a research program to identify how teachers cognitively proceed when designing courses, and to map this knowledge to IMS LD. In regard to the life cycle of a unit of learning problem, the group suggested a system that continually exchanges information between runtime and editing systems so that units of learning can be updated accordingly.

Relating IMS Learning Design to web 2.0 technologies

Last week I attended the “relating IMS Learning Design to web 2.0 technologies” workshop at the EC-TEL conference. The objectives of the workshop were to to explore what has happened in the six years since the release of specification both in terms of developments in technology and pedagogy and to discuss how (and indeed if/can) the specification keep up with these changes.

After some of the discussions at the recent IMS meeting, I felt this was a really useful opportunity to redress the balance and spend some time reflecting on what the the spec was actually intended for and how web 2.0 technologies are now actually enabling some of the more challenging parts of its implementation – particularly the integration of services.

Rob Koper (OUNL) gave the first keynote presentation of the day staring by taking us all back to basics and reminding of the original intentions of the specification i.e. to create a standardized description of adaptive learning and teaching processes that take place in a computer managed course (the LD manages the course, not the teacher). Learning and support activities and not content are central to the experience.

The spec was intentionally designed to be as device neutral as possible and to provide an integrative framework for a large number of standards and technologies and to allow a course to be “designed” once (in advance of the actual course) and run many times with minimal changes. The spec was never intended to handle just in time learning scenarios, or in situations where there is little automation necessary of online components such as time based activities.

However as Rob pointed out many people have tried to use the spec for things it was really never intended to do. It wasn’t build to manage highly adaptive courses. It wasn’t intended for courses where teachers were in expected to “manage” every aspect of the course.

These misunderstanding are, in part, responsible for some of the negative feelings for the spec from some sectors of the community. However, it’s not quite as simple as that. Lack of usable tools, technical issues with integrating existing services (such as forums), the lack meaningful use-cases, political shenanigans in IMS, and actually the enthusiasm from potential users to extend the spec for their learning and teaching contexts have all played a part in initial enthusiasm being replaced by frustration, disappointment and eventual disillusionment.

It should be pointed out that Rob wasn’t suggesting that the specification was perfect and that there had just been a huge mis-interpretation by swathes of potential users. He was merely pointing out that some critisism has been unfair. He did suggest some potential changes to the specification including incorporating dynamic group functionality (however it isn’t really clear if that is a spec or run-time issue), and minor changes to some of the elements particularly moving some to the attribution elements from properties to method. However at this point in time there doesn’t seem to be a huge amount of enthusiasm from IMS to set up an LD working group.

Bill Olivier gave the second keynote of the day where reflecting on “where are we now and what next?”. Using various models including the Garner hype cycle, Bill explored reflected on the uptake of IMS LD and explored if it was possible to get it out of the infamous trough of disillusionment and onto the plateau of productivity.

Bill gave a useful summary of his analysis of the strengths and weaknesses of the spec. Strengths included:
*learning flow management,
*multiple roles for multiple management,
*powerful event driven declarative programming facilities.
Weaknesses included:
*limited services,
*the spec is large and monolithic,
*it is hard to learn and hard to implement
*it doesn’t define data exchange mechanism, doesn’t define an engine output XML schema,
*no spec for service instantiation and set up,
* hard to ensure interoperability
*run time services are difficult to set up.

Quite a list! So, is there a need to modularize the spec or add a series speclets to allow for a greater range of interoperable tools and services? Would this solve the “server paradox” where if you have maximum interoperability you are likely to have few services, whereas for maximum utility you need many services.

Bill then outlined where he saw web 2.0 technologies as being able to contribute to greater use of the specification. Primarily this would involve making IMS LD appear to be less like programming through easier/better integration of authoring and runtime environments. Bill highlighted the work that the 10Competence team at the University of Bolton have been doing around widget integration and the development of the wookie widget server in particular. In some ways this does begin to address the service paradox in that it is a good example of how to instantiate once and run many services. Bill also highlighted that alongside technological innovations more (market) research really needs to be done in terms of the institutional/human constraints around implementing what is still a high risk technological innovation into existing processes. There is still no clear consensus around where an IMS LD approach would be most effective. Bill also pointed out the need for more relevant use cases and player views. Something which I commented on at almost a year ago too.

During the technical breakout session in the afternoon, participants had a chance to discuss in more detail some of the emerging models for service integration and how IMS LD could integrate with other specifications such as course information related ones such as XCRI. Scott Wilson also raised the point that more business workflow management systems might actually be more appropriate than our current LD tools in an HE context. as they have developed more around document workflow. I’m not very familiar with these types of systems so I can’t really comment,but I do have a sneaky suspicion that we’d probably face a similar set of issues with user engagement and the “but it doesn’t do exactly what I want it to do” syndrome.

I think what was valuable about the end of the discussion was that were were able to see that significant progress has been made in terms of allow service integration to become significantly simpler for IMS LD systems. The wookie widget approach is one way forward as is the service integration that Abelardo Pardo, Luis de la Fuente Valentin and colleagues at the University of Madrid have been undertaking. However there is still a long way to go to make the transition out of “that” trough.

What I think what we always need to remember that teaching and learning is complex and although technology can undoubtedly help, it can only do so if used appropriately. As Rob said “there’s no point trying to use a coffee machine to make pancakes” which is what some people have tried to do with IMS LD. We’ll probably never have the perfect learning design specification for every context, and in some ways we shouldn’t get too hung up about that – we probably never will – we probably don’t really need to. However integrating services based on web 2.0 approaches can allow for a far greater choice of tools. What is crucial is that we keep sharing our experiences, integrations and real experiences with each other.

Some thoughts on the IMS Quarterly meeting

I’ve spent most this week at the IMS Quarterly meeting in Birmingham and thought I’d share a few initial reflections. In contrast to most quarterly meetings this was an open event which had its benefits but some drawbacks (imho) too.

On the up side it was great to see so many people at an IMS meeting. I hadn’t attended a quarterly meeting for over a year so it was great to see old faces, but heartening to see so many new ones too. There did seem to be a real sense of momentum – particularly with regards to the Common Cartridge specification. The real drive for this seems to be coming from the K-12 CC working group who are making demands to extend the profile of the spec from its very limited initial version. They are pushing for major extensions to the QTI profile (it is limited to six question types at the moment) to be included, and are also looking to Learning Design as way to provide curriculum mapping and lesson planning to cartridges.

The schools sector on the whole do seem to be more pragmatic and more focused than our rather more (dare I say self-indulgent) HE mainly research focused community. There also seems to be concurrent rapid development (in context of spec development timescales) in the Tools Interoperability spec with Dr Chuck and his team’s developments in “simple TI” (you can watch the video here)

On the down side, the advertised plugfest was in reality more of a “presentationfest”, which although interesting in parts wasn’t really what I had expected. I was hoping to see more live demos and interoperability testing.

Thursday was billed as a “Summit on Interoperability: Now and Next”. Maybe it was just because I was presentation weary by that point, but I think we missed a bit of an opportunity to have more discussion – particularly in the first half of the day.

It’s nigh on impossible to explain the complexity of the Learning Design specification in half hour slots -as Dai Griffiths pointed out in his elevator pitch “Learning Design is a complex artefact”. Although the Dai and Paul Sharpels from the ReCourse team did a valiant job, as did Fabrizio Giongine from Guinti Labs with his Prolix LD demo; I can’t help thinking that what the community, and in turn perhaps what IMS should be concentrating on is developing a new, robust set of use cases for the specification. Having some really tangible designs rooted in really practice would (imho) make the demoing of tools much more accessible as would starting demos from the point of view of the actual “runnable” view of the design instead of the (complex) editor view. Hopefully some of the resources from the JISC D4L programme can provide some starting points for that.

The strap line for Common Cartridge is “freeing the content” and in the afternoon the demos from David Davies (University of Warwick ) on the use of repositories and RSS in teaching followed by Scott Wilson and Sarah Currier demoing some applications of the SWORD specification for publishing resources in Intralibrary through the Feedforward tool illustrated exactly that. David gave a similar presentation at a SIG meeting last year, and I continue to be impressed by the work David and his colleagues are doing using RSS. SWORD also continues to impresses with every implementation I see.

I hope that IMS are able to build on the new contacts and offers of contributions and collaborations that arose over the week, and that they organise some more open meetings in the future. Of course the real highlight of the week was learning to uʍop ǝpısdn ǝʇıɹʍ:-)

New (Facebook) group for anyone interested in pedagogic planners

As part of the past two LAMS European conferences, James Dalziel and the LAMS team have provided an opportunity to bring together a group of people with an interest in developing pedagogic planning tools. During each meeting it has become evident that there is a burgeoning community developing around pedagogical planning – not least from JISC with the Phoebe and LPP planning tools. There has also been a general feeling of how can we continue these discussions? So, in an attempt to do just that, I’ve set up a facebook group called Pedagogical Planners. If you or anyone you know is interested in this area, please join the group and share your projects and ideas, events.

I love sprouts!

And not just the green ones :-) David Sherlock in our Bolton office put me onto Sprout Builder, a very simple widget builder. I have had a play with some other so called simple widget building tools which lost my interest in about 5 minutes or when I realised that they didn’t work with macs, but I have to say this one has really got me hooked.

In about half an hour I had build a widget which displays the outputs for the JISC Design for Learning programme (just taking a feed from the programme delicious site), published it onto the Design for Learning wiki and in my netvibes page. I’ve now just created a widget for my last SIG meeting with audio/video files embedded and a location map which I put into facebook and the CETIS wiki.

Now I’m not claiming that these examples are anything unique, or particularly well designed. However, what I really like about this particular tool is the simplicity of it and the way it integrates services that I use such as rss feeds, maps, polldaddy polls, video, audio etc. Publishing is really straightforward with links to all the main sites such as facebook, beebo, netvibes, pagesflakes, igoogle, blogger . . . the list goes on. You can also make changes on the fly and when you republish it automatically updates all copies.

Tools like this really do put publishing (across multiple platforms/sites) and remixing content into the hands of us non-developers. There are many possibilities for education too, from simple things like creating a widget of a reading list/resources from a delicious feed to a simple countdown for assignments. (OK, that might be a bit scary, but heck a ticking clock works for most of us!). Simple tools like this combined with the widgets that the TenCompetence project are building (and showed at a recent meeting) are really starting to push the boundaries, and show the potential of how we can mix and match content and services to help enhance the teaching and learning experience.