Application Notes: ONIX advice worth reading from EDItEUR

To support their detailed ONIX documentation, international standards organization EDItEUR releases Application Notes. These notes are short white papers that look in-depth at a single ONIX topic that users are asking about or that EDItEUR is aware can be problematic.

You can see and download the full list of Application Notes here, but we thought we'd take the opportunity to highlight a few of them:

  • Audiobooks in ONIX is a three-page primer on what you need to include when describing an audiobook (and it includes points where you can look forward to future development).

  • Embedding HTML markup in ONIX 3.0 data elements is a seven-page treaty that forms the basis of any advice I give on HTML and, since your HTML shouldn't change with your ONIX version, it applies equally to ONIX 2.1.

  • Weights and dimensions in ONIX 3.0 is not one you'd expect to see, is it? Surely these are obvious. Yes, the basics are obvious but it's devastating when you realize that you can't depend on telling portrait from landscape orientation in your metadata feed. And trust me, among 2.5 million entries, you can't... Many argue that bad data is worse than no data and I agree with them. Read this once, do this one thing right, and be happy ever after — it's five pages, including a big diagram, lots of white space, and a short code list.

  • Describing Open Access monographs in ONIX 3.0: These four pages tell you what you need to know about metadata and your books in the Creative Commons.

  • 12 ONIX problems details common issues faced by data recipients (and is so good we featured it in BookNet Canada’s User Documentation here ).

  • Sales rights in ONIX 3.0: The best for last. If you learn something from weights and dimensions (and you will), imagine what clarity a treasure like this brings.

This originally appeared on the BNC Blog at Subscribe the the blog RSS at