Four Corners of the Sky: Through Chapter 4

Here it is, my first Big Library Reading diary post.

The first two pages of a novel are always hard for me. Sometimes I have to read every sentence twice. I don't know what the book is about. I have trouble keeping all the names straight. I react to images and get distracted from the book because my mind hasn't entered the book's full world yet. Four Corners of the Sky was no exception. Maybe I was supposed to read the blurbs and the reviews first.

So, through the Prologue and four chapters, Malone has laid his puzzle pieces out on the table, and he's succeeded in getting me interested in how they're going to be put together. At this point , the names seem kind of hokey. Annie Peregrine Goode, really? Emerald? D. K. Destin? But you have to grant the author some leeway to start; he'd better layer some meaning onto that primer coat by the end of the book. Some of the pieces are like the four corners of the puzzle, easy to spot by an experienced puzzle solver. The "four corners" image, for example. It's even on the first page of the prologue. Again, it strikes me as a bit unsubtle, but OK. I rather like being on the lookout for quartets. "Jack? Jack! Jack! Jack!"

Another corner piece is the "King of the Sky" - "Queen of the Sea" couplet. Should be interesting to see how Malone connects the modernish magic of the airplane with the exotic magic of an Incan totem. This is totally stream-of-consciousness, but I just saw Star Trek Into Darkness last night and something about this reminded me of the Kirk-Spock-Khan timeline reshuffling. But what's with the pink baseball cap?

I like reading about speed-obsessed impatient Annie, though I'm kind of groaning at the daddy issues. One thing really bothered me. She's driving her Porsche Carrera at 95 MPH over country roads while talking on her cell phone with probably-going-to-be-love-interest Vice Sgt. Dan Hart. (give-away name/title!). Doesn't she know how DANGEROUS that is????

Please no spoilers in the comments, ok?

Big Library Read Diary: Four Corners of the Sky

Although the first Big Library Read (BLR) started on May 15th, it wasn't until yesterday that I got Four Corners of the Sky onto my iPad. Four Corners is the book that Overdrive is making available for free in librararies around the world- at last count 7500 of them! My local library Montclair Public, is part of a regional consortium, BCCLS, that decided not to participate in the Big Library Read in its first incarnation. There wasn't enough advance notice for BCCLS  to participate in such an initiative and do it well.  "BCCLS doesn't enter into such endeavors half-heartedly and felt that a two week window wouldn't allow us the time and effort a project like this deserves" BCCLS Library Services Director Arlene Sahraie told me. I hear similar things from other libraries.

The rapid roll-out of Big Library Read shows up in other areas. I haven't seen a single mention of the program in the mainstream media; it's an initiative with historic implications, in my view. On the other hand, when the program's impact is studied, there won't be the confounding effect of non-library promotion.

On GoodReads, you can see the sudden, but modest effect of the program:

 We'll soon see if that's a one-time bump or the short end of a hockey stick.

I looked into other libraries where I would be entitled to library privileges. In New York City, where I have business, NYPL isn't participating, which might account for the lack of MSM interest. I applied for a card from Queens Public Library, one of the most innovative public libraries anywhere, which is participating in BLR, but I would have to show up in person to get the card approved. So I went to another New Jersey library which approved me for a card. They're a member of a different consortium, eLibraryNJ, that's participating, so I'm finally set to start reading. 

I'm interested to see if online conversations develop differently if an ebook is available to large numbers of people. So I've going to keep an online reading diary on this blog. There are 55 chapters of 4 corners, and I have a 2 week checkout period to work my way through it, so that's 4 chapters a day. We'll see how I do. It's good that I have the full 2 weeks even thought the program ends next Saturday. With BEA and IDPF on my plate, I won't have that much time.

I'm also going to collect here all the online conversations centered around this BLR that I can find, especially blog posts. So far, I haven't seen anything develop. So feel free add yours via the comments!

• My Diary
• Through Chapter 4
• Blogs
• nothing yet
• Twitter: 
• #biglibraryread 
• @michaelmalone10
• Facebook: 
• Chat with Michael Malone
• Michael Malone Page
• Goodreads
• Four Corners of the Sky
• Anne Arundel County Public Library discussion
• Huntsville-Madison County Public Library discussion
• The Four Corners of the Sky Book Discussion (AACPL, Maryland)
• Lower Macungie Library discussion
• LibraryThing
• Reviews

No-Return eBook Lending

CC BY-NC by RoadSidePictures

When I was a kid, glass bottles were sold with deposits- a few pennies each. As a six year old I would help my dad collect our bottles and put them in the huge trunk of our car. I got to keep the change that the grocery store gave us in return for the "borrowed" bottles. This racket was foiled by new technology: the bottle companies figured out how to make bottles so cheap that returning them didn't make sense any more.

Library books, in a funny way, are like deposit soda bottles. We borrow the bound paper objects and consume the stories and knowledge they contain at home. Then we return the book to the library so someone else can drink deeply at the same fountain. The technology is changing, and the books have become ebooks.

So why do these library ebooks, which cost nothing to duplicate, need to be "returned"? It's only the license that gets returned; the bits themselves just get deactivated (via some form of digital rights management, DRM). The reason for the return is market segmentation. Publishers want to make their books available in libraries, but not in such a way that the library book substitutes for a consumer book purchase.

How does this market segmentation come about? You buy print books instead of borrowing them from a library for two reasons:

1. buying the book is more convenient.
2. if you buy the book, you get to keep it.

Whether you get the book from the library or buy it from a bookstore, you get to read the same book.

Library ebooks have so far tried to create both of these distinguishing factors. If someone else has an ebook on loan, you can't read it. Just try borrowing a popular ebook from your public library. Chances are you'll have to wait in a long queue before it's your turn. There are also usability barriers caused by the library's DRM that add "friction" to the lending process. When the lending period expires, the ebook vanishes from your ebook reader. That's more convenient than with print, because you don't have to go back to the library to return the book.

If you think a bit more deeply about the ebook, you'll realize that purchased-book attribute #1, ease of acquisition, is a completely separate thing from attribute #2, getting to keep it.

Imagine two new types of library books: one that's super-easy to acquire, but it vanishes after two weeks. With a second type, you have to wait your turn to get the ebook, but you get to keep it.

What? Impossible, you say?

Au contraire!

This past week, we witnessed the world's first example of an easy-to-get-but-vanishing library ebook. It's titled The Four Corners of the Sky and it's the ebook being offered in over 4,500 public libraries around the world through Overdrive, the dominant vendor of ebooks for public libraries. On June 1, or thereabouts, all these magic copies will vanish.

The other type, the one-user-at-a-time-but-you-get-to-keep-it library ebook, has actually been around for a while, in a very below-the-radar way. I think it's time to turn on the klieg lights. Because unlike the vanishing ebook, the get-to-keep-it ebook doesn't depend on DRM for its reality.

Publishers such as Carina Press have been allowing Overdrive to sell their ebooks to libraries without DRM. When lent, these books don't get returned, and the DRM doesn't vanish them, but the library doesn't lend the book to another patron until the end of the lending period. So the borrower doesn't have to return the ebook, except on the honor system.

When a library licenses a Carina Press title, what they get is a lending-rate-limited ebook, rather than a one-user-at-a-time book. It's my hypothesis that lending-rate-limits are responsible for the vast majority of library-ebook market segmentation today, and that the return requirement is relatively inconsequential. If that's true, we can eliminate DRM for library ebooks.

In Italy, a company called Medialibrary has done exactly that. They work with about 40 Italian publishers and a network of 2,500 libraries. Libraries pay the standard market price of the ebook to get an "archival copy" (for ever). Then they pay a fee for each lending. The ebook downloaded by patrons has a digital watermark identifying the user and the library. There's a limit of 60 downloads per copy, after which the library has to buy a new copy.

And I'm not saying there's never value in "keeping" an ebook. A cookbook, for example, is not something you're done with after a week. Libraries aren't about these books, for the most part. So the conclusion still holds: libraries can eliminate usage restricting software from most of the ebooks they lend.

The end of deposit bottles changed the workflow of households, retailers and the beverage industry, and created other changes, good and bad, that required a lengthy period of adjustment. Today, thanks to a more efficient and convenient delivery system, we spend more money on bottled liquids than ever.

I think it’s worth working on better ways to distribute the stuff inside books as efficiently as possible. And I think libraries can help make it happen. With no-return ebooks lending.

What do you think?

Publishing Hackathon Pretty Much Ignores eBooks

The "First Annual" Publishing Hackathon was this weekend. As advertised, I participated and worked on an EPUB backmatter project. My awesome team consisted of me, Javascript/Ruby developer Max Jacobson (who's going to be even more highly sought-after when he finishes Rails school this summer), and TLC librarian Dianne Coan.

Here's our demo video:

 

Here's how we described the project:

Book Discovery INSIDE the eBook

When is a reader most receptive to reading suggestions? Right when they’ve finished a book of course! That’s why printed books have information about other books by the same author, the first chapter of the next book in the series and similar material at the end as part of the back matter.

Back matter has existed pretty much as long as books have. This includes the appendix, glossary, index, and bibliography. Back matter for digital books needs to be optimized to serve the needs of the digital reader. An informal survey by @suw indicates the most popular endmatter desires were other books by the same author and some information about the author.

Digital back matter for ebooks is not constrained by having to proceed the publication; unlike print, digital back matter can be kept up to date with the release of new content. For instance, if an author publishes a sequel, that title could be included in previously published ebooks.

It’s easy to insert a page listing an author’s other books at the end of an ebook, but how do you keep that list up-to-date? What if you’ve developed a great recommendation system to do “if you liked Pride and Prejudice, you’ll like X”? (or maybe “if you hated...”!)

The answer is to make use of the javascript capability of emerging ebook environments. Our project explores means of connecting to APIs from within an EPUB for the purpose of suggesting the user’s next read.

An existence proof is the “widget” capability of the iBooks iAuthor platform. It allows the insertion of html snippets into extended EPUB. Unfortunately, the javascript capability of ebook reading platforms, like the future, is unevenly distributed.

For this demo, we tested three reading EPUB environments, Readium, Readmill, and iBooks. We modified the Project Gutenberg EPUB version of Pride and Prejudice to include hooks and data to other books by Jane Austen.

Readium, which has been built as an EPUB3 reference environment, is the most capable for our purposes. It supports both javascript and connections to external web resources. In Readium, our EPUB displays the set of books by Jane Austen returned by the ReadMill API.

Apple iBooks has full javascript capability, but doesn’t allow connections to external resources (except perhaps via iBooks Author hooks- this deserves further investigation.) In iBooks, our EPUB displays a result page that we generated and embedded based on Jane Austen works published in 1813, when Pride and Prejudice released. We imagine that such embedded resources could be inserted at download time in a future production bookstore or library environment.

The Readmill environment does not support javascript at all at this time, so ironically, we’re not able to display the Readmill API results, or the iframe embedded resource.

Offline reading in Readium displays the resource embedded in the EPUB, similar to the iBooks version.

There were 30 projects in total presented at the end. Here's the list, along with my one sentence summary.

Banned Books in America

Website that maps book banning incidents and links them to Openlibrary

Book Discoverability: A Graphical Solution

Concept for browsing books as nodes on a graph.

Book Discovery INSIDE the eBook

This was us! Our demo crashed and burned. The popup screens from the wifi messed up the ebook reader display of embedded dynamic content.

BookCity Finalist!

Website that recommends books by connecting them to cities.

BookieGoer

Website that helps you lend the books you've borrowed from the library.

Booklvrs: Read. Discover. Meet.

App that advertises the ebook you're reading to the people around you.

bookmatchup

Website that multi-factor-matches you to books.

BookMob

Website that aggregates book recommendations from your twitter followers.

bookshelf.me

Website that displays books as if they were on a bookshelf. I'm pretty sure there was more to it.

Publy.io

Website that recommends books to users based on books they've liked.

Captiv Finalist!

App and Website that uses machine learning algorithms and your tweet about last night's party to combat the short attention span of Today's Readers. I may not have understood this one.

Coverlist Finalist!

Website that believes in judging books by their cover.

Evoke Finalist and clear judging favorite!

Pinteresty website that recommends books based on emotions categorization.

Happy Chapter

App that recommends books based on tags you click.

I read your Brain

Brain-sensing rabbit ears that wiggle depending on your response to a book from a website.

IGNITE

Website that lets users rate romance novels for steaminess.

KooBrowser Finalist!

Browser plugin that analyses what you read to better sell you books.

Library Atlas Finalist!

Mobile app that sends you geographically appropriate quotes depending on where you are. My favorite.

Literary Trinket with Book Wish

3D printed QR-ish code baubles. Cooler than it sounds.

Meadows

Website that turns reading into a game where you earn points.

Meme a book

Website that turns books into lolcats. (I may not have described this accurately.)

MovieReader

Website that recommends books connected to the movie you just saw.

NYPL Reinvent

Analysis of NYPL metadata advocating a divorce of the library from its classification system.

OkLetsRead!

Website offering crowd-funded serial fiction (ebooks).

Quiply

Website that recommends books based on a user's video viewing.

Reading Tollbooth: A Gateway to Book Discovery

Website to match kids to books.

Something2Read

Website that recommends books based on tags you click.

Valerie's Baby App

App that promotes literacy to a girl named Valerie by making sliding block puzzles and defining words at her.

Visibrary

Website that uses library data to make graphical book circles.

Vookstore

Website that turns ex-bookstore owners into book curation engines.

Interestingly, only 3 of the 30 projects addressed ebooks at all, which seems a bit odd to me, considering the industry's ongoing transition from print to digital. The emphasis on apps (7) and websites (21) is partly due to Hackathon's theme of book discovery, but it also says something about the tech industry. Apps and websites are what the NY tech industry is doing in 2013, not ebooks. Clearly, the publishing community developing ebooks and ebook standards needs to do more outreach to developers; the hackathon was a good first step.

It's also worth noting the growing importance of geo-tagging and other non-traditional metadata. In the new world of publishing discovery, readers want books that fit their mode right where they want to be. Neither MARC nor ONIX know enough to help.

My library friends should rest assured that the hackers did not at all ignore libraries. Although $1000 prize from NYPL was a factor, the ease of connecting to NYPL and OpenLibrary helped a lot. The RDA prize, it should be noted, went unclaimed.

Update: Sorry, Coverlist, I omitted your finalist status. Corrected!

Hack the Publishing Hackathon

Why a publishing hackathon?

Book discovery needs innovation. It’s never been easier to get a book into a reader’s hands—just one click. But, with over 10,000 books published each year on every topic imaginable, how do people find out about them? There are fewer bookstores to help readers discover exciting new authors and ideas. There’s currently no digital experience that replicates the serendipity of browsing bookshelves. Recommendation engines are fairly primitive – they know what you bought, but they don’t know why. It’s a disruptive opportunity that hasn’t been explored.

Seriously, the sponsors of this event don't think book discovery has been explored? I guess they were too busy suing Mr. Google to notice that Google Books is a pretty good discovery tool. I suppose they never thought to ask Mr. Wikipedia how many books are published every year.

All in all, I find the description of this hackathon INSULTING to just about every developer that's worked in the general vicinity of the book industry.

Umm. Mr. Steinberger. If you and Perseus really want to promote discovery innovation, then perhaps you have heard of Goodreads? They're driving some decent discovery of books. Maybe it doesn't count if Mr. Amazon is buying them. Perhaps you've heard of Amazon? They popularized the "If you liked this, maybe you'll like..." feature that everyone in the publishing industry tries to copy. If you don't like Goodreads, maybe I can introduce you to LibraryThing, which has been driving valuable book discovery in more ways than I can list here. I know that "library" in their name is a big turnoff for your big 6 colleagues, but libraries are huge book discovery machines. I don't suppose you want them to disrupt anything. And umm DP.LA????

People mostly discover books by word of mouth. Some  innovators promoting social reading include Readmill (who had their own publishing hackathon) and (giving props to the NYC home team) ReadSocial and the stuff Bob Stein has been exploring. And Kobo, Copia and Zola are doing some amazing things to integrate book discovery with ebook selling and reading environments. I've written previously about Jellybooks' fresh approach to discovery.

And some more on libraries. When I was at OCLC, we worked on real simple problems like "how do you discover the other editions of the same book?" and we found that publishers had NO CLUE what they'd published 5 years previous. So yeah, we did our bit.

But I'm coming to the hackathon anyway. because despite the ridiculous framing, this event has some clueful backers. NYPL for one. Small Demons for two. And they're even wasting prize money on a new age library metadata thingy. (I might be wrong about the wasting part.)

I'm hoping that some people will be interested in rethinking ebook front matter. Unglue.it needs books to work better all by themselves. The best discovery instrument for a book is the GDMF book, to my mind. So let the book do some work. With a little javascript. And no more DRM, thank you very much!