if:book's Kate Eltham is currently blogging for if:book from the O'Reilly Tools of Change for Publishing Conference in New York City.
Metadata serves multiple purposes for publishers, including supply chain information, marketing and merchandising, and rights expression. Publishers already know that metadata matters, and this workshop will update you on recent changes to existing standards like ONIX as well as brief you on emerging standards like OPDS. You’ll also learn practical steps for establishing definitive but flexible sources for metadata, including how to bring stakeholders together from across functional areas to manage internal policies and procedures. The workshop will also present case studies and examples of interesting ways publishers, developers, organizations and companies are exploiting their metadata.
There's metadata you create, and metadata created for you.
Metadata is multi-faceted (think of a diamond). Lots of stakeholders create, use, depend on it: publisher warehouse, publisher finance dept, bricks & mortar bookstore buyers, Amazon/BN, Goodreads/Librarything, Distribtuion (Ingram/B&T), typesetter & printing press, libraries, etc.
Adam Witwer: Metadata Operational Challenges in the Digital Era
POD removes some of the earlier needs re: warehousing, inventory management etc. Also decouples processes that use to be linked to reprint process, such as errata.
Metadata to manage content updates: errata fixes, sales data, severity of error, customer complaints, last updated, cranky author = managing the post-publication of each title, and of entire backlist
Versions vs Editions
eBooks and metadata: the key data is more about what I can do with the book, and less about the book itself and content. For example the distinct identifier [ISBN] for same title, multiple formats. Each identifier represents many different delivery points. e.g O'Reilly approaching 30 delivery points (new in last 12 months).
Metadata to manage ebook distribution:
- Where can it be sold?
- Rights exceptions
- Delivery method and credentials
- File-naming conventions
- Last update
- percentage viewable
Questions to ask: which of these are tracked internally, and which should be shared with stakeholders and channel partners?
Data comes from different sources and has different users e.g. price and font.
Need a way of managing data that scales and is flexible: FluiddB?
Don't forget user metadata!
Metadata is a way of enticing vendors, convincing them of the desirability of this title using tags.
eReader Aggregation & Distribution
OPDS = Open Publication Distribution System
check out http://www.feedbooks.com/api/primer
"RSS for ePub" Martin Fenner http://blogs.plos.org/mfenner/2011/02/06/opds-rss-for-epub-or-how-to-distribute-epub-files/
Publishers should have an OPDS feed.
Readers supporting it: ibis reader, bookserver, lexcycle stanza, aldiko, calibre, megareader
See Yelp, user-generated review aggregator.
A Bing search for Girl Who Kicked the Hornets Nest gets user ratings, number of people etc.
Seattle Public Library invites patrons to leave user comments, reviews, ratings on its website/catalogue.
Publishers need to track this data as well as they can.
Kindle Public Notes - public sharing/social reading of book marginalia. Amazon investing a lot in their customers, but not in their suppliers e.g. not sharing customer reviews programatically (neither do Google, Apple).
Alternatively, Scribd allows publishers to dive deep into stats for each of your documents
We need a metadata spec (another one!) for book reviews, customer data. Microsoft Press: custom pivot tables app for analysing data created by Microsoft LiveLabs, built using Siverlight
What is a Net Promoter Score?
Book Industry Study Group (USA) has produced best practice guidelines for metadata and they're available online.