Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
none
Table of Contents
style
Table of Contents
stylenone

Changelog

Date

  • Contributor Unnamed Persons

    • Released in stage/test

    • In prod from

  • EUDR, FSC, PEFC, carbon emission

    • Delayed expected delivery quarter

  • Contributor Role Code

    • Released (except B34)

  • Device support

    • Delayed expected delivery dates

  • Price condition

    • Delayed expected delivery quarter

  • Text and data mining

    • Released

  • “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.

Schedule / Status

Feature

Available from

Status

Contributor Unnamed Persons

  • import

Q4 2024

Status
colourBlueGreen
titleIn progressdone

Contributor Unnamed Persons

  • export

Q4 2024

In prod from

⚠️ Breaking change

Status
colourBlue
titleIn progressTEST / STAGE

Subject

  • export

September 2024

Status
colourGreen
titledone

EUDR, FSC, PEFC, carbon emission

  • import

Q4 2024Q2 2025

Status
titlenot started

EUDR, FSC, PEFC, carbon emission

  • export

Q1 Q2 2025

Status
titlenot started

Contributor Role Code

  • import

November 2024

Status
colourGreen
titleNot starteddone

Contributor Role Code

  • export

November 2024

Status
colourGreen
titleNot starteddone

Chapters in audio/text books

  • export

October 2024

Status
colourBlue
titleIn progressTEST / STAGE

Device support

  • import

Q4 2024

⚠️ End-of-life for old syntax

Status
titleNot started

Device support

  • export

Q4 2024

In stage from

⚠️ Breaking change

Status
titleNot started

Collection (publisher)

  • import

Q4 2024

Status
titleNot started

Collection (publisher)

  • export

Q4 2024

Status
titleNot started

Price condition

  • import

Q4 2024Q2 2025

Status
titleNot started

Price condition

  • export

Q4 2024Q2 2025

Status
titleNot started

Text and data mining

  • export

October 2024

Status
colourGreen
titlenot starteddone

Onix 3.1

Q4 2024

Status
titleNot started

Features / changes

Contributor

...

Unnamed Persons
Status
colourRed
titleBreaking 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 will be supported both for metadata to and from Bokbasen.

...

Expand
titleGuide

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)

Expand
titleExamples

<Contributor>
<SequenceNumber>1</SequenceNumber>
<ContributorRole>A01</ContributorRole>
<PersonNameInverted>Nordmann, Kari</PersonNameInverted>
</Contributor>
<Contributor>
<SequenceNumber>2</SequenceNumber>
<ContributorRole>A12</ContributorRole>
<!-- UnnamedPersons instead of PersonNameInverted -->
<UnnamedPersons>09</UnnamedPersons>
</Contributor>
<Contributor>
<SequenceNumber>3</SequenceNumber>
<ContributorRole>E07</ContributorRole>
<!-- UnnamedPersons instead of PersonNameInverted -->
<UnnamedPersons>05</UnnamedPersons>
</Contributor>

Subject

The Subject element contains classification from several different schemes.

...

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

...

Expand
titleGuide

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>

Expand
titleExamples

<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>Romaner</SubjectHeadingText>
</Subject>

<Subject>
<SubjectSchemeIdentifier>C8</SubjectSchemeIdentifier>
<SubjectCode>https://id.nb.no/vocabulary/ntsf/159</SubjectCode>
<SubjectHeadingText>Krim</SubjectHeadingText>
</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.

...

Expand
titleExamples

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.

...

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
titleExample

<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, support for we will add metadata describing chapters in audio books will be added to Onix records from BokbasenOnix 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
titleGuide

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 concideredconsidered.

Expand
titleExamplesExample (Audio Chapters)

<ContentDetail>
<ContentItem>
<LevelSequenceNumber>1</LevelSequenceNumber>
<AVItem>
<AVItemType>03</AVItemType>
<TimeRun>
<StartTime>0000000</StartTime>
</TimeRun>
<AVDuration>0010343</AVDuration>
<ComponentTypeName>Forord</AVDuration> <!-- 001h, 03m, 43s -->
</AVItem>
<ComponentTypeName>Kapittel</ComponentTypeName>
<<ComponentNumber>1</AVItem>ComponentNumber>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>04</TitleElementLevel>
<TitleText>The name of the first chapter</TitleText>
</TitleElement>
</TitleDetail>
</ContentItem>

<ContentDetail>

Expand
titleExample (Text Chapters)

<ContentDetail>
<ContentItem>
<LevelSequenceNumber>2<<LevelSequenceNumber>1</LevelSequenceNumber>
<AVItem> <TextItem>
<AVItemType>03<<TextItemType>03</AVItemType>TextItemType>
<TimeRun> <PageRun>
<StartTime>0010325<<FirstPageNumber>2</StartTime>FirstPageNumber>
</PageRun>
<NumberOfPages>22</TimeRun>NumberOfPages>
<AVDuration>0002649<</AVDuration>TextItem>
<ComponentTypeName>Kapittel</ComponentTypeName>
<ComponentNumber>1</ComponentNumber>
</AVItem>
<TitleDetail>
<TitleType>01</TitleType>
<TitleElement>
<TitleElementLevel>04</TitleElementLevel>
<TitleText>The name of the second first chapter</TitleText>
</TitleElement>
</TitleDetail>
</ContentItem>

<ContentDetail>

Device support
Status
colourRed
titleBreaking 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.

...

Expand
titleExample

<ProductFormDescription>Smarttelefon</ProductFormDescription>

<ProductFormFeature>
<ProductFormFeatureType>07</ProductFormFeatureType>
<ProductFormFeatureDescription>Smarttelefon</ProductFormFeatureDescription>
</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
titleGuide

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
titleExamples

<PriceCondition>
<PriceConditionType>07</PriceConditionType
<PriceConditionQuantity>
<PriceConditionQuantityType>02</PriceConditionQuantityType
<Quantity>12</Quantity>
<QuantityUnit>09</QuantityUnit>
</PriceConditionQuantity>
<ProductIdentifier>
<ProductIDType>15</ProductIDType>
<IDValue>9788205399815</IDValue>
</ProductIdentifier>
</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
titleExamples

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 or automated computer analaysis is regulated and forbidden.

...

Expand
titleGuide

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
titleExample

<EpubUsageConstraint>
<EpubUsageType>11</EpubUsageType>
<EpubUsageStatus>03</EpubUsageStatus>
</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.

...