Coming Changes in ONIX (2024/2025)

1 Changelog
2 Introduction
3 General note about compatibility
- 3.1 Introducing a new export-endpoint (v2)
4 Schedule / Status
5 Features / changes
- 5.1 Contributor Unnamed Persons Breaking change
- 5.2 Subject - Genre and form
- 5.3 Subject - Subjects
- 5.4 EUDR, FSC, PEFC, carbon emission
- 5.5 Contributor Role Code
- 5.6 Chapters in audio and ebooks
- 5.7 Device support Breaking change
- 5.8 Price condition (automatic renewed)
- 5.9 Collection (Norw. forlagsserie)
- 5.10 Text and data mining
- 5.11 GPSR - General Product Safety Regulation (EU)
- 5.12 Kulturrådets innkjøpsordninger (K-fond) Breaking change
- 5.13 Literary prizes
- 5.14 City of publication
- 5.15 Text content
- 5.16 Title type
- 5.17 From language
- 5.18 Contributor statement
- 5.19 Dewey Breaking change
- 5.20 Work as subject
- 5.21 Supporting resource - image of book’s back cover
- 5.22 Collection: original title
- 5.23 TextContent: short description
6 Onix 3.1

Changelog

Date

Date
Jun 17, 2025	Image of book-cover in production (v2)
Jun 12, 2025	Short description will be added to v2 only.
May 15, 2025	Image for book’s back cover will be added to v2
May 8, 2025	Work as subject will be added to v2
Apr 23, 2025	In v2: City of publication Accompanying material in TextContent Changes in text content New title types Contributor statement, from language added
Apr 9, 2025	Subject from NEO now in v2
Apr 3, 2025	Subjects will include language attribute, both for genre/form and subjects Reintroducing Literary prizes in v2
Mar 27, 2025	PriceCondition postponed until further notice. EUDR, FSC etc. moved to Q3 and v3-endpoint of Onix.
Feb 24, 2025	GPSR + Kulturrådet are now done
Jan 22, 2025	Introducing v2-endpoint for Onix Export. Most new features will be exclusive to the new v2-endpoint, see also deprecation-notice for v1.
Nov 29, 2024	Device support released in prod. Both methods supported until end-of-life for old syntax Feb 28, 2025
Nov 28, 2024	Collection type 11 released in stage/test Device support released in stage/test (both export and import) EUDR, FSC, PEFC, carbon emission support for EUDR is postponed, due to delays in the implementation of EUDR support for FSC, PEFC, carbon emission expected in Q2/2025
Nov 11, 2024	Contributor Unnamed Persons Released in stage/test In prod from Jan 31, 2025 EUDR, FSC, PEFC, carbon emission Delayed expected delivery Q2/2025 Contributor Role Code Released (except B34) Device support Delayed expected delivery dates Price condition Delayed expected delivery quarter Text and data mining Released
okt. 2024	Subject from NTSF released in addition to proprietary scheme Genre/form from Bokbasen’s proprietary scheme is sent in parallell, but will be deprecated.
Oct 25, 2024	“Chapters in audio and ebooks” deployed to test/stage “Text and data mining” deployed to test/stage

Introduction

To meet the customers demands for more metadata, we are releasing some changes at the end of 2024 / start of 2025. Note: Some of those are also breaking changes. Check the time-schedule.

We need your feedback by 20 October 2024 on when changes marked "critical change" can be handled.
If we do not receive feedback, this is interpreted as the changes being handled by you, and we follow the set schedule.

General note about compatibility

All changes are compatible with Onix 3.0 (covered by existing schema), and should therefore not break anything. We expect that customers will always handle that more and more fields are populated (as long as they are in the schema.

Introducing a new export-endpoint (v2)

When we introduce Onix 3.1 we see that we need a new endpoint to not break existing integrations.

All the new features will be available from export-endpoint “v2”. See dokumentation ONIX

Onix Export v1 - end of life Jun 30, 2025

We want all our customers to move to v2 to get all the new features, including Onix 3.1.

v1 is now deprecated and will be removed mid-summer 2025

Schedule / Status

Feature	Available from (endpoint version)	Status

Feature	Available from (endpoint version)	Status
Contributor Unnamed Persons import	Q4 2024	done
Contributor Unnamed Persons export	In prod from Jan 31, 2025 (only v2) Breaking change	done
Subject export	September 2024	done
FSC, PEFC, carbon emission, EUDR import	Q3 2025	not started
FSC, PEFC, carbon emission, EUDR export	Q3 2025	not started
Contributor Role Code import	November 2024	done
Contributor Role Code export	November 2024	done
Chapters in audio/text books export	January 2025 (only v2)	done
Device support import	Nov 30, 2024 End-of-life for old syntax Feb 28, 2025	done
Device support export	January 2025 (only v2) In stage from Dec 15, 2024 Breaking change	done
Collection (publisher) import	Q4 2024	done
Collection (publisher) export	Q4 2024 (only v2)	done
Price condition (automatic renewed) import	Q2 2025 Postponed until further notice	postponed
Price condition (automatic renewed) export	Q2 2025 Postponed until further notice	postponed
Text and data mining export	October 2024	done
Onix 3.1 import	Q2 2025	DOING
Onix 3.1 export	Jan 22, 2025 (only v2)	done
GPSR - General Product Safety Regulation (EU)	Q1 2025 (only v2)	Done
Kulturrådets innkjøpsordninger	Q1 2025 (only v2) Breaking change	Done
Subject from NEO	Q2 (only v2)	Done
Literary prizes	April 2025 (only v2)	Done
City of publication	April 2025 (only v2)	Done
Text content	April 2025 (only v2)	Done
Title type	April 2025 (only v2)	Done
Dewey	April 2025 (only v2) Breaking change	Done
From language	April 2025 (only v2)	Done
Contributor statement	April 2025 (only v2)	Done
Work as subject	May 2025 (only v2)	Done
Image of back cover	Q2, only v2	Done
Original title of collection	Q2, only v2	Done
Short description	Q3, only v2	DOING

Features / changes

Contributor Unnamed Persons Breaking change

Breaking Change

Only for export

Unnamed Persons allows positive indication of content generated by AI or where synthesised voices are used for audio content.

Unnamed Persons is part of the Contributor composite.

Unnamed Persons will be supported both for metadata to and from Bokbasen.

Unnamed Persons uses codes from List 19, combined with the element ContributorRole and codes from list 17.

Supported codes will be:

02 Anonymous (real person)
05 Synthesised voice - male
06 Synthesised voice - female
07 Synthesised voice - unspecified
08 Synthesised voice - based on real voice actor
09 AI (artificial intelligence)

<Contributor>
<SequenceNumber>1</SequenceNumber>
<ContributorRole>A01</ContributorRole>
<PersonNameInverted>Nordmann, Kari</PersonNameInverted>
</Contributor>
<Contributor>
<SequenceNumber>2</SequenceNumber>
<ContributorRole>A12</ContributorRole>

<UnnamedPersons>09</UnnamedPersons>
</Contributor>
<Contributor>
<SequenceNumber>3</SequenceNumber>
<ContributorRole>E07</ContributorRole>

<UnnamedPersons>05</UnnamedPersons>
</Contributor>

Subject - Genre and form

The Subject element contains classification from several different schemes.

Bokbasen will deprecate two proprietary vocabularies for literary form and genres, and replace them with terms from the official Norwegian thesaurus on genre and form (NTSF). The thesaurus is provided by the National Library of Norway.

All records will be updated with terms and URIs from NTSF.

Terms from NTSF will be supported in records from Bokbasen only.

Terms from proprietary vocabularies and NTSF will be included in records from Bokbasen in parallell to facilitate this transition

The Norwegian thesaurus on genre and form is identified by code C8 from list 27 in Subject Scheme Identifier.

Terms from the proprietary vocabularies was sent in Subject like this:
<Subject>
<SubjectSchemeIdentifier>24</SubjectSchemeIdentifier>
<SubjectSchemeName>Bokbasen_Form</SubjectSchemeName>
<SubjectHeadingText>Romaner</SubjectHeadingText>
</Subject>

<Subject>
<SubjectSchemeIdentifier>24</SubjectSchemeIdentifier>
<SubjectSchemeName>Bokbasen_Genre</SubjectSchemeName>
<SubjectHeadingText>Krim</SubjectHeadingText>
</Subject>

<Subject>
<SubjectSchemeIdentifier>24</SubjectSchemeIdentifier>
<SubjectSchemeName>Bokbasen_Form</SubjectSchemeName>
<SubjectHeadingText>Romaner</SubjectHeadingText>
</Subject>

<Subject>
<SubjectSchemeIdentifier>24</SubjectSchemeIdentifier>
<SubjectSchemeName>Bokbasen_Genre</SubjectSchemeName>
<SubjectHeadingText>Krim</SubjectHeadingText>
</Subject>

<Subject>
<SubjectSchemeIdentifier>C8</SubjectSchemeIdentifier>
<SubjectCode>https://id.nb.no/vocabulary/ntsf/25</SubjectCode>
<SubjectHeadingText language=”nob”>Romaner</SubjectHeadingText>
</Subject>

<Subject>
<SubjectSchemeIdentifier>C8</SubjectSchemeIdentifier>
<SubjectCode>https://id.nb.no/vocabulary/ntsf/159</SubjectCode>
<SubjectHeadingText language=”nob”>Krim</SubjectHeadingText>
</Subject>

Subject - Subjects

Bokbasen will deprecate the proprietary vocabulary for subjects, and replace them with terms from the official Norwegian thesaurus for subjects (NEO). The thesaurus is provided by the National Library of Norway, and will (if not delayed) be published 1st of April 2025.

All records will be updated with terms and URIs from NEO.

All records will contain terms in both Norwegian bokmål and Norwegian nynorsk. The language attribute will state the language.

Use the language attribute to choose which language you wish to use in your system / at your site.

Mapping from proprietary subjects to subjects from NEO will be provided.

More information will be posted here, when Bokbasen has more information about the publication date of NEO.

The Norwegian thesaurus for subjects is identified by code D3 from list 27 in Subject Scheme Identifier.

Terms from the proprietary vocabulary was sent in Subject like this:
<Subject>
<SubjectSchemeIdentifier>24</SubjectSchemeIdentifier>
<SubjectSchemeName>Bokbasen_Subject</SubjectSchemeName>
<SubjectHeadingText>Filosofi</SubjectHeadingText>
</Subject>

Both types will be sent for now, but “24”-block is now deprecated and will get an end-of-life date.

<Subject>
<SubjectSchemeIdentifier>24</SubjectSchemeIdentifier>
<SubjectSchemeName>Bokbasen_Subject</SubjectSchemeName>
<SubjectHeadingText>Naturvitenskap</SubjectHeadingText>
</Subject>

<Subject>
<SubjectSchemeIdentifier>D3</SubjectSchemeIdentifier>
<SubjectCode>https://id.nb.no/vocabulary/neo/1116</SubjectCode>
<SubjectHeadingText language=”nob”>Naturvitenskap</SubjectHeadingText>
</Subject>

<Subject>
<SubjectSchemeIdentifier>D3</SubjectSchemeIdentifier>
<SubjectCode>https://id.nb.no/vocabulary/neo/1116</SubjectCode>
<SubjectHeadingText language=”nno”>Naturvitskap</SubjectHeadingText>
</Subject>

EUDR, FSC, PEFC, carbon emission

Support for EUDR is postponed due to delays in the implementation of the regulation, and consequences for the Norwegian market.

Support for FSC, PEFC and carbon emissions will be added as planned.

ProductFormFeature and ProductFormFeatureType is used to indicate if a product is in compliance with EU deforestation regulations (EUDR), is FSC or PEFC certified, or information about a carbon emission scheme.

According to EUDR, provenance of raw material source plot must be stated using GPS coordinates. Publishers are expected to add both an identifier for a Due Diligence Record in the EU registry (DDS) and details of provenance of raw material for cover and body of the product.

Codes from list 79 Product form feature type identifies what type of information is sent in other subfields of ProductFormFeature.

Codes for FSC and PEFC certification: 30-36

Codes for carbon emission: 41-46

Codes for EUDR: 47-50

Due Diligence Statement

<ProductFormFeature>
<ProductFormFeatureType>50</ProductFormFeatureType>
<ProductFormFeatureValue>24FRXVV3VOS991</ProductFormFeatureValue>
</ProductFormFeature>

Provenance of raw material for cover

Example shows single GPS coordinate (latitude and longitude), denoting the centre of a 4Ha plot of land where the trees grew.

<ProductFormFeature>
<ProductFormFeatureType>48</ProductFormFeatureType>
<ProductFormFeatureValue>GB 202401</ProductFormFeatureValue>
<ProductFormFeatureDescription>51.544708 0.061076</ProductFormFeatureDescription>
</ProductFormFeature>

Provenance of raw material for body

Three or more GPS coordinates denotes a polygon outlining the forest where the trees grew.

<ProductFormFeature>
<ProductFormFeatureType>47</ProductFormFeatureType>
<ProductFormFeatureValue>GB 202311</ProductFormFeatureValue>
<ProductFormFeatureDescription>51.549040 -0.120975, 51.556838 -0.127326, 51.555092 -0.108261, 51.549040 -0.120975</ProductFormFeatureDescription>
</ProductFormFeature>

Contributor Role Code

Contributor role code is used to indicate the role played by a person or a corporate body in the creation of the product.

Support will be added for new codes from List 17 for both records to and from Bokbasen.

Code	Heading

Code	Heading
A15	Preface by
A19	Afterword by
A23	Foreword by
A36	Cover design or artwork by (children’s literature only)
A42	Continued by
A43	Interviewer
A44	Interviewee
B34	Sensitivity reader / editor

<Contributor>
<SequenceNumber>1</SequenceNumber>
<ContributorRole>A23</ContributorRole>
<NameType>04</NameType>
<NameIdentifier>
<NameIDType>01</NameIDType>
<IDTypeName>Bokbasen_ProprietaryID</IDTypeName>
<IDValue>90707439</IDValue>
</NameIdentifier>
<PersonNameInverted>Gaugin, Paul René</PersonNameInverted>
</Contributor>

Chapters in audio and ebooks

To facilitate navigation in apps for audio books, we will add metadata describing chapters in Onix records. We will also supply chapters for ebooks. We will start to support manual chapters, and then work with automatic chapters that publishers then need to approve.

Support for block 3 will be added.

AVItem in ContentDetail will contain information about chapter numbers and start time for each chapter.

LevelSequenceNumber indicated logical numbering, and will not necessarily contain the same number as the chapter number.

AVItemType includes codes from list 240, identifying if the part is front, body or end matter.
TextType includes codes from list 42, identifying if the part is front, body or end matter.

TimeRun will indicate start time for each chapter. Format for StartTime/AVDuration is “HHHMMss“.

If you want to supply a title, use TitleDetail. TitleType (list 15) should be 01. TitleElementLevel (list 149) should be 04.

Adding support for other subfields will be considered.

<ContentDetail>
<ContentItem>
<LevelSequenceNumber>1</LevelSequenceNumber>
<AVItem>
<AVItemType>03</AVItemType>
<TimeRun>
<StartTime>0000000</StartTime>
</TimeRun>
<AVDuration>0010343</AVDuration> 
</AVItem>
<ComponentTypeName>Kapittel</ComponentTypeName>
<ComponentNumber>1</ComponentNumber>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>04</TitleElementLevel>
<TitleText>The name of the first chapter</TitleText>
</TitleElement>
</TitleDetail>
</ContentItem>
…
<ContentDetail>

<ContentDetail>
<ContentItem>
<LevelSequenceNumber>1</LevelSequenceNumber>
<TextItem>
<TextItemType>03</TextItemType>
<PageRun>
<FirstPageNumber>2</FirstPageNumber>
</PageRun>
<NumberOfPages>22</NumberOfPages>
</TextItem>
<ComponentTypeName>Kapittel</ComponentTypeName>
<ComponentNumber>1</ComponentNumber>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>04</TitleElementLevel>
<TitleText>The name of the first chapter</TitleText>
</TitleElement>
</TitleDetail>
</ContentItem>
…
<ContentDetail>

Device support Breaking change

Breaking Change

Export:
- Will only give the new format
Import:
- We will still support the old syntax until given date

We will move away from using ProductFormDescription.

It will now be present as ProductFormFeatureDescription (code 07 from list 79). to allow the indication of multiple devices supported.

<ProductFormDescription>Smarttelefon</ProductFormDescription>

<ProductFormFeature>
<ProductFormFeatureType>07</ProductFormFeatureType>
<ProductFormFeatureDescription>Smarttelefon</ProductFormFeatureDescription>
</ProductFormFeature>

Price condition (automatic renewed)

Price condition is used to indicate when the subscription of a product is automatically renewed. Typically used for digital learning resources.

The duration of the license period is specified in PriceConditionQuantity (EpubUsageConstraint?).

Code 07 from list 167 is used in PriceConditionType to indicate that the rental or subscription will automatically renewed at the end of the period unless actively cancelled.

Code 01 from list 168 is used in PriceConditionQuantityType to indicate that the renewal time period is 12 months (09).

<PriceCondition>
<PriceConditionType>07</PriceConditionType
<PriceConditionQuantity>
<PriceConditionQuantityType>01</PriceConditionQuantityType
<Quantity>12</Quantity>
<QuantityUnit>09</QuantityUnit>
</PriceConditionQuantity>
</PriceCondition>

Collection (Norw. forlagsserie)

CollectionType is used to indicate what type of collection is described in the metadata.

Support for code 11 for identifying publisher’s collections will be added.

Publisher’s collections are bibliographic collections defined and identified by a publisher, often used for marketing purposes, and often with a distinct design style. The books in the collection does not necessarily have a specific order, shared subject or authorship.

Collections where the books in the collection have a shared subject, narrative or authorship, are identified by collection type 10. This collection type is independent of the publisher, and will be added as metadata to all editions of a book.

Collection Type 11 (publisher’s collection)

<Collection>
<CollectionType>11</CollectionType>
<CollectionIdentifier>
<CollectionIDType>01</CollectionIDType>
<IDTypeName>Bokbasen_ProprietaryID</IDTypeName>
<IDValue>150140617</IDValue>
</CollectionIdentifier>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>02</TitleElementLevel>
<TitleText>Bestselger Schibsted</TitleText>
</TitleElement>
</TitleDetail>
</Collection>

Collection Type 10, with part number element

<Collection>
<CollectionType>10</CollectionType>
<CollectionIdentifier>
<CollectionIDType>01</CollectionIDType>
<IDTypeName>Bokbasen_ProprietaryID</IDTypeName>
<IDValue>20090529101912_rine</IDValue>
</CollectionIdentifier>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>02</TitleElementLevel>
<TitleText>Percy Jackson</TitleText>
</TitleElement>
<TitleElement>
<TitleElementLevel>01</TitleElementLevel>
<PartNumber>1</PartNumber>
</TitleElement>
</TitleDetail>
</Collection>

Text and data mining

In all Bokbasen’s customer contracts, use of the product for extraction, automated computer analaysis or AI-training is regulated and forbidden.

This constraint will be added to the Onix-records in Epub Usage Constraint.

EpubUsageType will include information indicating that use of the content of the product by artificial intelligence systems is forbidden.

Usage type 11 is used in combination with code 03 in EpubUsageStatus, to state that text and data mining is prohibited.

<EpubUsageConstraint>
<EpubUsageType>11</EpubUsageType>
<EpubUsageStatus>03</EpubUsageStatus>
</EpubUsageConstraint>

GPSR - General Product Safety Regulation (EU)

General Product Safety Regulations (GPSR) of the European Union, came into force at the end of 2024 and mandates specific contact details for consumer queries relating to physical product safety, product liability, defects in the product etc. The requirements apply to both over-the-counter sales within the EU and to all online sales to EU customers, even for products like ‘books’ that are generally considered ‘safe’.

ProductContact will be added to metadata for all physical products.

<ProductContact>
<ProductContactRole>10</ProductContactRole>
<ProductContactName>{PUBLISHER_NAME}</ProductContactName>
<EmailAddress>{PUBLIC_EMAIL}</EmailAddress>
<StreetAddress>{POSTAL_ADDRESS}</StreetAddress>
<LocationName>{CITY}</LocationName>
<PostalCode>{POSTAL_CODE}</PostalCode>
<CountryCode>{COUNTRY_CODE_ONIX_91}</CountryCode>
</ProductContact>

Kulturrådets innkjøpsordninger (K-fond) Breaking change

Breaking Change

Export:
- Will only give the new content in v2

Kulturrådet (The Norwegian Cultural Council) administers several book acquisition schemes aimed at promoting Norwegian literature and ensuring its accessibility to the public.

Information about a book’s status in the acquisition schemes is provided in Onix-records from Bokbasen.

In V2, the records will include more detailed information about the book’s status.

ProductClassification will include information identifying four statuses in the acquisition scheme, in contrast to v1, which only states the values NKR_JA or NKR_NEI.

ProductClassification is used for multiple classification schemes, for information about K-fond, ProductClassificationName is “BOKBASEN_KULTURRÅD”

New values are:

Påmeldt
Innkjøpt
Avslått
Avvist

<ProductClassification>
<ProductClassificationType>07</ProductClassificationType>
<ProductClassificationTypeName>BOKBASEN_KULTURRAD</ProductClassificationTypeName>
<ProductClassificationCode>Innkjøpt</ProductClassificationCode>
</ProductClassification>

Literary prizes

Information about literary prizes will be reintroduced to records from Bokbasen.

A literary prize can be awarded to a specific work, or to an author.

When a prize is awarded a person, the information is inluved within the Contributor composite.

When a prize is awarded a work, the information is included as part of block 2.

Prize awarded a work:

<Prize>
<SequenceNumber>01</SequenceNumber>
<PrizeName>Nynorsk barnelitteraturpris</PrizeName>
<PrizeYear>2024</PrizeYear>
<AwardingBody>Noregs Mållag</AwardingBody>
</Prize>

Prize awarded an author:
<Prize>
<SequenceNumber>01</SequenceNumber>
<PrizeName>Nobelprisen</PrizeName>
<PrizeYear>2024</PrizeYear>
<AwardingBody>Svenska Adademien</AwardingBody>
</Prize>

City of publication

Information about the city associated with the publisher.
Mainly used by library users of Onix records.

The name of the city associated with the publisher will be included as a standardized textelement in City of publication in Block 4.

<PublishingDetail>
…
<Publisher>
<PublishingRole>01</PublishingRole>
<PublisherIdentifier>
<PublisherIDType>01</PublisherIDType>
<IDTypeName>Bokbasen_Kundenummer</IDTypeName>
<IDValue>4285</IDValue>
</PublisherIdentifier>
<PublisherIdentifier>
<PublisherIDType>06</PublisherIDType>
<IDValue>7080004117402</IDValue>
</PublisherIdentifier>
<PublisherName>Bonnier Norsk Forlag AS</PublisherName>
</Publisher>
<CityOfPublication>Oslo</CityOfPublication>
…
</PublishingDetail>

Text content

Accompanying material

Information about accompanying material in Text content with text type 11 added to the records.

Accompanying material is supplied in addition to the publication itself, and can f.i. be a loose map supplied with a travel guide or a pattern sheet supplied with a book about sewing.

General notes

Text content with type 01 is used for additional information in text format not supplied elsewhere.

Use of element TextSourceCorporate is modified, and element now contains ‘Bokbasen’ only.

Changed from:

TextSourceCorporate>Bokbasen_Note</TextSourceCorporate>

To:

<TextContent>
<TextType>01</TextType>
<ContentAudience>00</ContentAudience>
<Text>1. e-bokutgave tilsvarer 2. trykte utgave 2025</Text>
<TextSourceCorporate>Bokbasen</TextSourceCorporate>
</TextContent>

Title type

Added support for new Title type codes to specify type of alternative titles in Title detail.

Title types:

Code	Text

Code	Text