Nodes Coordination Group

NCG#8

December 2025

The two sessions of the meeting have been blended into a single report wherever possible for clarity and completeness. The meeting slides are available here (https://docs.google.com/presentation/d/1PJKPUQJ8tiverPEX31Nz0uTSlLZRwoihk59bvb8oV3M/edit?usp=sharing).

Introduction

Co-Chairs John Nicholls (first session) and Maria Cornthwaite (second session) welcomed participants. They noted that while this meeting implemented the structural changes adopted at OBIS-SG-13, to give the Nodes more space for discussion, the density of the proposed agenda slightly hindered participation possibilities. The Co-Chairs noted that an effort will be made to preserve discussion spaces in the upcoming NCG meetings.

“Developing a Data Extension for Documenting Socio-Biodiversity Information.”
A presentation by Clara Baringo Fonseca, OBIS Brazil Node Manager

Clara Baringo Fonseca presented the results of a CESP project focused on developing a Darwin Core extension for documenting socio-biodiversity information, aiming to better include, structure, and standardize data on species use, vernacular names, and holders of associated knowledge.

The underlying issues

The presentation highlighted a persistent gap in biodiversity data publishing: while species occurrences are well structured through Darwin Core, information on how species are used, by whom, and in which cultural or social contexts is poorly standardised or lost entirely.
This affects:

Recognition and visibility of Indigenous and local knowledge

Attribution and governance of traditional knowledge

Reuse of socio-biodiversity data in policy, conservation, and sustainability contexts.

What the extension does

The proposed extension:

Builds on the taxon core and the vernacular names extension.

Introduces new terms to capture:

> Type of use (useTo), supported by controlled vocabularies (for example, food, medicinal, ,

fuel, …).

> Organism part used (organismPart, organismPartDescription).

> Form of use (useForm, useFormDescription).

> Who uses the species (usedByType, usedByHolder), allowing representation of

Indigenous Peoples, local communities, fishers, quilombolas, and others.

> Source of knowledge (useSourceType, useSourceDescription).

> Spatial and temporal context (useWhere, useWhen).

Controlled vocabularies were developed for several key terms, and the extension documentation was produced in English, Spanish, and Portuguese.

How it was developed and tested

The extension was co-developed through:

A series of online webinars.

An in-person workshop (Brazil).

Collaboration between Brazil, Colombia, and Argentina.

It was validated through three study cases, which are particularly relevant for Nodes:

Historical literature (17th–19th century sources): highlighted limitations in attribution and governance but demonstrated that the extension can structure legacy knowledge.

Community-based interviews: showed that the extension works well for contemporary data collection, allowing rich documentation of users, uses, and sources.

Current collections and herbaria: revealed that socio-biodiversity information is often missing or poorly attributed in formal collections, reinforcing the need for better guidance.

Remaining challenges

Collective authority and co-authorship: Current publishing tools (such as IPTs) do not easily support collective or community-level attribution.

Licensing and consent: Traditional knowledge requires governance discussions beyond data structuring.

Temporal representation: Traditional knowledge does not always map cleanly to discrete dates, requiring careful use of temporal terms.

Marine applicability: Initial vocabularies are more plant-focused; marine and animal-based knowledge will require additional work.

The work will feed into discussions within the GBIF Task Group on Indigenous Data Governance, and further iterations are expected.

Additional clarifications from the Q&A

Further development will be needed to accommodate marine-focused controlled vocabularies.

To address the challenge of representing time in traditional knowledge spanning generations rather than dates, “useWhen” and “useWhere” can be employed to capture temporal context, but additional developments might help better answer that need.

These questions reinforced the need for additional validation, especially for marine and Indigenous knowledge contexts, and for continued discussion at technical and governance levels.

OBIS-GBIF Brazil Data Publishing Tool (beta version)
A presentation by Clara Baringo Fonseca, OBIS Brazil Node Manager

Clara Baringo presented the OBIS-GBIF Brazil data publishing tool (beta), designed to complement the Node’s IPT by providing stronger data organisation, validation, and quality-control workflows, especially for sampling-event and campaign-based datasets.

Why was this tool developed?

The tool responds to practical challenges faced by Nodes and institutions:

Difficulty tracking who publishes data, from which institutions and projects.

Limited flexibility in applying custom quality checks in IPT.

Challenges in managing campaign-based data with repeated sampling and measurements.

→ The tool is not intended to replace IPT, but to prepare and validate datasets before publication.

Core functionalities

Key features demonstrated include:

User and access management

Role-based access (institution administrators, project managers, contributors).

Ability to invite users and assign publishing rights.

Project- and campaign-based organisation

Datasets can be linked to projects and campaigns.

Validation rules can be defined per campaign

Enhanced validation and quality control

Possibility to define validation rules for variables (for example, pH ranges, oxygen values).

Integrated TDWG/GBIF quality tests with readable reports.

Errors and warnings can be reviewed and corrected directly in the interface.

Darwin Core mapping workflow

Step-by-step process:

Data upload

Darwin Core term mapping

Variable and measurement mapping

Quality checks and corrections

Variables are converted into:

measurementType

measurementValue

measurementUnit

measurementMethod

Unmapped variables can be retained in dynamicProperties as structured JSON.

Output and publication

The tool generates a Darwin Core Archive. The archive can be:

Published via an IPT

Downloaded for publication through another IPT or repository

Intended use cases and limitations

Clara Baringo Fonseca clarified that the tool is best suited for:

Small to medium-sized datasets

Campaign-based or project-based sampling

Datasets requiring custom validation rules

The tool is not designed for:

Very large, long-term aggregated datasets

Fully automated bulk publishing without human oversight

Additional clarifications from the Q&A

The tool will support different access models, including independent users.
An API for data quality functions is under development, which could allow reuse by other Nodes or tools.

The interface is intentionally designed to feel familiar to IPT users, lowering the learning curve.

Next steps / Nodes are encouraged to:

Consider how custom validation rules could improve data quality before publication.

Explore potential reuse of the quality-control components once the API becomes available.

Provide feedback on Integration with existing IPT workflows

OBIS Node-to-Node programme: implementation proposal
Presented by John Nicholls & Maria Cornthwaite, OBIS NCG Co-Chairs

The Node-to-Node Support Programme was presented as a core structural evolution of how OBIS Nodes support each other, moving from fragmented, ephemeral support channels to a documented, discoverable, and multilingual peer-to-peer system. The programme is designed to strengthen horizontal exchange between Nodes, reduce duplication of effort, and ensure that knowledge generated within the network remains community-owned and accessible to all over time.

The presented implementation is a proposal, open to comments, suggestions, and feedback from the OBIS Nodes. The working name proposed for the programme is OBIS Training and Technical Exchange Resource (OTTER). The implementation proposition aims to establish:

1. Discourse-based Node support hub

A dedicated Discourse space will be created, reserved exclusively for OBIS Nodes.
This space will include three sections:

- supports long-term archiving and structured discussions

2. OBIS FAQ as a living output

Under the proposed implementation plan, the OBIS FAQ would become a central knowledge hub for the OBIS Community. It would gather flagged content (issues and their solution) from all the OBIS support channels: Helpdesk, GitHub and Discourse.

  1. A question is asked on Helpdesk, GitHub and Discourse
  2. One or more contributors provide answers or solutions
  3. If deemed FAQ-relevant, the discussion is flagged
  4. The text is lightly edited using AI with human oversight
  5. The discussion is added to the OBIS FAQ, and includes the names of the contributors
    This ensures that:
    • recurring questions do not need to be answered repeatedly,
    • institutional memory is preserved and archived
    • Nodes can self-serve information more easily
      As noted in the discussion following the presentation, Node teams will need time to learn to assess discussions worth flagging, but this behavioural shift is key to making Discourse effective.

3. Multilingual access

Multilingual access is a core pillar of the programme, and will be achieved through a multi-approach:

4. Recognition and incentives for contributors

The programme explicitly recognises that Node-to-Node support is work and should be acknowledged. Planned recognition mechanisms include:

\5. Reorganisation of support channels (optional phased approach)

The proposal includes a proposal to close the Slack #support channel and replace it with an open-to-all support channel on the OBIS Discourse, distinct from the Node support channel, where resolved issues could also be flagged to be lifted into the FAQ. The migration will be incremental. Importantly, only the Slack #support channel would be closed. Other channels would remain, allowing for private Node communications.

\6. Next steps / Nodes are encouraged to:

- Review the implementation proposal and provide feedback

guidance shared by the Secretariat.

Steering Group Updates

Presented by Dan Lear & Katherine Tattersall, OBIS SG Co-Chairs

Follow-up from SG-13 and alignment with GOOS and BioEco

Following discussions at SG-13 in Bogotá, the Steering Group has continued close engagement with GOOS and the BioEco panel. The GOOS Biodiversity Plan, presented to the Nodes at SG-13, has since undergone further review and discussion with the GOOS team. A revised version of the plan has now been submitted to the BioEco panel for subsequent review, with additional iterations expected before being brought back to the OBIS Executive Committee for consideration.

Representation at high-level meetings and international fora

OBIS SG Co-Chair Katherine Tattersall has represented OBIS at several high-level meetings, including

perspectives were presented.

- The Ocean Biodiversity Observation Network (OBON) meeting, a UN Ocean Decade programme,

where OBIS approaches to eDNA and biodiversity data publishing were showcased.

- Additional events related to OBIS eDNA dashboards, including representation at the MOTI meeting.

Upcoming governance and coordination meetings

The next IODE management meeting will take place in Ostend on 28–29 January, bringing together IODE programme components and related bodies. Both SG Co-Chairs will attend. An in-person meeting with the GOOS team is planned in connection with this, alongside efforts to schedule a meeting with GBIF to advance work under the OBIS–GBIF Implementation Committee.

Engagement with GBIF and European initiatives

OBIS is exploring joint activities with GBIF in the context of European BioMon Week, to be held in Montpellier, France, in early May 2026. The event is coordinated by Biodiversa+ and co-delivered with GBIF, with potential joint sessions proposed on EOV–EBV alignment, data standards, data flows between infrastructures.

Next IODE Steering Group for OBIS meeting (SG-OBIS-14)

The next OBIS Steering Group meeting will be held in Ostend from 11–16 November, scheduled back-to-back with the World Conference on Marine Biodiversity (WCMB) in Bruges. This timing is intended to maximise participation and alignment with the broader marine biodiversity research community.

Data Coordination Group Updates

Presented by Ruben Perez Perez, OBIS DCG Co-Chair

DCG composition and participation

The Nodes are actively encouraged to join the DCG; interested participants can contact the DCG directly or reach out via the Secretariat or NCG co-chairs. All members of the OceanExpert subgroup within the DCG have now been added to the Slack channel to improve awareness of ongoing discussions and coordination, alongside formal Secretariat communications.

2025 work plan and deliverables

Following the OBIS workplan adopted at SG-OBIS-13, tasks in the DCG are organised into subgroups, each responsible for specific deliverables. A shared table (https://docs.google.com/spreadsheets/d/1yy1-_w3l3g4UeLot4Mq_pMJ5fV2mMLwq-n9HqRyBsiQ/edit?gid=0#gid=0) has been created where Nodes can volunteer for individual deliverables by adding their names; DCG leads will follow up to initiate subgroup work.

The group is currently reviewing:

Lessons learned from the previous year

Possible adjustments to working methods and group dynamics for the new cycle.

New thematic teams and cross-infrastructure collaboration

In addition to the planned deliverables, two new thematic teams have been established:

Collaboration with GBIF on the Darwin Core Data Package how-to guide
The DCG has been asked to support GBIF by contributing expertise to a how-to guide for the Darwin Core data package. A dedicated team has been formed and is already collaborating with GBIF counterparts. Additional interested Nodes are welcome to join this effort.

AI use and acknowledgement in relation to OBIS data
A new team has been created to explore AI usage of OBIS data, with a focus on developing a possible acknowledgement statement or guidance. This group is currently in an exploratory phase and will report back once ideas have been further developed.

Next steps

DCG meeting dates for the year have not yet been finalised. Invitations will be circulated once coordination with the Secretariat is complete; members were reassured that these are forthcoming.

The DCG is currently focused on making the new subgroups operational, initiating work on priority deliverables, and strengthening collaboration with GBIF and across OBIS technical communities.

Products Coordination Group Updates

Presented by Silas Principe, OBIS Secretariat Researcher, as well as Steve Formel and Jon Pye, OBIS PCG Co-Chairs

Recent meetings and ongoing focus

The Products Coordination Group has held its first meetings of the new cycle in recent weeks.

Discussions focused on keeping PCG meetings regular and continuous, advancing work on the OBIS products catalogue, and continuing the hands-on “workout” approach used previously in Bogotá to review and test catalogue entries.

Products catalogue development

The group conducted another round of interactive review sessions on the OBIS Product Catalogue. Nodes are encouraged to explore candidate entries in the catalogue, report bugs, gaps, or issues via the catalogue issues page on GitHub (https://github.com/iobis/obis-products-catalog/issues). Additional invitations to contribute feedback and test catalogue entries will be shared through the OBIS Nodes newsletter.

National pilot on policy uptake

The PCG revisited the idea of a national pilot demonstrating how OBIS presence data can be used in policy contexts. This builds on a previous presentation by Fisheries and Oceans Canada (DFO) on evaluating marine protected areas using OBIS data. Two key conclusions were highlighted:

A national pilot could effectively showcase policy-relevant OBIS data pipelines

There is interest in forming a cohort of Nodes to re-implement and adapt these workflows

Volunteers to help lead or participate in this pilot are still being sought.

External speakers and upcoming discussions

The PCG plans to invite contributors to present concrete product use cases at future meetings.

At the next PCG meeting (February), Eduardo Klein and Sachit Rajbhandari will present work on visualising and developing seabird biodiversity data products. These guest presentations are intended to inspire product development and better align OBIS products with user and policy needs.

Next steps

Further calls to engage with the OBIS Product Catalogue will be circulated shortly. Nodes are encouraged to test catalogue entries, provide structured feedback via the issues page, and participate in upcoming PCG meetings and pilot discussions. The PCG is looking ahead to February discussions and continued iterative improvement of OBIS products.

OBIS Secretariat Updates

Presented by Ward Appeltans, Head of the OBIS Secretariat

OBIS-GOOS FUST proposal

The Secretariat is currently preparing a funding proposal to be submitted in mid-February under the UNESCO Trust Fund for Science, in collaboration with GOOS. The proposal focuses on strengthening OBIS data products by developing modular, intermediate components that can support multiple downstream use cases, particularly decision-support applications. The objective is to bridge the gap between the OBIS database and applied tools by making products more operational, reusable, and policy-ready. In coordination with GOOS, the Secretariat has agreed to prioritise a marine heatwave use case to explore how marine heatwaves affect biodiversity. This use case is being co-designed with GOOS, with an initial pilot focus in the Caribbean. While marine heatwaves are the first focus, the work is intended to support multiple policy frameworks, including CBD and BBNJ, through adaptable components rather than single-purpose tools.

Outreach, presentations, and community engagement

OBIS has recently been presented at several external fora, including a dedicated session of the GBIF Technical Support Hour (featuring a presentation and discussion led by Elizabeth Lawrence, OBIS Training Officer) and with the DataONE community (featuring presentations and discussions by Steve Formel, OBIS Data Officer, and Ei Fujioka, OBIS-SEAMAP Node Data Manager). These presentations aim to strengthen visibility of OBIS data products and reinforce collaboration with adjacent data infrastructures.

eDNA Expeditions – call for sites

A call for marine sampling sites (https://obis.org/2025/12/17/Call-for-sites/) is currently open for participation in the eDNA Expeditions project. The project plans to support 25 sites, providing sampling kits and guidance to carry out 6–9 eDNA sampling campaigns per site. Priority is given to sites that can build on existing monitoring programmes and work in close connection with OBIS Nodes. The call remains open until mid-February, and Nodes are encouraged to help identify and connect suitable sites, including (but not limited to) marine protected areas.

OBIS engagement with the CBD Secretariat and the Cali Fund

The Secretariat has initiated discussions with the CBD Secretariat regarding the Cali Fund, which aims to support biodiversity action in developing countries. The purpose of the Cali Fund is to support countries in implementing the Global Biodiversity Framework, and especially their National Biodiversity Strategic Action Plans (NBSAPs). Only the Global South and SIDS can apply to the fund.

OBIS has been approached to support some of the biodiversity metrics used in the fund:

- “How many genetic resources does a country contribute, and how many genetic resources from that country are used?”

- “What are the capacity development needs in the country?”

There is a strong interest from the CBD Secretariat in relying on global data systems, such as OBIS and GBIF, rather than country-specific metrics, to ensure comparability. Countries could use OBIS to make their claim to get funding from the Cali Fund. This has a Direct implication for OBIS Nodes: national CBD focal points may push to ensure national data are in OBIS, because otherwise the metric will not show very strongly.