Posts Tagged ‘iPad’

A Wandering We Will Go

Posted on September 7th, 2010 by Nick Jackson

Today, after wresting the iPad from Paul, I was wandering around the GCW with it making some notes for another project (a new group room booking system if you must know). This felt quite cool I must admit, and let me get a grasp of how the iPad would feel if someone had to walk around with it all day. It actually felt quite easy, but that’s not the point of this blog post.

The point is that I was asked two library related questions by students simply because I had an iPad and looked authoritative. No uniform, no sign saying “ask our library staff questions – they’re the ones with iPads”, my ID clipped to my belt but not obvious.

As it turned out I was able to answer their queries using the web browser and the HiP interface, but for two people to ask questions in the middle of summer with no advertising or clear indication that I even worked in the Library should show just how receptive people are to the concept of a roving librarian.

Up next: our iPad interface, concepts for the new library web front-end, playing with RFID (hopefully), improved and automated Horizon to Jerome path and Journal integration!

Taking the library for a walk

Posted on September 1st, 2010 by Paul Stainthorp

Today we unwrapped the second* weapon in the Jerome arsenal.

iPad

It’s an iPad. 16GB with Wi-Fi.

Despite what you may be thinking, this wasn’t a vanity purchase or an indulgence (well… maybe just a leeetle bit…): rather, working on the principle that to catch a <noun>, you have to think like a <noun>, this is the device that we’ll use to build, test, demonstrate and evaluate all the bits of Jerome that we hope will coalesce around providing flexible, mobile, student-centred access to library data, resources, people and services.

So, if you see one of us [1|2|3|4|5] hovering around the GCW University Library holding an iPad and looking excitable, come and say hello. We might have something interesting to show you.

———

*(The first being our “un-server” which is now quietly steaming away in the background …more on this soon)