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

• GREI 2: HDV Task - Improve Dataverse Biomedical Metadata Support #174
• Investigate relevance of DDI-CDI use cases to the Dataverse Community and create implementation recommendations (was Aim 1.2.2)
  • Investigate DDI-CDI needs of Dataverse Community #285
  • Define a use-case for DDI-CDI support in dataverse #286
  • 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
  • As a user I would like to be able to export my dataset metadata via DDI-CDI #284
• Design and implement support for DDI-CDI according to recommendations (was Aim 2.2.1)

Complete

These tasks were described in the NIH OTA, Aim 2. Project work was rescoped in Year 3.
Design and implement integration with controlled vocabularies [was Aim 1.2.1]

• 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
• GREI 2: HDV Task: Support Multiple DataCite Providers #132
• Proposal: GREI Harvard Dataverse Repository and Dataverse Software Metadata Support dataverse.harvard.edu#230

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
• external vocab: for free text, Dataverse reaches out to skosmos when it shouldn't dataverse#9335

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)

[cmbz]

Status: June 2024

• We closed the GitHub issue at #10460, where we started to plan an evaluation of the "ROR-plugin", since members of the Dataverse UX WG will be evaluating the controlled vocabulary functionality as part of its first design sprint for improving the collection and use of metadata about people and organizations associated with deposits, including use of the ROR and ORCID APIs. We started planning that design sprint after #10460 was opened. The GitHub issue at IQSS/dataverse-pm#127 lists GitHub issues where we'll report the progress of the design sprint.

[cmbz]

Status: July 2024

Work commenced on the following issue:

• Define a use-case for DDI-CDI support in dataverse #286

[cmbz]

Status: Year 3, Q1

• Completion: 27%
• Work proceeded for three GREI 2 tasks during this quarter. GREI 2 Task 1 accomplishments include creating the Dataverse UX Working Group and finalizing a proposal for aligning Dataverse development with the GREI metadata recommendations. The GREI 2 task to support multiple DataCite providers is complete. This functionality enables consortia members and other groups using the same Dataverse installation to administer their own DOIs instead of the installation manager. Accomplishments towards improving biomedical metadata support this quarter included improving controlled vocabulary support, investigating the NIH HEAL metadata block currently in use at the Qualitative Data Repository and installing it on an instance of Dataverse on AWS for testing.
• See: NIH GREI Quarterly Progress Report: Year3 Q1 (March 2024 - May 2024)

[cmbz]

Status: Year 3, Q2

• Completion: 51.7%
• This quarter the team continued to implement version 1 of the GREI metadata recommendations with several strands of work, including 1) discussing a proposal for sending more Dataverse metadata to DataCite, 2) planning to evaluate the success of what's implemented, including usability testing and benchmarking the metadata about ORCIDs, ROR IDs, and related research objects that Harvard Dataverse publishes, and 3) leading the UX Working Group in the design of processes to review proposed metadata changes and recommend implementation approaches (see Meeting agendas and notes for Dataverse UX Working Group).
• Work also began to gather input from the Dataverse Community about their current and prospective DDI-CDI use cases.

[cmbz]

Status: Year 3, Q3

• Completeness: 54.8%
• During Year 3, Q3 the Dataverse team was involved in a number of metadata-related activities, described below:
  • Implementing GREI Metadata Recommendations. We continue to partner with the Dataverse UX working group to work towards implementing the GREI Metadata Recommendations. Redesign of the Dataverse citation metadata block is underway. The Dataverse team has reviewed and offered feedback on the UX Working Group's proposal. Additional work, including a technical feasibility assessment, is planned for Q4.
  • Dataverse Support for DDI-CDI. Several meetings were held involving DDI-CDI experts and interested Dataverse Community members to discuss the standard's value and possibilities for supporting it in Dataverse software.
  • Improving Biomedical Metadata Support with HEALS and CEDAR. The Dataverse team met with members of the Helping to End Addiction Long-Term (HEAL) Initiative team, representatives of the Open Science Framework (OSF), and interested Dataverse Community members to discuss requirements and options for Harvard Dataverse and Dataverse platform support.

[cmbz]

Status: Year 3, Q4

• Pending