#sugsnip – 200 days – the story so far

I’ve just scheduled the 200th consecutive day of #sugsnips (due to be published on Tuesday 19th July). Here’s a special foretaste for readers of my blog:

#SugSnip The 1967 Welsh Language Act required another Act (1993) to put the language on equal footing with English http://bitly.com/kAspeR

I last wrote about #sugsnips back in April, http://bit.ly/q9HgAD after I’d made the 91st daily posting to Twitter. Since then, I’ve passed the half way point (day 182), at which time I’d made over 200 individual postings – one per day PLUS bonus #sugsnips made especially during ‘named’ or ‘special’ weeks.

#SugSnip That’s 26 weeks done. 6 months. 200 specially researched tweets. Just half way! Thank you all for the RTs and the Papers 😉 BONUS Via Hootsuite

I posted my raison d’être back in January http://bit.ly/pfP9wI. Essentially, this was to create a daily Tweet, which contained some snippet of researched and verified information that could/would be of use or interest to anyone reading it.

Limited as we are by Twitter’s 140-character set-up, the initial challenge was to condense essential information into the Tweet along with relevant links. Research eventually led me to find Fur.ly, which not only shortens links but bundles them together: http://bit.ly/pF8Jzy. Further research led me to Bit.ly, which not only bundled but allowed short descriptions of the individual links contained – these could be used for instruction to readers (learners?) http://bit.ly/q1Ot7m. I still use Bit.ly because of its power. I don’t necessarily use it to its full extent in this exercise, but have done so with other, paid, work.

It’s worth noting here that Xtensis, who have hosted the NLN Materials for many years now, are working on a powerful URL aggregator that has all the potential to knock Bit.ly out of the water. http://www.xtlearn.com – why not register and play? Let Rod and Robin know what you think.

I’ve also tested several Tweet Schedulers during my first 200 days. http://www.twuffer.com has a nice interface and for a while was my first choice – but it missed the odd tweet, meaning that I had to ensure I read my Tweets every day just to check. Ditto: http://www.futuretweets.com – not reliable. I have eventually settled on http://www.hootsuite.com to schedule my #sugnsips. Hootsuite has not (yet?) let me down and presents me with a nice interface for creating and viewing my ‘pending’ Tweets.

#sugsnip readers have been very kind and many have been re-tweeted (RTd) or re-published in one of several http://paper.li/s, especially during ‘special’ weeks. Already researched and ready to go (I have to have a minimum of 50-60 ready for ease of mind) is a ‘Coats’ week (probably over summer!) and a ‘Materials’ week (probably mid September). I’m working on a ‘Wine‘ week too. Each is designed to show how teachers might bundle such short, sharp bits of information for learners to access. 🙂

Advertisements

Gateshead Induction

It’s been another busy week. I’d reached a stage in April, where I thought all my busy weeks had disappeared along with government interest in post 16 CPD, but since returning from France [link] I’ve been rock-on.

On Monday I was up and out of the house by 5.40am, to catch the early train to Newcastle. I’d been asked by the JISC RSC- Northern, to deliver two half day workshops for them on Mobile Learning. It didn’t start well because of assumptions I’d made. I’d assumed there would be computers available at the venue and had therefore not asked for any. No matter how foolish we think the question, we must never assume that it doesn’t need asking! So finding a room set out cabaret style, with no computers came as a shock.

The wonderful RSC team sorted this out, but it did lead to some uncertainties and some changes to the planned programme. Luckily, those attending seemed to remain engaged and were able to participate in a number of active learning activities. I arrived home about 7.30pm – and I’m still tired.

Then on Tuesday and Wednesday I completed the work I’d been doing with Nigel Davies on behalf of another JISC RSC; South East this time. I’d spend much of the previous week on this too. We’d been asked to research and develop a Moodle site that RSC clients could use on the subject of Induction. It took the two of us quite a while to track down everything we could on the subject from relevant web sites. We collaborated initially on an iEtherpad and then organised our findings by using a Mind42 mind map. We also spoke every day via Skype, which allowed us to share screens and re-organise the mind map on the fly.

We then agreed which section each of us would develop. I concentrated on the Generic aspects whilst Nigel concentrated on Learner specific and Staff specific inductions. The course is HUGE. We could not use Moodle-Book, so the ten topics take up a lot of space. However, we were also asked to present the course via Web 2.0 and for this we used Bitly (see my earlier notes regarding Bitly), which we believe worked just fine.

If you are registered with the RSC-SE, you can access the Induction course here: http://moodle-rsc.ukc.ac.uk/course/view.php?id=130

On Thursday I began planning for next week, when I will be working for most of the week with Di Dawson and James Clay at Gloucestershire College, and I attended a training session at RM’s Salford TEN centre, on their re-vamped VLE.

On Friday I travelled to Leeds, to work on the new Leeds College of Music learning platform. This is part of the work I’m doing for Lilian Soon, who is project managing this massive project. After a few visits and only making baby steps, I feel that we made great strides yesterday and that things are beginning to take shape.

Sharon met me off the train and we had a few beers, a curry and caught the 8.00pm bus home. Sorted!

bit.ly – a better LMS?

Some readers may have followed my exploration of facilities offered by http://fur.ly and how it might be used as a learning management system (LMS). At the end of my most recent post, (see 3, below) I said ‘watch this space’, as I intended to explore another service – http://bit.ly.

I have now had the chance to delve into bit.ly and explore what turns out to be its greater potential for use as an ad hoc LMS.

First of all, to get the most from bit.ly, you need to register. It does work as a URL shortener without registration, but to use it to its full potential (which I don’t think I have yet fully tapped), you do need to register. It’s a painless process.

When you have logged in, you will see that over time, the URLs that you have reduced in length are all logged in your ‘area’. If, as I have done today, you wish to bundle some links together you can do this. Simply click on the offer to bundle your most recent links. You then have the opportunity to add/delete links as required and to rearrange them. Where http://bit.ly has the edge over fur.ly, is the way it allows the LMS designer to add an introduction (instructions) and allows the end user to comment/collaborate on the outcomes. This looks like it might be a powerful feature but I haven’t explored it. Please let me know if you do explore it.

There is also an analytics section which I have not explored either, but which may in time come into its own. If you have a play with it, do please let me know how you get on.

Have a look at my David Lloyd George ‘lesson’: http://bit.ly/f4RX56

Interested users will see that I have once again added a Google Form to gain feedback – you could use this as a formative test at the end of the web site sequence.

Please do let me know what you think.

Related posts:

1) https://eduvel.wordpress.com/2011/02/27/fur-ly/

2) https://eduvel.wordpress.com/2011/04/11/the-power-of-fur-ly-part-one/

3) https://eduvel.wordpress.com/2011/04/12/the-power-of-fur-ly-%E2%80%93-part-two-lms/

The power of fur.ly – part two: LMS

Screen shot of EduVel blogAs I suggested in my previous post, fur.ly could be used for so much more than shortening URLs or even (as I have been doing within my #sugsnips) aggregating URLs. For instance, here is an example of it being used as a learning management system – LMS.

http://fur.ly/5hzo. [Please try this and let me know what you think]

All it cost me was a little time – everything else was free. [Late News – bit.ly can also do this. See end of post]

Obviously, anyone following the learning episode above will find huge pedagogical holes in what I have slung together, but that is all I did: I just slung a learning journey together from a few web sites I knew of and hoped that users/readers would ‘get’ the point of the exercise.

My biggest challenge was deciding upon a site that would allow me to have simple pages that linked the learning journey together, for this I chose http://shrib.com. Shrib has the advantage of (similar to all of the Etherpad clones) having an editable URL. Anyone following the route will notice that I’ve used bloom1, bloom2 and bloom3 as my ‘tail’. The downside (for now) is that these are probably editable by anyone – so just how I would overcome that remains to be seen – but for now it’s ok – it works.

I’ve used Shrib to provide online pages, which explain how to use the fur.ly page for going backwards and forwards through the web sites presented and what to do at each stage.

My preparation includes locating the web sites I wanted to use and the order in which I wanted to present them. I then created the intervening Shrib pages to separate the websites and finally – having decided what the user would need to look for on those pages, I created an end-test using Google Forms. In real life I might have asked the user to give me their name and email address, so that I could give them feedback but for the purposes of this demonstration the end test restricts itself to 2 simple questions and a comment box.

So, is this really a form of impromptu learning management system (LMS)? I think it is. I think it will suit those who are working outside of institutions (maybe WBL, ACL, Voluntary etc.) as a means of guiding learners. I’ve tried the resulting journey on my iPhone and it seems to work very well, opening each page as required and allowing me to contribute to the Google Form.

I’d love to know what you think. Please comment below or DM on Twitter.

LATE NEWS

Part of my investigation has allowed me to delve further into bit.ly http://bit.ly the URL shortener mentioned in my previous post. This may have great potential than fur.ly as it can bundle URLs too. It also presented the URLs in a friendlier way than fur.ly.  Watch this space.

fur.ly

I came across fur.ly today.

What a difference it will make to my #sugsnip series of Twitter postings. For more about #sugsnip please see my original post and last week’s review.

Fur.ly is a URL shortener!

It works in much the same way that bit.ly and snipurl (and many others) take long internet addresses (URLs = Uniform Resource Locators) and shrink them down to a more memorable size. (e.g. the address of last weeks #sugsnip posting reduces down to http://bit.ly/sugsnip and http://snipurl.com/25ph3l)

Fur.ly however, goes a stage further and can hold several links in one shortened URL.

For my #sugsnip series, this will be (eventually) a great boon. I say eventually because I already have quite a few set up with the Tweet-schedulers I mentioned in my previous post and a few more stored ready to go. The point of #sugsnip is to model the use of micro-blogging tools as a means of knowledge delivery – short, sharp bits of information that have all been double checked for accuracy.

The double-checking means that most #sugsnips carry two shortened URLs (usually by bit.ly) that direct the reader to two different web sites (there may well have been more) supporting the information supplied. Quite often I have to visit several sites, especially if one of my sources has been wikipedia, as many websites seem to just copy from there. I DO try to find corroborative evidence before posting.

However, the use of two URLs does take up valuable characters that could be used to introduce the subject in question. Using fur.ly will allow me to not only put my usual two URLs inside the one link, but others too – if I feel it to be useful.

Many thanks for the supportive comments I received after last week’s post – especially to Lisa who commented on the post itself. 🙂