Versions Compared

Key

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

...

Data exchange is never static. Here are some recent changes to best practices and standards that the industry is implementing.

New addition to the Canadian Bibliographic Standard
January 2017

Date Recommendations for Canadian Publishers

ONIX 2.1 is now a completely static standard

January 2017

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.

...


...

ONIX Codelist Issue 37 – the first ONIX 3.0 only code release!

Released April 6, 2017.

The next code release, 38, is expected July 2017.  Requests related to Issue 38 should be passed to BookNet before May 5, 2017.

Remember: The ONIX 3.0 schema's Codelist files and the Codelist documentation files will no longer contain the ONIX 2.1 only codes lists and codes. Here's a  link to the ONIX 2.1 Release Archive where you can still access final version of ONIX 2.1.

For your reference:  Here is a list of the ONIX 2.1 only Codelists that were dropped from Issue 37 for ONIX 3.0:  
6, 7, 8, 10, 11, 26, 33, 35–40, 47, 52, 54, 56, 63, 75, 78, 94. 95, 101

These Issue 37 Codelists were modified to drop ONIX 2.1 only codes:
List 1 has had codes: 12, 13, 14 removed
List 51 codes: 14, 15, 36 removed

Additions and changes in Issue 37 (applies to ONIX 3.0 only):

This document list all changes added to Issue 3637:  ONIX_BookProduct_Codelists_Issue_3637_Changes.pdf.   There are number of important changes and reading  There are some special case additions and numerous changes made to the note section to clarify meanings.  Reading the full document is recommended but here are some encouraged.  Here are the 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 biblio@booknetcanada.ca if you have questions or concerns on this change. 

  • 65 Availability – a new code has been added "Not yet available, postponed indefinitely" this allows a forthcoming title to be listed as "forthcoming" when it's publication date is unknown in support of  List 64's code "03"
  • List 81 Product content type – modifications have been made to ensure that codes are not restricted to digital products.
  • List 93 Supplier Role includes 3 new codes for physical suppliers to support drop shipments and direct to end-customer support.
  • Accessibility support is improved with additional codes in List 196 and List 175

Stay current: Update your Codelists, schemas and documentation regularly

...

Complete listings of the ONIX codelists in PDF and HTML formats can be downloaded from the EDItEUR website:

Issue 36 stand

ONIX 2.1 documentation, codelists and schemas:  http://www.editeur.org/15/Archived-Previous-Releases

ONIX 3.0 documentation:

  • Issue 37 stand-alone codelist documentation as readable PDF or HTML, plus comma-separated, tab-separated, XML and JSON files
  • Issue 36 37 TXT, CSV, XML, JSON files for loading into your data management applications, and XSD, RNG, DTD schema modules for use with older existing XSD, RNG and DTD schemas
  • Issue 36 37 has also been incorporated into the the Specification  and and Best Practice Guide  documentation documentation packages for ONIX 3.0

Need help finding the documentation?  Finding and Using the ONIX Manual


...

New addition to the Canadian Bibliographic Standard
January 2017

Date Recommendations for Canadian Publishers

...

ONIX 2.1 is now a completely static standard

January 2017

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.

...

2016 BISAC Subject Codes

November 2016

...