| Table of Contents |
|---|
Data exchange is never static. Here are some recent changes to best practices and standards that the industry is implementing.
...
ONIX 2.1 is now a completely static standard
January 2017
As of Code Issue 36 January 2017 EDItEUR will no longer update future ONIX 2.1 schema to include new "shared" code lists. In short: New codes in Issue 36 are part ONIX 2.1, but any new code in Issue 37 or after will not be.
Functionally this means that the ONIX 2.1 schema published by EDItEUR in January 2017 includes Issue 36 codes but will never be changed after this point. This marks the end of the extended twilight support offered by EDItEUR. Therefore: BNC BiblioShare will continue to process ONIX 2.1 as usual, but will base all future processing on the last published schema for Issue 36.
...
ONIX Codelist Issue
...
36
Released October 28January 23, 20162017.
EDItEUR has released a new Codelist update, 3537, and the next, 3637, is expected January April 2017. Requests related to Issue 36 37 should be passed to BookNet before November 25February 3, 20162017.
Changes:
This document list all changes added to Issue 3536: ONIX_BookProduct_Codelists_Issue_3536_Changes.pdf. Here There are number of important changes and reading the full document is recommended but here are some highlights:
- List 22 Language role code 21 (ONIX 2.1 and 3.0) now offers several language of audio track options to identify the track's language, its original language and its original language for multilingual audio product. Language of notes is now also supported (it's atypical in English but not unknown for other languages that text and notes are in different languages).List 27 Subject scheme identifier Edition code support for "International edition" and "Teacher's edition"
- List 51 (ONIX 2.1 and ONIX 3.0) now supports a value for Key Character Names specially to highlight fictional character names. In North America we'd recommend caution using this as retailers are using code 20 for Keywords and character names would be a typical inclusion. Check with trading partners before shifting data to the new value.List 51 Product relation code Product relation code: "Is later edition of first edition" to supplement the daisy chain created by "Replaces" this code links back to the first edition (no need was seen for an opposite code to link forward from the first edition)
- List 64 (ONIX 2.1 and ONIX 3.0) has new support for educational products to identify related teacher or student material. As well as there is a focused "shared content" code for products where neither product is wholly represented in the other. Reference the notes to understand the difference between the several shared contents code
- List 175 Product form detail (ONIX 3.0 only) supports "pull-the-tab-book" and two new values everyone thought were already there: a code for "Acid-free paper" and one for "Archival paper."
- List 147 Unit of usage (ONIX 3.0 only – digital use) A way to set a maximum times a "usage event" may occur during the purchase lifetime of a product.
...
- Publishing Status "Active, but not sold separately" for an ISBN only available as part of a larger product or pack
- List 65 (ONIX 2.1 and 3.0) Product Availability "Not sold separately" for an ISBN that must be bought as part of a larger product or pack
- List 71 (ONIX 2.1 and 3.0) Sales restriction type code – complimentary codes to specify Not for retail online / Online retail only
- There are several new codes or changee to ONIX 3.0 only list that improve or clarify digital licensing, but the most interesting addition is a new List 153 Text type code for a schema.org snippet.
Please contact biblio@booknetcanada.ca if you have questions or concerns on this change.
...
- Issue 35 36 stand-alone codelist documentation as readable PDF or HTML, plus comma-separated, tab-separated, XML and JSON files
- Issue 35 36 TXT, CSV, XML, JSON files for loading into your data management applications, and XSD, RNG DTD schema modules for use with older XSD, RNG and DTD schemas
- Issue 35 36 has also been incorporated into the Specification and Best Practice Guide documentation packages for ONIX 3.0
Need help finding the documentation? Finding and Using the ONIX Manual
...
2016 BISAC Subject Codes
November 2016
...
When should a publisher update their list is always a question: If a trading partner hasn't updated their system data can be lost, or sometimes the record won't get loaded, so it's good to give retailers time to up and generally publishers updating by Feb / March is fairly safe. If you've coded your biggest title carried a new BISAC Subject I'd get confirmation that my partners were ready to accept the data.
...
Thema version 1.2, updated August 2016 with Chinese national extension
The latest version of Thema, version 1.2, released April 2016, has had a major update with Chinese national extensions. See details here: Changes for Thema August 2016.pdf
...
ONIX 2.1 is no longer a formally supported standard.
End of 2015
The agreed upon "Sunset of ONIX 2.1" was the end of 2014, a year ago. The "limited twilight extension" ends with Code List 31 the last update of 2015 (well maybe something might sneak into List 32 in January but I doubt it). Here's a review of what that means:
- Companies that accept ONIX 2.1 now will continue to accept ONIX 2.1. Nothing will change in terms of who is accepting or using ONIX 2.1. BNC BiblioShare, for example, remains primarily focused on ONIX 2.1 because most of the data we get remains ONIX 2.1 (read more here).
- ONIX 2.1 only Code Lists – including the very important List 7 Product Form and List 78 Product Form Detail are now static. EDItEUR will no longer consider, document, or add to any value to an ONIX 2.1 only lists. We can continue to use and reference these lists, just not formally change them.
- Code Lists shared by ONIX 2.1 and ONIX 3.0 will continue to be updated for ONIX 3.0 use and so by default are updated for 2.1. For example, the very important List 5 Product Form Identifier is shared and updates will still be available for ONIX 2.1 so if you use the current ONIX 3.0 schema file for code lists (normally ONIX_BookProduct_CodeLists.xsd) with your ONIX 2.1 validation set up (read more here) you'll be able to utilize those changes. NOTE: EDItEUR is proposing that with Issue 36 (January 2017) removing the ONIX 2.1 only codes from ONIX_BookProduct_CodeLists.xsd
- BNC BiblioShare will update it's 2.1 set up with the new ONIX 3.0 Codelist file for as long possible to take advantage of that limited opportunity.
...
...
Active 979 ISBN-13s are in BiblioShare now
October/November 2015
There's only a few of them, but they represent real books actually being bought and sold in Canada today. Up to now any 979 ISBN in our data had been a test or a typo and not being traded. So let's pause for a moment and mark the functional end of the ISBN-10 in North America. It's been a long run and a good time.
...