Data exchange is never static. Here are some recent changes to best practices and standards that the industry is implementing.
ONIX Codelist Issue 34
Released July 25, 2016.
EDItEUR has released a new Codelist update, 34, and the next, 35, is expected October 2016. Requests related to Issue 35 should be passed to BookNet well before August 26, 2016.
Changes:
This document list all changes added to Issue 34: ONIX_BookProduct_Codelists_Issue_34_Changes.pdf, Please have a look as there are a number of small changes, particularly to the notes section clarifying use. Development of the latest ONIX revision, 3.0.3 continues with:
- Deprecation of List 167 – Price Condition Type (ONIX 3.0 only) codes 10 and 12 for Rental duration and Rental extension.
The new with ONIX 3.0.3 Price Constraint structure supports this now. - List 145 Price Identifier Type (ONIX 3.0 only) now includes support for proprietary product price type and price point identifiers
- Support for EPUB 3.1 added to List 220 – E-publication format version number (ONIX 3.0 only)
Note that Issue 36 (January 2017) may be the last version of the codelists usable with ONIX 2.1. This timetable has been discussed by the ONIX International Steering Committee, but is not yet ‘set in stone’, so comments are invited – to graham@editeur.org. To be crystal clear, this does not mean ONIX 2.1 will be unusable after the beginning of 2017 – it means only that no further new codes will be added, even as a side-effect of adding them to ONIX 3.0. ONIX 2.1 would be ‘frozen’ with Issue 36 while ONIX 3.0 continues to receive quarterly codelist updates. This is part of the phased reduction of support for 2.1.
- Issue 34 stand-alone codelist documentation as readable PDF or HTML, plus comma-separated, tab-separated, XML and JSON files
- Issue 34 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 34 has also been incorporated into the Specification and Best Practice Guide documentation packages for ONIX 3.0
Need help finding the documentation? Finding the ONIX manual -- so many choices
The 2015 BISAC Subject Codes – MAJOR REVISION
December 2015
The Book Industry Study Group (BISG) has released the annual update of BISAC Subject Codes. The current version is now the 2015 edition and include documentations of the changes as well as cumulative list of changes, making it easy to see what’s new and needs attention.
This is a major revision as it introduces over 500 new BISAC Codes – 446 of which are a completely new section of Young Adult codes.
BISG has recommended that end users (not senders) implement the new code list by January 31, 2016. This is a short deadline for a big change. As of early January it appears that, while end users are aware of and working towards implementation, that not everyone will be able to accept the new codes by that date. Metadata senders should be aware that both the companies they are sending data to and the software they are using to create it might not support the new codes yet. We know from previous years that BISAC code changes can create loading issues if the end user is not prepared – normally that affects a small number of titles, but this could affect many. BNC BiblioShare can, and has received files supporting the new codes, but it has also received records where the sender applied new codes but the file arrived with "empty" subject code elements. Their software didn't (yet) support the value.
General recommendations for data senders:
- Publishers and other senders should update their datasets AFTER January 31, 2016. If possible update all records simultaneously
- Publishers should confirm with their most important accounts they are ready before beginning to send updates, particularly if a Buyer meeting is imminent.
- Publishers should re-send records affect monthly until they are confident that all recipients have fully absorbed them (likely May or June)
- Check your software and ONIX file to ensure it supports and that you are exporting codes as you expect.
Resources on this major change:
- BISG Subject List, on-line reference and other formats
- BISG has a mapping of the old JUV 2014 codes to their equivalent and now split JUV and YA 2015 codes and literals.
- A BNC Webinar with BISG Subject chair Connie Harbison was held on Thursday January 14. Link to webinar archive.
- BNC Blog post January 19, 2016
- BNC Blog post December 10, 2015
- BNC Blog post December 22, 2016
For more information including questions about how to use the codes email BookNet Canada at biblio@booknetcanada.ca
Thema version 1.2
Released April 2016
See more here:
BNC THEMA to BISAC Translator Updated
Released March 2016 – supports BISAC 2015 to Thema version 1.1
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.
BISG_Best_Practices_for_Product_Metadata_6.1.15.pdf
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.
BNC THEMA to BISAC Translator is released
Released April 2014 – a new version
Read more here:
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.