For more information, membership details, to share ideas, thoughts, queries etc.
A simple guide for new users of ONIX.
Browse the ONIX code lists, or search for a specific term within the vocabularies. This browser is is available on the EDItEUR website, here.
Gain an overview of the small number of additions and minor changes made in ONIX 3.0 revision 5.
As detailed, below, a survey was carried out in early 2018 for all stakeholder organisations in the UK book industry that either send or receive (or both) data via ONIX to complete. The survey was open to ONIX 2.1 and ONIX 3.0 users alike. The responses received have helped BIC to gain an informed understanding of how and where the ONIX 3.0 standard is being adopted, what (as applicable) the obstacles to implementation are, what benefits organisations have derived from implementing ONIX 3.0 and so on.
What was the Purpose of the Survey?
This survey was for all stakeholder organisations in the UK book industry that either send or receive (or both) data via ONIX to complete - whether using ONIX 3.0 or not. Your participation helped BIC gain an informed understanding of how and where the ONIX 3.0 standard is being adopted, what (as applicable) the obstacles to implementation might be, what benefits organisations have derived from implementing ONIX 3.0 and so on.
What about organisations using ONIX 2.1?
Organisation using ONIX 2.1 (but not ONIX 3.0) were also eligible to participate on the survey.
What will we do with the survey results?
We may use the information provided by participants of this survey to create an industry report with regards the current UK ONIX 3.0 landscape that will be published on our website – particpants were asked for their consent (on behalf of their organisation) regarding this towards the end of the survey.
Participants that both send and receive data were encouraged to complete both surveys, which each contained 32-35 questions, consisting mainly of multiple-choice tick boxes, and should each have taken approximately 5-10 minutes to fill in.
Responses to these survey(s) were only accepted via SurveyMonkey.
Thank you very much to those who responded and/or contributed to the surveys.
This document summarises the additions and minor changes made in ONIX 3.0 revision 4.
This document summarises the additions and minor changes made in ONIX 3.0 revision 3.
This new message is intended to be used as a response to being in receipt of a conventional ONIX for Books message. The recipient can send an acknowledgement message back to the original sender simply to confirm receipt, to report successful processing, or to report any errors encountered. The use of this message is entirely optional but its use could end that 'falling into a black hole' feeling that senders sometimes get after they've sent out their data file.
For detailed core documentation, please see EDItEUR's website here.
This set of FAQs was originally compliled by Graham Bell of EDItEUR in June 2011 to explain how ONIX (and in particular ONIX 3.0) can be used to describe digital products. It has now been amended accordingly.
ONIX 3.0 was developed specifically to facilitate the description of data about digital content which has not been fully possible in earlier versions. This document, although it will also be helpful to those needing to describe digital metadata using ONIX 2.1, is designed to encourage the adoption of ONIX 3.0 and promote the benefits which will flow to the whole supply chain by doing so.
For any organisation using ONIX 2.1 after sunset and relying on the online DTD and XSD files provided by EDItEUR, some active steps to avoid failures in production systems will be necessary.
EDItEUR has now published a note describing the workaround you need to put in place to avoid failures in processing ONIX 2.1 files after sunset.
This document summarises the additions and minor changes made in ONIX 3.0 revision 2.
This document summarises the additions and minor changes made in ONIX 3.0 revision 1.
ONIX version 3.0 has now been published, representing a major step forward for the ONIX standard. The new release has been developed to address perceived shortcomings of the previous versions, especially for the description of digital products and publishers' marketing collateral, but also for the handling of multi-volume sets and series and to enable the blocking of records to permit more efficient updating. The new version is not backwards compatible with previous versions and the opportunity has been taken to remove elements which had become deprecated as a result of previous updates and revisions.
Introduction to ONIX for Books 3.0.
To see the full documentation for ONIX 3.0, click here.
The BIC Product Metadata Guidelines are intended primarily to help UK publishers in the preparation of ONIX data feeds, by setting out notes on data element inclusion and usage which have been reviewed and agreed by the BIC Product Metadata Group and in particular by the principal aggregators of UK book trade product information: BDS, Bowker and Nielsen.
The guidelines have been updated in 2011 to bring them more closely into line with international guidelines published by EDItEUR.
This document includes code lists applicable to ONIX release 3.0.2.
This set of FAQs has been compiled by Graham Bell of EDItEUR to explain how ONIX (and in particular ONIX 3.0) can be used to describe digital products. ONIX 3.0 has been developed specifically to facilitate the description of data about digital content which has not been fully possible in earlier versions. This document, although it will also be helpful to those needing to describe digital metadata using ONIX 2.1, is designed to encourage the early adoption of the new version and promote the benefits which will flow to the whole supply chain by doing so.
Book Industry Communication is a company registered in England and Wales. Company number 2589185.