One of the exciting things about 23 Things is that the ‘and so what’ question that I rashly asked people to think about has actually produced some very interesting thoughts and conversations. We veer from complete enthusiast, to ‘good for collaboration’ to yes I’ll do this, or that or the next thing but not others. I think this is encouraging!
For me, the journey (to use a rather over-used term these days) has been quite mixed. Some of the Things I have already ‘done’/played with and actively use, others I just got cross with and wondered what the point of them were. I suspect that this reaction does me no credit whatsoever as it is probably the ‘things’ that I am least familiar with that make me react in this way. Mea culpa.
However, one thing that I have become quite excited about is the simple act of blogging and making use of blogs for library pages and for other purposes such as online tutorials. After all the committee will have written 23 mini tutorials for the library community over the course of this programme, which many people have managed to do – so why not use this friendly, free tool for library tutorials? Several conversations with our Computer Officer about our library website have all pointed in this direction as well. Blogs are easily edited by anyone really and with our Library News already based on a blog we are half way there.
So –somewhat to my surprise I have a real goal for shaping what we do next in the Library, and I don’t feel all that bad about ignoring such things as twitter and delicious – for the moment at any rate! So there is good stuff out there.......
I agree that the blog format could be a really useful way of communicating with our library users, and perhaps even attracting non-users, if we make them sufficiently attractive and helpful. We could post helpful hints e.g. advice when searching for references on reading lists, or how to search for photographs in Cambridge archives. If we post these at the beginning of the new academic year they might be very useful to new students.
ReplyDelete