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
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 January 23, 2017.
EDItEUR has released a new Codelist update, 37, and the next, 37, is expected April 2017. Requests related to Issue 37 should be passed to BookNet before February 3, 2017.
This document list all changes added to Issue 36: ONIX_BookProduct_Codelists_Issue_36_Changes.pdf. There are number of important changes and reading the full document is recommended but here are some highlights:
- List 21 (ONIX 2.1 and 3.0) Edition code support for "International edition" and "Teacher's edition"
- List 51 (ONIX 2.1 and 3.0) 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 3.0) 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 firstname.lastname@example.org if you have questions or concerns on this change.
- Issue 36 stand-alone codelist documentation as readable PDF or HTML, plus comma-separated, tab-separated, XML and JSON files
- Issue 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 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
A new version, 2016 BISAC Subject codes, was released supporting 4582 codes in total. By the numbers the changes are:
- 93 Codes added (new subjects)
- 1 Code reactivated (was previously made inactive, now restored)
- 11 Codes were made inactive
- 68 Literals were updated (codes remain the same, definition tweaked)
The general expectation is that the industry will update their records – including backlist -- to reflect these changes. BISAC Subjects are designed to support retailers and as a list represents a snapshot of what a retailer needs to know, today. By updating your records yearly you ensure retailers can make the best use possible of all your records. The above changes only represent 4% of the list. This year, unless you publish graphic novels or histories of Great Britain you likely won't have many changes.
Creators and users are reminded that 2015 represented a major change to the BISAC Subject Codes with the addition of specific support for Young Adult subjects. If you didn't update last year, don't put it off this one.
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
See more about using Thema here: Thema Subject Codes
BNC THEMA to BISAC Translator Updated
Released March 2016 – the translator supports BISAC 2015 to Thema version 1.1.
While each standard is updated yearly, BISAC releases a new version in Nov / Dec and Thema updates in March / April. This makes syncing the two standards problematic. The translator is updated based on word done by BISG in January and February making it out of date foe Thema around the same it's released. Care should be taken to try to incorporate changes to Thema on with it's yearly release.
Read more here:
Active 979 ISBN-13s are in BiblioShare now
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.
Any company with a report based on ISBN-10 (Mother BookNet knows they're out there still and doesn't judge) should convert it to an ISBN-13 based one. Up to now you could still convert a 978 ISBN-13 to a unique ISBN-10 but you can't do that with a 979 ISBN-13 – there is no corresponding ISBN-10 to a 979 ISBN-13.
It is recommended that all companies test their systems to ensure that they really are ready for 979 ISBNs – funny things can happen when your primary identifier starts with new digits.
Best Practices for Product Metadata: Guide for North American Data Senders and Receivers
June 2015 – NEW EDITION RELEASED
A joint BookNet Canada / BISG document that defines the 32 most important pieces of data exchanged in the North American market, provides detail for ONIX 2.1 and 3.0 and offers advice on all product types including print and digital.
It and the EDItEUR ONIX for Books Implementation and Best Practice Guide for ONIX 3.0 (which can be used as a reference to understand many aspects of ONIX 2.1) should be the primary documents used by anyone using or implementing ONIX in North America.
Best Practices for Identifying Digital Products updated
An excellent document from 2011 is fully updated and made clearer and more specific.