...
EDItEUR clarified List 150 (ONIX 3.0 only, Use List 7 for ONIX 2.1) Product Form codes for multiple product entries to allow a better distinction between multi-item products (X* codes) and multi-component products (S* codes). The former, "item," is typically is broken down by the retailer and the items sold as individual products to clients (think a dump bin or a box of 10 copies of a book) while the latter, "component," are separate pieces that are described as products (and may even be available individually) but for this ISBN are sold as a group sold single unit to the end client (think a book and toy packagespackage). In either case Product Parts entries are provided to describe the individual item or component.
List 25 Illustrations and other content type, now now has a code for Table of Contents (joining codes for glossary, bibliography and index). While there are other ways in ONIX to embed or link to the book's TOC, this supports a way to code in within the metadata that the book has one. (NOTE: This addition While List 25 exists in ONIX 2.1 this additional code applies only to ONIX 3.0 as all . All the Code Lists for ONIX 2.1 remain at Issue 36 permanently.)
Dates are better supported in two ways: First, the default date, code "00" or YYYYMMDD has been clarified as a Common Era date and the string/open text option, code "12" for complex dates has been clarified to include BCE dates. Second, a new Supply Date has been added – Expected warehouse date. This will work with the Expected availability date (aka Expected ship date), the date . The availability or ship date denotes when you expect to START shipping from your warehouse. The new warehouse date is the date you expect to first receive the product in your warehouse.
Finally a way to provide a A final addition worth noting provides for a "recommended display order to " as a List 197 collection entry. Collections can be described in a number of ways that variations of order, and each can enhance marketing , this fills on some collections. Retailers have highlighted this sort of information as something that can help them sell in series or sets and the new code fills in a gap.
What ties all these new codes changes together is that they all represent improvements to the accuracy and clarity available in ONIX. BookNet cannot stress enough the importance of using a full ONIX code list and reading the notes that accompany each list. If you can meet the high standard of accuracy that EDItEUR allows you to support be sure to let retailers know it that they can rely on your meticulous detail. BookNet always recommends using the most accurate dates and codes you can genuinely sustain and support.
Stay current: Update your Codelists, schemas and documentation regularly
...