| Table of Contents |
|---|
...
- 93 Codes added (new subjects)
- 1 Code reactivated (was previously made inactive, now restoresrestored)
- 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 released 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 – 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 if it off this one.
When to should a publisher update their list is always a question as if : If a trading partner hasn't updated their system data can be lost. Generally , or sometimes the record won't get loaded, so it's good to give retailers time to up and generally publishers updating by Spring Feb / March is fairly safe, but if my . If you've coded your biggest title carried a new code 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
...
- 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)
...