Product Coordination Group

PCG#6

December 2025

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 (PCG), co-chaired by Stephen Formel and Jon Pye with Secretariat support from Silas Principe, met in two sessions. The agenda covered updates from the Secretariat, the development of the group’s annual plan, and a first hands-on test of the OBIS Products Catalogue.

Updates from the Secretariat

Meetings and notes. All PCG meetings until October 2026 have been scheduled and invitations sent to members. Meetings will take place ahead of the bi-monthly OBIS Nodes Coordination Group (NCG), to which the PCG reports. The group now keeps a single running document for its notes, which should make information easier to find.

New members. Tom Webb (University of Sheffield) and Yulia Egorova (AquaMaps) introduced themselves and were welcomed to the group.

Google Drive. Stephen Formel introduced the new organization of the OBIS Secretariat Google Drive folder. Some files or links may have been orphaned during the transfer, and members are asked to report any problems.

OBIS website. The coordination groups now have a page on the OBIS website (https://obis.org/community/coordinationgroups/), linked with OceanExpert. Members whose names are missing should let the Secretariat know. The e-mail list is not connected to OceanExpert, so both lists need to be kept up to date.

Public sharing of notes. Following a conversation in the Data Coordination Group, the public sharing of meeting notes is back under discussion. The Secretariat is considering sharing summary points on the website rather than full notes, and the Co-Chairs will discuss the approach.

Developing the annual plan

Stephen Formel introduced the group’s work plan, drawn from the 2026-2027 OBIS Work Plan agreed at SG-OBIS-13. An annotated agenda was to be published the same week. The PCG has three outcomes for the cycle:

The data product pilot. Members were reminded of the DFO Canada presentation from September 2025, and asked whether there was interest and capacity to test an extension of that idea in their own regions, toward a generalized approach. Ideas raised included the DFO example, ALAN, and collaboration opportunities around EBSAs.

→ Katherine Tattersall said she would explore the idea further. The Australian Node is currently more involved in data mobilization, but works in collaboration with other Australian groups (AODN/NESP or ARDC) that may be interested.

→ Eduardo Klein offered to showcase the reporting for government being carried out in a joint CSIRO-IMOS project.

→ Ben Donnelly noted his involvement with EBSAs and was happy to engage. Kit Elloran was noted as having relevant work in his region, to be followed up.

→ Ward Appeltans suggested the possibility of a sub-group for MPA, EBSA and area-based management support.

Products Catalogue test

Stephen Formel demonstrated a live test instance of the Products Catalogue, built on CKAN, and participants were invited to try the admin area. The instance remained open for asynchronous feedback over December, with issues to be logged on the GitHub repository (https://github.com/iobis/obis-products-catalog/issues). Feedback was particularly sought on vocabularies, such as product types, and on the review process.

Data ingestion. Products can be added manually or through Zenodo, which is the preferred route and works well with GitHub.

→ Sachit Rajbhandari asked whether plugins for other repositories would be available. Stephen Formel confirmed they would: Zenodo was chosen as the starting point because it was the repository the team knew best for prototyping, and others can be added in future.

Relationship with ODIS. Katherine Tattersall asked whether CKAN could connect directly to Nodes that act as their own repositories linked to ODIS, noting that adding a further layer such as Zenodo between the Node and the catalogue may not help visibility. Stephen Formel said this was possible and needs to be explored. Eduardo Klein asked whether the catalogue risked duplicating what already goes to ODIS. Stephen Formel acknowledged that some duplication might occur but did not see it as necessarily a problem, and Eduardo Klein noted that the catalogue may be more permissive in the types of product it accepts, which is of interest. Ward Appeltans added that ODIS is a technology, and that OBIS is the biological component of ODIS: the two are not in competition, since OBIS implements ODIS.

Structure of the catalogue. Stephen Formel presented an initial set of categories, open for discussion. Dan Lear recalled that EOVs had been suggested as thematic areas at the Bogotá meeting. Organizations, communities and groups are all connected to OceanExpert, which simplifies administration; in response to a question from Victor Chocho on how groups and institutions will be curated, Stephen Formel confirmed that this is handled through OceanExpert, where some fixes are still needed. Items currently labelled “Datasets” will be renamed “Products”, to avoid confusion with OBIS datasets. Clara Baringo noted that shapefiles are also needed and could form one product category.

Review process. There was general agreement that some review is needed but should be light. Stephen Formel favoured keeping it as lightweight as possible; Eduardo Klein saw value in some review to keep products of insufficient quality out; and Silas Principe agreed it should be light. Stephen Formel noted that curation still needs further thought, and that the group’s central challenge is discoverability: making things easier to find.

Experience with CKAN. Several members shared CKAN instances they are involved with:

→ Ben Donnelly suggested that a link with Global Fishing Watch might be of interest.

Other updates

Eduardo Klein offered to showcase a product from IMOS Australia at the next meeting: an aggregated, value-added, cloud-optimised file initially created by combining OBIS-AU seabird resources.

Jon Pye shared the GBIF animal tracking example (https://animal-tracking.hp.gbif-staging.org/occurrence/search?view=map), noting there may be lessons for the Products Catalogue in GBIF’s decision-making, though not necessarily in its software stack. Hanieh Saeedi suggested doing something similar for invasive species, interlinked with WRiMS.

Action items