Epic: GREI 2 - Consistent Metadata

[cmbz]

Overview

"Implement an initial set for consistent metadata models to enable discovery of NIH funded data in Generalist Repositories."

Tasks

GREI

These tasks were collectively agreed upon by all GREI repositories during the Year 2 retreat (2023/09)

• GREI 2: Task 1 - Continue to implement version 1 of the GREI Metadata Recommendation across repositories and collaboratively develop an updated version of the Recommendation #127
• GREI 2: Task 2 - Conduct comprehensive review of metadata structures #164

Harvard Dataverse

These additional tasks were proposed by the HDV team in the NIH OTA and other documents

• GREI 2: HDV Task: Support Multiple DataCite Providers #132
• Proposal: GREI Harvard Dataverse Repository and Dataverse Software Metadata Support dataverse.harvard.edu#230
• GREI 2: HDV Task - Improve Dataverse Biomedical Metadata Support #174
• Evaluate and document evaluation of ROR plug-in on Demo Dataverse dataverse#10460

Year 3 Scoping: Remaining Harvard NIH OTA Work

The tasks below were described in the NIH OTA, Aim 2. Although some tasks saw progress in Year 1 and Year 2, other tasks were stalled due to changing priorities collectively agreed up by the GREI repositories and due to resource constraints. Recommendations for next steps are provided.

• Design and implement integration with controlled vocabularies [was Aim 1.2.1]
  • Recommendation: Close this task as complete based on prior work below
  • Rationale: Work accomplished in closed issues below satisfies planned functionality outlined in the NIH OTA Aim 2.
  • Create a javascript for the frontend that supports Fundref dataverse#9150
  • 1.2.1 Deliverable Backlog Working Notes dataverse#9043
  • Spike: Discovery about integrating biomedical vocabularies into dataverse dataverse#8681
  • Spike: What work has already been done towards support for controlled vocabularies for metadata fields dataverse#8571
  • Make Dataverse produce valid DDI codebook 2.5 XML dataverse#3648
• Define use cases for DDI-CDI support [was Aim 1.2.2]
  • Recommendation: Discontinue efforts focusing exclusively on DDI-CDI, close the issues below, and instead align with work defined in: Proposal: GREI Harvard Dataverse Repository and Dataverse Software Metadata Support dataverse.harvard.edu#230.
  • Rationale: GREI members have prioritized implementing specific consistent metadata and controlled vocabularies for Year 3 and Year 4. We should focus on meeting these shared goals.
  • Spike: Define a use-case for DDI-CDI support in dataverse dataverse#8576
  • As a user I would like to be able to include DDI-CDI meta data with a dataset that I import, and be able to export my dataset with the metadata intact. dataverse#9160
  • Create a white paper that summarizes what we know and what we don't know about the state of DDI-CDI currently dataverse#9161
  • As a user I would like to be able to export my dataset metadata via DDI-CDI dataverse#9159
• Design and implement support for DDI-CDI [was Aim 2.2.1]
  • See "Define use cases for DDI-CDI support" above, for recommendation and rationale

Related

• NIH AIM:2 YR:2 TASK:1B | 2.2.1B | (cont from yr 1: 1.2.1) Design and implement integration with controlled vocabularies #83
• GREI 3: Task 1 - Implement filtered search by funder and by research affiliation in each repository using ROR #165
• Epic: Get the existing ROR plug-in working on the dataverse demo dataverse#9151
• Some Dataverse metadata fields seem not to be indexed correctly by DataCite dataverse#7072
• Support Hierarchical Controlled Vocabularies dataverse#434
• Spike: issue to locate or document support for DOIs and ORCID dataverse#9370

Resources

• Project: NIH GREI - Generalist Repository Ecosystem Initiative #124
• APPROVED - NIH GREI Coopetition Plan Year 3
• How does Harvard Dataverse follow GREI’s metadata recommendations? (Document)
• Support for Controlled Vocabularies in Dataverse
• Support for core PIDs in Dataverse (Slides)