In December 2021, Graham Bell, Executive Director of EDItEUR, posted a list of the top ONIX issues that cause the most problems for data suppliers. This list is an essential resource for ONIX trading partners to consider as they create and consume records and feeds.
This listicle is posted as an “Application Note” for the ONIX 3.0 Specification and is available with other Notes on the EDItEUR website at https://www.editeur.org/93/Release-3.0-Downloads/#How%20to .
Want to stay on top of ONIX implementation issues in a global discussion led by EDItEUR? Join the group at https://groups.io/g/onix .
Here’s Graham’s list, in ascending order:
12. Recipient requirements to omit certain data fields
11. Ignoring key data that is provided correctly
10. Ignoring repeats of common composites
9. Reading only one <ProductSupply> (market), or only one <Price>
8. Requirements to use non-standard codes, or worse, non-standard fields… (…or to add specific “codewords” into particular fields, often in order to support some business process or sales model)
7. “We support only the following codes” AKA '“data submission guidelines”
6. Not using “statement” fields like contributor statement and ‘rolling their own’ display fields algorithmically
5. Failure to process updates, or a tendency to stop updates at some point in the lifecycle
4. Creating “author pages” by matching names and not making use of publisher IDs or ISNIs
3. Online retailers failing to display mandatory safety information
2. Lack of transparency, consistency and feedback
1. Still demanding ONIX 2.1
Read the complete document below or at https://www.editeur.org/files/ONIX 3/APPNOTE Twelve ONIX problems 2.pdf