2 | 1.2.2 | Define use cases for DDI-CDI support | 5

[sync-by-unito[bot]]

References:

• Planning Board

Problem Statement

The DDI-CDI standard is still new. We are not aware of any use of it. That said, our last datapoint was in 2021. We need to determine what has already been done in this space and identify what use cases for the standard we might be able to implement that will move the standard forward.

Proposed Solution

We identified 2 use cases. First we can allow Dataverse to accept, store, and export the format without interpreting it. We can also enable Dataverse to export an existing dataset metadata in this format.

We also need to acknowledge that we are not very familiar with this standard and so doing some exploratory research which we can summarize and share in a paper will be helpful to us and likely helpful to others.

Acceptance Criteria

• [ ] Create a white paper that summarizes what we know and what we don't know about the state of DDI-CDI currently
• [ ] Be able to include DDI-CDI meta data with an imported dataset , and be able to export the dataset with the metadata intact.
• [ ] Create a white paper that summarizes what we know and what we don't know about the state of DDI-CDI currently

Links:

• NIH OTA document for this work
• Design Notes Document
• Backlog Grooming Board for 1.2.2
• Jim Myers notes
• Deliverable Sidecar Issue

Last updated: Thu Dec 15 2022 before I left for the holiday. No changes. Report: Dec 2022

Resources have been identified to review the DDI-CDI specification and identified two use cases which allows Dataverse to accept, store, and export the format without interpreting it and export to existing dataset metaset in this format.

12%

---

┆Issue is synchronized with this Smartsheet row by Unito

[mreekie]

This issue represents a deliverable funded by the NIH This deliverable supports the NIH Initiative to Improve Access to NIH-funded Data

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.

Other deliverables associated with this one: 2 | 2.2.1 | Design and implement support for DDI-CDI 2 | 2.2.2 | Define use cases for supporting biomedical metadata standards 2 | 3.2.1 | Design and implement biomedical metadata standards, and add funding related metadata 2 | 4.2.1 | Assess and improve metadata support

[mreekie]

In talking with Jim, he pointed out that the current list of issues that we collected around this do not address: 1) expand DDI support to include the recently released DDI-Cross-Domain Integration (DDI-CDI) schema

This may be more about tracking provenance of the data as it travels through time. net/net - we likely can't satisfy this by lining up what we have already and simply executing.

[mreekie]

Who:

• Jim
• Leonid
• Phil

Comment - we have to start from the very beginning on this one.

[mreekie]

Replaced this description today

---

The deliverables are: 1) Research DDI-CDI, 2) Determine parts of schema that are not currently supported, 3) Code and implement, 4) Test and document DDI-CDI.

2 | 1.2.1 | Design and implement integration with controlled vocabularies | 5#9027

2 | 2.2.1 | Design and implement support for DDI-CDI 2 | 2.2.2 | Define use cases for supporting biomedical metadata standards 2 | 3.2.1 | Design and implement biomedical metadata standards, and add funding related metadata 2 | 4.2.1 | Assess and improve metadata support

Link to Backlog Page

┆Issue is synchronized with this Smartsheet row by Unito ┆!Priority: Normal ┆!State: Approved ┆End Date: 2023-01-31T16:59:59.000Z ┆ItemIDHelper: 0025 ┆Start Date: 2022-10-03T08:00:00.000Z

[mreekie]

.

[mreekie]

Eliminating the sidecar issue: Notes all pasted here.

We had an initial meeting oct 20th and identified possible solutions for the deliverable.

Next step:

• [ ] Create the problem statement based on the notes from the meeting. in IQSS/dataverse-pm#6
• [ ] Create/associate issues that came out of the first meeting discussion as making up a proposed solution.
  • those go right on this board
• [ ] Review the board with Stefano

In subsequent conversations it's already been discussed that this deliverable appears to be of lower cost/benefit for our users than some of the other deliverables

This is a map to a summary of the points that came out of the meeting. CMAP

---

The possible steps that came out of the meeting were:

• Address some existing CDI problems that may be related to future support for DDI-CDI.
  • We have not specifically put any forward for this.
• IQSS/dataverse-pm#284
• IQSS/dataverse#9160
• IQSS/dataverse#9163 ---

[mreekie]

Last Updated: Mon Dec 5 2022

(1.2.2) Resources have been identified to review the DDI-CDI specification and identified two use cases which allows Dataverse to accept, store, and export the format without interpret it and export to exisiting dataset metaset in this format.

12%

[mreekie]

Last updated: Thu Dec 15 2022 before I left for the holiday. No changes. Report: Dec 2022

Resources have been identified to review the DDI-CDI specification and identified two use cases which allows Dataverse to accept, store, and export the format without interpreting it and export to existing dataset metaset in this format.

[mreekie]

priority discussion with Stefano;

• We are postponing work on this for now.
• The problem has not been well defined by the community yet.

[mreekie]

January update

(1.2.2) Two use cases which allows Dataverse to accept, store, and export the format without interpreting it and export to existing dataset metaset in this format. In a holding pattern on this pending more activity from the community on the definition.

[mreekie]

February monthly update

(1.2.2) Two use cases which allows Dataverse to accept, store, and export the format without interpreting it and export to existing dataset metaset in the DDI-CDI format. In a holding pattern on this pending more activity from the community on the definition. This activity is waiting for more input from the community although there is ongoing discussion. A meeting with Seoul National University, Shout Korea, was centered on harvesting, interoperability and metadata sharing at dataset level (see 1.8.2)..

[mreekie]

March Update

(1.2.2) This activity was completed at an extent of 20% in year 1 and transferred to year 2

[mreekie]

Draft year 1 summary: FY1 Annual Summary

This activity was completed at an extent of 20% in year 1. This year we examined two use cases. The first would allow Dataverse to accept, store, and export the format without interpreting it. The second would allow the export of an existing dataset in the DDI-CDI format. Work paused here pending more activity from the community on the DDI-CDI definition. Year 2 work toward completion will be tracked as yr:2 aim:2 task:2a (2.2.2A) starting at 20% complete.