As I mentioned earlier, you’ll either be making ebook files (the PDFs and epub files you sell) one by one, or you’ll have a system for generating them on the fly, as they’re needed. Let’s call the first method manual and the second automatic.
Manual systems are fine for book production, if each book is very different, or if you don’t have too many books to manage.
If you have a lot of books (let’s say more than 50 a year), it gets tricky to manage them manually. Remember, any one book could have a hardback, paperback, print-on-demand, PDF, epub, Kindle, and mobile-app edition. Try implementing a reprint correction across that lot in a hurry!
So you’ll want to think about implementing an digital-asset-management system, or DAMS. DAMS come in many shapes and sizes, but essentially they’re large databases for storing master copies of your documents. Usually, they store your content in a given kind of XML. XML is content tagged according to a fixed list of tag names, and a fixed structure (e.g. every B-head has a parent A-head).
In the best DAMS, you can paste and edit text straight into them, using a web-like interface. And when you want a book file in a particular format (e.g. epub or print-on-demand PDF), you press a button and the DAMS transforms your XML into the format you want instantly and automatically. If your tagging is thorough, a transformation can also pull out only the parts of a book’s content that you want. For instance, the exercises from a school book, or the recipes in a travel book. You can then start selling bits of your books, in addition to the whole books at once.
As you can imagine, good DAMS are expensive, but important for publishers with large lists, especially if their content is consistently structured. Many dictionary publishers, for instance, already use DAMS for their dictionary content.
Improvising your own DAMS
If you don’t or can’t have a DAMS, the next best thing is to improvise one, not from new software systems but from human systems and your existing in-house network. The key aspects of a DAMS are easy to replicate if all staff work the same way. The suggestions here will cost only your time setting them up:
|DAMS feature||Improvised alternatives|
|One place to store metadata (any kind of information about a book)||One database of titles that you can expand with new metadata fields as needed. In its simplest form, an Excel spreadsheet with columns for Dublin Core metadata tags. Include the location of the book files.|
|One place to store master files and working files||A well-organised shared network drive, where folders are created according to an agreed naming and tree structure convention. Particular folders contain the current master document and public-release versions of each output format.|
|One process for editing and saving files (the software you use and the formats you save in)||A standard set of software tools (e.g. KompoZer is a good, free editor for working with XHTML files; Calibre is for converting ebooks between formats) and procedures to doing so. (Later we’ll talk about setting up a knowledge-base for this.)|
|An automated backup system||Make sure your metadata, files and procedures are saved to backup every night and regularly stored off-site (e.g. backup drives swapped out every week).|