Summaries and key moments are machine-produced. Check the recording for the speaker’s exact words.
The short versionDwC-DP promises to carry the relational richness that previously pushed GFBio centres to ABCD, and a first DWB-to-DwC-DP prototype via the test IPT works.
↶Go back to 2025Data Package pilot · 1 connection↓
Revisit Living Data 2025 alongside this talk. These connections were checked against captions; related examples may come from different teams rather than a direct follow-up.
Related example
ABCD community support → a DWB mapping prototype
2025 Living Data
Anton Güntsch welcomes relational data exchange through DwC-DP and says the BioCASe help desk will extend support to it.
Two Decades of ABCD: Advancing Structured Biodiversity Data Sharing
and transmitting relational structures over the internet uh finally comes true. So what we would like to do as a bioase ABCD initiative is really to support this initiative for example for example by contributing to the development and maintenance of the ding code data package standard and also uh for developing templates for typical usage scenarios. We will however continue the bioase help desk. So we will not let the bioase ABCD providers alone but we will extend the focus of this help desk to structured uh highly structured data complex data using the DAC data package technology and um I can now can't read more what here on the slide um yeah that's actually again that we want to to integrate the Darving core data package structures into our help desk uh uh structures and that's exactly what I wanted to say.
2026 This talk
Tanja Weibulat shows mapping Diversity Workbench’s PostgreSQL tables to DwC-DP using the test IPT.
Mapping the Relational Data Schema of the Diversity Workbench (DWB) to the Darwin Core Data Package Data Model to fit better to GBIF´s New Data Model
tool and the Darwin Core Data Package instead of ABCD. So we get a Darwin Core Data Package. So we tried it. We installed an IPT, not the official one, but a test version, because only the test version includes, at the moment, the Darwin Core Data Package. So we were installing the test version of the IPT, and that's what was our first step. So that's a screenshot of the IPT installation. So first, we added our source data. What you can see here are all the tables from the Diversity Workbench, from the PostgreSQL data. So we accessed it directly via SQL. And second, we had to do the mapping of all this data. So the first one is always the Diversity Workbench table, and the second one is the Darwin Core Data Package table. And as you can see, it's often quite similar, but not all the time. So for example, we need to separate our observation data and the physical specimen data. That's separated here in the Darwin Core Data Package. It was together in the original one, and it leaded to occurrence data and material data down here. Then some things have been together. They share, for example, the event up here, the identification, and also the agents. And then we had to unite some informations like, for example-- Oops, sorry. This was not what was I want to be. So we have here our analysis and up here
A later example shows practical exploration of DwC-DP in an ecosystem that previously published through ABCD/BioCASe.
About this connection
Different presenters and projects are involved. This does not show that the earlier pledge caused this prototype, or that ABCD was abandoned.
This pilot covers one 2025 symposium and selected 2026 moments. Automatic captions can contain mistakes; audio has not been checked.
Overview
What this was about
Tanja Weibulat explained that GFBio data centres chose ABCD because early Darwin Core couldn't express DWB's complex relations. Their pipeline exports and filters DWB modules (withholding restricted data, anonymising people, rounding coordinates) into PostgreSQL, then maps to ABCD via BioCASe for GBIF and NFDI4Biodiversity. Limitations were that GBIF didn't display multiple identifiers, persons, roles or relations, and data papers needed manual entry. They prototyped mapping the same PostgreSQL tables to DwC-DP in a test IPT: observations and physical specimens split into Occurrence and Material, event, identification and agents shared, and analysis and processing combined into Material Assertion. Next steps are a GBIF sandbox comparison, metadata mapping and extending to the GFBio portal.
Why it matters. It is a concrete ABCD-to-DwC-DP transition test that matters for the many German data centres still publishing ABCD.
Key ideas
In the room
DWB publishing used ABCD because Darwin Core was 'too slow' to capture relations.
Pipeline: DWB modules → filtered export (withhold, anonymise, round coordinates) → PostgreSQL per data package → BioCASe → ABCD XML harvested by GBIF and NFDI4Biodiversity.
GBIF did not display multiple global identifiers, persons with roles, or relations present in ABCD; data papers needed manual entry.
Only a test version of the IPT currently supports DwC-DP; source tables were accessed directly via SQL.
Mapping required splitting observation vs specimen data into Occurrence and Material and combining analysis/processing into Material Assertion.
Dataset metadata must still be entered manually in the IPT.
Jump in
Notable moments
In their words
Transcript
Automatically generated captions can contain mistakes, especially in names and technical terms. Times are relative to the room recording.