Multiple-item collection, retailed as separate parts Multiple-component product retailed as a whole Sender must ensure the does not match any previously-sent live product record Record may be processed for test purposes, but data should be discarded when testing is complete. Sender must ensure the matches a previously-sent Test record Notice of acquisition of a product, by one publisher from another: sent by the acquiring publisher
Notice of sale of a product, from one publisher to another: sent by the publisher disposing of the product A Delete instruction is used ONLY when there is a particular reason to withdraw a record completely, eg because it was issued in error Note that a Delete instruction should NOT be used when a product is cancelled, put out of print, or otherwise withdrawn from sale: this should be handled as a change of Publishing status, leaving the receiver to decide whether to retain or delete the record. Use when sending an instruction to delete a record which was previously issued. In previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete record with the newly-received data
A block update implies using the supplied block(s) to update the existing record for the product, replacing only the blocks included in the block update, and leaving other blocks unchanged – for example, replacing old information from Blocks 4 and 6 with the newly-received data while retailing information from Blocks 1–3 and 5 untouched. In ONIX 3.0 only, use when sending a ‘block update’ record. Use for a complete record issued to confirm advance information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date Use for a complete record issued to confirm advance information approximately six months before publication or for a complete record issued after that date and before information has been confirmed from the book-in-hand Use for a complete record issued earlier than approximately six months before publication Text in red highlights new entries in this Issue. Text in blue highlights revised descriptions or notes in this issue.
Notes on the meaning and usage of the code value.Code label, often used for display of coded data.Zero for all lists which were added before Issue 1, and for any lists for which values have not yet been assigned. The number of the Codelist Issue in which the list was added.
The complete set of code list entries is also available in comma-separated, tab-separated, JSON and XML formats, as well as in multiple HTML files, and as XSD, RNG or DTD files integrated into the relevant XML schemas. While these limitations are not fully validated using the accompanying XML schemas, they may be rejected by enhanced validation in the future. Occasionally, a handful of codes within a particular list are defined as either deprecated, or not valid for use in a particular version of ONIX or with a particular data element. For details of which code list to use with which data element in each version of ONIX, please consult the main Specification for the appropriate release. Codes added since issue 36 are not valid for use in earlier versions of ONIX. This document does not differentiate explicitly between codelists for ONIX 3.0 and those that are used with earlier releases, but lists and some individual codes used only with earlier releases have been removed. The codelists are arranged in a single table for reference and printing. They may also be used as controlled vocabularies independent of ONIX. This document contains ONIX for Books codelists Issue 52, intended primarily for use with ONIX 3.0. These codelists are also available within a multilingual online browser at.
ONIX 2.1 remains fully usable, using Issue 36 of the codelists or earlier, and Issue 36 continues to be available via the archive section of the EDItEUR website ( ).
A full license agreement (DOI: 10.4400/nwgj) that governs their use is available on the EDItEUR website.Īll ONIX users should note that this issue of the ONIX codelists does not include support for codelists used only with ONIX version 2.1.
ONIX for Books Codelists Issue 52 ONIX for Books Codelists Issue 52Īll ONIX standards and documentation – including this document – are copyright materials, made available free of charge for general use.