...
Speak to your ONIX solution provider for your print titles (can be either external or in-house). Share the August 28, 2020 deadline with them and ask whether your systems are 3.0 ready. If not, when will you be able to produce 3.0 files for your print titles?
Key questions:
Does your provider understand the differences between ONIX 2.1 and 3.0?
Does your system do validation on the data/files it produces?
Which version of ONIX does your system support? (The current version, as of April 2020, is 3.0.7.)
Tip 1: Check which ONIX version your system uses
Which version of the codes lists are being used and how often are they updated? (The current version of the list, as of April July 2020, is Issue 4950.)
Tip 2: Check if your system’s code lists are updated
Does your system support "production feeds"?
Does your system have the ability to send updates only (a.k.a. deltas) as well as full files?
Will your system be able to support both 2.1 and 3.0 feeds by the deadline?
Note: The expectation is that data providers will need to support both 2.1 and 3.0 feeds for an indeterminate period of time, until all data recipients have transitioned to 3.0 feeds.
Review the list of essential resources and start reading!
Create a test 3.0 file from your system.
This is not converting ONIX 2.1 data to ONIX 3.0 but rather mapping data you prepared and gathered previously to the new version.
Tip 3: Why you can’t just convert 2.1 to 3.0
ONIX 3.0’s data points and how they are organized are unique and distinct from 2.1.
Tip 4: There are critical differences between ONIX 2.1 and 3.0
Do an internal review and assessment of your initial 3.0 file.
Tip 5: What to consider when doing an assessment of your 3.0 file
Collaborate with your colleagues in different departments and roles to identify opportunities and workflow enhancements to collect and organize additional data points.
For instance;
your editorial colleagues can source additional information to flesh out the contributor composite;
your production colleagues can inform you of any special features of the book;
your sales colleagues can provide information on comparable titles;
your marketing and publicity colleagues can provide information on any marketing initiatives; and
your distribution colleagues can provide information on any territorial sales information.
Tip 6: Expect to have new and useful metadata options to support
Identify the data points you currently do not support and need to collect and disseminate. Identify these to your ONIX solution provider and have them make updates to support the collection and distribution of these data points in your 3.0 files.
Make sure to include BiblioShare in your data distribution plans. Start sending data to us to test your systems. Review and apply any feedback.
Generate a test file for a primary recipient partner to test and validate. Ask for feedback. Review and apply feedback from primary recipient partner. Repeat until you are both satisfied with the resulting file and data.
Tip 7: Final considerations
Advise your other trading partners that you can now send ONIX 3.0 files and request a transition timeline. Do not stop sending your ONIX 2.1 file until you and your trading partners are sure everything is working properly.
...