...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Skisse til offentlig dokumentasjon / plan
Vi skriver ALT på engelsk.
Følg rett hierarki så TOC blir bra
Når den er klar for offentligheten, så flyttes den til det offentlige space (under ONIX3)
| Table of Contents | ||
|---|---|---|
|
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.
Schedule / Status
Innfasing av hver <hva> (ca. mnd som forfines etterhvert)
Klar status på om hver <hva> er deployet (test/stage + prod)
Eventuelle utfasinger (f.eks. når Onix 3.0 forsvinner)
...
Feature
...
Available from
...
| Status | ||
|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
...
Contributor Unamed Persons
import
export
...
| Status | ||
|---|---|---|
|
...
Subject
export
...
EUDR, FSC, PEFC, carbon emission
import
eport
...
Contributor Role Code
import
export
...
Chapters in audio books
export
...
Device support
import
export
...
Collection (publisher)
...
Price condition
...
Text and data mining
export
...
Onix 3.1
Features / changes
Contributor Unamed Persons
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.
Technical details
| Expand | ||
|---|---|---|
| ||
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) |
| Expand | ||
|---|---|---|
| ||
<Contributor> |
Subject
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 transitio
Technical details
| 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
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.
...
| title | Guide |
|---|
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
...
| title | Examples |
|---|
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
...
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> |
...
| Table of Contents | ||
|---|---|---|
|
Changelog
Date | |
|---|---|
| |
|
|
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.
Schedule / Status
Feature | Available from | Status | ||||||
|---|---|---|---|---|---|---|---|---|
Contributor Unnamed Persons
| Q4 2024 |
| ||||||
Contributor Unnamed Persons
| In prod from ⚠️ Breaking change |
| ||||||
Subject
| September 2024 |
| ||||||
EUDR, FSC, PEFC, carbon emission
| Q2 2025 |
| ||||||
EUDR, FSC, PEFC, carbon emission
| Q2 2025 |
| ||||||
Contributor Role Code
| November 2024 |
| ||||||
Contributor Role Code
| November 2024 |
| ||||||
Chapters in audio/text books
| October 2024 |
| ||||||
Device support
| ⚠️ End-of-life for old syntax |
| ||||||
Device support
|
In stage from ⚠️ Breaking change |
| ||||||
Collection (publisher)
| Q4 2024 |
| ||||||
Collection (publisher)
| Q4 2024 |
| ||||||
Price condition
| Q2 2025 |
| ||||||
Price condition
| Q2 2025 |
| ||||||
Text and data mining
| October 2024 |
| ||||||
Onix 3.1 | Q4 2024 |
|
Features / changes
Contributor Unnamed Persons
| Status | ||||
|---|---|---|---|---|
|
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.
| Expand | ||
|---|---|---|
| ||
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) |
| Expand | ||
|---|---|---|
| ||
<Contributor> |
Subject
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 transitio
| 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
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.
| Expand | ||
|---|---|---|
| ||
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 |
| 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.
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 |
| Expand | ||
|---|---|---|
| ||
<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.
| Expand | ||
|---|---|---|
| ||
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. |
| Expand | ||
|---|---|---|
| ||
<ContentDetail> |
| Expand | ||
|---|---|---|
| ||
<ContentDetail> |
Device support
| Status | ||||
|---|---|---|---|---|
|
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.
...
| Expand | ||
|---|---|---|
| ||
<ProductFormFeature> |
Price condition
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 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)
CollectionType is used to indicate what type of collection is described in the metadata.
Support for code 11 for identifiyng identifying publisher’s collections will be added.
Publisher’s collections are bibliograhpic 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 autorshipauthorship.
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 matadata metadata to all editions of a book.
| Expand | ||
|---|---|---|
| ||
Collection Type 11 (publisher’s collection) <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> |
...
/IDTypeName> |
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 |