The list below has all the mobile library catalogs that I’m able to find now. The link for each library goes to the mobile version of the catalog, if it’s linkable — Some (e.g. NCSU) apparently don’t have a direct link, in which case the link is to a more general page that has a link. I’ve taken screenshots on my iPod Touch of the search, list of retrievals, and complete record screens, for all catalogs on the list, that I’ve put in a Flickr set (tag for each library linked on the list). Pictures for five representative samples are below the list (indicated by an asterisk*). The combined screen Flickr pictures for all libraries, in the same format as the samples below, are here. (Catalogs added after this article first published, as labelled, have No Flickr pictures, for now.)

Boulder [Flickr]
Brig Young [Flickr]
California St Univ [No Flickr]
Curtin U (AU) [No Flickr]
Duke Univ [Flickr]
Iowa City* [Flickr]
Jönköping U (SE) [No Flickr]
LINCCweb [Flickr]
Miami Univ [Flickr]
MS State [Flickr]
NCSU* [Flickr]
Orange Co [Flickr]
Oreg State [Flickr]
Oxford [Flickr]
Stark Co [Flickr]
Texas Chr U* [Flickr]
Tri-College* [Flickr]
U Amsterdam [No Flickr]
U Brit Col [Flickr]
U Gent (BE) [No Flickr]
U Minnesota [No Flickr]
U No Carol [Flickr]
U Rochester [Flickr]
U Virginia* [Flickr]
UCoL (NZ) [No Flickr]

The screenshots for each catalog are color coded — Red is the beginning search screen, yellow is the list of retrievals, and green is the complete record. The Flickr set has separate, larger screenshots for each screen, and the color is maintained in those to make it easier to pick out different screen types.

Iowa City Publ Lib [Flickr] is one of four AIRPAC mobile catalogs from Innovative Interfaces (Boulder, ICPL, Orange Co, & Stark Co tagged together in Flickr set), all of which have similar look & feel.

NCSU [Flickr] is one of the first mobile catalogs, and still an excellent design.

Texas Christian (TCU) [Flickr] is notable because it has only a list of brief records for retrievals, with no links to a more complete record for each one.

Tri-College [Flickr] is interesting because it has a brief “drop down” complete record, that opens while keeping the context of the list of other retrieved items.

I chose Univ Virginia [Flickr] because I like its pleasing, simple design.

If you know of other mobile catalogs, send them in, via comment or email.

Eric Rumsey is at: eric-rumseytemp AttSign uiowa dott edu and on Twitter @ericrumseytemp

The slide below (from a recent webinar on the NCSU mobile library site) does a great job of conveying what I’ve been saying recently about the importance of keeping mobile sites simple. It also brings to mind the bottom sketch from a recent post. Taken together, these two graphics give me hope that, with the advent of mobile tech, libraries are catching on to simple design. Traditionally, the design of library interfaces (especially OPACs) has tended to take the “everything but the kitchen sink” approach, with way more information than users attend to (as shown in the bottom sketch). With the restrictions of small screen mobile-devices, though, I suspect the appeal of simple design will become more apparent, as shown nicely in the NCSU mobile catalog search.

17c62

Sketch from: Why Apple & Google Win – And Libraries Don’t

whyapple3_601

Related articles:

Eric Rumsey is at: eric-rumseytemp AttSign uiowa dott edu and on Twitter @ericrumseytemp

The mobile version of MedlinePlus that was released by the National Library of Medicine last week is an elegant example of what I’ve been talking about in recents posts on libraries making their sites mobile-friendly. Mobile is a great opportunity for libraries because the overriding consideration in creating a mobile-friendly site is SIMPLE Design — Eliminate everything but the bare essentials of the information being communicated — I think NLM has done an excellent job of this with Mobile MedlinePlus. What I especially like is the efficient use of screen space, as shown in the screenshots below — In going from portrait to landscape view, the text and picture grow larger to fit the screen (and the transition between views is very smooth, which can only be appreciated using a real device). … Simple mobile-friendly design like this comes naturally, I think, to librarians. So what are we waiting for?

Malaria – Top with Picture

photo12773

Malaria – Text

photo3477

Fifth Disease – Top with Picture

photo5677

Fifth Disease – Text

photo7877

Piercing & Tattoos –  Top with Picture

photo910772

Eric Rumsey is at: eric-rumseytemp AttSign uiowa dott edu and on Twitter @ericrumseytemp

Last evening, one day after the tragic earthquake in Haiti, I searched on my iPod Touch for mobile-friendly picture galleries of the quake, using Google Web, G-News, G-Images, and G-Blogs. I found a few traditional news sources with picture galleries (e.g. BBC, CNN), but they were not optimized for mobile, and were difficult/impossible on an iTouch (CNN employs Flash, so it’s unusable). Global Toronto, the second example below, is typical of the appearance of the traditional news sites. The Big Picture, in the third example below, does do a good job with mobile-friendly pictures, but like the Hyderabad News that’s in the first example, the Big Picture is a unique hybrid of traditional news and new,shifted media.

I had been noticing recently how good a job WordPress blogs often do with pictures. They’re especially notable because they adjust very smoothly to portrait-landscape change, resizing the picture to use screen space efficiently. So it wasn’t too surprising to find WordPress sites in my Haiti quake search. The top example below is from the Hyderabad (India) News, which seems to be a news-blog hybrid (definitely not a traditional news source, which is what I’m referring to in the title of this article). It displays pictures with smooth elegance, in typical WordPress fashion. Another WordPress source I found is the environmental blog feww.wordpress.com, which has just a few pictures, which do look good on an iTouch.

Hyderabad (India) News

photo32B77

Global Toronto

photo67p77

The Big Picture from Boston.com

photo89p77

Eric Rumsey is at: eric-rumseytemp AttSign uiowa dott edu and on Twitter @ericrumseytemp

In Michelle Kraft‘s article yesterday, Stop the App Madness, she says librarians should resist the temptation to jump on the “App bandwagon.” We don’t have the resources to create apps for all mobile platforms, she says. Good point, especially in medical libraries, where iPhone, Blackberry, and Palm are all used. But note that Michelle is NOT saying that we should resist the trend to mobile. On the contrary — Here are her words:

The most effective way to reach ALL of your mobile users is to create a mobile friendly website.  If your website is mobile friendly then you don’t have to worry how many of your users have iPhones, Blackberrys, Androids, Pixis, or whatever the next trendy sparkly new device, THEY ALL CAN USE YOUR CONTENT if your website is mobile friendly. Creating a mobile friendly website is the biggest bang for your buck [boldface by me].  It doesn’t require as much programming knowledge as an app and you are able to target way more people more effectively rather than constantly creating different apps.

I’m getting the feeling I’m on a roll … Two days ago in my article One iPod Touch per Librarian (OITPL), I suggest that libraries need to become more involved in the world of mobile devices. Early yesterday, I found one article that I thought related closely to this idea, and wrote about it. And then a few hours later, I discovered Michelle’s Biggest Bang article that also resonates with my OITPL article. …

I think Michelle is right on target — The world is going mobile, and we need to learn how to serve it. As I say in the OITPL article, we should see this as a great opportunity to help the world to discover the best way to design information on a small device, and in the process, win over the next generation of potential library users. (Note that, although I suggest in the previous article that libraries consider providing each staff member with an iPod Touch, I’m open to considering other devices if/when they become as practical as the iTouch — The underlying point is that we need to get mobile devices.

Related articles:

Eric Rumsey is at: eric-rumseytemp AttSign uiowa dott edu and on Twitter @ericrumseytemp

Yesterday, Dan D’Agostino published The strange case of academic libraries and e-books nobody reads. He questions the investment by academic libraries in eBook packages from publishers that can be read only on computer screens. This is unwise, he says, because studies show that people much prefer to read eBooks on eReaders and smart mobile devices (especially iPhones). I’m including a sizable excerpt because it’s so well-written and because it’s close to the bottom of the lengthy article, and might be missed by many readers:

Just as studies were beginning to show that readers will not read extended pieces of text on computer screens and would use these e-book collections simply for searching, not reading, the Kindle and the iPhone arrived. These devices have shown that dedicated e-readers and smart phones are e-book platforms par excellence; they make e-books work. But unfortunately for academic libraries they don’t work with the huge e-book collections they’ve amassed in HTML and PDF (at least not very well). The result being that as the ownership of e-readers and mobiles begins to increase across campuses, the library’s e-book collection is in danger of becoming a very expensive white elephant, underused at best and perhaps already obsolete.

Dan’s article especially caught my attention because two days ago in my article One iPod Touch per Librarian (OITPL), I suggest that libraries would do well to become more involved in the exploding world of reading on mobile devices. I see Dan’s article as a good example of this — In order for us to put pressure on publishers to provide eBooks on mobile platforms, as Dan suggests, we need to be experienced in using those platforms. And the iPhone/iPod Touch is clearly the reader’s choice now.

Eric Rumsey is at: eric-rumseytemp AttSign uiowa dott edu and on Twitter @ericrumseytemp

In a discussion of how to label the just-finished decade, some people, most notably Mike Cane, have suggested that it be called “The iPod Decade.” Brian Chen echoes this sentiment, calling the iPod the Gadget of the Decade because it “opened the doors to the always-connected, always-online, all-in-one-device world that we live in today.”

Tim Spalding, on the other hand, says this: “Resolved: The Os were the ‘Lost Decade’ for library tech—libraries made incremental advances, while others flew past them.” Having gotten an iPod Touch (aka iTouch) myself recently, I get the strong sense that much of what Spalding is talking about is the explosion in mobile, especially iPhone/iTouch, use, especially by young people, in the last few years — which has made few inroads in the library world.

So what about the next decade in libraries? How can we catch up to Spalding’s world that’s flying past us? My suggestion is that we get on the mobile wagon as quickly as we can. And the most practical way to do that right now is the iPod Touch (most of the capabilities of an iPhone without the phone and its high monthly AT&T costs).

Mobile Friendly Design: A Great Opportunity for Libraries

The premium in designing information for mobile displays is Simplicity — Dotcom sites are feeling very pinched because small mobile device screens don’t leave much room for ads and Bells&Whistles —  Popular mobile news sites, for example, have mostly the text of news stories on their pages. Likewise, blogs that are well-optimized for mobile (WordPress Rocks!) have just the essential text and accompanying pictures.

A simple, streamlined screen-environment fits us in libraries very well — We don’t have to worry about squeezing ads on our pages, and we’ve never tried to compete with dotcom Bells&Whistles. So mobile seems like a natural for us.

So why haven’t more libraries adopted mobile tools? There certainly are libraries that have developed mobile interfaces for some of their services. But a big barrier to more general of embracing of mobile in libraries is that the information that we have in the “library silo” — most notably the online catalog — is generally not in mobile format (**see below). I suspect that many users, when they see that our “mobile sites” don’t include the catalog, are going to lose interest quickly.

The cost of an iTouch is in the $150-$200 range, making it practical for most libraries to consider providing each staff member with one. The real investment, I think, is going to be learning how to integrate library services with them. It’s going to take an adventurous, visionary administration to accomodate staff time to “play around on the new toy” to learn how to use it.

In many ways, I’m finding the mobile interface on the iTouch to be “uncharted waters.” The standards for what makes a good mobile site are yet-to-be-written — Bloggers, journalists, publishers, web developers — are all hard at work looking for the best approach, competing for the users’ attention. Whoever gets it first will be the winner in the next decade — Hopefully libraries will do better than in the last one.

I’d be remiss if I didn’t mention the inspiration for the cute title of this article —  One Laptop per Child (OLPC) of course — And just in case anybody’s paying attention, I’ll the first to apply the new acronym — OITPL 😉

**Library Catalogs in mobile format – The only ones I’ve been able to find that have what I would call a truly optimized interface, to make them readable on an iTouch, are North Carolina State Univ, Iowa City Public Library, and Univ North Carolina — Please tell me if you know of others!

Related articles:

Eric Rumsey is at: eric-rumseytemp AttSign uiowa dott edu and on Twitter @ericrumseytemp

Since the announcement by Apple last week of new iPhone OS software that will become available in June, publishers Adam Hodgkin and Mike Shatzkin have been having an interesting dialog about the future of the eBook market, and how iPhone 3.0 will affect the competition between Amazon, Apple, and Google. Most of my posting here will be a presentation of the views of Hodgkin and Shatzkin on the eBook market, but I think an article by Ben Parr, at mashable.com, on more general effects of iPhone 3.0, does a good job of setting the stage for the discussion of eBooks. In his discussion of the new ability to purchase items within an application, Parr seems to be talking about the same thing that Hodgkin sees as being so revolutionary about the new iPhone OS (Correct me if I’m wrong on this, Adam). So, first — an excerpt from Parr’s posting:

The new iPhone 3.0 software includes the ability to copy-and-paste, a landscape keyboard, and push notifications. However, none of these updates are as revolutionary as the new features Apple offers to iPhone application developers. The one to watch [especially] is the ability to purchase items within an application. This is a feature that matters because of the vast opportunities that it presents to both developers and users. … If the iPhone application store revolutionized the mobile as a platform, then the iPhone 3.0 OS may very well be the spark that revolutionizes the mobile as its own economy. [boldface here & below added]

With the new iPhone OS, Hodgkin thinks that Apple has put themselves into a leading position in their competition with Amazon and Google for the eBook market:

The announcement earlier this week about Apple’s iPhone OS 3.0 made it at last pretty clear how Apple is going to become a player and the strategy is so simple and solid that I am surprised that more of us did not see it coming. Apple has taken the very sensible position that it doesn’t need to be a big player in the digital books or the ebooks market to win the game hands down. Apple is going to let authors, publishers and developers get on with their business and work out how the digital books market is going to work and Apple is just going to collect the market-maker’s fee for letting it happen, on and in the iPhone arena. … The position that Apple have announced for themselves is stylish, decisive and agnostic. Apple doesn’t mind whether books are based in the cloud as web resources, or shipped around the internet as book-specific file formats. Web-based books, digital editions and ebook file formats can all run easily on the iPhone if that is what is needed: “Open house, come over here and play”. That is the message from Cupertino.

Shatzkin, however, thinks that Hodgkin has jumped too quickly for Apple, and he says that the competition is still wide open:

Hodgkin sees brilliance in Apple’s move not to enter the proprietary ebook wars, but simply to be a facilitator of sales to iPhone users … [But his article] took no note of Sony, Stanza, or the potential impact of broadly-distributed epub files. … It also took no note of Barnes & Noble’s recent purchase of Fictionwise or the fact that Waterstone’s has teamed with Sony Reader for distribution in the UK. … I think, most of all, this analysis omits full consideration of the discrete functions served by the retailer in the supply chain. … Apple is not providing the full suite of retail services. … It isn’t just too early to predict a winner; it is too early to declare the finalists.

Hodgkin posts a reply on his blog to Shatzkin:

Shatzkin has not understood what Apple are doing with the strategy announced for the iPhone 3.0 SDK. They are tackling the retail environment head on and building the retail functions. Shatzkin thinks that Apple will fail the retail test. Did Mike view the video presentation with which Apple gave a preview of 3.0 SDK? Consider that the very first item that Scott Forstall discusses (before even ‘cut and paste’!) is the way that they have enhanced the App Store. Note that its a store. A place where consumers shop. It is a retail store which enables developer creativity and it will support discovery of books, magazines, games etc, browsing and sampling, search, metadata, price choice and traditional bookstore price anarchy, and after sales support (though some fulfillment and much support will fall to developers and publishers). Most striking is the near total freedom that publishers are given on pricing (99c — $999). … It is surprising that anyone would think that Apple who have made such a considerable success of Apple stores and online retail selling will find themselves out of their depth with digital books. Nobody would say that building a retail system for digital books is going to be easy, but Apple clearly are a good candidate to do it. Especially now that they have announced this co-optive strategy.

When a link is clicked to a specific page in GBS Mobile, the page that always opens is the entry page for the book. There doesn’t seem to be a way to link successfully to specific pages. I’ve tried this in several examples, and have had the same experience in all of them. An example below illustrates.

In this example, I’m trying to link to a group of pages starting with page 31. But when the link below is clicked, it goes to the entry page, which is page 21, with the same URL as below except that the page number is 21 instead of 31.

http://books.google.com/googlebooks/mobile/#Read?id=yb8UAAAAYAAJ&page_num=31
[This link and the link in the image below are the same]

After this link is clicked, and it goes to page 21, then it does work to change the number from 21 to 31, and it goes to page 31. The right > next to “Pages 21-30” also works.

When the link is clicked to go to page 31, and ends up on page 21, clicking the Back button goes to page 31. And the address bar initially initially reads 31, but then changes to 21 – So when the link is initially clicked, it does “pass through” page 31, but apparently there’s some signal on page 31 that tells it to redirect to page 21.

Does anyone see what’s happening here? Any help would be much appreciated! Please post suggestions in comments, or in Twitter.

.

.

.

.

.