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 dokuwiki.cpjobling.net.

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

#SocMedHE17

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.)

status_url

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 cpjobling.github.io/stories.

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

#ALTC Winter Conference – Day One

2017-12-12_09-39-20Today, was day one of the 2017 ALT Winter Conference (#altc) and I was supposed to chair the 10:00 am session “The Great Sussex Podblast” to have been delivered by Pete Sparx, George Robinson and Tab Betts from Technology Enhanced Learning (TEL) at the University of Sussex. Unfortunately, problems with the Conference Webcasting platform (Blackboard Collaborate Ultra) and it’s back up (Blackboard Collaborate Classic) meant that the session had to be cancelled. Hence, my first opportunity to moderate a webcast of any kind passed me by! The guys did, however, create a video, slides (bit.ly/podblast-altc) and you can hear the Podblast podcasts here: soundcloud.com/teachingwithtech/sets/great-sussex-podblast-digital.

In other events, there were five tweet chats. I was able to participate in VLE Minimum Standards—Lessons from the Sector (hashtag: #UCISAVLE) and watch the
#altc blog showcase (hashtag: #altcshowcase).

I then had a meeting to attend so I will need to catch up with the other sessions via the webinar recordings and wait for the storify versions of the tweetchats:

I will have more time tomorrow to attend the live sessions.