Continuing our series of blog posts on graduating your data from ONIX 2.1 to 3.0, Tom talks about Sales Rights and introduces some changes in the handling of territory statements, as well as a new element that helps reduce ambiguity.
ONIX 3.0: Schema getting stricter
How and why to use BISG's Educational Taxonomy
ONIX 2.1 to 3.0: Collections
ONIX 2.1 to 3.0: Helping you make the transition
This is the first in a series exploring the differences between ONIX 2.1 and 3.0, and how to navigate your metadata through the transition.
In this first installment, Data Guru Tom Richardson explains why and how data traders ought to adopt ONIX 3.0, and gives an overview of the topics he’ll be covering this summer.
The Unseen Hand of Metadata
BNC metadata guru Tom Richardson looks back on how his book-buying habits have changed in the past year, and how the unseen hand of metadata may be at work…
This is the first year I can really see changes in my personal book-buying habits. Like many others, I’ve found that I’m buying books more often again. This has a lot to do with the convenience and direct nature of buying ebooks. (Feeling down at midnight no longer requires scavenging closets for books.) But I’m also buying print more and often based on its object-value; I like a well-made book, with diagrams and illustrations, and not too many photos. But why the change?
ONIX 2.1 Is Riding off into the Sunset
ONIX 3.0 – A Gnome’s Perspective on Digital Values for the Faint of Heart
Shiny New BiblioShare Webform Features
We’ve made a few improvements to BiblioShare Webform based on great feedback from publishers who use the tool. We’ve added new fields to give you broader access to the ONIX standard and – for you CataList users – to make some data easier to transfer to BNC CataList. We’ve also added new selection functionality to help you customize your exports. Read on for a short run-through of the major changes that are now available on the site.
ONIX 2.1 to 3.0 Converters: What They Can and Can't Do
Converting ONIX 2.1 to ONIX 3.0 is a very useful way to learn where “stuff” goes in ONIX 3.0 but publishers are confused why, once they’ve done the conversion, it’s just not good enough. I’ve been participating in arguments about it–and, as always, after the fact, came up with a succinct explanation. Be happy you weren’t involved in my long ones! Read on for an explanation of why ONIX 2.1 to 3.0 converters fall short, and how you can make good use of them anyway.