49th Teachers launches with hundreds of classroom resources to help discover Canadian kids' books

In developing a website platform for book publishers, we wanted to provide fully featured page layouts that publishers can customize. We've built many custom publisher websites, but with ReaderBound it is important to offer ready-to-use widgets as building blocks for editors to organize into their own layouts. By achieving this balance, ReaderBound is a flexible but powerful platform.

ReaderBound is a powerful website platform that helps publishers easily showcase and sell their books online.

It combines sophisticated content management and e-commerce solutions, client support, website hosting, and maintenance into one convenient package.

We often explain the ReaderBound benefits in terms of what it enables you to do. However, one of its key benefits is what it takes off your plate: a number of site maintenance worries.

As the plot thickens on book sales trends (with paper books now making a solid comeback and ebook sales on the decline), one thing that hasn’t changed is readers’ thirst for content.

In the world of books, book publishing and bookselling, the metadata exchange format “ONIX” is the preeminent method of communicating information about a book. In spite of the fact that ONIX is a rather flawed standard and protocol for exchanging bibliographic information, it is the standard which everyone has settled on. Mugo has been working with ONIX since 2003, first building a freely available ONIX management system as a proof of concept for the Centre for Canadian Studies in Publishing at Simon Fraser University and most recently building a turn-key system for an ONIX website - that is - an ONIX powered website.

The problem:

One of our favourite projects, The 49th Shelf, aggregates a lot of data from a diversity of sources. Naturally, there is a range of quality; but even more than that: different sources often refer to the same physical object in different ways. Specifically, a person who writes several books can be referred to in a variety of ways:

• John Reynolds
• John L. Reynolds
• John Lawrence Reynolds

There are some heuristics to resolve most of these cases, but there are always seem to be some that defy the code and require a manual fix.

This process has to be performed on the production site, so we want to minimize the amount of time that the data is inconsistent and we don't want to run untested code.

Recently, we built a map interface for The 49th Shelf's Read Local: The 100-Mile Book Diet website project using the Google Maps API. The website is an online book community focused on Canadian books. Users can visit the map section to find Canadian books by geographic location, and they can also pin books on the map, selecting locations that are meaningful to the books in some way. 

Allowing anybody to participate in the evolution of the Read Local map means that we have to pay particular attention to the "Add a Book" user experience. If the user experience is intuitive and pleasant, people will be much more willing (and able) to pin a book and help make the map more useful and fun. On the other hand, a confusing interface can hamper the accuracy of the pin data (in the case where books are pinned in the wrong location) and turn people off from participating.

Here's a look at two main considerations regarding user interface design and optimization in the "Add a Book" workflow.