On TitlePage a block update using ONIX 3.x allows publishers to send updates for only specific sections ("blocks") of a product record rather than resending the entire record. When a block update is received, TitlePage replaces the data in the supplied block while leaving all other previously supplied product data unchanged.
Who this is for
This article is for users responsible for managing the data feeds for publishers or distributors who upload ONIX files to TitlePage and want to:
- Understand ONIX's block update capability.
- Use block updates to update their TitlePage catalogue.
What is a block update for TitlePage?
In ONIX 3.x, a block update is a method that allows publishers to update only specific sections ("blocks") of a product record rather than resending the entire ONIX record. The product record is divided into 8 defined blocks. When a block update is submitted it contains only the blocks that require updating, leaving the rest unchanged.
This is commonly used when you wish to update only one field, such as availability, while leaving the rest of the bibliographic data unchanged.
A full product record must be available on TitlePage before block updates can be processed. Block updates cannot be used to create a new product.
Why block updates are used
Block updates are designed to reduce file sizes and processing time by allowing senders to transmit only the metadata that has changed.
They are also useful when data originates from multiple systems, enabling for example bibliographic data (blocks 1 to 5) to be sent from one system and supply data (block 6) from another.
How to format an ONIX file as a block update
A block update ONIX 3.x file uses the standard ONIX message structure, consisting of a Header followed by one or more Product records.
Within each Product record, NotificationType must be set to 04 (block update), and the record must include the product identifier (for example, ISBN) together with only the block or blocks being updated.
When TitlePage receives a record with NotificationType 04, it replaces any previously stored data in the supplied blocks and retains all other existing product data.
Because the supplied block fully replaces the previously stored version, the entire block must be included in the update, as any elements not provided may be removed during processing.
Further information is available in the EDItEUR application note on block updates.
Related articles
- ONIX Update Workflows, an overview of all the ways to update your catalogue
- Complete Reload and Record Reset, which supports block updates in a split workflow
- ONIX Versions, requirements, codelists, the ONIX versions TitlePage supports
Further information
For further information please contact TitlePage support.