March 23rd, 2011 Brian Herzog
Joe Murphy, Science Librarian, Coordinator of Instruction & Technology, Yale University
Chanitra Bishop, Instruction & Emerging Technologies Librarian, Indiana University
Jason Clark, Head, Digital Access & Web Services, Montana State University
Foursquare and Libraries - Chanitra Bishop
Location-based mobile apps use your device's GPS data to locate information about what is going on around you. The advantage is the potential for targeted marketing to users in a specific geographic location
Examples: Foursquare, Brightkite, Yelp, Gowalla, Google Places
People like them because they are fun, almost like games, and can earn points and badges for their activity.
Foursquare allows you to
- check in to different location
- create a to-do list for locations
- find out what frineds are doing
- learn about events, restaurants, etc in a location
Notes of caution: you are broadcasting where you are, so people could follow up, or know where you are not (ie, your house)
Foursquare and Libraries
Libraries can claim your location and/or add new locations
- give each feature of your library a location (cafe, DVD collection, reference desk, etc) to promote those services to people on Foursquare
- gives you the opportunity to run promotions
- engage with patrons, award the mayor
- use tips, descriptions, photos, and tags to share information
- update incorrect user-generated information
Where are You? Locations and Library Applications - Jason Clark
How does location matter for libraries?
Content isn't just enough anymore - now the context is also important (about 50% of Google searches have some geographic component). Neat mashup: Wildlife near you (plotting flickr photos on a map to show animals in your area)
- Mapping (give context in a snapshot)
- Check-in like Foursquare - Darien Library gives a totebag to patrons who check in
- Crowdsourcing geo information - maps.nypl.org allows people to overlay historical infomration on current city maps, and also allow people to correct errors
- Local interest apps - San Jose WolfWalk historical walking tour of campus
Getting Started - Tools
February 8th, 2011 Brian Herzog
Something I really like about smartphones are apps like CardStar and Key Ring - they let you input the numbers from all the club and rewards cards from your keychain and display the barcode on your phone.
Patrons also use these apps for their library card numbers, and some libraries aren't sure how to handle the library-card-on-smartphone situation. It hasn't really come up in my library, but I know our traditional scanners won't read barcodes off a smartphone screen. So, I thought I'd do some research to find out what it would take to accommodate these patrons.
The reason it doesn't work is because traditional barcode scanners are designed to read laser light reflected off a solid surface. Smartphone screens are emitting light, so an entirely different technology is needed.
The scanners that can read barcodes on smartphones are called CCD scanners (what that stands for is less important than a short description or a compare/contrast between CCD and traditional laser scanners).
After learning this, I started looking around at the different models and costs of CCD scanners. I stumbled across a Quora post mentioning a company called FaceCash* which sells scanners for $30. That's cheap enough for experimentation, so I contacted Aaron Greenspan (FaceCash founder) and bought one.
And it worked. I plugged it into a computer's USB port, held it up to an iPhone with a library card displayed on it, and Beep, the scanner read it just like it should. I'm always shocked when tech things work right out of the box. And happily, the scanner also reads** regular barcodes too.
So now, for just $30, my library can accommodate those patrons who make their lives easier*** through mobile technology.
Recent studies show this is fast becoming the standard in the business world - especially airlines. So the only question is whether or not libraries are willing to honor "virtual" library cards.
I don't see why not. It doesn't seem like fraud would be any more of an issue with this than with regular library cards. When we sign up a patron for a new library card, we give them a wallet card and a keychain card - so already there is more than one copy of the card in existence, which means more than one person could be using it. Since we don't make people show a picture ID when they present their library card, people could already be using someone else's card and we'd never know. Besides, if it's good enough for the TSA and airline security, I think we can manage.
But best of all, accepting these means that it's easier for patrons to bring their library card with them to the library. This is both better customer service and will save staff time in not having to look patrons up. Now that I have this scanner, I just have to wait for a patron to come in who needs it - what a strange feeling to be ahead of the curve.
*FaceCash is a new way to pay for things - you add money to your FaceCash account, and install the FaceCash app on your phone. Then when you're in a store or restaurant that accepts FaceCash, the app displays your account barcode for the business to scan, and also a picture of your face, so the clerk can verify that you are actually you. With more and more personal data being stored in phones, the visual verification is a great idea. If my library charged fines, I'd want to sign up us to accept FaceCash.
**One limitation of CCD scanners is their short range - just a couple inches, compared to 8-10" range of traditional scanners. Plus, the scanner I bought is trigger-operated, rather than motion-operated like our existing scanners. So, even though it can read both physical and digital barcodes, I don't think we'll swap out what we've got for it, but instead just plug it in and use it when a smartphone patron comes to the desk.
***I like just about anything that reduces waste and clutter. These apps let you store useful information easily, instead of lugging around a whole deck of various cards, and that makes life better. Read a few more tips to simplify your wallet, so you don't end up like George:
Tags: barcode, card, device, devices, libraries, Library, mobile, phone, phones, public, scan, scanner, scanning, smartphone, smartphones
February 3rd, 2011 Brian Herzog
Just a few quick blurbs on some upcoming events that caught my eye - the first two for Boston-area people, and the third for all of New England:
I seem to be all about mobile technology lately - and MobileCampBoston is a day-long event devoted to it. The day looks organized into three tracks - Programming, Design, and Business/Marketing, so attendees can focus on their area of interest. Should be a great day of learning, and best of all, it's free.
Boston Radical Reference: Volunteer at the Community Change Library
Members of Boston Radical Reference will be volunteering at the Community Change library, which houses some of the best sources of information on racism in the United States. The plan is to conduct a comprehensive inventory of the collection, going book by book, to catch errors in the catalog, determine subject areas in which to expand, and identify books that need repair.
NELA-ITS Spring Workshop
I'm part of the IT Section of the New England Library Association, and we're designing this year's Spring Workshop to address the intersection of mobile technology and libraries. We're still working out the details, but the overall plan is to devote the morning to a sort of "state of things/orientation" as far as libraries and mobile tech goes, then lunch, and then an afternoon panel of librarians demo'ing ways they're using mobile tech in their own libraries. If you've never been to an NELA-ITS workshop before, they're a good time, and very focused on practical information.
I'll be at all three of these events - if you see me, please say hi.
Tags: boston radical reference, Conferences, event, events, libraries, Library, mobile, mobilecampboston, nela, nela-its, public, volunteer
February 1st, 2011 Brian Herzog
I don't know how I missed this before, but only recently Boopsie for libraries reached my radar screen - it's a company that will create a mobile version of a library's website and catalog.
There are other options* out there, but Boopsie seems like a great and easy alternative to creating your own mobile website. And even better, they also mobile-ize the catalog, which I couldn't do (although apparently non-catalog services are more popular with mobile patrons).
Pricing seemed reasonable (for what you get) - a library near me is in the process of signing up, and reported the cost is in the few-thousand dollar range (or, it would be roughly $10,000 for our whole 36-library consortium to sign up). Lots of libraries are already using them - Sarah has a good write-up on San Jose's experience, and WorldCat and ALA also use their app.
I'm not trying to pitch Boopise, so much as I'm pitching the importance of libraries having a way to serve mobile patrons - using vendors like this* are an option for libraries who can't do it themselves.
*Library Anywhere from LibraryThing
is another mobile website+catalog solution, and seems to be cheaper
Tags: app, apps, boopsie, catalog, devices, libraries, Library, mobile, phones, public, smartphone, website
December 16th, 2010 Brian Herzog
Remember a few months ago, when I was inspired by Steve Butzel's presentation at NELA2010 and created a mobile version of my library's website? I bet you have that date marked on your calendar.
Anyway, one lingering problem I had was some mechanism to automatically detect mobile devices when they visited our website, and reroute them to the mobile version instead of the full web version. I finally had some time this week and was able to accomplish that - aided by the fact that it was easier than I expected.
The ultimate goal is to redesign our entire site along the lines Brett suggested, by creating a stylesheet specifically for mobile devices. Brad pointed out that the Canton Public Library employs this, awesomely: visit their site and slowly make your browser window smaller, and watch the website flip from "full web" mode to "mobile" mode.
- Php is more fun, and I know our server runs php
The website offering the php method is http://detectmobilebrowsers.mobi, and very happily they make it available free for non-profits. Here's what I did:
- Read and reread their website
- Downloaded the main bit of code, and uploaded it to our web server
- Used their Function Generator to create the snippet of code to paste into the top of our homepage. I chose to treat all of their options as a mobile browser, and redirect them to http://www.chelmsfordlibrary.org/mobile - the resulting code looked like this:
(this should be two lines of code, but it wraps because of the width of my blog - if you use this code, make sure the second and third lines above are actually one long line)
- I copy/pasted that code into our index.html homepage. However, because this is php code, it had to go between php tags, (<?php and ?>), so the complete code I actually added to the top of our page was:
(again, see note above about line wrapping)
- Note that the path in the "require_once" line must match where on your web server you actually saved the mobile_device_detect.php file (downloaded in Step 2)
- Now, the last step was a little tricky, because it involves editing the .htaccess on the server. It's easy though, and one of their faq answers explains it.
Basically, .html files don't normally run php code - .php files do that. So if our homepage was index.php instead of index.html, I could have skipped this step. Instead, in order to make .html pages execute php, I had to add a few lines to our server's .htaccess file - which was no trouble at all - and then everything worked splendidly
That is, at least, so far. I've done some testing with mobile devices and (as suggested) with the User Agent Switcher Firefox add-on, and all of that has worked. But please, if you have a mobile device, visit our homepage (http://www.chelmsfordlibrary.org) and let me know if you don't get redirected to our mobile site.
A couple other notes:
- I also added a link to the mobile site in the upper-left corner of the homepage, in case the redirect doesn't work
- I only added this auto-detect to the homepage. I thought about adding it to every page, but our full site has a lot of information our mobile site doesn't - especially descriptions of our events. If I added the redirect to every single page, people with mobile devices basically wouldn't have access to any of that. So, my thinking is to provide mobile users with the (robust) basics, but if they want more than that they'll have to endure our not-great coding until we're able to redesign the entire site to be mobile-friendly
This was easier than I was expecting, which makes me think I missed something.
Update: someone pointed out a gap in my logic. On the mobile site, there is a link to "Visit our main site" which linked back to our full homepage. However, since the homepage redirected people to the mobile site, anyone clicking that link from the mobile site just got looped right back to the mobile site. So, I changed that link to go to our About page. Again, this is a good reason to just have mobile-friendly stylesheets like Brett and Brad suggest above.
Tags: auto-detect, cell, cell phone, code, coding, conference, detect, iphone, libraries, Library, mobile, phone, phones, PHP, public, redirect, smart, smart phone, smartphone, steve butzel, website
October 28th, 2010 Brian Herzog
You're probably sick of hearing about things I picked up at NELA2010, but I'm not done yet.
In the very last session of the conference, Steve Butzel from the Portsmouth (NH) Public Library demonstrated the Online Newsstand he created to boost their online magazine usage. That was neat in itself, but what I really took away from his talk was that I needed to - and easily could - create a version of our website specifically designed for mobile phones.
He showed theirs (in beta), which is simple and awesome. It inspired me to give it a try.
I started on http://chelmsfordlibrary.org/mobile/ yesterday, and am still working on it yet (in fact, I haven't even told anyone at my library yet that I'm doing it - surprise!).
I don't have a cell phone and so haven't tested this on a smartphone yet. I have been using testiphone.com (an online tool Steve highlighted - there are other tools, too), so please give it a try and let me know how it works.
Steve's point was that it could be very simple - hours, directions, events, a contact link, and a purchase suggestion link for patrons who are in a bookstore (great for people with apps like RedLaser). Here's the logic of what to include:
- Directions (right now it just links to Google Maps, but I need to also include a link for our branch library)
- Ask a Librarian (haven't created this yet, but it will be a simple email form)
- Purchase Suggestion (also not done, but will be a simple form)
- Upcoming Events (our calendar was not at all mobile-friendly, so I just grabbed the rss feed and ran it through feed2js.org to create just a list of our upcoming events. There could be separate feeds for adult events, childrens events, etc., but that might be overkill)
- Link to the catalog (I also embedded a catalog search, but that might be too much. And I found the catalog isn't entirely mobile-friendly either - we'll be moving to the Evergreen ILS soon, so I'll wait and see on this, otherwise I'd investigate LibAnywhere from LibraryThing, which Steve also mentioned)
- Link back to the main library website for everything else
The next trick will be getting our regular homepage to automatically detect mobile devices and reroute them to the mobile website. I haven't even attempted this yet, but have done a little research.
Apparently, cell phones and smartphones aren't just a fad after all, so having a website that works well on these devices is just as important as a browser-based website - and this will only become more important as a way to serve our patrons on their terms. I was happy with how easy it was. Now I need to find out what my coworkers think.
Tags: cell, cell phone, conference, iphone, libraries, Library, mobile, nela10, nela2010, new england library association, phone, phones, public, smart, smart phone, smartphone, steve butzel, website