The Gilbane Advisor

Curated for content, computing, data, information, and digital experience professionals

Page 216 of 931

The Gilbane Group’s Publishing Practice’s Blueprint Study is Now 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.

See my blog in Publishing Practices about some of our Blueprint findings.

And let us know what you think!

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.

 

 

 


W3C Call for Review: XML Entity Definitions for Characters Proposed Recommendation

The W3C (World Wide Web Consortium) Math Working Group has published a Proposed Recommendation of “XML Entity Definitions for Characters.” This document presents a completed listing harmonizing the known uses in math and science of character entity names that appear throughout the XML world and Unicode. This document is the result of years of employing entity names on the Web. There were always a few named entities used for special characters in HTML, but a flood of new names came with the symbols of mathematics. Comments are welcome through 11 March. Learn more about the Math Activity. http://www.w3.org/Math/ http://www.w3.org/TR/2010/PR-xml-entity-names-20100211/

Mr. Copy Launches DocuShare on Demand

Mr. Copy, a Xerox company serving California, announced its latest offering, DocuShare on Demand. DocuShare on Demand is aimed at helping small-to-midsize businesses manage the vast amount of paper and digital content created on a daily basis. This hosted Enterprise Content Management (ECM) solution enables document management, collaboration, review and approval as well as web publishing to support information sharing across a company by employees. When coupled with Xerox scan-enabled multifunction devices from Mr. Copy, DocuShare on Demand provides a complete document management solution from one vendor. DocuShare on Demand can save users up to 90 percent of operational and storage costs relating to document management. In addition, the new service should improve operational efficiencies by cutting the time it takes to find vital information. Compliance Ready and Easy to Deploy DocuShare on Demand takes the hassle of compliance away from the day-to-day operations of a company. Compliance for HIPAA, FERPA, Sarbanes-Oxley and 37 other state privacy laws are included in the package. In addition, DocuShare on Demand can be deployed in days or weeks instead of the months required for other solutions. With this digital solution, there is no infrastructure to purchase or maintain. http://www.mrcopy.com/

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.
 

Lucene Open Source Community Commits to a Future in Search

It has been nearly two years since I commented on an article in Information Week, Open Source, Its Time has Come, Nov. 2008. My main point was the need for deep expertise to execute enterprise search really well. I predicted the growth of service companies with that expertise, particularly for open source search. Not long after I announced that, Lucid Imagination was launched, with its focus on building and supporting solutions based on Lucene and, its more turnkey version, Solr.

It has not taken long for Lucid Imagination (LI) to take charge of the Lucene/Solr community of practice (CoP), and to launch its own platform built on Solr, Lucidworks Enterprise. Open source depends on deep and sustained collaboration; LI stepped into the breach to ensure that the hundreds of contributors, users and committers have a forum. I am pretty committed to CoPs myself and know that nurturing a community for the long haul takes dedicated leadership. In this case it is undoubtedly enlightened self-interest that is driving LI. They are poised to become the strongest presence for driving continuous improvements to open source search, with Apache Lucene as the foundation.

Two weeks ago LI hosted Lucene Revolution, the first such conference in the US. It was attended by over 300 in Boston, October 7-8 and I can report that this CoP is vibrant, enthusiastic. Moderated by Steve Arnold, the program ran smoothly and with excellent sessions. Those I attended reflected a respectful exchange of opinions and ideas about tools, methods, practices and priorities. While there were allusions to vigorous debate among committers about priorities for code changes and upgrades, the mood was collaborative in spirit and tinged with humor, always a good way to operate when emotions and convictions are on stage.

From my 12 pages of notes come observations about the three principal categories of sessions:

  1. Discussions, debates and show-cases for significant changes or calls for changes to the code
  2. Case studies based on enterprise search applications and experiences
  3. Case studies based on the use of Lucene and Solr embedded in commercial applications

Since the first category was more technical in nature, I leave the reader with my simplistic conclusions: core Apache Lucene and Solr will continue to evolve in a robust and aggressive progression. There are sufficient committers to make a serious contribution. Many who have decades of search experience are driving the charge and they have cut their teeth on the more difficult problems of implementing enterprise solutions. In announcing Lucidworks Enterprise, LI is clearly bidding to become a new force in the enterprise search market.

New and sustained build-outs of Lucene/Solr will be challenged by developers with ideas for diverging architectures, or “forking” code, on which Eric Gries, LI CEO, commented in the final panel. He predicted that forking will probably be driven by the need to solve specific search problems that current code does not accommodate. This will probably be more of a challenge for the spinoffs than the core Lucene developers, and the difficulty of sustaining separate versions will ultimately fail.

Enterprise search cases reflected those for whom commercial turnkey applications will not or cannot easily be selected; for them open source will make sense. Coming from LI’s counterpart in the Linux world, Red Hat, are these earlier observations about why enterprises should seek to embrace open source solutions, in short the sorry state of quality assurance and code control in commercial products. Add to that the cost of services to install, implement and customize commercial search products. The argument would be to go with open source for many institutions when there is an imperative or call for major customization.

This appears to be the case for two types of enterprises that were featured on the program: educational institutions and government agencies. Both have procurement issues when it comes to making large capital expenditures. For them it is easier to begin with something free, like open source software, then make incremental improvements and customize over time. Labor and services are cost variables that can be distributed more creatively using multiple funding options. Featured on the program were the Smithsonian, Adhere Solutions doing systems integration work for a number of government agencies, MITRE (a federally funded research laboratory), U. of Michigan, and Yale. CISCO also presented, a noteworthy commercial enterprise putting Lucene/Solr to work.

The third category of presenters was, by far, the largest contingent of open source search adopters, producers of applications that leverage Lucene and Solr (and other open source software) into their offerings. They are solidly entrenched because they are diligent committers, and share in this community of like-minded practitioners who serve as an extended enterprise of technical resources that keeps their overhead low. I can imagine the attractiveness of a lean business that can run with an open source foundation, and operates in a highly agile mode. This must be enticing and exciting for developers who wilt at the idea of working in a constrained environment with layers of management and political maneuvering.

Among the companies building applications on Lucene that presented were: Access Innovations, Twitter, LinkedIn, Acquia, RivetLogic and Salesforce.com. These stand out as relatively mature adopters with traction in the marketplace. There were also companies present that contribute their value through Lucene/Solr partnerships in which their products or tools are complementary including: Basis Technology, Documill, and Loggly.

Links to presentations by organizations mentioned above will take you to conference highlights. Some will appeal to the technical reader for there was a lot of code sharing and technical tips in the slides. The diversity and scale of applications that are being supported by Lucene and Solr was impressive. Lucid Imagination and the speakers did a great job of illustrating why and how open source has a serious future in enterprise search. This was a confidence building exercise for the community.

Two sentiments at the end summed it up for me. On the technical front Eric Gries observed that it is usually clear what needs to be core (to the code) and what does not belong. Then there is a lot of gray area, and that will contribute to constant debate in the community. For the user community, Charlie Hull, of flax opined that customers don’t care whether (the code) is in the open source core or in the special “secret sauce” application, as long as the product does what they want.

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/

« Older posts Newer posts »

© 2025 The Gilbane Advisor

Theme by Anders NorenUp ↑