This article provides guidance on supported ONIX versions, current codelists, and required metadata, so your ONIX files align with TitlePage and industry standards.
Who this is for
This information is for technical contacts at publishers and distributors who maintain or upload feeds to TitlePage, and need to know about:
- The current TitlePage codelist version.
- Checking that their ONIX file is working correctly.
- Requesting feedback from APA staff.
Current codelist
TitlePage currently supports codelist revision 71. Information about this release is available on the EDItEUR website.
Current ONIX specifications
TitlePage supports the full scope of the ONIX 3.1 standard, with continuing support for ONIX 3.0. TitlePage also provides limited legacy support for ONIX 2.1.
TitlePage ONIX requirements
All ONIX files submitted to TitlePage must comply with the EDItEUR standards for ONIX 3.x. Any additional TitlePage-specific requirements that extend beyond the EDItEUR standard are detailed in the TitlePage ONIX Data Elements sheet.
Where elements or composites are marked as optional on the Data Elements sheet, individual fields within them may still be mandatory if the composite is supplied. Publishers must ensure compliance with these internal requirements when providing metadata.
All files submitted to TitlePage must successfully pass EDItEUR XSD validation. See the validation article for further details.
TitlePage does not accept the ONIX short tag format. The Reference Name tag must be used in all cases.
TitlePage update requirements
Keeping records accurate and current is a requirement for all TitlePage contributors. Record currency is monitored using the Last Modified Date displayed on each product record, helping ensure that contributors update their metadata regularly.
As a minimum, the TitlePage User Agreement requires records to be updated at least once per week for contributors with large title volumes, or at least once per month where records are maintained manually.
As best practice, records should be updated as soon as practicable after any changes to the product data.
ONIX 2.1 support
TitlePage provides limited legacy support for ONIX 2.1. The subset of ONIX 2.1 fields accepted by TitlePage is available on the accompanying ONIX 2.1 fields sheet.
Any publisher still operating in ONIX 2.1 should upgrade as soon as possible. With the release of newer ONIX standards, ONIX 2.1 is now considered obsolete and is no longer actively supported across the industry.
Further information
For further information please contact TitlePage support.