Data exchange is never static. Here are some recent changes to best practices and standards that the industry is implementing.
ONIX Codelist Issue 35
Released October 28, 2016.
EDItEUR has released a new Codelist update, 35, and the next, 36, is expected January 2017. Requests related to Issue 36 should be passed to BookNet before November 25, 2016.
Changes:
This document list all changes added to Issue 35: ONIX_BookProduct_Codelists_Issue_35_Changes.pdf. Here are some highlights:
- List 22 Language role code (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 (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 (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.
Please contact biblio@booknetcanada.ca if you have questions or concerns on this change.
- Issue 35 stand-alone codelist documentation as readable PDF or HTML, plus comma-separated, tab-separated, XML and JSON files
- Issue 35 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 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
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 restores)
- 11 Codes were made inactive
- 68 Literals were updated (codes remain the same, definition tweaked)
For more information see the BISG Subject List, on-line reference and general information. The BISAC to Thema Mapping will be release later.
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 – 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 if off this one.
When to update is always a question as if a trading partner hasn't updated their system data can be lost. Generally publishers updating by Spring is fairly safe, but if my biggest title carried a new code I'd get confirmation that my partners were ready.
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:
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.
In short, nothing has changed for using ONIX 2.1, but it's now fully unsupported and formally static. One of the drivers for the transition to ONIX 3.0 will be companies' unwillingness to accept or trade using an unsupported standard. ONIX 2.1 is at that point. Having said that, North American metadata remains almost universally ONIX 2.1 based either because only ONIX 2.1 is supported or because what ONIX 3.0 files are available are "converted" from 2.1 without adding full ONIX 3.0 support (read more here)
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.
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.
What's New In Bibliographic Standards
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
February 2013
BISG Policy Statement POL-1101 -- Best Practices for Identifying Digital Products
An excellent document from 2011 is fully updated and made clearer and more specific.