Product Coordination Group

PCG#11

October 2026

The two sessions of the meeting have been blended into a single report wherever possible for clarity and completeness. The text of this summary was edited with the help of AI.

Introduction

The OBIS Products Coordination Group met in two sessions. The agenda covered the governance and release plan for the OBIS Products Catalogue, statistics on Node pages to support reporting against CBD Targets 20 and 21, and preparations for SG-OBIS-14.

Products Catalogue

Status. Products are being added to the catalogue incrementally, starting with those developed by the OBIS Secretariat, where the Secretariat can update the metadata as required. There is still a long way to go before the catalogue can be considered rich and fully functional, and the hope is to begin adding products from the community soon. The catalogue was designed so that it can be connected to ODIS, but it does not yet have connected status; Silas Principe will check this.

Catalogue governance and release plan

Thanks were extended to everyone who commented on the governance proposal. Most comments could be incorporated, and those still open were discussed in the meeting, with the aim of final comments and ratification. The release plan is a KPI for 2026-2027. Ward Appeltans will review the current text and provide input.

Derived products, DOIs and provenance. Ward Appeltans is looking at derived products, such as cases where researchers download all OBIS and GBIF data of a particular type, carry out an analysis, and publish the full dataset alongside their paper. OBIS can already create DOIs for a subset of data that link to all the underlying data, and this needs to be promoted more, because provenance control is being lost. These DOIs are not currently linked to a particular snapshot. One possibility is for them to resolve to one of the periodic snapshots, in which case users would need to be instructed to use the snapshot when creating their subset. In all cases, the underlying data must be properly cited and its licences respected.

→ Eduardo Klein asked whether OBIS is ready to issue DOIs for queries that point to the right archive. It was noted that OBIS does not currently archive data on a regular basis, and that some people are using OBIS data under licences that do not respect the original licences. A share-alike approach might be one solution.

→ Pablo Deschepper suggested flags for specific methods, and filters.

Repositories and direct upload. Members were asked to flag other repositories they would like the catalogue to support. Products can also be uploaded directly to the catalogue, but the benefit of a landing page in an external repository is that the catalogue entry stays synced to the latest version of the product.

Open questions. The group discussed whether the PCG could play a role in curating or reviewing submitted products. It also discussed a proposal that a product could be excluded if it is no longer maintained or useful. Ideally the catalogue would hold products that are still maintained, but a register of products that are no longer maintained still has value as a snapshot of a point in time. On reproducibility, the question was whether a product with a good methods section but no code should be accepted, or whether the catalogue should be strict. One option is different categories of product: maintained; no longer maintained but of interest; and not openly available (for example, Indigenous content) but worth publishing. Eduardo Klein noted that a product his team created is very well documented and its code exists, but is bespoke to their system, and that the curation process of the catalogue matters more.

→ In the second session, Dan Lear recalled that Katherine Tattersall had suggested potential tags to describe product status. Jon Pye stressed that the objective is not to disqualify products but to showcase what is available.

→ Tom Webb raised the case of a “stack” of products: a product that is not purely a model, a derived dataset or anything else, but a mix of these. Dan Lear pointed to the BODC vocabulary for EMODnet processing levels (https://vocab.nerc.ac.uk/collection/EPL/current/), and the group discussed including these processing levels in the recommended metadata. Tom Webb shared an EMODnet paper that used these product levels and added a “computational tools” box (see figure 1 of https://doi.org/10.1016/j.marpol.2024.106578).

Node page statistics for Targets 20 and 21

The two CBD targets under discussion are:

Rather than publishing a periodic report, for example every year, the OBIS website could be improved by including Node metrics on each Node page, with scope for other, potentially even more interesting, metrics to follow. Pieter Provoost is exploring an elegant metric of the “growth of information” in each area, still in development, which incorporates taxa, number of cells and year. Jon Pye noted that it resembles a metric OTN uses to determine the value of a single observing station when weighing operations costs against station value. When the statistics will appear on obis.org is a KPI for 2026-2027, with nightly caching and API development under consideration as approaches.

Demonstration. Silas Principe demonstrated a prototype showing taxonomic completeness, depth coverage, records by year, records by month (seasonality) and published records by year, among others, with a button to generate a report that can be saved as a PDF. The same approach could be used to enrich information at the dataset level, including dataset-level insights.

Problems. The information currently comes from the metadata of datasets published by Nodes (when each was created, published and updated). As a result, it is not possible to say how many records were published in a given year if a dataset has since been updated. Using past snapshots or archives would give an accurate view of growth over the past year. Eduardo Klein noted that versioning cannot recover the past, but can be put in place for the future. Katherine Tattersall asked whether the information could be obtained from the IPTs; Dan Lear noted that this may vary from organization to organization, and Pieter Provoost suggested checking the IPTs for older dataset versions.

EOVs and effort information. Ward Appeltans asked how effort information for EOVs will be made available, noting that it is a potentially important metric.

Preparations for SG-OBIS-14

A hands-on activity is planned at SG-OBIS-14 on potential metrics and information to add to the database, including how to produce periodic reports, with examples such as OTN, Ecuador and Brazil. Silas Principe will describe the activity. A further idea is a short demonstration of how to add products to the catalogue. Jon Pye will attend remotely.