Versions Compared

Old Version 56

changes.mady.by.user Tom Richardson

Saved on

compared with

New Version 57

changes.mady.by.user Tom Richardson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

  • 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
 

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

 

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:  

...

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

...

  • 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)

...