Table of Contents | ||
---|---|---|
|
Changelog
...
Date
...
Table of Contents | ||
---|---|---|
|
Changelog
Date | |
---|---|
Introducing v2-endpoint for Onix Export. Most new features will be exclusive to the new v2-endpoint, see also deprecation-notice for v1. | |
| |
| |
| |
|
|
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
...
|
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
Note |
---|
Onix Export v1 - end of life 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 | ||||||
---|---|---|---|---|---|---|---|---|
Contributor Unnamed Persons
| Q4 2024 |
| ||||||
Contributor Unnamed Persons
| In prod from (only v2) ⚠️ Breaking change |
| ||||||
Subject
| September 2024 |
| ||||||
FSC, PEFC, carbon emission
| Q2 2025 (only v2) |
| ||||||
FSC, PEFC, carbon emission
| Q2 2025 (only v2) |
| ||||||
Contributor Role Code
| November 2024 |
| ||||||
Contributor Role Code
| November 2024 |
| ||||||
Chapters in audio/text books
| October 2024January 2025 (only v2) |
| ||||||
Device support
| ⚠️ End-of-life for old syntax |
| ||||||
Device support
| January 2025 (only v2) In stage from ⚠️ Breaking change |
| ||||||
Collection (publisher)
| Q4 2024 |
| ||||||
Collection (publisher)
| Q4 2024 (only v2) |
| ||||||
Price condition (automatic renewed)
| Q2 2025 |
| ||||||
Price condition (automatic renewed)
| Q2 2025 |
| ||||||
Text and data mining
| October 2024 |
| ||||||
Onix 3.1 | Q4 2024 |
| TBA |
| ||||
Onix 3.1
| (only v2) |
| ||||||
GPSR - General Product Safety Regulation (EU) | Q1 2025 (only v2) |
|
Features / changes
...
Expand | ||
---|---|---|
| ||
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> |
Expand | ||
---|---|---|
| ||
<Subject> <Subject> |
EUDR, FSC, PEFC, carbon emission
...
Expand | ||
---|---|---|
| ||
Due Diligence Statement <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> Provenance of raw material for body Three or more GPS coordinates denotes a polygon outlining the forest where the trees grew. <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.
...
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 |
Expand | ||
---|---|---|
| ||
<Contributor> |
Chapters in audio and ebooks
...
Expand | ||
---|---|---|
| ||
<ContentDetail> |
Expand | ||
---|---|---|
| ||
<ContentDetail> |
Device support
Status | ||||
---|---|---|---|---|
|
...
It will now be present as ProductFormFeatureDescription (code 07 from list 79). to allow the indication of multiple devices supported.
Expand | ||
---|---|---|
| ||
<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/EpubConstraint?.
Expand | ||
---|---|---|
| ||
Code 12 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. |
Expand | ||
---|---|---|
| ||
<PriceCondition> |
Collection (Norw. forlagsserie)
...
Expand | ||
---|---|---|
| ||
Collection Type 11 (publisher’s collection) <Collection> Collection Type 10, with part number element <Collection> Collection Type 10, with part number element <Collection> |
Text and data mining
In all Bokbasen’s customer contracts, use of the product for extraction or automated computer analaysis is regulated and forbidden.
This constraint will be added to the Onix-records in Epub Usage Constraint.
Expand | ||
---|---|---|
| ||
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. |
Expand | ||
---|---|---|
| ||
<EpubUsageConstraint> |
Onix 3.1
In February 2023 the Onix Steering Committee agreed that in addition to adding new features to Onix, various data elements that were deprecated, plus the <Gender> tag were to be removed. This necessitated the labelling of the revision as release 3.1.
Aside from the removal of the deprecated elements and <Gender>, these updates are all
optional and fully backwards-compatible.
Bokbasen will do a revision of Onix both to and from Bokbasen, to make sure that the records are compatible with version 3.1
The deprecated elements has originally not been supported by Bokbasen, and the upgrade to Onix 3.1 should not cause problems for customers of Bokbasen.
...
title | Deprecated elements |
---|
Deprecated elements in Onix 3.1_
Audience code
Conference
CurrenzyZone
DateFormat
PromotionContact
Reissue
Gender
...
Text and data mining
In all Bokbasen’s customer contracts, use of the product for extraction or automated computer analaysis is regulated and forbidden.
This constraint will be added to the Onix-records in Epub Usage Constraint.
Expand | ||
---|---|---|
| ||
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. |
Expand | ||
---|---|---|
| ||
<EpubUsageConstraint> |
Onix 3.1
In February 2023 the Onix Steering Committee agreed that in addition to adding new features to Onix, various data elements that were deprecated, plus the <Gender> tag were to be removed. This necessitated the labelling of the revision as release 3.1.
Aside from the removal of the deprecated elements and <Gender>, these updates are all
optional and fully backwards-compatible.
Bokbasen will do a revision of Onix both to and from Bokbasen, to make sure that the records are compatible with version 3.1
The deprecated elements has originally not been supported by Bokbasen, and the upgrade to Onix 3.1 should not cause problems for customers of Bokbasen.
Expand | ||
---|---|---|
| ||
Deprecated elements in Onix 3.1_ Audience code Conference CurrenzyZone DateFormat PromotionContact Reissue Gender Language, PriceType and Currency in Header |
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.
Expand | ||
---|---|---|
| ||
<ProductContact> |