Comparing ONIX 3.0 and 2.1 Codelists / Deprecated 2.1 Elements

ONIX 2.1 became static as of ONIX CodeList Issue 36 – see more information here.  There are 2 types of code lists relevant to that change. 

• Code lists that are unique to ONIX 2.1 that are replaced or made redundant by a separate code list or change unique to ONIX 3.0.  These code lists are already static with no change since 2014 or eariler.
• Code lists that are shared by ONIX 3.0 and ONIX 2.1.  These code lists are expected to end for ONIX 2.1 with Issue 36 and remain static thereafter.  Any development on these code lists for Issue 37 or beyond will only apply to ONIX 3.0.

The balance of the code lists are unique to ONIX 3.0 and not listed here.

A big caveat:  If EDItEUR set up a new code list it's because the "design" of ONIX data exchange has almost certainly changed.   This should NOT be used for mapping to ONIX 3.0 but can be used as a starting point to help you understand where the data stored in ONIX 2.1 has shifted to in 3.0.   You'll even find there are changes in code lists shared between 2.1 and 3.0 that predate those forced by ONIX 2.1 becoming static with Issue 36. 

Code lists in each version are distinct and should be treated as distinct.

ONIX 3.0 is a new standard with improved data handling and accuracy.  All (useful) data stored to support ONIX 2.1 will have a place in ONIX 3.0 but it might not be presented identically.  The mapping from your data set to ONIX 2.1 should be different than your mapping to ONIX 3.0 in many (but not all) cases.

ONIX 2.1 only code lists and their 3.0 only equivalent, including code lists that are withdrawn or redundant in ONIX 2.1

Graham Bell of EDItEUR answered a similar question (a request for a list of deprecated ONIX 2.1 elements) this way:

The simple answer is that none of the deprecated elements of ONIX 2.1 are present in 3.0. Deprecation is an indication that a particular field can be done a better way, even within 2.1, and most of the fields deprecated in 2.1 have preferred alternatives in 2.1. In almost all cases, it is these preferred alternatives that were then carried forward into ONIX 3.0. Thus, if your 2.1 has been updated to avoid the deprecated elements, the transition to using 3.0 is that much simpler – your system is half way there already.

There are nearly 50 deprecated elements in 2.1. I’ve listed them below, with their nearest equivalent in ONIX 3.0:

Deprecated element in 2.1 – equivalent field or composite in 3.0

AlternativeFormatEAN13 - use RelatedProduct composite

AlternativeFormatISBN - use RelatedProduct composite

AlternativeProductEAN13 - use RelatedProduct composite

AlternativeProductISBN - use RelatedProduct composite

Annotation - use TextContent composite

BookFormDetail - use ProductFormDetail

ConferenceDescription - no real equivalent in 3.0 (use TextContent to describe nature of product)

CopublisherName - use Publisher composite

CoverImageFormatCode - use ResourceVersionFeatureType

CoverImageLink - use ResourceLink

CoverImageLinkTypeCode - no equivalent, use URI in ResourceLink

DefaultLinearUnit - no default equivalent, use Measure composite

DefaultWeightUnit - no default equivalent, use Measure composite

Dimensions - use Measure composite

DistinctiveTitle - use TitleDetail composite

DOI - use ProductIdentifier composite

EAN13 - use ProductIdentifier composite

EAN13OfSet - use CollectionIdentifier composite

FormerTitle - use TitleDetail composite

Height - use Measure composite

InterestAge - use Audience composite

IntermediaryAvailabilityCode - use ProductAvailability

ISBN - use ProductIdentifier composite

ISBNOfSet - use CollectionIdentifier composite

ISMN - use ProductIdentifier composite

LanguageOfText - use Language composite

MainDescription - use TextContent composite

OriginalLanguage - use Language composite

OriginalPublisher - use Publisher composite

PrizesDescription - use PrizeStatement

PublisherProductNo - use ProductIdentifier composite

PublisherSeriesCode - use CollectionIdentifier composite

ReplacedByEAN13 - use RelatedProduct composite

ReplacedByISBN - use RelatedProduct composite

ReplacesEAN13 - use RelatedProduct composite

ReplacesISBN - use RelatedProduct composite

ReviewQuote - use TextContent composite

RightsRegion - use Territory within SalesRights composite with list of countries and regions

SeriesISSN - use CollectionIdentifier composite

SponsorName - use CorporateName within Sponsor composite

SupplyToRegion - use Territory with Market or SalesRights composite with list of countries and regions

TextCaseFlag - use textcase attributor

Thickness - use Measure composite

TranslationOfTitle - use TitleDetail composite

UPC - use ProductIdentifier composite

USSchoolsGrade - use AudienceRange composite

Weight - use Measure composite

Width - use Measure composite

AvailabilityCode (not actually deprecated, but *strongly* advised to update) - use PublishingStatus and ProductAvailability

One more note. There are a few fields in 2.1 that are used in two different ‘places’ in the data structure. They may be deprecated in one place, and not in the other. In this case, they do NOT appear in the list above. As an example, the ConferenceRole field is deprecated outside the Conference composite (PR.9.2), but is still mandatory and not in any way deprecated inside the Conference composite (PR.9.7).

Graham

Graham Bell