Back when the OU used to push all its course materials out to students in print form, I think the first presentation of a course used to have its own print run. Errata lists for mistakes identified during the presentation would be mailed out to students as supplementary print items (with their own publication number) every so often, and changes made to a master copies of what would become a revised versions of the main print items for later presentations. When a student received an errata list, it was up to them to mechanically make changes to their print items (scribbling out the wrong bits and writing in the corrections, for example), but at least then they’d have a copy of in-place corrected materials.
There generally aren’t that many errata in an OU course, but there always seem to be some that slip through the net, so how do we deal with them now?
With online delivery, I think we’ve got ourselves in a bit of a pickle when it comes to handling errata. (This post/rant is a bit of a mountain/molehill thing but it’s symptomatic of something-I-don’t-know-what. Fed-up-ness, perhaps.) Changes can’t be made to content that has gone live to students in case some students have already seen it (or something?!), and to ensure that everyone gets to see the “same” version of the course materials irrespective when they saw it. Which of course they don’t, because some folk go through the materials before an error is spotted, and some of them don’t read or spot the errata list that gets published in an announcements feed in the VLE sidebar. For those students who do read the errata list, it doesn’t really help much because you can’t update the material unless you print it all out and make changes to the hard copy, or grab your own, annotatable electronic copy and update and work from that. So I reckon the workflow you end up with is that you you have to keep an eye on the errata list whenever you read anything. Which sucks.
One thing I did wonder was whether we could add an errata annotation layer on top of the course materials. For several years, the OU Annotate tool has provided a browser bookmarklet that can overlay an annotation tool on top of a well structured HTML page (which rules out things like annotating PDFs). By highlighting broken text in a suitably vivid colour, putting the errata note in as a comment, tagging the comment with an errata tag, and making it public seemed to provide a quick solution:
The experience could be improved by adding an errata channel or filter that could be used to highlight just errata items, rather than all comments/annotations. I even started wondering whether there could be a VLE setting that would pull in errata tagged items and display them by default, overlaying them onto the course materials without the need for firing up the OU Annotate toolbar. But that would be a bit like publishing the VLE hosted materials with track changes switched on though, which would look a bit rubbish and make it obvious that there were errors we knew about but hadn’t fixed. Which there are; but we can’t; because the materials once published have to be left set in stone for that presentation of the course. (Except when they aren’t.)
The presentation could be improved further for the majority, who reach the errata’d item after the mistake has been found (“pathfinder” students who work through the materials quickly often spot errors before the majority even get to them), simply by us making the change when the error is spotted and before the student gets to see it…
Alternatively, we could make the change but highlight the text in some way to show that it had been changed, perhaps popping up a full errata note – including the original and the change that was made – if a student hovered their mouse cursor over the changed item. An even cleaner view could be provided with a setting that disabled any highlighting of error-correction terms.
One way of doing this would be to go back to the source and annotate that…: the original course materials are written in an XML document which is then rendered down to HTML and various ebook offerings. (For some reason, PDFs aren’t necessarily always produced, perhaps because of accessibility issues. For the students who want the PDF but don’t care about the accessibility features, they’re left to create their own workaround for generating the PDF. Perfect. Enemy. Good. Got to be equitable myth, etc.) Tagging the doc with the change as a change and leaving the original as an annotation then reflowing the HTML would mean the VLE materials would get the update and also be able to reveal the historical view. Of course, for students who downloaded an ebook version or generated a PDF before an update and reflow wouldn’t get the update, and, yada, yada, too difficult to even think about, don’t bother, stick with errata lists, make it the student’s fix responsibility… (Of course, if you downloaded all the ebooks at the start of the course and don’t go back to the VLE to check the errata list, then, erm… arrgh: remember Rule 1: check the VLE for the errata list before you read anything.)
Another route might be to base every student’s view of the course on a fork of the original that uses a form of version control that only displays changes to the materials that the student has already encountered. So if I read chapter 1, and an error is found, when I revisit chapter 1 the change is made and highlighted as a change. If I get to chapter 2 after a chapter 2 error has been found, the update is made before I reach it and not flagged to me as a change. This would mean everyone’s copy of the course materials could be different of course – I hesitate to say “personalised”…!;-) – which could be hugely complicated, but might also allow students to make changes directly to their own copy of the course materials. Git-tastic…
Rather, it seems to me that we have taken a completely depersonalised route to our materials that means we can’t countenance any situation that requires change to a document that everyone is supposed to have in exactly the same form. (One reason for this is to prevent confusion in the sense of different people talking about possibly different versions of something that is ostensibly the same.)
Anyway – all of this makes me think: is personalised learning about offering students stuff that only contains significant differences, but not minor differences? Because minor differences (like corrected typos in my copy but not yours) are just different enough to make you uncomfortable, but major differences, (you get a completely different paragraph or sequence/ordering of content) are “personalised”. Uncanny, that…
OUseful.Info, the blog... 