Mobile Library Apps
Sheryl Bai, Benjamin Smith, Chris Tonjes, Bill McLendon, and Aaron Schmidt
This session started with a presentation about the use of Handheld devices at the UCHC School of Medicine. Sheryl Bai said that the School has been supporting mobile devices since 2001. Back them, PDAs were the newest tool. A lot of medical resources were only available in mobile formats, which helped to move the School to move toward mobile devices. There was also a grant that the school received to give PDAs to the residents (students) at the School. Then selected faculty members were given PDAs with per-loaded databases of information and named "Faculty Champions." Some faculty took to the technology right away but others did not. In 2003, the library started loaning PDAs to student volunteers through something they called the "Student Champion Program." They started having a PDA Clinic and PDA Tune-Ups where students and faculty can receive training and technical support for their devices. They also created a website dedicated to the PDA services that helped support the services.
Benjamin continued the sessioin by discussing the current PDA initiative of the program. The first step is to require that second year medical students use the PDAs. They then check with the faculty to find out what databases they want the students to use on the devices. They then test some of the handhelds with the various databases. They create instructions for how to do the simpler tasks and send letter to the students about the program. They then meet with the small group of students and help them learn how to use the PDAs and afterward act as a resource for the other students. They also hold a "handheld orientation" where they demo the databases for them. Some of the considerations they've had to consider have been which devices to use and which OS to use (Wiindows Mobile 2003 or Mobile 5). They have had to caution students that when they purchase their own handhelds or smartphones, that they are not just buying the device but an ongoing data plan. The screen resolution on smartphones is lower than on normal screens/PDAs.*** Sometimes that wreaks havoc with the data and makes it hard to read. Windows Mobile 5 vs. Windows Mobile 6 cause problems. On PDAs and smartphones there are different versions and therefore they work differently, much less the differences between the two versions. Some of the Pocket PC Utilities they use include dotPocket, DeepFreeze from Faronics, ActiveSync, Microsoft Remote Display Control, My Mobiler, and the Windows Mobile Device Center.
Next, Chris Tonjes spoke about the Washington D.C. Public Library's iPhone Application. The goals for their iPhone application included working toward horizontal integration of their ILS, providing an alternative delivery of the catalog, giving them the library's first foray into the mobile world, leveraging the power of the iTunes app store (which they believe is the delivery method of the future), and providing tangible, near-term ROI and extended library use and awareness. The iPhone release road map started months ago, but they plan to improve the user interface, add RSS feeds of library info, add more account features, and release that in the 2nd quarter of 2009. In the 4th quarter of 2009 they plan to provide "full" account features, links to library multimedia, and allow for direct downloads. In the 2nd quarter of 2010 the plan is to offer eCommerce using iTunes and offer even easier and more direct downloads. From 12/21/2008-3/1/2009, there have been 2199 downloads in 17 countries. About 100 programming hours went into the creation of the app. The code for their app is available for download at http://dclibrarylabs.org. Hurrah for sharing code!
Bill then talked about the SMS Text messaging from their catalog for My Account features (overdue and hold notices, etc.). This was desirable to cover smartphone users who don't use the iPhone. They also felt that in their community many people of different ages use SMS. The SMS message includes a link to their account so that right from their notice they can renew, etc. It is an opt-in service on the website registration page. They are also attempting to increase library event participation via same day notification to the SMS users. He did note that you do have to tailor the messages to SMS length and message size requirements. If you have a system that supports categorization of your patrons, you can have them receive targeted messages to their interests. For their ILS, Sirsi Dynix, there was no library cost to extend notices and announcements to going out via SMS instead of email. They schedule the messages to go out in the middle of the day so they are not disturbing users in off-hours and give them time to pick up items or come to an event. They send out an average of 100 SMS notices daily.
Aaron finished off the session by discussing his work on the look and feel of the iPhone app. Aaron sketched design options on paper before presenting the final recommended design to the library. He showed the different designs to regular people to get feedback before starting. He says the design is very simple, which it is. There is a .psd file that has all of the different elements of iPhones, so Aaron used Photoshop to mock-up the final design. The first page offers two options: searching the catalog or looking at hours and locations. Clicking on the phone number of a location will call the library and clicking on the address launches a map. In the catalog you can click on the library location, place a hold (which requires entry of your username and PIN, which can be saved). And just like on the regular catalog you can choose a pick-up location. Next, they want to make the design different. Aaron would like to use the barcode reader applications of iPhones (taking photos of a book's barcode, which would immediately place a hold on that item at your library).
Audience questions included #1: whether there were restrictions on who was allowed to download the app. The answer is no, everyone can use it. #2: Was it difficult to work through the iTunes app process? Yes, their first version was rejected, they needed to add an error message for the flight mode, and it cost $100 to join the iPhone app developers' group. #3: On the back-end, how does the SMS work? The OPAC works with email already, so they used email-to-SMS tools to provide access. (I'd like to learn more about how they did that in SirsiDynix…) #4: Clarifying question about the number of development hours. The 100 hours included the self-training and learning process. #5: What made them devide on an iPhone app and not a web app. The introduction of the iPhone app store was revolutionary, says Chris, so there was no question that it would be done via an iPhone app. #6: Did they have problems when contacting the local service providers about the application since it comes from one email address and others have had problems with then being blocked because they were considered to be spamming.
***Clarification from Benjamin Smith, emailed to me after this was posted: The clarification I’d like to make is that not all Smartphones have a lower screen resolution, in fact most have the same resolution with only a few having a lower resolution. We mainly point it out to students so that they are aware to look out for devices that may have a lower resolution. To extend that thought another issue with display is that a lot of Smartphones have a smaller screen size than regular PDAs which also contributes to making the information harder to read.
CIL2009
Recent Comments: