If you follow me on Twitter (or are in touch with me on Facebook) you may have noticed me occasionally sharing something from the EduFutura account such as this tweet back in September.
EduFutura is a non-profit organization which I’ve been a member of for some time now. The EDGE project (Empowering Digital Teachers) which it has been a partner on for the past two years is EduFutura’s first big project and as we’re a small organization, for some of us these project activities have been taking up quite a bit of spare time.
I’ve been meaning to write up a short overview of the project for… well, basically since it started, but if you’re a reader of this blog you won’t be surprised it’s taken me this long to get around to it. Actually, I’m aiming for this to be a very brief post, just to share that one of the two chief results of the project – the Guidelines for Online and Digital Teaching and Learning – is finally available in six (project partner) languages: English, Polish, German, Croatian, Italian and Spanish. The idea is to write up a follow-up post later on, to provide a bit of background on how the guidelines were produced and what else the EDGE team has been up to.
The guidelines aim to answer a series of questions about the digital aspect of teaching and learning, grouped around the following themes:
There are around 30 questions overall and each is covered by about 2 pages of what we hope is practical and accessible text, including links to helpful resources.
We’d love it if you could take a quick look at the table of contents (p. 3-5) and choose a question you find relevant in your context. It would be great to hear your feedback on the answer given in the guidelines!
Also, if you find the document useful, please feel free to tell others about it!
A brief digression: have you noticed how it sounds almost strange to be describing students/courses as ‘online’? It’s like all courses now have some kind of online component and it’s hard to even imagine a time – just four semesters ago! just four course iterations ago! – when teaching a semester-long course online wasn’t exactly routine and it seemed important to note that for context. Or maybe it’s just me?
Anyway, the way my audio files are structured and presented has developed over time into a Tips on what to watch out for chapter in each unit guide (a Moodle book resource). The tips are divided into Things that were done well over the past week or so and Things to watch out for in the current unit. The ‘developed over time’ bit makes it sound as if a whole lot of development has been going on but this setup has in fact been in place pretty much since I started using the H5P course presentation (see the second link above for a more detailed account of how that came about).
One thing that became obvious pretty quickly was that a lot of the recordings in the Things that were done well category needed to be recorded over again each semester, as each group was slightly different in the things they did well and it was tricky to stay neutral in these recordings. What I mean by ‘neutral’ is avoiding any mention of something group-specific. I knew that I should strive for this in theory, if I wanted to be able to reuse the recordings, but in practice it’s surprisingly difficult to speak to a group of students without references to that particular group. Try it and go back to the recording in six months’ time. I guarantee you’ll find phrases that will make you groan. For instance, you’re commenting on forum activity and you hear yourself saying, “I can see that several people have added comments to this thread…”, whereas this semester, with your luck, no one has added anything to that thread.
The Things to watch out for in the current unit files were easier to reuse because they’re basically general advice on what to keep in mind as you complete a particular activity, so aren’t linked to any individual group. An example would be how to approach a glossary activity: if there are any areas students commonly slip up on, what to watch out for with regard to the final exam and so on.
The most time-consuming aspect of working with these files is that you have to listen to them again every six months before you re-record. I guess what you could do is just assume that all the Done well recordings need to be re-recorded and not waste time listening to those from last semester but I always hoped that I could at least use some of them again, possibly dealing with minor differences by adding an explanatory text box as in the screenshot.
Also, those in the Current unit category would sometimes need to be re-recorded as well because there would be changes to the way some activities were set up or some advice was too specific. For instance, only today I realized that advice on pair work included a 2-minute segment on how to make sure exchange students were not left out but this semester we don’t have any exchange students. This segment was somewhere in the middle of the recording, so I used 123 Apps’ trim audio and audio joiner to excise the bit that was no longer relevant.
When I’d first introduced audio files to the course, I was really curious to see what the students thought, so I added this as a possible reflection topic for their learning journals. It was actually student reflections that helped me realize one longer recording might be demanding to stay with and might be more easily processed if broken up into shorter files. Although student perspective was key to this change, I didn’t add audio as a reflection topic for the next two semesters. Then last semester I added this poll.
Just over half the group opted for “I listen to the comments and generally find them useful” and out of the rest only one person chose “I don’t listen to the comments”. The way the poll was designed basically only told me whether students listened to the audio and to some extent if they saw the comments in a positive light. I planned on following this up with a reflection topic but didn’t. The results didn’t seem overly negative, i.e. most students said they listened to the comments, so I probably didn’t see a pressing need to get more feedback, although it would definitely be useful to know more about why some felt the comments didn’t help them.
This semester I introduced another tweak, partly brought about by the fact that since I’d started recording audio comments I was aware of the fact that there was no transcript and that ideally there should beone, both in accordance with accessibility guidelines and also because it’s okay, I think, not to force people to listen at a certain speed (or even twice that speed) if you can offer them the option of glancing at a transcript and picking out the main points. The other reason for the tweak was, as is so often the case, Twitter.
I started using the tool in the tweet with the Done well comments. I realize now that it says this particular tool is aimed at social media use, which I don’t recall being in focus that much back in February. I suppose it may have been and another reason for choosing it may have been the (subconscious) idea that anything to do with social media would appeal to students. Anyway, using it didn’t address the transcript issue because what you do is add captions, which should make it easier to follow what the person is saying but you still can’t process the information the way you would with a transcript available. Also, I have since learned that screen readers can only read transcripts, not captions. This wasn’t an issue for the students I’ve had these past semesters but if you’re making a recording for a larger group of students (on a MOOC, say) it would definitely be important.
An upside I noticed is that recordings made with this tool are definitely shorter, which is great as I tend to ramble the minute I don’t prepare notes on what I want to say. The captions are generated by the software, so that’s done quickly but I still need to clean them up and it’s much quicker and easier if there isn’t much waffle. In fact, compared with the first screenshot above, in which there are three topics in the Done well section, this semester I only had one topic/video per Done well section. I really did plan on checking with the students if they noticed any difference between just audio and these recordings with a visual component, but the end of the semester is here and I don’t seem to have done that. Maybe next semester.
What are your thoughts on audio in courses which are mostly delivered asynchronously online? Do you think you would prefer engaging with the audio as opposed to going through transcripts? What strikes you as the ideal length for audio recordings?
It all started on Twitter, as these things do. I had covid and was stuck at home, so it was as good a time as any to do some marking. Then I came across Neil’s tweet.
I recommend you click through for the answers because quite there were a few suggestions and several people mentioned text expanders, which is useful for context, but the answer that caught my eye was this one:
I don’t use Linux, so I’m not entirely sure why I decided to try espanso out. Now I think about it, I’m pretty sure Neil tweeted an update on how well it was working out for him. Anyway, espanso works on Windows and Macs, although I use it on Windows most of the time.
I did need a little bit of help installing the program but I probably would’ve been able to do it myself if I’d put in a little effort. The point is, it’s pretty simple and quick. (To be fair, it was more complicated to install on a Mac.)
The idea of this post is to reflect a little on the past 6 months of using it and note down some pros and cons.
First of all, this is what it looks like in practice. Please ignore the huge gap between the top and the bottom comment; it’s my first attempt at a gif.
And it works everywhere. If I typed :main idea it would expand like in the gif regardless of whether I was commenting on a Word doc, typing in a Google doc, in the Moodle gradebook…
My initial reaction was – this is bliss! My days of spending ages on marking are over! All I need to do is add the comments which are already in my comment bank to espanso and I’m all set.
This is why in the end it wasn’t as easy as that.
I have a huge number of comments in my comment bank. I’ve written about the comment bank I have in Google Docs in this post and in Google Keep in this one. At first I thought it would only take a long time to transfer them all to espanso, but then I realized that I would have to come up with as many triggers as there are comments. (The trigger is the combination of : and the word or letter combination that gets expanded.)
It probably wouldn’t be that taxing to come up with a long list of triggers, but eventually I didn’t because it became obvious I couldn’t remember them all. In my comment banks the comments are categorized by unit and activity (in Google Docs) and by aspect of writing like punctuation or formality (in Google Keep). Categorization isn’t possible in any meaningful way in espanso, so you’re probably best off if you choose a trigger that will most easily remind you of the longer comment you wanted to add (or vice versa).
What tends to work best (for me) is if I add a whole word or word sequence, like “comma splice”. Great, I hear you say, so do that. But the longer the trigger is, the more likely you are to mistype something and then you need to delete what you’ve typed and start again (at least if you’re using Windows). Also, if you want to use “comma” as part of a trigger for anything other than comma splice comments, you can’t. Say you wanted to use “comma not needed” as a trigger. The nanosecond you type :comma, espanso expands it to your comma splice comment. You could use “unnecessary comma” as a trigger, but it’s not what I think of first when I see one – when I start typing, my brain has already categorized that as a comma-related error, and “comma” is the word that first comes to mind, not “unnecessary”. So if you’re old and forgetful, you’ll catch yourself going through the espanso bank, muttering “Why did I ever think I’d remember “unnecessary comma”?!” You get the idea. This is just an example, incidentally; I’m not that concerned about commas.
In order to really save time and reduce the potential for confusion, the triggers need to be short. Ideally, just a few letters. But the shorter they are, the easier they are to forget. Did I say old and forgetful? Add stressed out over a million things. Coming up with a trigger like “spe” for spelling sounds easy enough to remember… okay it is. That one is. But when I have a comment which is essentially just positive feedback on participating in a discussion in unit 4, that is quite tricky to reduce to a three-letter combo that I will remember longer than a day. Yes, you are right to wonder how I deal with PINs. 😛
What I tend to do now is work with up to 20 triggers. I always open up espanso before I start to remind myself of the triggers and attendant comments. Then I mark everyone’s work in the unit I am currently grading, where I won’t need that many different comments because the mistakes and the things done well tend to be quite similar. When I move on to the next unit, I prefer to work with the same triggers and update the expanded feedback in espanso. I won’t be needing the comments for the unit I’ve just marked until next semester anyway. Then the trigger for my positive feedback can always just be “yes” and for negative comments/suggestions for improvement it can be “no” – definitely easy to remember.
What I’ve also decided works for me is adding as much text as possible to one single trigger. In other words, instead of thinking up three different triggers for three variations of positive comments, I add all three to the same trigger, delete the unnecessary/non-applicable comments when the text expands (and then customize further if needed).
In short, the tool isn’t as ideal as I’d initially expected it to be, but it does speed up the feedback process considerably once you’ve figured out how it can best serve you. I still use the comment banks and, of course, a large number of comments are personalized and context specific anyway, so nothing really helps there.
What do you do to speed up the marking and feedback process? If you have any tips, either on how to use text expanders more efficiently or which other tools have been useful to you, I’d love to hear them!