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.
Date | |
|---|---|
15.5.2025 | Image for book spine will be added to v2 |
8.5.2025 | Work as subject will be added to v2 |
23.4.2025 | In v2: Accompanying material in TextContent Changes in text content New title types Contributor statement, from language added |
| Subject from NEO now in v2 |
| Subjects will include language attribute, both for genre/form and subjects Reintroducing Literary prizes in v2 |
| PriceCondition postponed until further notice. EUDR, FSC etc. moved to Q3 and v3-endpoint of Onix. |
| GPSR + Kulturrådet are now done |
Introducing v2-endpoint for Onix Export. Most new features will be exclusive to the new v2-endpoint, see also deprecation-notice for v1. | |
| |
| |
| |
| Subject from NTSF
|
|
|
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.
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.
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 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 |
Feature | Available from (endpoint version) | Status |
|---|---|---|
Contributor Unnamed Persons
| Q4 2024 |
|
Contributor Unnamed Persons
| In prod from (only v2)
|
|
Subject
| September 2024 |
|
FSC, PEFC, carbon emission, EUDR
| Q3 2025 |
|
FSC, PEFC, carbon emission, EUDR
| Q3 2025 |
|
Contributor Role Code
| November 2024 |
|
Contributor Role Code
| November 2024 |
|
Chapters in audio/text books
| January 2025 (only v2) | |
Device support
|
|
|
Device support
| January 2025 (only v2) In stage from
| |
Collection (publisher)
| Q4 2024 | |
Collection (publisher)
| Q4 2024 (only v2) | |
Price condition (automatic renewed)
|
|
|
Price condition (automatic renewed)
|
|
|
Text and data mining
| October 2024 |
|
Onix 3.1
| Q1 2025 | |
Onix 3.1
| (only v2) | |
GPSR - General Product Safety Regulation (EU) | Q1 2025 (only v2) | |
Kulturrådets innkjøpsordninger | Q1 2025 (only v2)
|
|
Subject from NEO | Q2 (only v2) |
|
Literary prizes | April 2025 (only v2) |
|
City of publication | April 2025 (only v2) |
|
Text content | April 2025 (only v2) |
|
Title type | April 2025 (only v2) |
|
Dewey | April 2025 (only v2)
|
|
From language | April 2025 (only v2) |
|
Contributor statement | April 2025 (only v2) |
|
Work as subject | May 2025 (only v2) |
|
Image of book spine | Q2 |
|
Breaking Change
Only for export
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) |
<Contributor> |
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> |
<Subject> <Subject> |
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: Both types will be sent for now, but “24”-block is now deprecated and will get an end-of-life date. |
<Subject> <Subject> <Subject> |
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> 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 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 |
|---|---|
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> |
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. 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> |
<ContentDetail> |
Breaking Change
Export:
Will only give the new format
Import:
We will still support the old syntax until given date
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.
<ProductFormFeature> |
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> |
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> Collection Type 10, with part number element <Collection> |
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> |
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> |
Breaking Change
Export:
Will only give the new content in v2
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 |
<ProductClassification> |
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> Prize awarded an author: |
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> |
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. |
<TextContent> |
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> |
Added support for new Title type codes to specify type of alternative titles in Title detail.
Title types:
|
Translated into Norwegian from the English edition (type 16) <TitleDetail> |
Translated into Norwegian from another language than the original language. From language added to the Contributor composite and used with Contributor role B06 (translated by).
<Contributor> … |
Free text showing how the authorship is described in the publication.
Mainly used by library users of Onix records. For display use only.
<ContributorStatement>Solvej Balle ; oversatt av Trude Marstein</ContributorStatement> |
Modification of Subject element for Dewey numbers.
Added support for multiple codes in Subject scheme identifier; 01, 02 and 46 Added element Subject scheme version for Dewey edition. Dewey number sent in Subject code (previously subject heading text), with datestamp attribute. |
<Subject> |
If a work is about another work, a link to the mentioned work will be added to the Onix record.
The Subject element will include an identifier to Bokbasen’s works.
SubjectSchemeIdentifier is 24 and SubjectSchemeName is ‘Bokbasen_Work_As_Subject’ SubjectCode contains an identifier, and SubjectHeadingText the preferred title of the work. |
<Subject> |
For paper books, a link to an image of the book’s spine will be added to the Onix record.
Code for book spine will be added to codelist 158 in issue 70 of the codelists. As soon as the code is available, Bokbasen will implement this as a part of Supporting resource, in the element ResourceContentType. Link to the image will be included in ResourceLink. |
<SupportingResource> |
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.
Deprecated elements in Onix 3.1_ Audience code Conference CurrenzyZone DateFormat PromotionContact Reissue Gender Language, PriceType and Currency in Header |