Nielsen Initial Notes on ONIX 3.0 Submissions in Q1 2010
Thursday, November 19th, 2009
ONIX 3.0
Notes for senders of ONIX 3.0 files to Nielsen Book, October 2009
Nielsen are working towards acceptance of ONIX 3 files from suppliers while continuing to accept series 2.* ONIX files for the foreseeable future. Our initial intention approach is to accommodate the variations and key additional elements in ONIX 3 into our existing database and products with minimal disruption. We will move to ONIX 3 outputs at a later stage in consultation with our data customers.
Work on ONIX 3 implementation is underway. We expect to be able to accept test files by the end of the year, and live files in Q1 2010.
Record Type “Block Updates”
In accordance with the statement of UK practice by the UK ONIX Group, Nielsen will accept EITHER Full Update Records as usual OR Block 6 (P&A updates) only, for initial implementation of ONIX 3; these may be mixed in the same file (the notification type is provided at record level) but we prefer separate files for each type.
Message Header
In accordance with the amended schema, Nielsen require ONIX3 files to include the mandatory ‘release’ attribute, with the value ‘3.0′ in the top-level element.
P5 Collection / P6 Product title detail
Nielsen will use Collection and Title data in existing fields on our database, and in products, to create well-formed title strings that avoid duplication of data.
P20 Global publishing status & dates / copyright
Nielsen will continue to recommend the statement of publishing status and publication date at item (global) level using P20, in addition to market-specific details as required. If a global publication date is not provided, we will use instead the market-specific date that matches the Country of Publication.
P21 Territorial rights and other sales restrictions
We are concerned about the introduced facility to state what rights DO NOT apply in a given territory with no requirement to state what rights DO apply. As we hold Rights information as a table, we need a clear indication of the situation (Non-Exclusive Rights, Exclusive Rights, or NFS) for each territory included.
We require senders, if using the “Countries Excluded” structure in a Sales right composite (eg Exclusive Rights for Word excluding US and Canada) to send an additional composite specifying the rights position for the excluding country/ies (eg NFS in US, non-exclusive rights in Canada, etc)
P22 Related works
Nielsen will expand our list of relation types to accommodate include links to Works identified by ISTC.
P24-26 Product Supply
We re-assert the position that met with general acceptance on a Listserv discussion in favour of mutually exclusive markets in Product Supply composites. Having overlapping markets (eg because one supplier serves two markets) is effectively organising the markets to fit the supplier. We can see this might be attractive for publishers, but for all recipients of the data, ie aggregators organising data for retailers in specific markets and retailers operating within specific territories, there is a strong requirement to receive all the supply data that is pertinent to a given market, including all suppliers to that market (rather than being presented with all markets that are served by each supplier).