TOC, RIP

May 7, 2013 in Conferences, Digital Publishing Platforms, Publishing Industry News by robert.weisberg

Those of us in the shallow, print-y end of the digital publishing pool can be forgiven for thinking that Tools of Change was the company, and tech publisher O’Reilly and its Safari Books Online merely adjuncts of that glorious and grueling confab. Which made last week’s announcement that O’Reilly was discontinuing the Tools of Change conferences (the New York flagship and its smaller meetings, including those timed to book fairs in Frankfurt and Bologna) and its blog all the more surprising.

In retrospect, we shouldn’t have been all that surprised.

Topmost for me is concern for the two indefatigable leaders of the TOC conferences, Kat Meyer and Joe Wikert, who are out of jobs, though I trust not for long, considering their skill in bringing the conferences together and expanding its scope over the past several years. (Which can be cold comfort–as we all know, physical, butt-in-chair jobs are harder and harder to come by in the vaporware publishing world we increasingly inhabit.)

Which is only one of the reasons that the end of TOC could have been anticipated. Besides the slushy misery of hosting a huge conference in New York every February, the very digital technologies that we trumpet to make virtual visits and bit-driven reading possible can render lots-of-butts-in-conference-chairs harder to justify. (The museum world still seems to like its get-togethers, thank goodness, and if the need to meet our colleagues in person is a residue of the academic-world conference mentality, I’m all for it.)

But as anyone who’s been to more than a few of these things and eventually got over the “why am I here?” nerves, what made these conferences so valuable were the conversations sprouting like tubeworms in the tectonic gaps between panels, often running into and through the next scheduled talks. (Check out any run of tweets from a conference Twitter stream or Epilogger–if people hailed what they learned chatting with a newfound colleague instead of sitting in too-cold-or-too-hot ballrooms, then save the date for the following year.) This past February, at my third TOC, I finally felt empowered to miss a panel or two in favor of talking to people whom I’d found, or who found me, on the conference message board. Those conversations continue to this day, broken up by weeks in the here-to-Neptune timelapse of modern time un-management, and I expect they will bear fruitful results, if only through metaphors and pie-high schemes that make this digital age so strange and nervy and exciting.

But just as a trillion-dollar manned space program is an inefficient way to develop Tang, a giant conference is an expensive excuse for chats, both for those who are supposed to attend, and for the organizers. There are only so many iterations of the question, “so what’s next for digital publishing?” or “what’s the new platform or tech we need to invest in?” Eventually, the descriptions of the tech become the thing itself, especially in digital publishing, in which the agile process of putting content together can become the product. How many digital pubs could be birthed in three days? (And try monetizing that. And, yes, it’s being done in “hack-a-thons” everywhere. Or so I’ve heard.)

So, while bummed, I get O’Reilly’s reasoning for stopping for conferences, though the callous manner in which it was announced has the publishing world extremely annoyed. A little odder is their decision to focus on “bringing their own tools to market.” They are extending their own in-house publishing platform, an authoring-to-publication tool, and monetizing it, leveraging the considerable brand recognition they’ve developed on the mutual backs of their Safari Books and, since (to quote The Matrix) “Fate, it seems, is not without a sense of irony,” the TOC conferences themselves.

But the question is, are the conference audiences in search of such a platform? That’s exactly what came across at this year’s TOC, as the platform-and-protocol mania of previous events gave way to a more flexible, audience-driven set of goals. I have no doubt that O’Reilly can pull off the techie end, but have they read the market correctly? Were the TOC conferences actually Trojan Horse marketing experiments? (Not that there’s anything wrong with that. Okay, there is.) The money that went into my attendance at TOC is not going to be rerouted to chase the next collaborative platform. It’s not the idea that’s the problem. It’s that, in this day and age, it’s hard to go with one vendor’s version over another.

I wish O’Reilly the best because it’s bad karma to do otherwise. (And it would be the epitome of hypocrisy for me to have told people “eh” when Amazon bought Goodreads, and to then bash O’Reilly in public when they chase dollars–I mean vision–in a different way.) I wish Kat and Joe the very, very, very best because they’re the actual victims here. (I suspect that the carcass of TOC will feed more than a few smaller, more nimble conferences which will be great.) Personally, I’m extra bummed because I had spoken with Kat recently about getting more museums and other non-profits to attend future TOC events–as panelists–and describe the great things that museum technologists have been doing while the publishing world convulsed into spasms at each new digital flavor of the season. Of course, all the information presented at these conferences will be available over the intertubes, but the handshakes and the chats will be a little harder to generate in the skype-a-verse, and for that, we should all be bummed.

Congratulations! The Bliki wins Best of the Web for ‘Best Museum Professional Website’.

April 24, 2013 in Conferences by Liz Neely

The Best of the Web award for Best Museum Professional Website.

The Museum Digital Publishing Bliki won the ‘Best Museum Professional Website’ Best of the Web award at this year’s Museums and the Web conference! Best of the Web is a prestigious annual contest to recognize the best museum work on the web. Sites are nominated by museum professionals from around the world and reviewed by a committee of peers.

The Best of the Web evaluation committee appreciated that the Bliki had been developed through a process of discussion within the museum and publishing communities. The committee also noted that access to the member list reveals it as a thriving, active community. Further committee comments called the Bliki “well-organized and easy to navigate,” adding that “the straightforward, non-flashy design complements the focus on the site’s compelling long-form content. The conference and event wiki is particularly helpful.”

The Bliki debuted at the National Museum Publishing Seminar in Chicago to best reach museum publishers and vendors whom do not generally attend web and technology conferences. Since its launch in June 2012, the Bliki has featured approximately 50 thought-provoking posts providing both practical information and creative approaches. The wiki section allows for collaborative authorship to catalogue bibliographies of publishing conferences, professional development opportunities, relevant presentations and other resources.

The Bliki has 112 subscribers to its blog and 52 registered members. These numbers are not large, but the site is decidedly a long-tail niche interest. Drawing from information provided by the members, the Bliki has achieved its audience goals consisting of a mix of museum publishing professionals, digital media technologists, collection information specialists and trade publishers. Google analytics reveals visits from 31 publishers, 91 museums and other cultural institutions, and 146 colleges and universities. Readers of the Bliki come from 88 countries and visits to the site average approximately 1,011 per month.

To allow for the broadest set of opinions, the Bliki is not directly affiliated with an institution. Liz Neely and Amy Parkolap of the Art Institute of Chicago moderate and contribute to the Bliki. Greg Albers, publisher at Hol Art Books, and Robert Weisberg of the Metropolitan Museum of Art are flagship contributors as well as advisors to the site. Other members have also contributed engaging posts and all are welcome to contribute.

Thanks to you all as readers, contributors, and subscribers for making the Bliki a successful space for advancing the museum digital publishing conversation while building a cross-functional museum publishing community.  As the Bliki’s one year anniversary approaches, we’ll be conducting a member survey to evaluate how the site can best meet your needs in the future. We’ll also implement badging to reward and acknowledge participation with the site. These first nine months have established a strong foundation from which to build a robust dialogue around digital publishing in museums.

Congratulations on being part of the award-winning Museum Digital Publishing Bliki!

The power of well-considered publishing: Graphite from the IMA

April 4, 2013 in Digital Publishing Platforms, Digital Strategy by Greg Albers

Regular readers know I’m a curmudgeon when it comes to iBooks Author, and yes this is another iBooks Author post, but guess what? It’s positive! The Indianapolis Museum of Art has just released its first all-digital exhibition catalogue for the current show, Graphite (December 7, 2012–June 2, 2103). It’s available through iTunes for $4.99 and was published with iBooks Author. Three features of the book immediately caught my eye as worth sharing and, for those of you undertaking your own iBA projects, worth emulating.

#1: Following is a screen shot from the Artists section of the book. See the navigation links at the top? There’s one for each of the four main sections of the book and they run along the top of most of the book’s pages. This isn’t a feature of iBooks Author, it’s something the IMA team designed to address iBA’s inherently tricky internal navigation tools, and to facilitate a looser and more seamless jumping around reading experience for the reader. Smart. Even better? See the name and progress bar graphic in the upper right? That’s another IMA add-on and it tracks where you are in each section. Super smart.

Screen shot showing unique navigation

#2: Next, a screen shot from the Exhibition Tour section. Yes, that’s right. The catalogue to the show includes installation shots of the show itself. Art historians out there immediately understand how valuable this is, but even for regular readers, how great is it to visit an exhibition you love and buy the book to then have it include a record of your actual experience of the show? Pretty great. And, because the catalogue’s digital, this can be achieved while still having the publication available for sale during the run of the exhibition.  In this case, the IMA got it out about four months after the opening date, but I think significantly less is perfectly possible.

Screen shot of the Exhibition Tour section

#3: The final thing I want to point out is video. We all know that video can be inserted into e-books, and many art publishers have taken advantage of this to include artist interviews and other “enhanced” features. In the introductory essay to Graphite though, the IMA includes the full video of artist Richard Serra’s 3-minute film, Hand Catching Lead, 1968. I first saw the work a couple of years ago at SFMOMA in the big Serra retrospective there. To come across it again, in its entirety, in the palm of my hand, was fantastic. For me as a reader, this is of real value. I’m amazed not to have seen artist video works included like this before. And for all the Rights & Reproductions nuts out there, note that this video piece was cleared with Artists Rights Society and comes from MOMA, so yes, it’s possible.

Screen shot showing video inclusion

So, to the team at the IMA that made this all possible—especially Director of Publishing and Media, Rachel Craft—congratulations! You brought hope to this young curmudgeon’s heart. Unfortunately, for our readers, there’s bad news here as well. The IMA recently came under new directorship and the institution’s commitment to cutting-edge digital publishing (among other things) has shifted away. Rachel and many others were laid off last month and it seems as though this first great #digpublishing effort from the museum will likely be their last. That’s a shame, but perhaps the rest of us will take to heart, and to code, their terrific effort.

 ps. San Francisco: Rachel is heading your way, snatch her up while you still can!

UPDATES, May 23, 2013:

• Rachel reminded me to give a well-deserved shout out to Jay David at TOKY Branding + Design who was a major collaborator on some of the unique elements I pointed out in Graphite‘s design. Shout!

• Apparently, negotiating the rights for the Serra video took 6 months. Thanks @AYoungRandR!

• You can now get more of the inside scoop on Graphite‘s development in this talk from the 2012 Museum Computer Network conference in Seattle, now available on YouTube: Agile Digital Publishing with Rachel Craft, Jay David and the IMA Lab’s Kyle Jaebker.

 

Talkies to Ebooks: Industry Disruptors

March 28, 2013 in Digital Strategy by Amy Weber Parkolap

A demonstration of a Vitaphone sound system for use in films by a Western Electric engineer in 1926.

In “Mobile Native Publishing: The Rise of Dynamic Content Services,” Mark Sigal draws the parallel between the disruption that the “talkie” created in the film industry in the 1920s to the recent introduction of the ebook in the publishing sector.  This very apt analogy is teased out to show what the publishing industry can learn from the film industry’s adaptation to a new technology some 90 years ago.  Sigal writes, “The talkie not only changed how movies were made and the economics of the business itself, but critically, it changed our concept of what a movie could be.”   And as a result, learning to create content for the new medium –writing for a movie with sound/writing and designing for a multimedia screen layout as opposed to a page layout–is of utmost importance.  Sigal writes, “The talkie wasn’t destined to become silent film with words, so too it follows that in the age of smartphones and tablets, publishing will evolve to become much more than a simple carbon copy of print. Every medium, after all, has its own set of native methods, and these methods, in turn, shape the medium.”  To find out more about what this concretely means for the publishing industry, data, and content creation, read Sigal’s article here at Tools of Change.

Digital Publishing Review — Inkling Habitat

March 15, 2013 in Digital Publishing Platforms, Organization and Workflow by Patrick Phillips

Mid February, Inkling Habitat was announced and I jumped in and produced a promotional title and am now producing a monograph and a multiple artist collection. Here’s a sketch of my experiences, along with a bit of a critique. This is intended as an overview. I am willing to share more in comments or in another post.

Accessibility
Must say right up front, Habitat uses modified xml, called s9ml. While it does output to EPUB, interactive features using s9ml outputs nonstandard EPUBs. Producers who are concerned with out-of-the-box universal accessibility will rightly grumble. (Look to People’s eBook to address art ebook universality.) Another limit: right now Habitat outputs to iPad and iPhone. The Inkling team apparently has Android on its roadmap. It is important to note that Habitat automatically produces browser-ready HTML5 output, so titles produced in Habitat are viewable (and sharable) via the web. Even with its accessibility limits, Habitat does have real benefits worth considering.

Workspace
Under the hood Habitat is a HTML5/xml and CSS3 browser-based editor with some jQuery and Inkling enhancements. This is a good starting point for cross-browser/platform applications. If you’re familiar with web production Habitat will be an easy and natural fit. Code and title previews are presented in the same browser window, and CSS edits are immediately viewable. The structure of the book while it is being constructed, as well as the structure of the file directories/UI in Habitat, are logically presented. Each new project comes preset with the same base file and feature structure. For me, the order of the workspace quickly made it easy to work in.

Book Structure
The building blocks of Habitat books are modular xml “pages” — Habitat calls them “cards.” The cards are code blocks that can be dragged and dropped into chapters to form a structured book hierarchy. On the up side, through drag an drop the feature and structure outline of your title can be put together quickly. On the down side, if you are producing a title that is a simple monograph all this could seem structure-heavy. It did for me. It took a little effort to move this structure out of the way of the story, and honestly I am not completely certain the final result is perfectly balanced. Iteration and experimentation will help.

This structure issue is due in part to the fact Inkling’s business began as a textbook publisher. Textbooks are unit/chapter/section driven and notoriously figure and “furniture” laden. There is a lot going on in them and as a result a lot going on in Habitat. Still, having done the work to address deep structure challenges up front, Habitat provides a full and modifiable toolbox book designers can draw upon. This toolbox helped me think through design needs and will be handy when we have more challenging titles (next month.)

Design
There are many good aspects of Habitat and a few reservations. Reservations first.
Because of its textbook DNA, Habitat’s modular, drag and drop “furniture” (figures, callouts, guided tours, lists) has a textbook design DNA as well. People unfamiliar with CSS and who want a quick title will end up using the modular book furniture out of the box, and a lot of Habitat books will have a similar “textbooky” feel.

This is a similar problem designers had at the beginning of desktop and web publishing — the technology was so attractive people forgot to design. However, once people understood how to manipulate style and structure (and CSS was established) good design began to flourish. People will have to bring design skills and focus — along with a willingness to re-style Habitat elements — in order to build and design a wide range of beautiful Habitat books. The last thing we need is a bunch of cookie-cutter textbook DTP.

Once you have gotten accustomed to the platform and past the structure issues Habitat’s design versatility becomes apparent. Because everything is built around clear, modular HTML5 code and a library of CSS classes, and because you can customize CSS classes easily, Habitat becomes very flexible for designers. Full frame images and backgrounds, drop caps, line-height, superscript, and custom fonts all are fairly easily employed by modifying CSS classes. And, all of this can be pushed to create innovative designs. There is even a (limited) design and code library to draw from. Different from iBooks, which locks you into established patterns and funnels designers into a kind of DTP mentality, Habitat is quasi open source.  This is dangerous to say, I know; however, because you can restyle classes, create your own style sheets and even add jQuery elements Habitat is more versatile and “open” than some other platforms.

I found as I developed my own styles, swapped SVG images in for icons, laid out custom pages and modified Habitat figures I had created my own book design toolbox. Once you have produced a well-designed structure and template and published a title it is possible to save this to your book production dashboard to draw from and modify for another project. Ultimately, what solid design templates provide is peace of mind and my own unique design DNA. I can now get to work.

Collaborative Workflow
Very importantly, the entire production environment has a robust ticketing system that allows cloud-based collaboration and editing. In my opinion, this feature makes the entire platform. Without a collaborative ticketing/workflow overlay Habitat would not be adopted widely — it simply would not be professional enough to build far-flung teams around great design and efficient production. With cloud-based collaboration and workflow, Habitat allows teams to draw on global designers, content curators and editors. This alone is a breakthrough “feature” that could enable Habitat to have a significant impact on digital book design and delivery worldwide.

Habitat Support
Did I mention that Habitat is free? Including prompt and helpful support? Including code and copy review? When I was ready for a final release and I realized I had several Habitat editors and proofers working on my title as a team for free I walked around my kitchen in amazement — honestly a little giddy. I was producing a new title collaboratively with dedicated people across the country in California who were professional and knowledgeable. This human aspect of Habitat is evident in their design, engineering, focus and purpose.  Without this I would not recommend the platform. With it, a whole lot can happen.

Stuff I’ve Left Out (Lots)
In the interest of space, I haven’t addressed many key things. In terms of basic design: interactivity, page flow, verticality vs. horizontality. I have left out other basic elements of user engagement — Habitat’s handling of video, slideshows, full glossaries, searchable text, shareable comments, highlights, and bookmarks. As for workflow, I haven’t mentioned that styles set up in InDesign can be mapped to Habitat CSS classes. Or, that once published book content can be found in web searches, and pages and sections can be shared through social media and email. I haven’t mentioned that titles are always updatable, with a simple push of new content to user’s tablets and phones.

In terms of user scenarios and applications, because of Inkling’s textbook background, people can design and use these books as discovery and teaching platforms. And, with all this, designers and producers can build social interactivity into engaging books with tablets, browsers and desktops in mind.

Perhaps above all, I haven’t gone into how Habitat titles are integrated with Inkling’s store. Commerce integration makes possible a new kind of publishing entity that can collaborate/design/publish/distribute all under the same platform. Habitat may be a step or two ahead of the transition from publishing empires to small, agile publishing studios. But, once it addresses some platform limits and people create a variety of well-designed, useful and meaningful books, it has put a versatile tool in people’s hands that could accelerate the entire process. We’ll see…

[Note: For anyone who would like images associated with this post I'm happy to provide. They may help.]