ONIX Codelists Issue 52 released

,

Codelists Issue 52 for ONIX 3.0 has been released.* Complete listings of the ONIX codelists in PDF and HTML formats can be downloaded from the EDItEUR website:

  • Issue 52 stand-alone codelist documentation as readable PDF or HTML

  • Issue 52 TXT, CSV, XML, JSON files for loading into your data management applications

  • Issue 52 XSD, RNG, DTD schema modules for use with existing XML schema files (but note that it is better to download the latest 3.0.7 schemas since they incorporate a handful of small improvements)

  • The ‘strict’ XSD 1.1 with Issue 52 (the strict XSD must be updated each time there is a new issue of the codelists, as it includes some codelists within the XSD itself)

  • The online browser for the ONIX code lists at ns.editeur.org/onix has been updated to issue 52

Need help finding and using the documentation? Read this.

It should go without saying that everyone should review the document summarizing the changes and update their systems, but we’ve highlighted some changes of particular note for you below.

Product type

List 9 Product classification type, adds the following codes, both only valid in ONIX 3.0:

Code Label Note
13 HTSUS US HTS (or HTSA) commodity codes for import of goods into USA (10 digits, without punctuation). See hts.usitc.gov/current.
14 Schedule B US Schedule B commodity codes for export from USA (10 digits, without punctuation). See uscensus.prod.3ceonline.com.

Unpriced item

List 57 Unpriced item type, adds the following code, only valid in ONIX 3.0:

Code Label Note
07 Calculated from contents Price calculated as sum of individual prices of components listed as Product parts.

EDItEUR says that in this case, “all the individual components must be listed as Product parts (…) and must be available as products in their own right.”

To learn more about grouping products in ONIX, read this three-part blog series written by BookNet Canada’s standards guru Tom Richardson:

Website

List 73 Website role, adds the following codes, both only valid in ONIX 3.0:

Code Label Note
47 Publisher’s website for digital preservation The URL of the publisher’s preservation service, or a more specific URL for access to its preserved copy.
48 Third party website for digital preservation The URL of the preservation service (e.g. clockss.org, or a more specific URL for access to its preserved copy.

A note from EDItEUR: “The two codes above should be used both as a ‘flag’ to indicate a product or its contents have been lodged with a long-term digital preservation service, and to indicate which service. Multiple preservation services can be listed using multiple repeats of the composite.”

Product content type

List 81 Product content type, adds the following code, only valid in ONIX 3.0:

Code Label Note
43 Scripted pop-ups E-publication contains pop-ups or other functionality offering (e.g.) term definitions, cross-links or glossary entries. [Note this should not include (e.g.) dictionary functionality that is part of the reading system.]

Feature type

List 160 Resource feature type, adds the following codes:

Code Label Note
07 Resource alternative text <FeatureNote> is alternative text for the resource, which might be presented to visually-impaired readers.
08 Background colour of image resource <FeatureNote> is a 24-bit RGB or 32-bit RBGA colour in hexadecimal, e.g. fff2de for an opaque warm cream. Used when the resource — for example a 3D image of the product — includes a background, or if used with an alpha channel, when the image is irregularly shaped or contains a semi-transparent shadow thrown against a background.
09 Attribute of product image resource <FeatureNote> is an ONIX code from List 256 that describes an attribute of a product image resource (e.g. perspective, content).
10 Background colour of page <FeatureNote> is a 24-bit RGB colour in hexadecimal, e.g. ffc300 for a rich yellow-orange, used when the resource supplier requests a specific background colour be displayed behind the resource on a web page.

Resource feature

List 256 Resource feature type, adds the following codes:

Code Label Note
01 Image shows product in packaging Image shows retail product only, in packaging.
02 Image shows product (without packaging) Image shows retail product only, without packaging.
03 Image shows product and accessories Image shows product (with or without packaging) and accessory items not included with product.
04 Image shows assembled product Image shows product in final form (e.g., an assembled toy or model, completed puzzle).
05 Image shows assembled product Image shows product in final form (e.g., an assembled toy or model, completed puzzle).
06 Image shows multiple products Image shows multiple copies of the product, or multiple related products.
07 Image shows detail of product Image shows part of product, for example inside pages of a book or detail of part of a toy.
21 3D perspective ‘front’ Shows front cover, spine and possibly top edge of pages (or equivalent for non-book products or packaging).
22 3D perspective ‘back’ Shows back cover, spine and possibly top edge of pages (or equivalent for non-book products or packaging).
23 3D perspective ‘front foredge’ Shows front cover, foredge and possibly top edge of pages (or equivalent for non-book products or packaging).
24 3D perspective ‘back foredge’ Shows back cover, foredge and possibly top edge of pages (or equivalent for non-book products or packaging).
47 3D perspective ‘horizontal’ Product is horizontal (e.g. lying on table).
48 3D perspective ‘vertical’ Product is vertical (e.g. standing on table).

For a typical 3D image of a book, codes 21–24 define which “corner” of a product is closest to the “camera” — for example code 21 indicates the upper left corner of the front cover (for a conventionally-bound book, and note this can (at least theoretically) be extended to 22 other corners, edges or faces if necessary).

A photo of an orange hardcover book.

For this image, the various codes might be combined like this:

<ResourceFeature>
 <ResourceFeatureType>08</ResourceFeatureType>                 <!-- background colour -->
 <FeatureValue>FFFFFF<FeatureValue>                                         <!-- white -->
</ResourceFeature>
<ResourceFeature>
 <ResourceFeatureType>09</ResourceFeatureType>
 <FeatureValue>02<FeatureValue>                                     <!-- product only -->
</ResourceFeature>
<ResourceFeature>
 <ResourceFeatureType>09</ResourceFeatureType>
 <FeatureValue>21<FeatureValue>            <!-- top left corner of cover in foreground -->
</ResourceFeature>
<ResourceFeature>
 <ResourceFeatureType>09</ResourceFeatureType>
 <FeatureValue>48<FeatureValue>                               <!-- product is vertical -->
</ResourceFeature>

*A note to ONIX 2.1 users

ONIX 2.1 users should note that codelist updates no longer apply to ONIX 2.1 and users should continue to use Issue 36. ONIX 3.0 code lists and schema modules no longer contain codes or lists unique to ONIX 2.1. You can still obtain the correct ONIX 2.1 schema and codelists from the Archived Previous Releases page.

BookNet Canada still recommends that you use and periodically update your copy of EDItEUR’s best practices guide. It’s an essential ONIX 3.0 guide, but much of the information in it applies equally to ONIX 2.1.

BookNet would like to pause, catch its breath, and note to ONIX 2.1 users that there’s now a full decade — 10 years — of new development available to users in ONIX 3.0. You should be considering what your systems need to support. ONIX 3.0 is easier to develop than you think, and it supports greater accuracy and detail in all aspects of data trading. Read more BNC blog posts on ONIX & bibliographic standards here.

Tagged: ,

Subscribe to BookNet’s weekly eNews

Sign up with your email address to receive news and updates every Tuesday.

You can unsubscribe at any time. We respect your privacy.

Latest

See all latest posts