Slides from a recent workshop for Library staff at the University of Lincoln, on a number of current bugs in our access to electronic resources and software – how to identify and diagnose problems; what to suggest to users; the cause of the problem; and if/when the problem will be fixed.
Posts Tagged ‘slides’
A whole contingent from Lincoln—Andrew Beeken, Trevor Jones, Elif Varol and I—are at the Cambridge University Clinical School at Addenbrooke’s Hospital in Cambridge, for a mashed library event – Mashcat.
Mashcat is “a mashed library event focussing on cataloguing data. For cataloguers, developers and anyone else with an interest in how library catalogue data can be created, manipulated, used and re-used by computers and software”. It’s being sponsored by DevCSI.
Next week, along with a colleague from the @GCWLibrary, I’m attending a meeting of the Talis Aspire User Group (TAUG) at the University of Derby. As new customers of Talis Aspire (see lists.library.lincoln.ac.uk), we’ve been asked to do a 5-minute, 2-slide “meeting new customers” presentation, covering where we are with our Aspire ‘tenancy’, our experiences, expectations, and any questions we have.
Here are our two slides:
I’m doing a ten-minute whistlestop presentation on copyright © and licensed copying for re-use in educational resources, for an event called ’Sharing Practice; open approaches to teaching and learning‘, organised as part of the OER work at the University of Lincoln.
‘Better Resource Discovery – Is there a business case?’
An exploratory workshop to identify business cases for new modes of resource discovery based on real service drivers
David Kay from SERO asked me to talk for 10 minutes on Lincoln’s approach to open bibliographic data and open discovery; what our ‘business case’ might be; what we’re doing to put it into practice; and how the institution might become aware of and judge our success.
‘Business case’ isn’t a phase that falls from my lips naturally… however: I am uneasy about our getting too comfortable under a protective ‘shield’ of (mainly JISC-funded) project-based development: it may protect us from a large amount of flak, and provides us with an enviable amount of freedom, but by definition it’s only there temporarily.
We need to build ourselves some new shields – perhaps ones less impregnable, but ones that are more persistent and less easily dissipated once projects ends. And to do that, we need to create more useful, disruptive institutional services like this one. Our business case is ‘being a university‘; how do we create convincing applications from open tools and data that further that business?
My slides are on Google Docs.
JISC formally launched phase two of the Information and library infrastructure: Resource discovery programme on 11 January 2012 in Birmingham. CLOCK weren’t able to attend in person, but we sent these slides in our absence. They’re good for a quick overview of the aims of the CLOCK project.
I’m helping out my colleagues at the University’s Riseholme Park Campus Library on Monday, with a library induction for new foundation degree (FdSc Agriculture and Environment / FdSc Equine Management and Training) students.
I used to do | loads of | these inductions | all the time (in the days when I was an ‘Academic Subject Librarian’, with responsibility for HE food and agriculture programmes, as well as for computer science)… these days, not so much.
This is my usual approach to induction slides: pretty pictures, not too much text. I worry that we bombard freshers with far too much information in induction week. I talk over these slides about what the Library does and how people can use our services. But I try not to ram loads of facts, links, and passwords down people’s throats too early on.
It was the annual University of Lincoln Library staff away day on Tuesday. I performed my turn: a 20-minute presentation on QR codes in academic libraries: the culmination of our (JB, PC, CL, MN, PS, EV) little internal mini-project. (There were two other mini research projects which reported on Tuesday: one group looked at improving the student experience; the other at the best ways of promoting new library resources.)
Then we broke off into groups to consider various questions arising out of the work of the project groups. My question was this:
How could we support and encourage the use of mobile devices in the Library?
We talked around this for a while: should we be supporting their use? (We certainly support and encourage the use of desktop PCs as tools for accessing library resources and services: so why not mobiles? Part of the problem, I think, is that we’ve not reconciled our historic library-y attitude to mobile phones with the possibilities of mobile computing. Whatever: we need to come to terms with them once and for all, decide on a position, and stick to it!)
Even given that we should be prepared to support mobile devices: do we need to encourage people to use them in the Library? (People seem to be adopting smartphones perfectly readily without the need for encouragement from libraries…) Perhaps what we need to encourage is not the use of mobile devices per se, but for students and academic staff to re-consider the use of them as valid devices for learning.
We also need to remember that ‘mobile devices’ ≠ just phones, but also mp3 players, tablets (e.g. iPads), e-book readers, netbooks, etc. etc.
After a while, we narrowed it down to six recommendations for the Library: three things we could do now, with no additional money, to support the use of mobile devices – three further things that we can plan to do in the future, which would require a bit of funding.
Do now with no extra money:
- Add QR codes to print journal box labels, to link our print holdings to the corresponding e-journal record (c.f. this photo);
- ‘Soft launch’ the mobile version of RefWorks (RefMobile) to our users;
- Ask colleagues within the Library who are already smartphone enthusiasts (they know who they are!) to demonstrate their toys to the rest of us.
Do in the future with a bit of funding:
- Run a marketing campaign to encourage people to re-consider their mobile phone as a useful academic tool (“the classroom in your pocket“?);
- Systems development – make sure as many of our systems as possible have a valid mobile user interface, and target development at those systems which are lagging behind;
- Purchase tablet devices for library staff to use when ‘roving’: providing support to students away from the help desk (“…you don’t need to log in, I can show you on this!“).
I’m at De Montfort University in Leicester tomorrow, giving a presentation at the CILIP UC&R East Midlands members’ event: Making an Impact. My presentation is about our involvement in the JISC-funded Library Impact Data Project (LIDP) with the University of Huddersfield. My slides are online.
If you want to skip the monkey and head straight for the organ-grinders, my presentation borrows fairly heavily from two documents produced by the LIDP project team at Huddersfield:
- Stone, G. (2011) Looking for the link between library usage and student attainment. In: CILIPS Annual Conference, 7 June 2011, University of Glasgow. (Unpublished)
- Pattern, D. (2011) If you want to get laid, go to college… In: Welsh Libraries, Archives and Museums Conference, 12-13 May 2011, The Metropole, Llandrindod, Wales. (Unpublished)