Curated for content, computing, and digital experience professionals

Category: Publishing & media (Page 21 of 53)

Blueprint Study is OUT!

Our Blueprint study is the first in-depth look into ebook-related issues from the book publishers’ perspective, tying digital considerations to the everyday book publishing processes (A Blueprint for Book Publishing Transformation: Seven Essential Processes to Re-Invent Publishing.) Book publishers across all segments are embracing ebooks, but they require guidance grounded in what they actually do, more than simply a focus on technology.

Here is the figure in the study reporting on the book publishing segment breakout participating in the Blueprint survey that has trade publishers showing very strongly, at nearly one-third of respondents. This was a somewhat surprising showing to us, with our long and in-depth experiences with STM and education publishing. It’s good to get confirmation on claims we—and many others—have been making about trade publishing finally getting into ebooks in a serious manner.

Blueprint Fig 1.jpgOur expectations were thrown in other ways, too, and again because of The Gilbane Group traditional market focus, we’re we’ve been following content management platform development and helping with implementation in the enterprise for two decades.  We’ve seen a lot of software and hardware go into companies to make their content creation, handling, and distribution more integrated.  When it comes to book publishing, however, planning still starts—and, for many—ends with Word docs and spreadsheets. We believe this will change in the years ahead, and we certainly see a number of strong efforts toward integration of publishing processes out among the vendor community’s offerings.  Process integration must and will happen in book publishing, but we con only guess at the timetable for this, presently.

Blueprint Fig 7.jpg

One reason for our faith in book publishing process integration is that almost half of the surveyed respondents claim that they’re routinely working on print and digital versions concurrently, and this number goes to about three-quarters if the concurrent development is not necessarily routine, but pursued nonetheless. These numbers tell us several things, but the best news form them may be that book publishing is, indeed, seriously engaged in ebooks.  Technology has a fierce and deserved reputation for being over-hyped (and, yes, despite my best efforts to get into Heaven, I’m guilty enough of this charge myself, in too many instances over the years); ebooks are in early days, but the inflection point is solidly behind us.

Blueprint Fig 9.jpg

One proof of “early days” is the high level of confusion about ebook formats.  This confusion on the part of book publishers isn’t about what these formats are, but rather how to produce the various desirable (or market-demanding) ebook formats. While some publishing platforms offer flexible format production, many book publishers are using outside partners—like Blueprint sponsor Aptara—to take on conversion and production.

 

Blueprint Fig 39.jpg

Speaking of ebook formats, our next study, now in planning stage, looks to describe the various practical approaches for book publishers wanting to master this often-confusing issue.  Working title: Ebooks, Apps, and Formats:  The Practical Issues of XML, ePub, PDF, ONIX, .AWZ, DRM, ETC.

Stay tuned. Drop a line.

 

 

 


Mergers, Acquisitions, and the Publishing Processes Integration Challenge

From our new study, A Blueprint for Book Publishing Transformation: Seven Essential Processes to Re-Invent Publishing:

[Today’s] publishing processes are replete with spreadsheets and ad hoc databases (many built in FileMaker and Microsoft Access). These are used for tasks as various as tracking and calculating royalties, managing contracts, tracking digital assets, and managing editorial and production schedules.

Mergers, acquisitions, and divestments have an impact on both processes and their associated systems and tools. A large publisher that acquires a smaller one might move quickly to have the new group adopt processes and systems used by the larger company. Or, seeing that the new group has unique needs and requirements, the publisher might leave their processes and systems intact.

Of the process areas we looked at, planning is one where investments in technology range widely. In regard to editorial and production processes, some publishers have gone so far as to specifically redesign this process with an eye toward “digital first”—the idea being to have digital products ready first—or sometimes “media neutral”—with the idea being print and digital products are developed in concert. Aptara, one of the sponsors of Blueprint, sees a lot of their recent business with publishers helping the publishers do just this. (Blueprint is also available from the Aptara site.)

While the desktop war has largely seen QuarkXPress cede more ground to Adobe’s Creative Suite in a lopsided two-horse race, the broader market for editorial and production systems is wide open, with a long list of small- and medium-sized vendors carving out corners of the marketplace.

Despite these many editorial and production tools and systems, the Blueprint survey results does shed light on some trends we have seen in practice at publishing companies. These trends include:

  1. Even print books have digital workflow and digital underpinnings.
  2. XML is gaining in usage, and being seen further upstream in the editorial process.
  3. Book publishers are taking more control of their assets.
  4. Outsourcing is the rule and not the exception in editorial and production.

We see this penetration of XML as highly significant, especially in a survey where trade and educational publishers account for two-thirds of the respondents and STM, Professional, and Legal accounts for only 22%. These latter segments, after all, represent the early adopters for XML usage upstream in the workflow (and SGML before that), and trade and educational publishers have traditionally lagged. It suggests to us that market forces are driving publishers to work hard at creating the kind of multi-channel publishing XML is best at driving.

Another of Blueprint’s sponsors is Really Strategies (you can download Blueprint from them, too), which offers R/Suite, a publishing-focused content management system that incorporates Mark Logic’s XML repository platform. There is a lot more for publishers to do to integrate their various publishing processes, but getting control of source files is the best first step.

Let us know what you think of the Blueprint study, and stay tuned for news of upcoming studies from The Gilbane Group Publishing Practice.
 

Adobe Releases Digital Publishing Suite

Adobe has released a series of tools designed to expedite digital publishing across various platforms. Digital Publishing Suite allows publishers to upload articles directly from InDesign CS5, and supports PDF and HTML5. The software can run on RIM’s PlayBook, Samsung’s Galaxy Tab, Apple’s iPad and forthcoming Android platforms. The software allows dynamic user control of online publications, and readers are able to resize pages and move content around to suit their needs. Graphics, video and audio content can be built into the publications. The full version of Digital Publishing Suite will be available next year for a $699 licence fee, but beta code is now available from Adobe. http://www.adobe.com/

What’s Next with Smart Content?

Over the past few weeks, since publishing Smart Content in the Enterprise, I’ve had several fascinating lunchtime conversations with colleagues concerned about content technologies. Our exchanges wind up with a familiar refrain that goes something like this. “Geoffrey, you have great insights about smart content but what am I supposed to do with all this information?” Ah, it’s the damning with faint praise gambit that often signals an analysis paralysis conundrum for decision-making.

Let me make one thing perfectly clear — I do not have an out-of-the-box prescription for a solution. It’s not simply a matter of focusing on your customer experience, optimizing your content for search, investing in a component content management platform, or adopting DITA – although, depending on the situation, I may recommend some combination of these items as part of a smart content strategy.

For me, smart content remains a work in progress. I expect to develop the prescriptive road map in the months ahead. Here’s a quick take on where I am right now.

  • For publishers, it’s all about transforming the publishing paradigm through content enrichment – defining the appropriate level of granularity and then adding the semantic metadata for automated processing.
  • For application developers, it’s all about getting the information architecture right and ensuring that it’s extensible. There needs to be sensible storage, the right editing and management tools, multiple methods for organizing content, as well as a flexible rendering and production environment.
  • For business leaders and decision makers, there needs to be an upfront investment in the right set of content technologies that will increase profits, reduce operating costs, and mitigate risks. No, I am not talking about rocket science. But you do need a technology strategy and a business plan.

As highlighted by the case studies included in the report, I can point to multiple examples where organizations have done the right things to produce notable results. Dale and I will continue the smart content discussions at the Gilbane Boston conference right after Thanksgiving, both through our preconference workshop, and at a conference session “Smart Content in the Real World: Case Studies and Real Results.”

We are also launching a Smart Content Readiness Service, where we will engage with organizations on a consulting basis to identify:

  • The business drivers where smart content will ensure competitive advantage when distributing business information to customers and stakeholders
  • The technologies, tools, and skills required to componentized content, and target distribution to various audiences using multiple devices
  • The operational roles and governance needed to support smart content development and deployment across an organization
  • The implementation planning strategies and challenges to upgrade content and creation and delivery environments

Please contact me if you are interested in learning more.

In short, to answer my lunchtime colleagues, I cannot (yet) prescribe a fully baked solution. It’s too early for the recipes and the cookbook. But I do believe that the business opportunities and benefits are readily at hand. At this point, I would invite you to join the discussion by letting me know what you expect, what approaches you’ve tried, where you’ve wound up, what you think needs to come next – and how we might help you.

The Pull of Content Value

Traditionally, publishing is a pushy process. When I have something to say, I write it down. Perhaps I revise it, check with colleagues, and verify my facts with appropriate authorities. Then I publish it, and move on to the next thing – without directly interacting with my audience and stakeholders. Whether I distribute the content electronically or in a hard copy format, I leave it to my readers to determine the value of whatever I publish.

However, as we describe in our recently completed report Smart Content in the Enterprise, XML applications can transform this conventional publishing paradigm. By smart content, we mean content that is granular at the appropriate level, semantically rich, useful across applications, and meaningful for collaborative interaction.

From a business perspective, smart content adds value to published information in new and compelling ways. Let’s consider the experiences of NetApp and Warrior Gateway, two of the organizations featured in our report.

NetApp
As a provider of storage and data management solutions, NetApp has invested a lot of time and effort embracing DITA and restructuring its technical documentation. By systematically tagging and managing content components, and by focusing on the underlying content development processes, writers and editors can keep up with the pace of product releases.

But there is more to this publishing process orientation. Beyond simply producing product information faster and cheaper, NetApp is poised to make publishing better. The company can now easily support its reseller partners by providing them with the DITA tagged content that they can directly incorporate into their own OEM solutions. Resellers’ customers get just the information they need, directly from the source. With its XML application, NetApp incorporates its partners and stakeholders into its information value chain.

Warrior Gateway
As a content aggregator, Warrior Gateway collects, organizes, enriches, and redistributes content about a wide range of health, welfare, and veteran-related services to soldiers, veterans, and their families. Rather than simply compiling an online catalog of service providers’ listings, Warrior Gateway restructures the content that government, military, and local organizations produce, and enriches it by adding veteran-related categories and other information. Furthermore, Warrior Gateway adds a social dimension by encouraging contributions from veterans and family members.

Once stored within the XML application powering Warrior Gateway, the content is easily reorganized and reclassified to provide the veterans’ perspective about areas of interest and importance. Volunteers working with Warrior Gateway can add new categories when necessary. Service providers can claim their profile and improve their own data details. Even the public users can contribute to content to the gateway, a crowd sourcing strategy to efficiently collect feedback from users. With contributions from multiple stakeholders, the published listings can be enriched over time without requiring a large internal staff to add the extra information.

Capturing New Business Value
There’s a lot more detail about how the XML applications work in our case studies – I recommend that you check them out.

What I find intriguing is the range of promising and potentially profitable business models engendered by smart content.  Enterprise publishers have new options and can go beyond simply pushing content through a publishing process. Now they can build on their investments, and capture the pull of content value.

E-Reader Devices in Flux, But So What?

Repeat after us: What happens to specific devices or formats, such as Kindle or the iPad, will not be a significant factor for book publishers.

The title of this blog is taken from a sub-section heading in out Industry Forecast chapter in our just published 277-page study, A Blueprint for Book Publishing Transformation: Seven Essential Processes to Re-Invent Publishing, as is the quote above.

We’ve been following ebook efforts for well over a decade, and for some of us, thinking back to CD-ROM or the Gutenberg Project , the timeline is deeper yet. I mention this perhaps to excuse some of our assumptions going into the work of the Blueprint study, which was that many book publishers remained nervous about participating in ebooks because of the uncertainty about ebook formats among their potential customers, themselves, and, indeed, the market at large. We were, largely, wrong.

For one thing, a good part of book publishers—even trade—are already working with XML.  Here’s a quote from the new study:

There will remain plenty of help for book publishers to deal with the format flux, and, as book publishers move more completely into digital workflow—and especially grow in sophistication in regard to XML content format within editorial and production processes—the difficulties to meet specific output format demands will ease.

 Overall, we have come to understand that the convergence of functionality supporting enhanced ebooks among general-purpose mobile communications and computing devices, along with emerging standards for display, sale, and distribution of ebook titles, will also make platform issues for digital publishers largely moot. Recent announcements of new tablet devices, such as those by Samsung, which projects 11 million unit sales in 2011, simply expand market numbers rather than confuse markets. That is, if, as a book publisher, you handle your content in a way that can be created once and used in many ways.

To be clear (as we hope the following quote from the study is):

…book publishers should involve XML formats as early in the publishing process as possible. We are convinced ebook formats will evolve and change, and new ones will emerge. XML stands today as the one standard format that will enable publishers to best create, manage, and curate content over time. Moreover, the future will expand how XML and metadata can support strong integration among the various publishing processes within the publisher’s own work.

 As per our agreement with the sponsors of the Blueprint study, the sponsors have a 30-day exclusive distribution for the study, and Blueprint won’t be available through Gilbane.com for a few weeks yet.  We’ll be posting announcements from the study sponsors , providing download links as we get them.

eZ unveils eZ Publish Enterprise 4.4

eZ has introduced eZ Publish Enterprise, which provides a package of software and services in a integrated, pay as you go product. As an eZ Publish Enterprise product, you will get all the power of the eZ Publish community project, along with professionally supported software that includes additional Enterprise features and services. This release of eZ Publish Enterprise integrates all the Enterprise services into a Service Portal in the administration interface of eZ Publish, making administrators’ lives simpler. With version 4.4, eZ Publish provides users a range of features that will help them succeed in their day-to-day use of eZ Publish, whether they are end users, occasional contributors, editors or administrators. The brand new built-in Online Image Editor will provide a simple way for editors to perform the most common tasks of photo management in eZ Publish. New with this version is the native support for HTML5 video without need for advanced development. Publishing on mobile devices such as the iPhone and iPad has been made easier. User Generated Content gets a helping hand with the addition of native support for reCaptcha, the Google-based free captcha service on the web, which helps prevent your website from being infested by spam. A new User Session handler gives more possibilities for the configuration of web servers. File system-based user session management multiplies the performance of eZ Publish servers when talking to a large audience of anonymous users. A new Archiving toolkit implements large volume archiving scenarios where old content can be moved to archive repositories, and can still be searched and rendered with the eZ Publish presentation engine. eZ Publish 4.4 improves section management, multi-site setup, and extension loading, but the biggest news is the Developer Preview of the forthcoming eZ Publish API. The eZ Publish API shows the way for developing remote applications for new devices. Connecting to eZ Publish and using its content and functionalities is easier than ever. The light-weight remote API makes eZ Publish the platform of choice for Mobile Content Management, whether you focus on the iPhone and iPad platforms, Android or Blackberry. The new Newsletter system, developed in collaboration with the CJW partner, an eZ partner and active member of the eZ community, is a prime example of community innovation. http://ez.no/

How Smart Content Aids Distributed Collaboration

Authoring in a structured text environment has traditionally been done with dedicated structured editors. These tools enable validation and user assisted markup features that help the user create complete and valid content. But these structured editors are somewhat complicated and unusual and require training in their use for the user to become proficient. The learning curve is not very steep but it does exist.

Many organizations have come to see documentation departments as a process bottleneck and try to engage others throughout the enterprise in the content creation and review processes. Engineers and developers can contribute to documentation and have a unique technical perspective. Installation and support personnel are on the front lines and have unique insight into how the product and related documentation is used. Telephone operators not only need the information at their fingertips, but can also augment it with comments and ides that occur while supporting users. Third-party partners and reviewers may also have a unique perspective and role to play in a distributed, collaborative content creation, management, review, and delivery ecosystem.

Our recently completed research on XML Smart Content in the Enterprise indicates that as we strive to move content creation and management out of the documentation department silo, we will also need to consider how the data is encoded and the usefulness of the data model in meeting our expanded business requirements. Smart content is multipurpose content designed with several uses in mind. Smart content is modular to support being assembled in a variety of forms. And smart content is structured content that has been enriched with semantic information to better identify it’s topic and role to aide processing and searching. For these reasons, smart content also improves distributed collaboration. Let me elaborate.

One of the challenges for distributed collaboration is the infrequency of user participation and therefore, unfamiliarity with structured editing tools. It makes sense to simplify the editing process and tools for infrequent users. They can’t always take a refresher course in the editor and it’s features. They may be working remotely, even on a customer site installing equipment or software. These infrequent users need structured editing tools that are designed for them. These collaboration tools need to be intuitive and easy to figure out, easily accessible from just about anywhere, and should be affordable and have flexible licensing to allow a larger number of users to participate in the management of the content. This usually means one of two things: either the editor will be a plug in to another popular word processing system (e.g., MS Word), or it will be accessed though a thin-client browser, like a Wiki editor. In some environments, it is possible that both may be need in addition to traditional structured editing tools. Smart content modularity and enrichment allows flexibility in editing tools and process design. This allows the  use of a variety of editing tools and flexibility in process design, and therefore expanding who can collaborate from throughout the enterprise.

Also, infrequent contributors may not be able to master navigating and operating within a  complex repository and workflow environment either for the same familiarity reasons. Serving up information to a remote collaborator might be enhanced with keywords and other metadata that is designed to optimize searching and access to the content. Even a little metadata can provide a lot of simplicity to an infrequent user. Product codes, version information, and a couple of dates would allow a user to hone in on the likely content topics and select content to edit from a well targeted list of search results. Relationships between content modules that are indicated in metadata can alert a user that when one object is updated, other related objects may need to be reviewed for potential update as well.

It is becoming increasingly clear that there is no one model for XML or smart content creation and editing. Just as a carpenter may have several saws, each designed for a particular type of cut, a robust smart content structured content environment may have more than one editor in use. It behooves us to design our systems and tools to meet the desired business processes and user functionality, rather than limit our processes to the features of one tool.

« Older posts Newer posts »

© 2024 The Gilbane Advisor

Theme by Anders NorenUp ↑