Table of Contents
| Table of Contents | ||
|---|---|---|
|
...
The experience of companies who have done the development to make a transition from 2.1 to 3.0 report that it's easier to do than they expected but it's sad and undeniable fact that many print publishers and retailers in North America have not made the transition yet. This means that anyone starting out has to at least consider supporting both ONIX 2.1 and 3.0.
Amazon's 3.0 request
Amazon has requested that all physical book ONIX feeds be submitted in ONIX 3.0 by December 31, 2020. No deadline has been specified for digital ONIX but it is already dominated by ONIX 3.0 and the expectation is that it will follow shortly thereafter. This request applies globally to all Amazon divisions. Watch for more announcements from other retailers and companies supplying data.
...
...
...
ONIX 2.1 is No Longer a Supported Standard
As of early 2017 the ONIX 2.1 will not be updated further. Codelist Issue 36 (released January 2017) is the final code list for this version and the only one required going forward. Not being supported does not mean it is not used. ONIX 2.1 can remain in use for however long two companies choose to continue to trade data using that version. In North America ONIX 2.1 continues to be used for many physical book metadata transfers, though this is an ever-changing landscape.
BookNet Canada continues to recommend:
- All data suppliers continue to support ONIX 2.1 for North American data transfer
- If you can support ONIX 3.0 in addition to ONIX 2.1 please do so and ensure trading partners are aware of the option. This will facilitate retailers and other aggregators developing ONIX 3.0 support
- No one should switch from ONIX 2.1 to ONIX 3.0 without first notifying their trading partners. We think you'll find that you will still need to support ONIX 2.1
- New implementations of ONIX have a hard decision: ONIX 2.1 will not be supported for much longer but it remains the practical choice in our market.
ONIX 3.0 users should update their code lists for Issue 37 and beyond. ONIX 2.1 users should use code list Issue 36 going forward.
If you need help, contact biblio@booknetcanada.ca.
ONIX is currently defined as: ONIX 3.0.7
Changes for ONIX 3.0.7.pdf October 31, 2019 adds a new
...
Amazon's 3.0 Request
Amazon has requested that all physical book ONIX feeds be submitted in ONIX 3.0 by December 31, 2020. No deadline has been specified for digital ONIX but it is already dominated by ONIX 3.0 and the expectation is that it will follow shortly thereafter. This request applies globally to all Amazon divisions. Watch for more announcements from other retailers and companies supplying data.
BookNet Canada has compiled supporting documentation at https://booknetcanada.atlassian.net/wiki/spaces/UserDocs/pages/1149894942/Transition+to+ONIX+3.0%3A+Essential+Resources+for+Data+Providers as well as a benchmarking / progress calendar for data providers at https://booknetcanada.atlassian.net/wiki/spaces/UserDocs/pages/1144129720/Transition%2Bto%2BONIX%2B3.0%2BCanadian%2BMarket%2BCountdown%2BCalendar.
ONIX is Currently Defined as ONIX 3.0.7
Changes for ONIX 3.0.7.pdf October 31, 2019 adds a new
- This is an addition of a new Block 7 Promotional details and it has new tags assigned as P.27
- It's placement in the ONIX tree is between Block 2 (Marketing & collateral) and before Block 3 (Content)
- The placement is logical as it's about book promotion and comes after marketing & collateral but there's no easy way to avoid it be out of numerical order as a block or P number.
- As expected the Block PromotionDetail cannot repeat (only Block 6 Product supply can repeat to allow for multiple market support) but it contains the PromotionalEvent composite that can repeat.
- This "Events" section is specifically about promotional events – book signings, author tours, media appearance – and transmitting information in advance of the event (The Block 1 P.8 Event section is for books about Events or Conferences)
- The Promotional Event composite can repeat for different events and each event has to have at least one composite but can contain multiple dates in an Event Occurrence section. The above documentation and the ONIX manual provide a full explanation.
...
Editeur.org has a number of papers describing the changes as well as an overview document Best Practice Guidelines that explain both what needs to be recorded and why.
Implementation LISTSERV
Join Yahoo Groups ONIX_IMPLEMENT email list
Their archive of messages goes back beyond 2000 and covers a wide range of topics. Correct ONIX usage may be a matter of correctly matching code list definitions but it often depends on a consensus between suppliers and end users. This can vary between markets (each country has its own flavour of ONIX) and this forum is where the consensus begins.
Canadian-specific questions can be sent to biblio@booknetcanada.ca and if necessary will be brought to the attention of the Bibliographic Committee (where Indigo is an active member).
...
ONIX 3.0 users should update their codelists using the list at https://ns.editeur.org/onix/en. ONIX 2.1 users should use code list Issue 36 (the final code list for this version and the only one required going forward).
Current North American Metadata is Defined by:
Version 3.0.7 -- Revision 7
ONIX Code List 49 ONIX_BookProduct_Codelists_Issue_49_Changes.pdf
Version 2.1.3 – Revision 3 (Revision 4 is largely about changes for Japan)
ONIX Code List Issue 36 is the last code list that should be used for ONIX 2.1
BISAC Subject Code list 2018 edition and Regional Themes
Thema Version 1.3.2 (last updated April 2019)
The overview of ONIX for Books at the Editeur website(Revision 4 is largely about changes for Japan)
ONIX Code List Issue 36 is the last code list that should be used for ONIX 2.1
BISAC Subject Code list 2018 edition and Regional Themes
Thema Version 1.3.2 (last updated April 2019)
The overview of ONIX for Books at the Editeur website.
Implementation LISTSERV
Join Yahoo Groups ONIX_IMPLEMENT email list
Their archive of messages goes back beyond 2000 and covers a wide range of topics. Correct ONIX usage may be a matter of correctly matching code list definitions but it often depends on a consensus between suppliers and end users. This can vary between markets (each country has its own flavour of ONIX) and this forum is where the consensus begins.
Canadian-specific questions can be sent to biblio@booknetcanada.ca and if necessary will be brought to the attention of the Bibliographic Committee (where Indigo is an active member).
Questions?
If you need help, contact biblio@booknetcanada.ca.