Define a use-case for DDI-CDI support in dataverse

[mreekie]

Overview

This is in support of:

• an NIH grant "The Harvard Dataverse repository: A generalist repository integrated with a Data Commons",
  • Aim 2: Increase support for biomedical and cross-domain metadata standards and controlled vocabularies,
    • 1#. expand DDI support to include the recently released DDI-Cross-Domain Integration (DDI-CDI) schema

The goal here is to define a use-case for DDI-CDI support in dataverse. The definition of this spike will get better as we work more with NIH. It is likely that the dataverse team will need to work with the other data repository teams on fleshing this out.

Details

There is a lot going on in Aim 2, pasted below.

This question focuses on the first point only, about expanding "DDI support to include the recently released DDI-Cross-Domain Integration (DDI-CDI) schema"

Aim 2:

Increase support for biomedical and cross-domain metadata standards and controlled vocabularies

One of the useful characteristics of the Dataverse open-source software is its extensive support for metadata standards and additional custom metadata. The standards currently supported include the Data Documentation Initiative (DDI), Dublin Core, DataCite, and Schema.org.

In particular, DDI makes a Dataverse repository interoperable even at the variable/attribute level since it supports variable descriptive and statistical metadata. This allows data exploration and analysis tools to integrate easily with the repository and discovery engines to find variable information.

In this project, we propose to

1. expand DDI support to include the recently released DDI-Cross-Domain Integration (DDI-CDI) schema,
2. build on existing support for biomedical-related standards relevant to NIH-funded research cases, following the recommendations from https://fairsharing.org/,
3. expand descriptive and citation metadata to support funding information and related fields, and
4. integrate with external services to enable the support of controlled vocabularies for any metadata field, based on standardized, widely used data dictionaries. The HMS Research Data Management group will participate in the development of these standards and vocabularies for biomedical datasets, working directly with research laboratories.

Related

• Epic: GREI 2 - Consistent Metadata #116
• Project: NIH GREI - Generalist Repository Ecosystem Initiative #124

Related Resources

• Notes on Dataverse Deliverablas for NIH OTA
• NIH OTA Progress Notes
• NIH OTA
• Fair Sharing
• DDI CDI: Cross-Domain Integration
• DDI CDI: Cross-Domain Integration public review

[mreekie]

Len mentioned that Phil, Steve, and Leonid possibly may know something about this.

[sbarbosadataverse]

What is DDI-CDI and what problem would it resolve/could resolve?
We should have use cases before we define a use case
NIHGREI has not discussed this nor has a plan to work on this
SB grabbing some input from other communities on any use cases or needs they may have for this, checking if any GREI repos are doing this or any of the associated tasks.
It could be the project this year is gathering feedback on why this is needed by the community.

[jggautier]

The webinar announced in this forum post mentions DDI-CDI and might be helpful for understanding what it does.

[sbarbosadataverse]

Status: July 2024

• I received feedback and think we should make this goal for part of 24-25, investigating and gathering community feedback on supporting this, and decide and implement in later Spring 25 @cmbz

[pdurbin]

We should definitely re-watch the talk by Arofan Gregory from DCM2024 in Mexico where he covered DDI-CDI: https://youtu.be/LA1BbkV3Efk?si=X9C_zNgzwnDbYQNz&t=13096 . Here are the slides: https://osf.io/p6xnz

In addition @landreev plans to be at a Schloss Dagstuhl conference in October where he'll meet Arofan and others: https://www.dagstuhl.de/en/seminars/seminar-calendar/seminar-details/24413