100 things

Terese Bird

Terese Bird portrait

As with all good people you discover online, I came across Terese Bird by way of her high quality work around all things digital media. Terese kindly offered to be interviewed about her typical day and interest in digital books. Thank you Terese for taking the time to answer my questions and being my first interview subject!

Tell us about yourself

I am a learning technologist with the Institute of Learning Innovation at the University of Leicester. We primarily do research into learning and learning innovation, disseminate findings, and construct practical teaching and learning models which apply the findings, for our own university and beyond. I assist with the research in ways such as figuring out how to implement new or tricky technological trials or solutions, setting up and analysing data from online surveys, and conducting focus groups and interviews. I present findings in workshops and conference presentations, and write about project findings whenever I can — through blogging, project reports, and other writing projects.

What’s a typical day like for you?

I don’t think I have a typical day. This morning I had to buy milk, coffee and tea on my way in to work, in preparation for day 1 of a two-day workshop on Learning Design – the 7Cs of learning design, which is a framework developed by our director, Professor Grainne Conole. Once at work and seeing to the refreshments, room, and technology, I greeted guests — 12 medical educators from one of our local hospitals, plus a few visiting scholars at ILI — and got everyone settled into the session. While Grainne taught her sessions, I helped discussions, took photos and tweeted about the session on our Twitter account @learninginn. I spent lunchtime setting up laptops and testing microphone and playback facilities on the demonstrator computer, in readiness for the session I later taught on Rich Media Learning Materials — the strengths and weaknesses of and tips to create text, audio, and video learning materials especially usable on any mobile device. Once the workshop ended at 4pm, I spent the rest of the workday, and much of my evening, setting up meetings and replying to emails.

How did you get interested in digital publishing?

I got interested in digital publishing in 2009 because it was a focus of research in the JISC-funded DUCKLING project our team worked on. My job was to figure out how to load locally-authored learning materials onto Sony e-readers (the first e-reader available in the UK), to be shipped to distance masters students around the world. I stumbled upon the software Calibre and just fiddled with it until I had a method of nicely converting Word documents into first lrf, then epub. This was pretty ground-breaking stuff in 2009, and it helped me to win the ALT Highly Commended Learning Technologist of the Year 2010.  (Sorry for the plug but I’m kinda proud of that.)

What are your go-to tools or software for writing?

My go-to tool for my own writing is either directly into WordPress, or Microsoft Word. Hey, it works. My go-tool for an ebook is iBooks Author. It’s free and it offers good-looking templates, because I cannot design my way out of a paper bag. It saves as a pdf and as .ibooks, which might be all I need. If I need epub, then I copy and paste the text and images into Pages and export as epub. If I had a copy of Indesign I would probably just use that to do everything, but Indesign isn’t cheap and it doesn’t strike me as simple to use, so for now I’ll stick with easy and cheap (iBooks Author and Pages).

Where would you like to see digital publishing going?

I would like to see digital publishing offer financial rewards primarily to the author, and to the publisher as long as s/he offers added value. I would like good textbooks to be available in rich, innovative formats at low prices for students. I would like to see teachers and academics being empowered through academic publishing, and I would not like to see publishers trying to take over teachers’ roles as is beginning to happen now.

As for the technology of digital publishing, I don’t really think it’s necessary for there to be one uniform way for all mobile devices to be able to read an ebook. I don’t mind there being an Apple and an Amazon and a Samsung and a Google. Companies need to earn money because people need to earn money.

If the Napster model had prevailed over iTunes, musicians would be earning less money these days. I wish publishers could find a way to really add value, to support authors and allow digital innovation all at the same time.

In a few years we’ll probably have people crashing into each other on the pavement because they’ll be wearing Google Glass and trying to read ebooks and walk down the street at the same time. Or even worse – trying to read ebooks and drive at the same time! You read it here first!

04 Publishing jargon

On my ebook publishing journey I have begun to stumble across processes, stages and phrases that use traditional print terminology. I will note them here for my own sanity and maybe that of others as I figure where it makes sense we should use existing and established phrases.

  • Galley proof – used to describe review copies of a print book
  • Uncorrected proof – commonly used in place of ‘galley proof’ for digital books
  • Name of punctuation and general typography – a list down the right of key technical terms…. a tilde is not a squiggle!

03 Under the cover of the MRC ebook

Collection of mobile devices with the mrc ebook
Photo Credit: Nigel Goldsmith

Last week the Medical Research Council released it’s new annual report in various digital formats. Tribehut (that’s me yeeeah) planned, designed and built the ebook versions.

I have been banging on about making ebooks for some time and this caught the attention of Matt Jukes. Ever the ‘digital’ experimentalist, Matt asked if I would be interested in making the digital versions of their annual report ‘Advancing Medicine, changing lives’. I jumped at the opportunity.

With budgets being squeezed and a general ban on many print outputs, the public sector has been forced to turn to ‘digital’ outputs. For those of us who love ‘digital’ now is the time to stand up and to demonstrate that digital might actually be good.

I felt this project could act as a perfect demonstration of just how good digital can be and I wasn’t planning on dropping the ball.

Planning and design

One of the key aspects of a ensuring a successful project workflow is to get one defining voice on the client side, in this case Matt, and to get the content at the very beginning of the project. Assumptions about content will not only waste time but lead you down the wrong path as you simply cannot make judgements without seeing all the pieces.  Thankfully the team at the MRC had already produced the PDF version so this wasn’t an issue. I was sent the PDF along with a short brief which gave me enough to assess the project requirements and commit to the project. Note – ensure that the ‘final’ content is really that, I have been burnt before with being sent an old ‘final’ version which stops a project dead.

The original beautiful design was created with ‘print’ very firmly in mind. From the PDF (I call this the blueprint), I discussed with Matt the sticking points in regard to any potential limitations, constraints and show-stoppers in relation to the technologies we’d be employing. Those decisions not only helped to manage expectations but also enabled me to make appropriate design choices.

For example, most ereaders and reading apps tend to over-ride many of the designers choices, such as font choice. So my suggestion was to leave the font choice to the reader and/or device. Also, the PDF version has some graphical flourishes in the margins which visually link articles across a page spread, but this is lost in the ebook – the viewport (what you can see at any given time) is not fixed as it is with print. For better or worse, an ebook is primary about text and so we agreed to keep the pretty graphics for chapter starts and within sub-sections where they are context specific.

Regarding what devices we needed to target, we had no previous data, so I couldn’t be sure what devices the audience had. Thus the ebook needed to work across as many devices, apps and configurations as is reasonably possible. Furthermore, being an annual report it required a minimum 1 year shelf life. Rather than making an assumption that everybody would be using either the Apple iPad or an Amazon Kindle I planned to make it work very well across the board. This means building a well constructed epub and Kindle mobi file with a sprinkling of technical features that are unique to the iPad or Kindle. Luckily ereaders ignore what they don’t support so there wasn’t too much to worry about regarding this.

I am a fan of rapidly building something as soon as possible, test it and then refine.
At this point both sides were ready and excited to move to the code phase.

Coding

Until Matt and the team could ‘see and use’ the ebook it would be difficult to complete the project so I pre-warned them that the previews were just that (we ended up with 25 iterations with 13 being the first MRC saw).

At this point I requested all of the PDF assets, which included all source imagery and colour palettes for the build.

I needed a final EPUB2 file and an accompanying Kindle mobi file. I chose to stick with EPUB2 over the newer EPUB3 as it isn’t widely supported yet and also I didn’t have any use for the specific EPUB3 features. No reason to reduce compatibility for the sake of being an early adopter – showing off experimental features was too high risk in this scenario.

For this build I used an HTML editor called Coda (but you could use anything as long as it has find+replace with REGex support as a bonus).

I took all of the text from the PDF and dumped each section of content into a plain html panel within Coda.  I then re-built all of the sections, adding tags etc until I was happy that I had all of my content with placeholders for the images. Some of this can be automated to reduce heavy coding BUT be aware that automation may disappear your content…so I just used a few regex commands to mass add things like paragraph tags.

Next I built a global template epub page with 1 sentence of text and ensured that the template worked.

From the working template I added each section and then added the other required files for an epub such as the mimetype, xml and content.opf which includes links to all the assets used and metadata.

An epub file has a strict bunch of required files so pay attention at this point of the build.

The kindle file is built using the Amazon conversion tool “KindleGen” from the EPUB file. It has a few of its own quirks so I made sure I had read the documentation.

At this point I had Baldur Bjarnason kindly look over my files to sanity check my decisions. He found and squashed a few bugs so was well worth an extra pair of eyes.

Testing and refining

At this point I would like to stress the huge value in documenting your changes in a simple changelog. It is too easy to forget what changes you made 3 versions earlier and things break because of this. I kept brief notes in one simple text file with all code changes included and rationale. This was also useful for when Matt and the team made change requests so we could all see who, when and what got changed.

Screengrab of notes

I used a bunch of test devices, which I recently wrote about to ensure the EPUB worked as widely as possible. During this phase changes included:

  • the cover image was simplified to work at small preview thumbnail sizes.
  • all chapters got pretty graphics from Vin Kumar, MRC designer.
  • graphic file sizes were optimised, particularly to help mobile readers.
  • section page breaks were forced for the Apple iPad to stop sections starting in odd places.
  • hyphenation was adjusted as the defaults were hideous.
  • validate, validate, validate,

With each change came improvement to the final reading experience.

The KindleGen app comes with a previewer so that you can simulate your test file in any of the kindle hardware versions without buying older devices. Sweet!

Screengrab of kindle gen previewer

Which shows you an accurate preview

Kindle preview

Decisions or compromise

In the end we managed to reach a great place for the final EPUB. Yet not all reading experiences will be equal. The iPad and the Kindle both have fantastic results (even the images were adjusted to work in low contrast for kindle).

As some reading apps like to overly control the reading experience, details like the colour section headings aren’t included in the nexus 7 apps Akido which likes to make all text 1 colour, over-riding my choices. However these things are beyond our control so all we can do is include them and let the reader app chose to include or ignore them. Maybe some day the app will update with these features included. A great example of this was towards the end of testing, the Adobe Digital Editions app upgraded to v2, making all the previously black headings appear as intended – the colour of the section it belonged to.

Screengrab of Adobe Digital Editions

Our ‘digital’ world is always evolving so even these compromises are really just decision points. If everything was static or we didn’t have much choice I would be even more upset, so I sleep happy.

Launch

When I pushed the final two files to Matt I got the jitters as I was very excited to let the world see our hard work.

I hope that this project will encourage others to consider the ebook format along side PDF outputs and that this post has shed some light on the process.

I would like to say that I got to work with some truly great people on this project and would like to thank Matt Jukes, Vin Kumar, Matt Durant, Baldur Bjarnason, Nigel Goldsmith, Roberta Perli and Stephen Gray for feedback and use of devices.

Matt has written about his experience of the project too, so do let us know what you think.

Below is what an EPUB looks like under the cover.

Breakdown of an EPUB

If you enjoyed this post then check out my 100 things about digital publishing series.

Follow me on twitter @zakmensah

02 ebook testing kit

Various ereader hardware stacked upon each other

I have just finished up a consultancy project building an ebook that i’ll talk about soon. The photo above shows the kit that I used to test the ebook at various stages. I produced two files in the process: EPUB for most devices including the iPad and a Mobi file for the Kindle hardware and app version.

  • Laptop with various reading software – Adobe Digital Editions v2.0, Kindle app, ibis reader, Kindle previewer (lets me test all versions of the hardware on the computer and saves buying hardware).
  • iPad with the Kindle app and ibooks (i used 3 iPads v2+3)
  • Google nexus7 with the Kindle app, Aldiko reader (lame) and Moon+reader (also lame), ibis reader
  • Kindle Paperwhite
  • Nook Simple Touch
  • Kindle 2nd Gen – it was kicking around so why not?!
  • Kindle previewer (allows you to test in all versions including the Kindle Fire)
  • Kindle Touch
  • Sony PRS-350 (thanks Stephen) – great to see how e-ink handles colour graphics
  • iPhone 4 with the Kindle app, ibooks and also ibis reader
  • HTC One X with Kindle app and ibis reader

For each device, the ebook displays and behaves differently so it is essential to test on the devices that you think will be used. Mr Andy Clarke said it best:

Designers need use only a subset of devices, because what matters most is that we develop an affinity for how our designs work on any type of device when we hold it our hands. To be clear, how a menu feels when used on a smartphone is a very different issue from whether it technically works on a particular make or model of smartphone. That’s why designers don’t necessarily need to buy a myriad of smartphones and tablets, just those they need to develop an affinity for.
Andy Clarke, Encouraging Better Client Participation In Responsive Design Projects

Sound simple right?! I got the list partly from what I have been using anyway and then from The mobile read wiki which has popular community input.

I will write more about ebook building, testing and frustrations in future posts.

By the way, my favourite reader is the now in limbo ibis reader which I read on my mobile phone or nexus7.

01 Why bother with ebooks?

Mobile everything has been much hyped over the past few years with figures of device ownership and network activity usage both up, up and away. Within the mobile space, one topic t intrigues me more than others, which is the idea of the digital book, made possible by ebook readers, tablets, computers and software. The NMC Horizon report, an annual look at what’s hot in education and technology has been waving the flag for ebooks since 2010  saying that by 2012 ebooks should be beginning to hit their stride and gaining widespread use. I think they might just be right.

The current digital book is largely relegated to hastily cobbled together editions of existing print books wrapped in an often poorly built PDF file. I can live with this, knowing that there must be light at the end of the tunnel (hopefully not a train) as duplicating print books has been tried, and now we have begun to look at that is next. Whilst I do believe that benefits such as having access to a library at my fingertips, fast searching and 24/7 distribution are great features, those alone are only scratching at the surface of what a digital book could be.

In Post-Artifact Books and Publishing Craig Mod writes:

  • The way books are written has changed.
  • The canvas for books has changed.
  • The post-published life of a book has changed.

Suddenly these three sentences thrust what digital books are becoming into the light. I feel it is worth considering each in context of education.

The way books are written has changed.

The process used to be be of isolation with author> select reviewers > Publisher > seller. Martin Weller’s 2011 book The Digital Scholar came into being in part from his public blog writing on many of the thoughts and topics that went on to become the book. The comments and statistics could have been one method of seeing what “sticks” to inform the book process. Which was then further honed by his tribe using various social tools.

Over the past year or so I have been following with interest as Gráinne Conole writes Designing for learning in an open world, sharing each chapter of it, using the web to “…act as a space to invite discussion and debate on emergent issues. ”

We are able to use ‘digital’ tools and communications to reach those at whom the book is aimed from day zero. Services like Kickstarter have enabled people to float an idea for a book and get the funding BEFORE day 1.

The canvas for books has changed.

We now have a countless number of ways to read digital books. From dedicated hardware such as the Amazon Kindle, to tablets such as the Apple iPad, Google Nexus 7 and more mainstream computers and mobile phones with book reading capabilities. These devices along with ‘apps’ let us read on a digital book on a new type of canvas from print.

My current favourite reader is the ibis reader which allows me to upload EPUB books and access them on all my devices and sync the page I am reading so i can effortlessly move from one reading device to the next. At the 2012 Digital Book conference, Liz Daly, creator of ibis reader spoke about the possibility of streaming books becoming a possible future (spotify for ebooks), helping us become file format and device agnostic.

I can imagine a near future where education book release will be “digital by default”, saving print for core texts.

The post-published life of a book has changed.

A digital book never has to be complete, like Wikipedia, edits can be made and released with ease. New versions being released as “dot” versions much like how software upgrades are done. Being digital, the book may be discovered by a far greater amount of people, and will be easily distributed via established library catalogues and newer services like Apple iTunes U. Services like Amazon allow you to publicly share your ebook reading lists and highlights,  suddenly these unique digital social features might start to find usefulness for education books. Teacher and learner sharing notes on the same books, this opens the door to potential new pedagogical exploration.

I am now reading as many digital books as I am print books and I continue to marvel at the idea of what is coming next.