Following on from the workshop for librarians (see earlier blog post for further information), Jisc Collections are now hosting a workshop in the same topic for publishers. The event will be held at the Jisc Offices in London on 22nd January and aims to highlight what librarians need to know from publishers about their resources with regards to their mobile compatibility (based on the discussions from the earlier workshop with librarians).
You can book a place at: http://www.eventbrite.co.uk/e/mobile-resource-issues-publisher-workshop-tickets-9511871263. Please feel free to pass the details to publishers or other resource providers you think may be interested.
22nd January, Jisc Offices, Brettenham House, 5 Lancaster Place, London, WC2E 7EN
11.00 – 3.30pm
Considerable work has been conducted around the issues of mobile access to library resource, in particular within the Mobilising Academic Content Online project: http://www.open.ac.uk/blogs/macon/
In the light of that work and the recent Jisc Collections workshop on mobile access issues for libraries (http://www.researchinformation.info/news/news_story.php?news_id=1341), this workshop will attempt to highlight for publishers what librarians need to know about their resources in the mobile context such as:
Does it have device twinning / linking for access?, Does it have an “app”?, Is the app fully functional?, Is mobile federated access available?, Is the content in HTML5?, Does it reflow?, Too many redirects in the process? and much more.
The workshop will discuss how such information can be best collected, collated and surfaced within the community as well as examining the support that publishers could provide in this area.
We’ll also look at how evaluation criteria of mobile resource functionality, usability and access methods might be defined and how this work could be taken forward in an international environment with a focus upon looking at common best practice.
The structure of the day will include:
- Scene setting
- Summary of activity in the area
- What libraries want: A Mobile Manifesto
- Examining Evaluation Criteria
- Way forward
Lunch will be provided.
Please note that this workshop is aimed at academic publishers, interested librarians should contact Mark Williams.
Further reading on this topic can be found:
Research Information – “A Manifesto for Mobile” Mark Williams & Ben Showers, JISC
Jisc Mobile Workshop “Accessing library resources via mobile” Jo Alcock, Birmingham City University
UKSG 2013 – “Integrating mobile technologies into the academic library” Claire Gill & Claire Graverly, University of Surrey
UKSG 2013 – “Mobile publishing / publishing on the move” Victoria Wright, Taylor & Francis
Insights Journal – “Mobile authentication and access: any time, any place, any device?” Mark Williams, Jisc
[SIGN UP HERE]
If you have any questions please contact:
T: 02030066042 (Direct)
Jisc Collections and Janet Ltd
On 16th July, I attended a workshop hosted by Jisc Collections to discuss issues around accessing library resources via mobile devices. The focus of the morning was sharing some of these issues through a series of presentations, and the afternoon focused on a workshop whereby we discussed, in groups, the current key issues and steps we could take to help solve some of these.
The event opened with an introduction by Mark Williams (Jisc Collections) and Ben Showers (Jisc Programme Manager) who shared the intended outcomes of the day. We then had a presentation from Keren Mills (Open University) who gave an overview of the Jisc-funded Mobilising Academic Content Online (MACON) project. Keren started her presentation by sharing the issues around users having to jump from mobile websites to apps for different content, and how this isn’t an efficient workflow for them. For this reason, the project focused on providing accessing to OU library resources via a mobile interface for their discovery service (EBSCO). One of the biggest issues they tackled as part of the project was authentication – sometimes this can cause problems on mobile devices as there are too many redirects for the browser to cope with, or it can be difficult for the user to work out what details they need to put in and where. By prompting users to login as soon as they start their search, this means they should only need to login once per search session to access content through the discovery service. They also adapted the design based on user feedback, and produced a best practice toolkit for delivering academic content to handheld devices (this includes recommendations about content formats, delivery, user requirements, and usability). Keren’s slides are below:
Following Keren’s presentation, I gave an overview of some of the work we did as part of the Jisc m-library community support project relating to this topic. In particular I focused on the Pathway to Best Practice on Providing access to resources via mobile devices. I shared some of the examples in this including Newcastle University’s LibGuide on Mobile apps and resources, University of Birmingham’s advice for users, and the Library Success wiki. I then shared some examples of the sorts of options available from publishers and providers at the moment to demonstrate the variety of different options. This included mobile websites, mobile apps, and a multitude of different approaches to logging in. My slides are below:
The next presentation, from Claire Gill and Claire Gravely at University of Sussex, gave some more detail on some of the options available and what this meant for libraries. At University of Sussex, they spent some time checking providers to see what mobile options were available. Of the 170 checked, 17 had mobile optimised websites and 28 had mobile apps (14 of which they classed as ‘usable’ i.e. access to full text, only having to login once, and easy to access). They then showed us some examples and shared the good and bad of each based on the things their users were likely to want to use the app for. The slides are below:
The final presentation was from Claire Grace (Open University) who spoke about the user’s expectations and the role of the library in checking access to resources. She explained that many of our users will have different devices for different purposes (e.g. they may use a phone/tablet for browsing websites and searching for resources, but prefer to use an ereader for reading books) and we need to understand this to know how best to support them. They are also likely to have different expectations for the different devices they use. The number of different devices (hardware and software) make it difficult for libraries to check access to resources. Claire encouraged us to push for standards and testing during development so we’re not finding that things don’t work as they should.
After lunch, we had a brief discussion about UK Federation and mobile access. A couple of resources were recommended for people to check out:
This led into the group discussions where the aim was to discuss the main concerns and offer suggestions for ways forward. There were some really interesting discussions about whether apps or mobile websites are preferable (most agreed mobile websites in this situation), issues and potential solutions for authentication (such as for example a mobile friendly version of Shibboleth or other authentication methods), and the issues around duplication of effort across the sector and how we can reduce that.
Jisc are writing up the notes from the discussions and will be sharing the outcomes in due course, but in the meantime I thought I’d share some of the main messages and suggestions for ways forward that I picked up on, which seemed to come under three themes:
This included organising and participating in wider discussions with libraries, publishers, and users to understand each other’s perspectives and work towards the common goal of simple access to resources regardless of the device used.
- Shared resources
This included ideas such as contributing to a shared resource with details of mobile websites/apps – something that both libraries and publishers can contribute to (possible the Library Success wiki, or something similar)
- Shared best practice
This included developing a set of standards or a specification for publishers to use when developing their mobile websites.
It was really useful to get a group together to discuss these common issues, and I certainly came out of the workshop much clearer about what needed to be done. If this is an area you are interested in, please subscribe to the blog (links at the top of the right column) as I’ll make sure to post updates.
There have been a few posts on the blog about QR codes, but so far we haven’t looked at how to change them visually to fit into branding guidelines. Jacqui Lockwood from University of Warwick worked on a project to do just that for their library, and this post shares her experiences and provides you with tips for doing the same.
Jacqui Lockwood is the Learning Grid Officer at the University of Warwick Library. Her role mainly involves working alongside the Learning Grid Coordinators, assisting in the smooth running of the four Grid sites and developing the service to ensure it is at the forefront of innovative teaching and learning within the university. She also is involved in marketing, disability awareness, and QR code working groups as well as several other projects. Before this post she worked as a Library Adviser in the Enquiry Support Team and was involved in the development and marketing of the recent Just ASK campaign.
Where it all began
So, let’s face it, QR Codes look rubbish. They’re boring, monotone, blocky, and ugly.
Despite this, they do provide a quick and easy route for customers to reach web based information and resources. The question is how can we use QR Codes without ruining the aesthetics of the overall product?
For those who don’t know, a QR Code is 2-D barcode developed by Denso Wave (QR Code is a registered trademark of Denso Wave) with the aim of being easily read by a scanner and the potential to hold a great deal of information. On release in 1994, it was originally picked up by automotive companies to help keep track of manufacturing processes. However, thanks to Denso Waves decision not to exercise their patent rights and the emergence of barcode scanning software available on smartphones, advertising moguls saw an opportunity.
It wasn’t long before these little black and white boxes started appearing everywhere, from posters to trucks, drinks cans to coins. The trouble was that people were starting to get a little bored.
So, what was next? One by one, companies and ad agencies started to play around with a rather useful feature of QR Codes – the ability to have an error correction capability of up to 30%. Although this was originally created to assist with the restoration of data, even if the symbol is partially dirty or damaged, it can be exploited to include branding as part of the image.
Applying it in the Library…
With such a strong brand identity in place in the University of Warwick Library, it seemed possible to incorporate this into QR Codes to make them part of our designs rather than a scar on them. In May 2012, with the development of the Just ASK campaign building pace, there was an opportunity for me to give this a go.
Warwick Print and the Just ASK marketing team had finalised the branding for the campaign….
The design seemed to lend itself quite well to the development of a branded QR Code. It took quite a while to get it quite right though…
Starting out with the full word in the middle of the code, although it works and looks quite nice, it didn’t quite keep in with the branding as much as we’d like, so it was back to the drawing board.
Taking the original image from the branding and popping a black QR code over the top worked in matching the branding but the results when trying to scan the code with such a dark background weren’t ideal. People aren’t likely to spend ages trying to get a code to scan, it needed to work first time.
Version 3 became the shining light in this project, the QR code would work in the red and blue picked for Just ASK (the Stewards using black meant that they’d never be much of a problem.)
Version 4 – the final product
As incorporating the codes into the advertising went on, the text at the bottom was abandoned and we were left with three clean, crisp, and far less boring QR Codes ready to stick wherever was relevant. All three scan quickly, even when reduced down and printed to sizes below 1.5cm square.
We added them to our advertising material and that was that…
So, how’s it done?
When first playing about to get an idea of how much you can utilise the error correction capabilities, we started off using Gimp (mainly because it was the only image editing software, besides paint, that I had on my computer!) This was, at times, a little fiddly and it proved easier when playing around, to import the different sections as layers and move them about in Microsoft Publisher.
Once I’d realised the sorts of sizes you can get away with, the colours that work and don’t work, and the key locations that need to be kept free of any branding, it was back to proper image editing software to get them just right.
With the help of our in house IT team, the final QR Codes were created in Adobe Illustrator as vector files. This meant we could change them to any desired size without losing resolution and convert them in to JPEGs when required. The main reason we did this was to ensure that, no matter where we send to image to for printing, it should always arrive as a sharp image. Initial JPEG files sent to the printers came back blurry when incorporated on to leaflet designs.
Developments since then…
Since working on this project, a number of sources have appeared that can help people created braded QR codes without the need for fiddly work in image editing software.
First off is Denso Wave’s own service, LogoQ, the only issue here being that it isn’t a free service. If you’re after a free tool, Unitag helps you customise a branded code to high extent via their free service with the option to pay for more customised work.
Of course, nothing works better than doing it yourself. Any free tool will have limitations on how close you can get it to your branding style.
Would we do it again?
There have been a few other experiments with branded codes at the University of Warwick Library since this project, but the use of all QR Codes, branded or not, is still quite low.
What we learned from this is that, for short campaigns and adverts, branded codes give us a great way of connecting our customers to webpage they may otherwise overlook without compromising our strong marketing style. There is also only a place for these little codes if there is a requirement for the customer to access online material, a pointless link to a redundant website would be a waste of time for both the creator and the scanner.
Now for some top tips…
- Keep testing your code.
Don’t think that because it worked when the added features were a millimetre one way that it will work when you move it. Every time you make an alteration scan that code!
- Print out test sizes.
Try printing out lots of size variations of your created code and check they all scan. If the QR Code has a lot of data in it, reducing the size can make the individual components hard to pick up by your scanner.
- Try different scanning devices.
Don’t just rely on your smartphone. Get an iPad out, or borrow someone else’s smartphone (preferably a different make or model!). You need to make sure that anyone who comes to scan your code should be able to.
- Don’t make one just for the sake of it.
QR Codes can be irritating if they don’t serve a purpose. A recent trip to a nearby library presented me with a QR code on a plasma screen that informed me that the corridor below it led to the toilets. Is that really necessary? Codes that don’t provide the customer with something they might actually be interested in can make them reluctant to bother scanning any of the others you put in place.
Myself and Ben Showers (Jisc) were invited to deliver a webinar this afternoon on behalf of UKSG on the topic of mobile technologies. The details are below:
The Mobile Advantage: Developing mobile services and resources for libraries and content providers
Ben Showers (Jisc) and Jo Alcock (Birmingham City University)
To equip attendees with an understanding of the current mobile landscape and to help them consider the impact this has on libraries, publishers and users in providing access to resources and services.
By the end of this webinar, attendees will be able to:
- Understand the current mobile landscape including mobile devices, technologies, and latest developments
- Share example case studies of how mobile technologies have been used to support delivery of library services and library content
- Plan next steps forward for investigating use of mobile technologies in their own work environment
The webinar will provide an overview of current developments in mobile services and resources for libraries and content providers. We will set the scene by sharing some facts and figures about the current mobile landscape and considering this in a library environment.
The main body of the webinar will focus on sharing examples, advice, and case studies in the following thematic areas:
- Developing Mobile Library Services
- Access to Content
- The Mobile Advantage
We will conclude with a reality check to apply the ideas into a real world context and a call to action for those considering developing mobile services or mobile content.
We hope to provide attendees with an overview of some of the interesting ways libraries and publishers are using mobile devices to help deliver content and services to users. Some examples include:
Mobile library services:
- Roving enquiries such as ‘Roving Librarian’ at University of Huddersfield
- Loaning mobile devices such as Radcliffe Science Library (University of Oxford)
- Bibliographic management such as Jisc m-biblio project at University of Bristol
Access to content:
- Summon Mobile
- Cambridge Journals Online (option to send articles to Kindle, Dropbox or Drive for mobile reading)
- University of Sussex part of SCARLET+ project
We also wanted to highlight to attendees some examples of intiatives that have only been made possible by mobile technologies, which we termed as ‘The Mobile Advantage’. This included:
Mobile technologies provide us with an opportunity to do something new; to rethink the ways we’ve always done things. The particular affordances of mobile (its portability, functionality, personalisation) mean it enables things to be done in new ways, and for new things to emerge entirely.
Hopefully, the examples and resources shared in this post, the blog and the community as a whole highlight that developing mobile services and content doesn’t need to be expensive or complex. Rather, there are a number of cheap or free services and approaches that mean there shouldn’t be any barriers to getting started with mobile library development.
For more resources see the #mlibs resources widget in the right hand side of the blog (which you can subscribe to if you wish).
Jisc Collections are hosting a free workshop on the topic of mobile access to library resources. Further details below and at http://mobilejisccollections-estw.eventbrite.co.uk where you can book your place.
16th July, Jisc Offices, Brettenham house, 5 Lancaster Place, London, WC2E 7EN
10.45 – 3.30pm
Considerable work has been conducted around the issues of mobile access to library resource, in particular within the Mobilising Academic Content Online project: http://www.open.ac.uk/blogs/macon/
In the light of that work, this workshop will attempt to gain consensus on what librarians need to know about their resources in mobile terms (such as: does it have device twinning?, does it have an “app”?, is the app fully functional?, is mobile federated access available, is the content in HTML5, and much more).
How such information can be best collected, collated and surfaced within the community will be discussed as well as examining the support that Jisc Collections could provide in that area.
The workshop will also look at how evaluation criteria might be defined and how this work could be take forward in an international environment looking at common best practice.
The structure of the day will include:
- Scene setting
- Summary of activity in the area
- What libraries want
- Publisher case study on developing mobile access
- Articulating the issues
- Way forward
Lunch will be provided, and there is limited support available for attendees who require help with travel costs (please contact firstname.lastname@example.org directly).
Further reading on this topic can be found:
UKSG 2013 - ”Intergrating mobile technologies into the academic library” Claire Gill & Claire Graverly
UKSG 2013 - “Mobile publishing / publishing on the move“ Victoria Wright, Taylor & Francis
Insights Journal - ”Mobile authentication and access: any time, any place, any device?“ Mark Williams
If you have any questions please contact:
T: 02030066042 (Direct)
A lightning talk at the recent UKSG conference focused on Integrating Mobile Technologies into the Academic Library, based on the experiences of University of Surrey. In this guest blog post, Claire Gill and Claire Gravely share more information about some of the initiatives at University of Surrey Library to support staff deliver services, and to support users. Claire Gill is Virtual Support & eServices Developer, who became interested in mobile technologies as part of her role is to maximise the accessibility and usability of the website and e-resources. Claire Gravely is Information Resources Advisor, who was previously involved with e-resource management and access, which sparked an interest in access to information and resources through new technologies.
After seeing an increase in the number of users with mobile devices such as smartphones and tablets we decided to investigate the different options available to the Library to support this usage.
Our approach from the start has been to focus on what we can do or change now. This allowed us to take a step back from whether or not we would be able to create and support a mobile app, which seems to be all the rage, and to focus on what was in front of us and the quick wins we could achieve.
Focus on Staff
A first step was to get Library staff introduced to the technology. We held some initial training sessions in which staff were invited to come along and try out a few different tablets and e-readers. This allowed them to have a play with the devices and they were given some basic instructions to show them how a user might access some of our resources through these.
A number of iPads have now been integrated into the staff workflows. We have an iPad for troubleshooting and testing which is used by web development and the e-resources team. The user support team have recently implemented a roving service which now also uses iPads which have been colour coordinated with library staff lanyards to give a more professional presence around the library.
The academic liaison librarians have started to use iPads to support students, and also to take to meetings across campus – they have found them particularly useful to show changes to the website and new resources to their faculties while out and about.
Focus on the user
We wanted to find out what our users wanted from the Library on their mobiles, so we put a poll on our blog, and then held two focus groups.
What came out overwhelmingly was that students didn’t really care where information came from – the Library, or other parts of the University – and wanted an app that would combine all information in one place.
We have therefore been holding talks with the University’s Digital Platforms team looking at creating a University-wide app with input from all departments.
In the meantime we have been doing the things we can do in the Library. We have implemented QR codes (we use bit.ly to generate these, as we can get statistics). We currently use these on posters, and electronic displays, to link to further information online, or to the contact details of our Academic Liaison Librarians. While the statistics show a relatively low usage of these, the effort involved in creating them is negligible, so we feel it is worth it.
Another easy implementation – just changing a setting – was the mobile version of our Library Catalogue, which is now available for students to search for and renew books on the move – this was a very popular request that came out of the focus groups.
We have created mobile friendly versions of our opening hours page, and of our room bookings site – the latter of which was another need highlighted by the focus groups – and we are working on getting this linked to the physical rooms by use of qr codes.
We have investigated the different apps available for resources we subscribe to and are working on a new webpage to promote the most useful ones to students.
Things to Consider
Some tips for others looking to start implementing mobile technologies would be:
- Don’t get too bogged down in the app vs mobile responsive design argument
- Look for things you can change with the resources you have:
- Changes to optimise webpages that students use most
- Look for simple uses of free technology such as QR codes to get people started
- Don’t forget that what works on a monitor may not work on a small phone screen – be prepared to change your way of thinking
- Don’t forget your staff! If you are expecting your users to use apps and mobile devices then they will come to you for help – make sure your staff are comfortable with the technology
- Speak to your users! There is no point building fancy apps or responsive web design for pages they won’t use. Focus groups are a great way to get feedback on what your users really think
One of the common barriers preventing implementation of mobile technologies is staff awareness and familiarity. A number of different methods have been used to assist in this area of skills development, and 23 things programmes have been developed to support development of mobile skills – see for example the open 23mobilethings course.
University of Glasgow have developed a 23 things style course for introducing their staff to mobile devices and technologies, and their experiences are shared in this guest blog post by Kay Munro and Karen Stevenson. Kay Munro is convenor of the University of Glasgow Library’s Mobile Technologies Group. Kay is a College Librarian providing support to the College of Social Science. Karen Stevenson is a member of the University of Glasgow Library’s Mobile Technologies Group. Karen is the Library Systems Manager and a member of the Digital Library Team.
23 Things Mobile is a self-directed training course, designed to introduce Library staff to mobile technology and its applications that has been developed by the University of Glasgow Library. The 23 things concept has been widely adopted in recent years and, when looking for an online training model to support a Library staff skills initiative on mobile technology, it was an obvious one to consider. However, because of the dynamic nature of the topic, we wanted to provide staff with a fun and interactive experience which incorporated opportunities to come together to try out devices, apps and activities using the wide range of devices and facilities available in the Library’s Live Lab. So a hybrid model, based on the 23 things idea, was developed.
Glasgow’s 23 Things Mobile course is made up of three elements: VLE content, a private blog and group sessions in the Live Lab. The majority of the content is delivered via our VLE, Moodle, which allows us to create visually rich and interactive content. The dedicated blog hosted on WordPress allows participants to engage with each other and share their experiences and thoughts about the course content or related aspects of mobile technology. The Live Lab concept, established at an early stage in Glasgow’s mobile strategy, had been developed to provide Library staff with the opportunity to use a wide range of mobile devices in a dedicated space within the Library, or to borrow for use at conferences or at home. The Live Lab sessions for 23 Things Mobile took place half way through the course and brought participants together in small groups to try out a range of devices and a series of fun, but related, tasks which covered all aspects of the course content.
A decision taken early in the process was that the focus would be on mobile technology in general and not specifically on its application to libraries. The aim was to develop skills generally to increase confidence and familiarity with all aspects of the mobile environment. The course content was created in-house, but did incorporate content from external sources, such as the websites of the major device manufacturers and software developers as well as blogs and other social media outputs from the technology and academic communities. The content was a mixture of text, images, video, audio, presentations and quizzes. Using the 23 things model, the course was structured around a number of themes with several ‘things’ grouped together in each theme.
- Devices: phones, tablets
- Networks: wifi, 3G/4G, the cloud
- Applications: mobile web, apps, QR codes
- Communicating: blogs, text/instant messaging, email, Facebook, Twitter
- Library stuff: ebooks, ejournals, mobile databases
- Fun stuff: Live Lab, music, photos/videos, gaming
- Other: introductory session, mobile futures, 23 Things round-up quiz
The order of the main themes was determined to ensure that the course was progressive, allowing participants to build on knowledge from week to week. We also tried not to make any assumptions about the skill level of participants. The course was therefore designed to be introductory but with opportunities for discovery of more technical aspects via optional ‘Geek spots’.
The first version of the programme was tested with a small pilot study of 23 participants. This gave us the opportunity to test both the content and the administration of the course. It ran for 10 weeks during late summer 2012. Fifteen participants (65%) completed the whole course. Of the eight participants who failed to complete the course, two only failed to complete the final week but four completed less than 50% of the course. Evidence gathered from post-pilot interviews with participants who failed to complete the course and analyses of the Moodle logs suggest that making time each week proved difficult for certain grades of staff. The reasons for this appear to be varied, but holidays, illness and the pressure of work all seemed to be contributory factors. It was clear that some individuals struggled to motivate themselves to complete the course once they had slipped behind with the weekly programme. A few participants also reported that they felt that they already knew a lot about mobile technology and/or had no interest in certain aspects of the course.
Reassuringly, 100% of participants who responded to the post-pilot survey said that they would recommend the course to a colleague and in response to questions about course content, 90% indicated that it was pitched ‘just right’. The most popular element of the course was the Live Lab session, “I like the idea of getting mixed groups of people together and letting them have the space to play around”. Several respondents asked for more of this type of activity during the course, while others recommended that more support should be available during the Live Lab session.
Following on from the pilot, the course was approved by Library senior management and has now become a mandatory training requirement for all Library staff. The course is currently being rolled out in a number of tranches, with 40 per tranche, to all daytime staff in the first instance. On the basis of pilot feedback, the course structure was reduced to 8 weeks plus an introductory session, which also gives participants the opportunity to meet each other. Where necessary, participants who are not in positions which allow them to manage their own working day are timetabled a 1 hour slot each week specifically for this activity.
The amount of time and commitment to delivering a staff training programme of this size and complexity in a large academic library is considerable. The course is currently administered by 3 members of the Library’s Digital Media Skills Group. The expectation is that, in the future, colleagues who have been through the 23 Things Mobile course will be able to contribute to its ongoing administration and provide support for current participants. Some of the pilot participants have already taken the opportunity to become ‘Geek buddies’ and are actively engaged in the 23 Things Blog and are also providing invaluable support during the Live Lab sessions. We hope that as the pool of staff completing the course increases, more ‘Geek buddies’ will emerge and will contribute not only to the administration and support for 23 Things Mobile, but will become involved with updating content.
The end … so far
The first tranche of 40 staff, post-pilot, are coming to the end of the course, and the second tranche is just underway. It looks like we are heading for 100% completion rate of tranche 1 participants, and there have been high levels of interaction in the blog about the course and other aspects of mobile technology. Here are just a few comments from the group who are just finishing:
I’ve just completed the quiz and feel genuinely deflated that my 23 Things experience is over; 8 weeks have just whizzed past! Good luck to the recently enrolled newbies, I hope you enjoy as much as I have and learn lots of new things…or 23.
I can’t believe it is 8 weeks since we started 23 things mobile! I suppose time is really fast when you are having fun? I have learned quite a lot during the course, and I can now show off to my friends when they ask what does that mean? or how can you do this on your mobile?
The course was well paced, extremely informative, varied, interesting, thought-provoking, and, ultimately, somewhat scary (Week 8 and the future!). But above all it was FUN, as promised at our induction! … And may I ask if former participants are still allowed to blog occasionally should the desire seize them?
Access to the Moodle and blog remain open to all previous participants. This allows them to refresh their knowledge as content changes and keep updated with the Library’s mobile initiatives, and hopefully, to continue to support their colleagues as they embark on the 23 Things Mobile adventure. For the course administrators, delivering the programme to our evening and weekend staff will be the next challenge!
A longer version of this paper will appear in Issue 58 of SCONUL Focus: http://www.sconul.ac.uk/page/sconul-focus
This guest blog post is based on a current QR code project to help students with referencing. Nic Howorth and Sarah Munks are Subject Librarians at the University of Huddersfield. Sarah is based at the Barnsley campus and has responsibility for Art, Design and Architecture and Music subject areas. Nic looks after the School of Education and Professional Development. Both regularly deliver information skills sessions to students and staff.
To make use of QR code and mobile technology to provide in-hand, timely, text specific referencing advice for students.
- Utilise QR code/mobile technology to improve student’s citation and referencing skills
- Provide referencing support to students anytime, anywhere
- Enhance the student learning experience using mobile technology
- Cross collaboration: liaise with module leaders to ensure key texts are included in the project
- Cross collaboration: liaise with academic skills tutor to ensure referencing and citation information is accurate
- To reach those student who may be unwilling to ask for help
- Promote QR codes as a tool for learning
The project is based at our campus library in Barnsley and is investigating the willingness of students’ use of mobile and QR code technology to access learning support. Recent research has suggested that the rise in use of mobile technology is resulting in more and more learning taking place outside the traditional classroom or lecture theatre (Solvberg & Rismark, 2012) and the increase in and availability of mobile devices and developments in technology (smartphones, tablets, portable music players etc) allow users to readily and easily access the internet or download applications (Walsh, 2012).
Students want more choice with regards to when and how they learn and increasingly want to be able to use their own mobile device to access teaching and learning materials. Using QR Codes is an ideal way of utilising user owned mobile technology to engage and support learners. As a result a short survey was conducted at the campus and revealed 66% of respondents owned a smart phone, and 68% of these students would use it to access help with referencing which started the project.
Two courses were identified within the School of Education and Professional Development but with a different demographic of students for each course. The project hopes to identify if students on a particular course and part of a particular demographic were more or less likely to use mobile technology to access learning support. A reading list from a PGCE in-service module and Early Years BA (Hons) module were utilised and a blog entry for each title on the reading lists was created. The blog entry advises students how to produce an in-text citation and reference using our institutions Harvard referencing guide. QR codes were then produced linking to each of the blog entries and attached to each text on the reading lists with text advising students what the code was for. A decision was made early on to promote the QR codes to one group of students and leave the other to their own devices with a view of seeing if promotional activities make a difference with regards to usage.
- During December we promoted the QR codes in referencing sessions delivered to the PGCE cohort.
- During March we ran an exit survey to gauge the level of awareness of QR technology amongst our student population. The results are being reviewed.
- The project is still on-going and the next steps are to arrange focus groups with students to gain qualitative feedback. In particular the usefulness of delivering advice/support using QR codes and mobile technology, the analytics of hits/views to the blog posts will also be reviewed.
We used the free Kaywa QR code generator as this allowed us to produce and save multiple QR codes. We have since discovered Power QR which allows you to produce a QR code then change what it links to remotely without having to re-produce or re-print additional codes. This wouldn’t have worked for our referencing project but would be ideal if you’re thinking of using QR codes as promotional tools (i.e. you could link to a different site/resource each week using the same QR code).
As the referencing information was probably going to be viewed using a mobile device we used WordPress to create our blog as their blogs are optimized for viewing on a mobile device. Where possible, we included an image of the book cover for each blog post to make it more visual – see the Mobile Referencing blog for examples.
Solvberg, A., and Rismark, M. (2012) ‘Learning spaces in mobile learning environments’. Active Learning in Higher Education. 13 (1), pp.23-33.
Walsh, A. (2012) Using mobile technology to deliver library services: A handbook. London: Facet.
We’ve previously shared some tips and advice about how to use QR codes, but today we’re looking a slightly different angle – how do you decide which tool to use? To cover this topic we have a guest blog post from Neil Ford, Academic Liaison Development Manager for Library and Learning Support at Bournemouth University. Neil has previous experience in health, public, commercial and academic libraries, current interests include: digital literacy and academic skills support, QR codes, collection development, co-creation of reading lists in academic liaison.
Recently colleagues and students who want to use QR codes in their work have been asking “which tool should I use”? With so much choice it can be a difficult question, and one that depends partly on what you want to achieve with your QR campaign. In this post, I’m going to discuss some criteria that can be used to evaluate URL shortening and QR code generating tools. I’ll be drawing on experience using these tools on a recent project at Bournemouth University that introduced QR codes to our book shelves to guide students to relevant ebooks.
Many online tools now enable you to create shortened URLs and QR codes. This dual functionality makes a lot of sense as the shorter the URL, the easier the QR code is going to be to scan.
Are all URL shorteners equal? Well no!
In terms of technical performance there is quite a difference between different providers.
Another point to consider is whether the tool been designed as a URL shortener or as a QR code generator or both? This might seem like a silly question but, how the tools developers see the product, could have a profound effect on its usability for your purpose (see the section on user interface below).
The size and quality of a QR code can have a significant effect on how easy it is for devices to scan. It’s worth comparing the images that different tools produce to see how well the image meets your needs. How big is the QR code that is produced? Will it meet your needs or will you need to edit it using an image editor?
Again this may not matter too much if you are only producing a couple of codes. If you’re working with large numbers of codes you will want to avoid too much work manipulating images. In general: the larger the image, the better! It’s much easier to shrink an image and maintain quality than vice-versa.
The media that you use to deliver your QR codes will affect how important this criteria is to you. If you are producing codes for a small handout or business card then image size may not matter (as users can get right up close to scan the code). If you’re using codes on posters, signage or lecture slides it may be more of an issue. Creating and testing a prototype using a variety of tools will help you to find out which tools meet your needs.
How easy is it to shorten the URL and get a QR code out of the interface? If you are just producing a few codes for posters then this may not be such a concern for you. If however you are producing hundreds or even thousands of codes then ease of use is going to matter! Even a couple of extra clicks could make a great difference. Half way through our QR code project at BU, Bit.ly’s user interface was “enhanced”, which added extra steps to the process of getting to a QR code. Whilst you can’t control how web tools develop their interfaces, you can select a tool that demonstrates concern for their user community when implementing change.
Seeing the number of hits on your QR code should be a key part of your ongoing evaluation of your QR campaign. Does the service you’re using to create your shortened URLs and QR codes enable you to see the usage? Statistics about how and when your users access library resources can be part of the added value that you can get from a QR campaign. As well as promoting resources, usage statistics can tell you about how and when your users want to access library resources.
You may need to dust off your crystal ball for this one. Free, web-based tools offer us great opportunities but it’s important to remember that, even though the tool may be “free” you are investing your time and work in using it. There is always a risk that the tools will change, move, or even disappear… (did anyone else feel slightly nervous when that whole Delicious thing was going on?). While there are no guarantees, if reliability is important to you then it may be worth going with a well-established tool like Google, even if you prefer a different user interface or URL shortener. If the worst happened and the tool that you’ve used for your url shortening were to disappear, how easy would it be to move your shortened urls and QR codes to another platform? Keeping a record of the targets that your QR codes point to is one way to recover from such a disaster with minimum fuss!
Persistence vs flexibility
Similar to the last point, you may want to consider the life cycle of your shortened URL/ QR code. One of the main reasons that we chose to use Bit.ly for our QR code shortener was that it guaranteed that the shortened URL was persistent and would not expire. At the time this seemed like a benefit. Reflecting back though, being able to change the target of our QR codes would have been a better attribute. Shortly after our QR codes were added to the shelves, we learnt that our library catalogue (our QR codes point to catalogue searches for ebooks) had changed ownership and as a result would be changing their URL! This means that we will need to create new shortened URLs and QR code labels for about 1,000 catalogue searches!
Fortunately, we have recorded our searches and will be able to complete the work efficiently. Looking on the bright side, this gives us an opportunity to re-evaluate the tools we’ve been using and move to one that better meets our needs in terms of usability, metrics and flexibility.
I hope this has been a useful reflection. I’d love to hear about your experiences creating QR codes. Which of the criteria above are important to you? Do you have any other considerations when choosing this sort of tool?
This guest blog post is written by Annmarie Lee, an Assistant Liaison Librarian – Enquiry Services for Library and Learning Resources at Birmingham City University. On a day to day basis she is part of a team that provide enquiry services at the University’s Health library and Art and Design libraries. She has participated in several strategic projects including the development of a single Help Desk within the libraries, the implementation of a library online chat service and more recently the use of mobile technologies in libraries.
As part of Library and Learning Resources’ Mobile Technologies working group at Birmingham City University, a small working group was established to look at the development of the library facility on the Birmingham City University Mobile App (iBCU).
Surveying other libraries
Our first task was to find out what functionality is currently being offered by libraries through mobile apps. We devised a short survey asking libraries to share with us what their mobile app included.
A total of 28 responses were received from both public and academic libraries both within the UK and internationally.
Respondents indicated that 61% used Apple devices for their library apps, followed closely by 54% using Android devices. 82% indicated that they used a mobile web app (accessed via mobile browser).
In terms of library features, contact details, a facility to search for books and library opening hours prevailed with the highest response rates. Library locations and account information were also popular features available. The one feature we were particularly interested in was the ability to book library tutorials via a mobile app; however no respondents listed this as a feature of their mobile app. The chart below shows more information on the results:
Surveying our users
Following on from this, we decided to survey our users to see what library features they would like to use through a mobile app. In order to avoid a clash with the National Student Survey and also to gain insight from users who may already be familiar with mobile apps, we decided on conducting a Facebook and Twitter poll posing the following question:
Early results indicate that managing library accounts are of most interest, with searching for books, accessing electronic resources like e-books and e-journals, and booking study rooms also likely to be popular features.
The iBCU app already has a library facility to view your account details. The next step will be to work with ICT to look at the feasibility of adding functionality to this like the ability to renew items. A separate working group has also been established to look at embedding mobile apps like that of the EBSCO database into the existing iBCU app.