ONIX for Books Codelists Issue 52
Total Page：16
File Type：pdf, Size：1020Kb
ONIX for Books Codelists Issue 52 25th January 2021 DOI: 10.4400/akjh Go to latest Issue All ONIX standards and documentation – including this document – are copyright materials, made available free of charge for general use. A full license agreement (DOI: 10.4400/nwgj) that governs their use is available on the EDItEUR website. All 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 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 (https://www.editeur.org/15/Archived-Previous-Releases). These codelists are also available within a multilingual online browser at https://ns.editeur.org/onix. Codelists are revised quarterly. Layout of codelists This document contains ONIX for Books codelists Issue 52, intended primarily for use with ONIX 3.0. They may also be used as controlled vocabularies independent of ONIX. The codelists are arranged in a single table for reference and printing. This document does not differentiate explicitly between codelists for ONIX 3.0 and those that are used with earlier releases, but lists used only with earlier releases have been removed. Codes added since issue 36 are not valid for use in earlier versions of ONIX. 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. 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. While these limitations are not fully validated using the accompanying XML schemas, they may be rejected by enhanced validation in the future. 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 schemas. ONIX for Books Codelists Issue 52 Codelist headers These are laid out with three columns: 1. Codelist number 2. List name 3. The number of the Codelist Issue in which the list was added. Zero for all lists which were added before Issue 1, and for any lists for which values have not yet been assigned. Codelist entries These are laid out in five columns: 1. Code value used in ONIX message data 2. Code label, often used for display of coded data 3. Notes on the meaning and usage of the code value 4. The number of the Codelist Issue in which the entry was first added. Zero for all codes which were added before Issue 1 5. The number of the Codelist Issue in which the description or notes were most recently revised, and blank for entries that have never needed revision Color coding Text in red highlights new entries in this Issue. Text in blue highlights revised descriptions or notes in this issue. Codelists Issue 52 Value Label Notes Iss Rev List 1 Notification or update type 0 01 Early notification Use for a complete record issued earlier than approximately 0 six months before publication 02 Advance notification Use for a complete record issued to confirm advance 0 (confirmed) 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 03 Notification confirmed on Use for a complete record issued to confirm advance 0 11 publication information at or just before actual publication date, usually from the book-in-hand, or for a complete record issued at any later date 04 Update (partial) In ONIX 3.0 only, use when sending a ‘block update’ 0 42 record. 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 previous ONIX releases, and for ONIX 3.0 using other notification types, updating is by replacing the complete record with the newly-received data 2 ONIX for Books Codelists Issue 52 Value Label Notes Iss Rev 05 Delete Use when sending an instruction to delete a record which 0 was previously issued. 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. A Delete instruction is used ONLY when there is a particular reason to withdraw a record completely, eg because it was issued in error 08 Notice of sale Notice of sale of a product, from one publisher to another: 2 sent by the publisher disposing of the product 09 Notice of acquisition Notice of acquisition of a product, by one publisher from 2 another: sent by the acquiring publisher 88 Test update (Partial) ONIX 3.0 only. Record may be processed for test purposes, 26 but data should be discarded when testing is complete. Sender must ensure the <RecordReference> matches a previously-sent Test record 89 Test record Record may be processed for test purposes, but data 26 should be discarded when testing is complete. Sender must ensure the <RecordReference> does not match any previously-sent live product record List 2 Product composition 9 00 Single-component retail 9 39 product 10 Multiple-component retail Multiple-component product retailed as a whole 9 39 product 11 Multiple-item collection, Used only when an ONIX record is required for a collection- 9 39 retailed as separate parts as-a-whole, even though it is not currently retailed as such 20 Trade-only product Product available to the book trade, but not for retail sale, 9 39 and not carrying retail items, eg empty dumpbin, empty counterpack, promotional material 30 Multiple-item trade-only Product available to the book trade, but not for general 9 39 pack retail sale as a whole. It carries multiple components for retailing as separate items, eg shrink-wrapped trade pack, filled dumpbin, filled counterpack 31 Multiple-item pack Carrying multiple components, primarily for retailing as 21 39 separate items. The pack may be split and retailed as separate items OR retailed as a single item. Use instead of Multiple-item trade-only pack (code 30) if the data provider specifically wishes to make explicit that the pack may optionally be retailed as a whole List 3 Record source type 0 00 Unspecified 0 01 Publisher 0 02 Publisher’s distributor Use to designate a distributor providing primary 0 46 warehousing and fulfillment for a publisher or for a publisher’s sales agent, as distinct from a wholesaler 03 Wholesaler 0 04 Bibliographic agency Bibliographic data aggregator 0 05 Library bookseller Library supplier. Bookseller selling to libraries (including 0 academic libraries) 3 ONIX for Books Codelists Issue 52 Value Label Notes Iss Rev 06 Publisher’s sales agent Use for a publisher’s sales agent responsible for marketing 4 the publisher’s products within a territory, as opposed to a publisher’s distributor who fulfills orders but does not market 07 Publisher’s conversion Downstream provider of e-publication format conversion 15 service provider services (who might also be a distributor or retailer of the converted e-publication), supplying metadata on behalf of the publisher. The assigned ISBN is taken from the publisher’s ISBN prefix 08 Conversion service Downstream provider of e-publication format conversion 15 provider services (who might also be a distributor or retailer of the converted e-publication), supplying metadata on behalf of the publisher. The assigned ISBN is taken from the service provider’s prefix (whether or not the service provider dedicates that prefix to a particular publisher) 09 ISBN Registration 18 Agency 10 ISTC Registration Agency 18 11 Retail bookseller Bookseller selling primarily to consumers 28 12 Education bookseller Bookseller selling primarily to educational institutions 28 13 Library Library service providing enhanced metadata to publishers 36 or other parties List 5 Product identifier type 0 01 Proprietary For example, a publisher’s or wholesaler’s product number 0 or SKU. Note that <IDTypeName> is required with proprietary identifiers 02 ISBN-10 International Standard Book Number, pre-2007 (10 digits, 0 14 or 9 digits plus X, without spaces or hyphens) – now DEPRECATED in ONIX for Books, except where providing historical information for compatibility with legacy systems. It should only be used in relation to products published before 2007 – when ISBN-13 superseded it – and should never be used as the ONLY identifier (it should always be accompanied by the correct GTIN-13 / ISBN-13) 03 GTIN-13 GS1 Global Trade Item Number, formerly known as EAN 0 9 article number (13 digits, without spaces or hyphens) 04 UPC UPC product number (12 digits, without spaces or hyphens) 0 05 ISMN-10 International Standard Music Number, pre-2008 (M plus 0 14 nine digits, without spaces or hyphens) – now DEPRECATED in ONIX for Books, except where providing historical information for compatibility with legacy systems. It should only be used in relation to products published before 2008 – when ISMN-13 superseded it – and should never be used as the ONLY identifier (it should always be accompanied by the correct GTIN-12 / ISMN-13) 06 DOI Digital Object Identifier (variable length and character set 0 beginning ‘10.’, and without https://doi.org/