Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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)

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

Dokument ferdig
(sett (tick) når ferdig dokumentert)

Status
NOT STARTED
IN PROGRESS
DONE

Contributor Unamed Persons

  • import

  • export

NOT STARTED

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

 Guide

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)

 Examples

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

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

 Guide

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>

 Examples

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

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.

 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

 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

 Example

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

Device support BREAKING CHANGE

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.

Technical details

 Example

<ProductFormDescription>Smarttelefon</ProductFormDescription>

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

Epub usage constraint

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.

 Guide

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.

 Example

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

Onix 3.1

  • No labels