onix 2.1 to onix 3.0

  • ONIX 2.1 to 3.0: Sales Rights

    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

    If you produce ONIX files, you should be aware that EDItEUR’s schema validation, which is used to ensure your data is loadable and readable by data receivers, is about to get stricter. You can find out how to get ready by reading all about it here.

  • ONIX 2.1 to 3.0: Collections

    To kick off our blog series on improving your ONIX 3.0 data, Tom Richardson explores Collections, including how it works, why it matters, and how to know if you’ve screwed up. If you work with book metadata, make sure to read this post and help make the world a better place for data traders.

  • 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.

  • ONIX 2.1 Is Riding off into the Sunset

    On December 31, ONIX 2.1 is making like a cowboy and riding off into the sunset after 11 great years on the metadata ranch. If you send or receive ONIX, it’s likely that you have questions. Get your answers here!