Metadata

General Information and Introduction

PASA spearheads metadata initiatives to assist publishers and other partners in the supply chain. This committee aims to serve members of PASA by providing information on updates to the ONIX and Thema standards, documentation and resources that will be useful, commenting on proposed adjustments to the standards and policies, and representing PASA and publisher interests at key metadata engagements.


Minimum Metadata Requirements for the South African market - PASA Metadata Committee
9 October 2023

For best results for your ONIX metadata, the generation of product records should be done by having as complete a rate a message as is possible; making strategic choices about the data that is required for the type of publishing that you are engaged in.

This document was produced by the Metadata Committee of the Publishers Association of South Africa (PASA) as a result of requests from stakeholders in South Africa to have an agreed-to, technically capable list of minimum requirements that could be applied across the industry locally. This list is intended to be used as a guide, and in conjunction with a more comprehensive list such as is available here

ONIX codelists Issue 65. This list is intended to be a summary of minimum requirements, and should be read in conjunction with the Best Practice Guide then link to the PASA version of the fuller best practice guide

We encourage you to consider this a good point at which to begin producing ONIX messages, and to expand into the more detailed use of other features, which will be required when dealing with services and recipients external to South Africa.


Minimum Metadata Requirements List

Particular metadata fields for each product are required. This list is intended to be used as a reference list of ONIX 3.1 data elements. More detail on each data element group is given in the PASA Product Metadata Guidelines (which we strongly recommend a working knowledge of), and of course the full standard documentation is available from EDItEUR at this link  https://www.editeur.org/93/Release-3.0-and-3.1-Downloads/#Specifications. A comprehensive EDItEUR Implementation and Best Practice Guide is also available.

  • Product identifiers: 13-digit GTIN product number (formerly EAN-13 article number). Normally this is the same number as the ISBN (with first three digits 978 or 979)
  • Product form and format (for example audio, paperback, hardback, EPUB etc.) including dimensions and packaging, or for digital products, the file format
  • Collection if the product is part of a series or collection
  • Book title. Separate title and subtitle into unique fields. Do not insert marketing information in the subtitle field.
  • Contributor (forenames and surname) and role (for example author, editor, translator, illustrator etc.) Include sequence numbering where there is more than one contributor
  • Edition number (2nd, 3rd etc) and/or edition type (abridged, bilingual, large print, school edition etc) whenever applicable
  • All languages in the text must be indicated
  • Extent, playing time and other content such as the number and type of illustrations.
  • For digital publications, include information on accessibility standards conformance where applicable
  • At least one Thema subject category code
  • Audience for the product
  • Short description of the product (other marketing text such as reviews, a long description is also valuable)
  • Front cover image
  • Publisher and imprint name
  • City and country of publication
  • publication date of the current edition
  • Publishing status (for example active, forthcoming, no longer available, out of print, remaindered, etc.)
  • Sales rights and sales restrictions specified across all territories (ie where can the product be sold, and where it cannot be sold)
  • Related products such as the ISBNs of the new edition or alternative formats
  • Supplier information (for example distributor to end-customers, retailer, sales agent, etc.)
  • Recommended retail price (including VAT) in South African Rands, and a price to be used as a basis for export sales (probably in Rand, without VAT)

Compiled by the PASA Metadata Committee

9 October 2023

Download the full Metadata Requirements List here: download me!


FAQ's

ONIX (ONline Information EXchange) is the international standard for representing and communicating book industry product information in electronic form.

ONIX for Books is a standard specification for communicating book, audiobook, e-book and digital audio metadata between publishers, various intermediaries like distributors, wholesalers and data service organisations, and retailers in the book supply chain.

EDItEUR provides an overview of ONIX here (https://www.editeur.org/83/Overview/) and a 15-minute pre-recorded webinar-style briefing here (https://www.editeur.org/files/videos/20230410%20ONIX%20briefing%20720p.html).

(From BISG and Editeur)

Metadata is the vital details about a book that allow distributors and retailers to easily identify what it’s about and successfully market it. These include ‘bibliographic’ data such as the ISBN and publication date, title, author or series. But it also includes marketing collateral – descriptive text or abstracts, images such as the cover of the product – and commercial information such as the distribution arrangements and pricing.

For publishers, experience has shown that ONIX brings two important business benefits.

  1. It standardises the way publishers communicate about books to the wider industry, making it possible to deliver rich product information into the supply chain in a way that is understood by both the sender and the recipient. The standard enables much of the metadata exchange to be automated, an important consideration as the volume of new publications continues to rise.
  2. A single set of metadata can be maintained and used for all downstream requirements, including the creation of advance information sheets, catalogues and other promotional material. In principle at least, the same metadata can be used without modification for many different uses and with many different data recipients.

For supply chain partners such as distributors and wholesalers, data intermediaries and retailers, ONIX offers these benefits:

  1. A faster turnaround time for loading product information into business systems
  2. Less (or no) need for manual intervention (e.g. copying information from AI sheets) and therefore a lower risk of error.
  3. ONIX reduces the need to deal with multiple proprietary data formats, and thus reduces support costs.
  4. Standardising the way the industry shares information allows third parties such as trade associations or data aggregators to develop metrics and benchmarking for data quality and timeliness.

(from Editeur)

This report from Nielsen also looks at the benefits of metadata: https://nielsenbook.co.uk/metadata-report/

Publishers who want to adopt ONIX could consider these options:

  1. develop or commission bespoke software for managing product metadata, and build in support for ONIX for Books;
  2. acquire a third-party application for product data management which supports ONIX.; or
  3. contract to use a web-based ‘in the cloud’ service which supports online data entry and delivery of ONIX output to designated recipients.

ONIX is not so complex that creating a bespoke system is beyond the capabilities of a small internal development team. There are also many application and service providers that would enable you to manage your metadata and deliver it to the industry via ONIX feeds. You’d need to assess the cost and practicality of creating your own bespoke system against what various service providers can offer you and decide what is best for your business. Most but not all publishers choose to work with a service provider.

(From Editeur)

ONIX aims to cover the widest possible range of needs, and it therefore includes many elements which are specialised to particular forms of publishing or particular markets. Nobody uses all the elements available, and only a very small number are mandatory.  The minimum set of data elements for a trade publisher is a little different from that of an academic publisher and depends on your business requirements and those of your supply chain partners. Some receivers may choose not to use certain data elements if their business does not require that data, or may ask for one option rather than another (though the latter is discouraged).

EDItEUR provides a comprehensive Implementation and Best Practice Guide that offers advice on the most commonly useful ONIX 3.0 or 3.1 data elements. See https://www.editeur.org/93/Release-3.0-and-3.1-Downloads/#BestPractices

The PASA Metadata Committee has published their own guidelines for implementation and ‘good practices’, building on the global EDItEUR advice. If you are buying a third-party system or service, you need to check that it complies with the EDItEUR guidelines.

(adapted from Editeur)

EDItEUR provides high-quality and authoritative face-to-face and online training programmes to its members (including PASA), and to non-member organisations, at a reasonable cost (members qualify for lower training fees). If you are interested in receiving training please contact the South African National Metadata User Group (SANMUG) or EDItEUR. The user group provides implementation help, workshops and formal training.

(adapted from Editeur)

Don’t make the metadata the responsibility of the one techy person who may be in charge of the system you use. Instead, make it something everyone is responsible for throughout the life cycle of the book. An editor, publicist, rights associate, and sales manager all have different material they can add and update in your metadata system.

Add information to your metadata as things happen, and keep updating it as things change. For example, if you are long-listed for an award, add this to your data, and keep the status updated throughout the award process. Continue this process throughout the lifecycle of the book – starting at inception of the publishing project and ending only after the product goes out of print.

If your system allows, set it up so that it automatically sends updates to your trading partners whenever metadata updates have been made.

Proofread your metadata. Even better, use your own ONIX metadata to feed your public-facing website – there’s no better way to ensure errors are spotted and corrected.

Get it right first time wherever you can – mistakes are sometimes difficult to rectify once in the supply chain. However,  accept that publishing plans change over time, so what’s right now may not still be correct in three months’ time.

Don’t leave it too late. Many booksellers like to have (or even require) a full set of metadata for all new releases several months ahead of publication date.

Regularly review all of your metadata to ensure there are no missing metadata elements (particularly the “Required” metadata elements), including cover image. Housekeeping/data cleaning is important.

Ensure you are informed of and keep up to date with the latest Code Lists and ONIX releases and encourage your trading partners to do the same.

Yes. ONIX is not built around the needs of any one country, or any one supply chain.

Although the Reference XML tag names are in English, this is just a convenience, and the data carried within most data elements is language-independent. Whether a book is known as a hardback (English), a hardcover (American English), eine gebundene ausgabe (German) or 精装书 (Mandarin), the ONIX data is the same (<ProductForm>BB</ProductForm>).

Where the data is text in a particular language – for example, the text of a contributor’s biography – the text can be provided in any one language – or in several languages in parallel.

To facilitate text in multiple languages, ONIX can use Unicode: whether your metadata is in Latin script (for English and most European languages), Cyrillic (for Russian), Arabic script, Hanzi or Kanji (for Chinese and Japanese) or Hangul (for Korean), Unicode covers what you need. Codelists are available in some of these languages too.

(From Editeur)

Many South African publishers are familiar with BIC Codes – a classification system that allows you to add codes to your title metadata so that they are categorised correctly by subject (e.g. Crime Fiction). BIC Codes have been withdrawn as of February 2024. Thema replaces the use of BIC Codes.

Thema is aimed at a global audience, with significantly more categories, more flexible use of ‘qualifiers’ and multilingual options that don’t exist in BIC Codes. ‘Thema is managed by EDItEUR and an international group of stakeholders, and is free to use. It aims to enhance the merchandising, discoverability and potential sales of books by simplifying the communication of accurate and detailed subject information across international markets and reducing the need to maintain numerous national subject schemes.’ (Editeur)

(from Editeur)

NB EDItEUR has a longer FAQ at https://www.editeur.org/74/FAQs


PASA Non-compete Declaration

Draft: South African National Metadata User Group (SANMUG) non-compete declaration

19 February 2024

As a member of SANMUG, attending meetings and/or other SANMUG Events, either in person, or virtually, and with due care to ensure that contacts with competitors do not otherwise create a basis for anti-competitive conduct, I declare the following:

Before attending a meeting

(i) I will ensure that I have received a meeting agenda in advance and, should there be concerns about any agenda content, I will raise those concerns directly with

While at a meeting

* Current, near-past or imminent pricing, costs, discounts.

* Future business plans.

* Current, near-past or imminent output levels, including stock/W-I-P, inventories,

production, sales, volumes or capacity.

* Bidding tactics.

* Specific customers, territories, market shares or product or service lines and offerings.

* Wages, salaries, remuneration paid by participants.

* Specific terms and conditions of sale.

* Credit terms and discounting arrangements.

* The timing and effect of any planned manufacturing or plant shutdowns (or start-ups).

* The timing of any price increase or decrease.

* Any other competitively sensitive topic.

In addition, I will ensure that:

* I will stick to the agenda

* I will not engage in informal or side conversations with other members

* I will exercise good judgment at all times

Should things go wrong, like anti-competitive behaviour, inappropriate remarks, I will ensure the following:

* I will not engage in the improper conduct

* I will raise the matter directly with the chairperson and ask that concerns/objections are noted in the meeting minutes

* Should inappropriate discussions continue, I will leave the meeting immediately and have it recorded in the meeting minutes, making comprehensive notes as soon as possible after leaving the meeting, including the time the issue was raised or comment made, what was stated (‘word-for-word’ or as near as possible), other members comments and my own actions.

Further, that I will evaluate critically what the meeting is aiming to achieve, while being vigilant, for instance, that activities like standard or policy setting don’t restrict entry into the industry, don’t deter innovation, nor discriminate against competitors or otherwise inhibit the ability of persons to compete.

Download the full Metadata Requirements List here: download me!


Criteria for selecting an ONIX supplier

Some criteria for choosing a supplier for your ONIX needs

Are you looking for help with creating ONIX records for your books? You don’t have to code XML yourself! There are various ONIX software suppliers on the market that cater to publishers’ needs and can assist you with implementing ONIX for Books standards in your workflows.

Here are some questions to ask about potential suppliers:

  • Do they provide accurate, consistent ONIX messages to receivers that are in line with current ONIX and Thema specifications (e.g. ONIX1 and Thema 1.5)?
  • Do they have reputable distribution partners that receive their metadata? Do they send to your big distributors and booksellers?
  • Do they have a reputation for handling metadata produced? Do they have a low error rate with organisations who provide assessments? e.g. BIC, Editeur
  • Do they have similar clients to your business size and unique business requirements?
  • Do you need other services that they are able to assist with? (e.g. book metadata management, title management, content management, production, royalties, forecasting)
  • Are they responsive to your queries even if you are from a small organisation?
  • Do they participate in industry-wide standards bodies?
  • Are they able to manage multilingual metadata?

Download the full Metadata Requirements List here: download me!


Product guidelines – Forthcoming


General

Click the link to learn What Metadata is: What is Metadata



Current ONIX Codelist – Browse the ONIX Codelists or search for a specific term

Click the link for the current ONIX Codelist, where you can browse the ONIX Codelists or search for a specific term: click here


Thema

What is Thema?  Thema is the global and multilingual subject classification for books, e-books and audiobooks which has already gathered wide international support: More info here

Using Thema – a guide, click here

View the current Thema Category Browser: here

Click the image to be redirected to the introduction to Thema video


PASA Metadata Committee

This committee aims to serve members of PASA by providing information on updates to the ONIX and Thema standards, documentation and resources that will be useful, commenting on proposed adjustments to the standards and policies, and representing PASA at key metadata engagements. This work around policy and standards could be directly beneficial to PASA members to expand the depth of ONIX and Thema for particular local needs.

Terry Morris, Louise Grantham, Nigel Ryan, Kirsten Perkins, Gabrielle Jacobs, Silma Parker, Estienne van Wyk, Pinky Magadla, Gill Moodie, Laetitia Cassels.


Training for PASA members

PASA has undertaken (with generous support from the FP&M SETA) to fund training for approximately 45 member publishers before the end of 2024. We have also secured funding for 2025 for a similar number of people, including a course of the advanced ONIX usage. We hope by the end of 2025 to have also provided advanced ONIX training for at least 70 people who in turn will enrich our publishing companies and the broader industry. NB This training is for PASA members only.

16 July 2024 – Thema, a briefing for marketers: This will be a brief and basic overview of what Thema is and how it can help with the discoverability and marketing of titles in South Africa and beyond.

For further details and registration, contact PASA (e-mail pasa@publishsa.co.za)

16 to 18 September 2024 – ONIX Essentials plus training course. Please follow the link to register https://www.editeur.org/3/Events/Event-Details/692

5 to 7 November 2024 – ONIX Essentials plus training course. Registration link forthcoming but please send queries to PASA (pasa@publishsa.co.za)


SA National Metadata User Group

PASA also convenes South Africa’s National Metadata User Group which comprises publishers, retailers, distributors and agents, university information science and publishing departments, and the National Library of South Africa. This is a leading cross-industry group with the clear and focused intention of ensuring that all books published in South Africa are afforded the technical and cataloguing investment to ensure they are discoverable and accessible. PASA also represents the broader national interest in presenting and contributing to the development of subjects and technical and language requirements to the International Steering Committee for ONIX and Thema.

PASA, SABA, Booksite Afrika, Caxton Books, Blue Weaver Distribution, PUKU.