I spent two days last week at the Learning Technologies 2017 exhibition, working on the LEO stand (below). This annual event is split over two floors, with a paid conference upstairs and free exhibition downstairs. The stand was really busy for both days and the whole team came away absolutely exhausted, but I did manage to wander around the exhibition looking to see what the trends were this year and seeking out interesting new products.
This year was my fourth Moot and it was another cracking event. Dublin is a welcoming and accessible location so it was good to be back here. I attended the two conference days on May 12-13, but the conference was topped and tailed by a workshops day on the 11th and a developer hackfest on the 14th.
First ever workplace learning stream
Of particular interest for me was that for the first time the conference featured a workplace learning stream. Despite Moodle topping multiple surveys of the the most widely used workplace LMSes, previous Moots have typically been dominated by the education sector. It’s great to see the focus gradually shift and the conference become more representative of real world Moodle users. It was nice to hear Moodle HQ presenters reinforce that future Moots would be structured along similar lines.
The workplace stream consisted of case studies from:
- Civil Service Learning
- University Hospital Southampton
- Health and Safety Authority
- An Irish law company
- A US Healthcare company
There was also a good analysis of the business impact of long term support vs yearly upgrades from the conference organiser, Gavin Henrick. The workplace stream was well attended, and I look forward to more of the same in future years! Continue reading “MoodleMoot 2015 Review”
Following on from my initial exploration of Google Glass, I was keen to see what my kids would make of this device. As anyone who has seen a toddler using an iPad will know, some technology is just so intuitive that kids take to it like a duck to water. So I wondered what challenges Glass would throw up for a child, whether they would reflect my own challenges and frustrations in getting familiar with this device. After all, I had to undo decades of engrained user interface practice, whereas my daughter only had a few years of computing under her belt. Sharing Google Glass with my daughter turned out to be just as exciting and eye opening as I had hoped, but what really surprised me was the rather sobering reflection it led to, about just what kind of future we are leading our children towards.
Firstly, a word of warning. Officially Google Glass is not supposed to be used by children under 13 years of age, whose eyes are still developing. This was disappointing to find out, as I was looking forward to what my kids might make of it. I actually stumbled across the age guidance on the Google Glass Help site, there was nothing on the Glass box to indicate a danger to children, although I later found an FAQ card inside the box, in tiny print, with the age guidance on. Like many people who buy a gadget, I tend to try the device first and read the booklets later. I blame Apple for shipping mobile devices that ‘just work’! Google really need to stick a “13+ years” on the box. Smallprint just doesn’t cut it, this is kids’ eyesight we’re talking about. Otherwise we will end up with lots more uninformed parents posting videos like this one I found on YouTube, once Google Glass hits the retail stores.
Google do not give any background to their age restriction, however the Children’s BBC site CBBC has interviewed a professor from the Royal College of Opthalmologists, who suggested that the reason for the restriction would be due to the unknown effects of Glass on developing eyes, and that the age of 13 was likely used just because no research has taken place yet. He stated that children’s eyes are actually fully developed by 7-8 years, and that children basically have their adult eyes by then.
Based on this advice and after a discussion with my wife, we decided to let our daughter, who is nearly nine years of age, have a go on Google Glass, but only after her younger brothers had gone to bed, otherwise there would be hell to pay!
After a lapse of several months we finally had a MoodleBrighton meetup last week. It was good to see everyone again and to catch up on what’s been going on, and we had a couple of new faces too. It was a good session, loosely based around an exploration of Moodle 2.6 with attendees coming from Sussex Uni, Brighton Uni, Moodlerooms and Epic.
The category and course management interface has been reworked. It looks much tidier now and the rework makes it significantly quicker to perform common tasks.
Image: Category and course management
There is a bulk course creation tool now too. We get asked about this from time to time at Epic so it’s a useful new feature, especially when migrating to a new Moodle site if you are unable to automated the migration of courses into the new system.
Standardised plugin installation and management was a hot topic. There is a lot of interest in this feature, drawing the inevitable WordPress comparisons and discussions around just how wise it is to allow site admins to automatically install and update plugins that could be of dubious quality, directly into a live site. This feature has been around a few versions now and continues to improve though in M2.6 with multiple improvements and fixes.
The ability to backup and restore very large courses of over 4GB caused a bit of a stir from the Brighton University attendee where they struggle to perform this task using Blackboard. The cause of this is a PHP limitation which is apparently being fixed in PHP5.6, but in the meantime Moodle 2.6 includes a workaround for the issue.
There are apparently improved course resource and activity edit icons which improve usability on all screens. I say apparently because they actually look pretty poor (see below) in that icons are various different sizes, are not in vertical alignment with each other and move to all sorts of bizarre positions when you resize your browser. It’s so bad, I raised a bug. A work in progress this one, for sure.
Image: Above showing viewport width of 1030px – icons of all sizes and alignments
Image: Above showing viewport width of 820px – weird wrapping behaviour
There are BIG improvements to Tiny MCE, or the HTML Editor, as most of us know it. It looks miles better now, see below. But it still needs a lot of work on mobile devices, especially the file picker, which I am sure a developer would tell me is not part of Tiny MCE. However to an end user it is an integral part of the content editing experience and it remains difficult to use on a mobile. But the editor itself looks a treat now, a huge improvement.
Image: TinyMCE toolbar improvements
Email notification for new users added manually is very useful for us at Epic, as this is a common requirement in workplace learning Moodles. When a user is created manually, the user can now be sent a welcome email with their login information. Simple, and very useful.
There is a minor improvement to the Open Badges implementation with badges now being awarded more quickly. This is a very minor fix in this release but it prompted quite a long discussion among the group about Open Badges in general, their impact on gamifying courses and how the Open Badges implementation in Moodle is a bit all over the place, with settings and display pages here there and everywhere. Well, at least four different places that we could see. A really popular feature this one though, and I’m sure Moodle’s Open Badges implementation will only get better with time.
The next feature we stumbled across caused a bit of a storm: “PDF submissions can now be directly annotated by teachers“. The Sussex Uni attendee commented that document uploads tend to be in Word format rather than PDF at their institution, but hey, this one still rocks! A great new feature.
So that’s pretty much the stuff we looked at over about 90 minutes. It was really the tip of the iceberg to be honest, as this release is absolutely jam packed full of new features. There were lots of things that we didn’t get round to having a proper look at including:
- Simplified forgotten username and password reset process
- New Single Activity Course Format
- Grade-based conditional availability now updated immediately after grading
- Ability to change forum digest settings on a per-forum basis
- Lots of SCORM player and SCORM report improvements
- Support for Microsoft Skydrive repository
There are also bags of improvements for developers including LOADS of performance improvements and API/Web Service improvements.
One thing that was very apparent is that a lot of effort is being put into improving usability which was warmly received by all attendees, with a recognition that it’s very much a journey that Moodle is starting out on and with lots still to do. It’s all heading in the right direction and that can only be a good thing.
To finish up we took a look at the Essential theme that has been the talk of the town in recent months. It looks pretty cool too. All that, plus the usual quantities of salacious Moodle gossip and a few pints of beer afterwards, all made for a cracking xmas MoodleBrighton!
See you there in 2014. Updates at MoodleBrighton on Google+
Essential theme demo site at http://2013.imoot.org/
It’s that time of year when all the movers and shakers attempt to predict what will be big in 2013. Well there are no such predictions here. However, they do say you can predict the future by learning lessons from the past, so I’m going look back over the past year instead and ask: what was crap about 2012? (I should reiterate that these views are, of course, entirely my own…) Continue reading “2012 – a year of learning technology failures”
Every year Jane Hart runs the Top 100 Tools for Learning survey over at C4LPT. Here is my personal 2012 Top Ten which I have submitted, in no particular order.
Google Reader – one of the first things I do every morning is get updated on the news via Google Reader, with which I subscribe to a range of RSS feeds and pull in Google Alerts for certain keyword combinations. A major source of learning for me, most of my feeds are related to learning technologies and bloggers I follow.
Google Alerts – I have about 10 alerts running for certain keywords relative to my field, which I monitor through Google Reader. The Alerts service is one I’ve been using for some years and I find it indispensable.
Moodle Docs – a superb resource on all things Moodle. If you want to know something about Moodle, consult the Docs first!
December sees the release of Moodle 2.2 which is now under code freeze and being put through the rigours of the Moodle QA process to iron out those last niggling issues prior to official launch. The beta is already available on the Moodle Downloads page and the team are encouraging people to download and test it and feed back any issues found.
The beta release is also a good opportunity to have a play around with the new features. These can be broadly split into end-user and developer features. While much of the fanfare has been around end-user features in the various previews that have been blogged to date, there are significant code-level changes taking place under the hood in Moodle 2.2 which will also have far-reaching effects. Of particular note are some major improvements in mobile support; while Moodle 2.1 and its associated iOS App laid down a lot of mobile groundwork, the mobile capabilities of Moodle 2.2 should help make Moodle a real contender in the mobile LMS space.