December 2024
The text of this summary was edited with the help of AI.
The first meeting of the OBIS Products Coordination Group (PCG) was chaired by Stephen Formel, with Secretariat support from Silas Principe, and hosted on MS Teams by OBIS-USA. The agenda covered introductions and members’ hopes for the group, updates from the Secretariat, a review of the purpose of the PCG as set out at EC-6, the resources members could contribute, and the Products Catalogue.
Participants introduced themselves in the context of OBIS and described what they hoped the group would achieve. The hopes expressed included:
Members fell broadly into three groups: those using the PCG as a touch point for OBIS, to listen and learn; those wishing to contribute but without specific ideas yet; and those wishing to contribute with specific ideas.
Indicators for the CBD. OBIS is referred to in the CBD target indicators. Ward Appeltans suggested the group could help develop indicators and other products that help countries monitor and report to the CBD, going beyond a simple count of records. Victor Chocho and Hanieh Saeedi highlighted the importance of such indicators and tools as a source of information for BBNJ, CMS, CITES and IPBES.
Project results. Ward Appeltans reported on the final results of eDNA Expeditions (dashboard: https://dashboard.ednaexpeditions.org/), which was presented at a press conference, and of PacMAN (https://portal.pacman.obis.org/), which held a successful final meeting in Fiji. Both can be developed further and promoted. Recent results for MPA Europe (https://shiny.obis.org/distmaps), on which Silas Principe is working, have also been positive: the European Commission was very impressed with the distribution maps and highlighted the project’s success in achieving the FAIR principles.
Members were reminded of the purpose of the PCG as set out at EC-6. The EC-6 document records where the group has come from and which tasks were identified as priorities.
The EC-6 notes proposed that the first PCG meetings should be used to identify the scope of resources available to carry out the group’s actions, including how much time Nodes can contribute outside meetings, and whether Nodes have compute or other resources to share. This item was folded into the Products Catalogue discussion. OTN uses GeoServer, and nationally CKAN, and can share expertise in both; it can also teach Carpentries courses on topics such as Git and GitHub. VLIZ also uses GeoServer and can share its expertise.
The EC-6 notes identified the Products Catalogue as a clear priority, to inform users about the existing data products supported by OBIS.
JupyterHub and CKAN. Silas Principe reviewed the status of the infrastructure on behalf of Pieter Provoost. OBIS runs a JupyterHub (https://jupyter.obis.org/), and Pieter Provoost has proposed CKAN as the catalogue platform (https://ckan.obis.org/). The idea is not to show the same data as OBIS but the products derived from it; for now the instance holds only a few examples, such as the gridded product and the full OBIS export.
→ Jon Pye noted that oceanographic data providers in Canada also use CKAN, and that CKAN is stackable: for example, the CIOOS Atlantic catalogue (https://catalogue.cioosatlantic.ca/en) nests into the national CIOOS catalogue (https://catalogue.cioos.ca/). Hanieh Saeedi added that Senckenberg uses CKAN for its research data management metadata.
→ Salvador Fernandez said VLIZ has experience using GeoServer with data products and was happy to discuss it. Jon Pye explained that GeoServer is an OGC-standard geospatial data server, and that OTN runs one too.
Proposed infrastructure. All code lives on GitHub. Products are developed in the JupyterHub and, once in good shape, move to Airflow, an Apache technology for scheduling runs of code from GitHub. Airflow produces the products in a data lake, from which they are catalogued in CKAN and GeoServer.
The group worked through a set of open questions:
→ Ben Donnelly described how his team approaches data downloads and packaging, for example asking users before they download whether they would like to discuss the data or have any questions, to get a better understanding of why people use the data. Jon Pye noted that data consultations involve a balance between consultation and open, FAIR data: it is valuable to hear how data is being used, and knowing why is very useful for funders, but putting up barriers often turns people away. Ben Donnelly agreed, stressing that the aim is not to create barriers but to understand better what makes an ideal data product for different users.
Members began recording the relevant products, solutions and experience they could share:
| Product or solution | Description | Node, person or institution |
|---|---|---|
| GeoServer experience | Publishing data (from PostgreSQL) and data products (from NetCDF) | EurOBIS (EMODnet) / Salvador Fernandez / VLIZ; OTN / Jon Pye; OBIS-AU / Sachit Rajbhandari; OBIS-SEAMAP / Ben Donnelly |
| CKAN experience | Metadata catalogue advertising and contextualizing available datasets | OBIS Deep Sea |
| Product and file interoperability standards | CF- and COARDS-compliant NetCDF files hosting biodiversity data products, with a guide and demo | EurOBIS (EMODnet) / Salvador Fernandez / VLIZ |
| GitHub Carpentries training | Teaching users how to collaborate using Git and GitHub | OTN / Jon Pye; OBIS-SEAMAP / Ben Donnelly |
| GeoNetwork metadata catalogue | OBIS-AU / Sachit Rajbhandari | |
| Metadata generator (JSON-LD and sitemap), in development | Submitting a GitHub issue automatically generates metadata in JSON-LD using schema.org vocabulary, and a sitemap. To be used for EOV datasets and to make it easier to add entries to ODIS | Elizabeth Lawrence / OBIS Secretariat |
Rows for compute (HPC) available to Nodes or PCG partners, and for storage, were added but not yet filled in.