Summer To Do List

It’s graduation next week, the official end of the University year and the start of the summer battery recharge. Inspired by a comment from my friend and colleague Chris Hall made at yesterday’s #SUSALT18 Conference, I thought that it was time to reactivate my blog with a few thoughts on what I want to achieve over the summer.

So here, in no particular order, are the things on my todo list.

  • Annual module review of my own modules.
  • Final Board of Studies meeting
  • Away day for programme review (planning to use the ABC LD Toolkit 2018 from UCL)
  • Learn how to use the Rohde-Schwartz instrumentation in our labs
  • Play with National Instruments micro DAC
  • Produce a how-to for embedding OneNote class notebooks into Blackboard
  • Survey of my college’s Blackboard sites
  • Develop guidance for achieving the minimum standard
  • Help the University to define the data requirements for Annual Programme Review
  • Prepare my Senior Fellow HEA application
  • Train as an IET Accreditor
  • Properly flip my semester 2 courses.
  • Finish Laurillard’s Teaching as a Design Science and finally read Talbert’s book on Flipped Learning and Nilson’s on Specifications grading.
  • Continue to advocate for wider use of Microsoft Teams for Committees, Work Groups, Communities of Practice, Courses and Students within my University.
  • Go on holiday
  • ALT Conference

Some of these will be part of my CPD, some may be of interest to my readers. However, I make no promise that any will become the subject of a future blog post.

One reason that I haven’t felt the need to Blog for a while is that I have been keeping a (nearly daily) Journal in TiddlyWiki. It’s live, hosted in GitHub pages and reachable at

BYOD4LChat Number 1

I created this page as a proof of concept using CoDog’s link extraction tool on the story that was curated by Sheila McNeil.

Observations, long tweetchats like this should be edited in the Text view in WordPress. Rendering the tweets in the Visual HTML editor view is not something that the WordPress can cope with, but is probably necessary if you want to add commentary to a chat rather than a straight record.

The page will take a long time to load as each tweet has fetched as HTML, embedded in the post and rendered by the browser! (I assume Storify caches the embedded tweets somehow to avoid overloading the Twitter APIs.)

There’s a danger that you might crash your WordPress server!

Conclusion, a story which can be archived as a static website (See Archiving Tweetchats) may actually be preferable!

Here is the Archived Chat

BYOD4L 2018

Cat in sillhouetteIt’s time for Bring Your Own Device for Learning 2018 (my 6th) and this year there are 5 additional C’s (Confidence, Capability, Copyright, Community and Celebrating) to add to the usual menu of ConnectingCommunicating, Curating, Collaborating, and Creating.

I’m probably not going to have the freedom that I had last year to contribute as much as I would like, but I will be using a new curation tool – TiddlyWiki  – and its mobile editing app Quine.

You can follow my progress by checking out my Byod4L TiddyWiki on Dropbox. Just download a copy of index.html and open it in a browser.

To Be or Not to Be?

[Cross posted from my Work Blog.]


Sarah Bernhardt as Hamlet, with Yorick's skull (photographer: James Lafayette, c. 1885–1900).
Sarah Bernhardt as Hamlet, with Yorick’s skull (photographer: James Lafayette, c. 1885–1900). Image from Wikimedia Commons as published in Hamlet (Wikipedia).

I’ve had a work blog, courtesy of my employer Swansea University, for a number of years, but rarely use it.

Instead, I tend to post most often in this personal blog.

So, at the start of this new year, a time for reflection and resolutions, I find myself asking myself should I keep this blog and start using it more systematically or should I abandon it?

In answering this, I suppose I intended my work blog to be a place for reflecting on my teaching and learning and to support my students taking my courses?

This blog was meant to be more personal, but in reality, takes on more of these work-related issues than my work blog does.

Should I, therefore, copy the posts over from my work blog to this blog, and have a single place to reflect? Or should I leave things as they are?

For an open practitioner (as I hope that I am) Is there an advantage in having separate work and personal blogs?

Are there disadvantages?

Which is the real me?

What do you think?


Reclaiming my sites

My adventures of Domain of One’s Own with Reclaim Hosting continues.

I’ve just resurrected the Dokuwiki that I used for various modules related to Internet and Communications Technology (ICCT). You’ll find this at its new home at

I’ve also set up a new development blog using the static-website generation tool Nikola. You’ll find Crispy Dev hosted at as well as on GitHub at


My co-presenters Sue Beckingham, Neil Withnell, Chris Rowell and Deb Baff at last year’s SocMedHE16If the twitter hashtag (#SocMedHe17) I followed today was anything to go by, the 3rd Annual Social Media in Higher Education conference, held today at Sheffield Hallam University, was a great success.

I made a twitter moment and a Storify story (plus archive) of the event, but from my remote vantage point, the highlights were:

I went last year and I hope to go next year. I just need something to present!

Extra: Scott Turner made a TAGS database of #SocMedHE17.

Archiving Tweetchats – Experiment 1

If you take a TAGS file (I used this one: BYOD4L 2016-2017 (@cpjobling)) and sort it in time order, you can then copy column Q (status_url) and paste the data into the HTML view of a WordPress page or Post to get a similar archive to that which @Storify produces.

Unfortunately, there seems to be a limit (on hosted WordPress at least) and only the first N tweets are shown (where N is to be determined). If there are more than N, only the links are shown. Also, retweets will need to be romoved from the data because they are not shown correctly.

(There is a bug in TAGS, the HTTPS protocol has to be used for WordPress to embed a tweet, but Martin records HTTP in the status URLs … A simple fix.)


How to archive your Storify stories on GitHub pages

Yesterday, Storify announced the retirement of its Storify service. This leaves a lot of users, including myself, with Storify stories linked into their blog sites and nowhere to host them when the service closes. Storify has provided an export feature, which can output a whole Storify store as a static HTML5 webpage, and GitHub provides a way to host static websites via its free GitHub pages feature. I, therefore, yesterday tweeted about a proof of concept trial:

Today, I’ve created a simple video to show how it was done.

I’ll be archiving my own collection of stories over the next few days and updating the links on this blog. To see my collection, visit

This solves the problem for historical tweetchats. We, as a community, now need to find a new way to curate our future chats!