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

[cmbz]

Overview

• Task 1: Continue to implement version 1 of the GREI Metadata Recommendation across repositories
• Deliverable: Continue to iterate individual repository implementation plans to support version 1.

Epics and Issues

Year 4

• GREI 2 Task 1 - Develop citation metadata block improvements punch list (Year 4) #356
• GREI 2 Task 1: Review punch list of citation metadata block improvements (year 4) #357

Year 3

UX Design and Testing

• GREI 2: Task 1 - Review proposal, existing GitHub issues related to improving the collection and use of metadata about people and organizations associated with deposits, including use of ROR and ORCID, think about users for validating solution (Understand stage) #275
• GREI 2: Task 1 - Define metrics and signals to evaluate success of solution for improving the collection and use of metadata about people and organizations associated with deposits, including use of ROR and ORCID (Define stage) #276
• GREI 2: Task 1 - Propose redesigns of citation metadata block and use and build on controlled vocabulary functionality in order to improve the collection and use of metadata about people and organizations associated with deposits, including use of ROR and ORCID (Sketch stage) #258
• GREI 2: Task 1 - Review proposed redesigns of the citation metadata block and the use and possible adjustment of the controlled vocabulary functionality for improving the collection and use of metadata about people and organizations associated with deposits (Decide stage) #259
• GREI 2: Task 1 - Create testing prototype of redesign of the citation metadata block and the use and possible adjustment of the controlled vocabulary functionality for improving the collection and use of metadata about people and organizations associated with deposits (Prototype stage) #260

Software Development

• Feature Request: Add ROR to the citation metadata block author identifier field dataverse#11075
• Epic: GREI 2 Task 1 - Adjust code for creating DataCite exports to include the ORCIDs, ROR IDs, and metadata about related research objects that are collected using the redesigned citation metadata block and external vocabulary scripts #224
• Resend metadata to PID providers when metadata schema used to register PIDs is modified dataverse#5144
• Deploy 'External Vocabulary' scripts, developed by QDR, to Author and Funding fields on Harvard Dataverse dataverse.harvard.edu#326

Related

• Metadata recommendations from GREI Metadata and Search Subcommittee
• Proposal: GREI Harvard Dataverse Repository and Dataverse Software Metadata Support dataverse.harvard.edu#230
• Support Research Organization Registry (ROR) IDs dataverse#6640 (2025-04-05: Awaiting prod deployment)

Resources

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

[cmbz]

Status: March 2024

• @sbarbosadataverse, @jggautier, and @cmbz met to discuss the status of Proposal: GREI Harvard Dataverse Repository and Dataverse Software Metadata Support dataverse.harvard.edu#230 and details about how Harvard Dataverse follows NIH GREI’s metadata recommendations, and to identify and remove blockers.
• @jggautier organized the Dataverse UX working group and its first meeting and proposed that working group members help with research needed for following the GREI recommendations
• @jggautier updated proposal for aligning Dataverse with NIH GREI metadata recommendations
• @jggautier updated the GitHub issue at Align or merge DataCite metadata exports dataverse#5889 with a proposal for sending more metadata to DataCite

[cmbz]

Status: April 2024

• @jggautier proposed a series of time-constrained activities called a design sprint where the Dataverse UX working group would help align Dataverse with the NIH GREI metadata recommendations by researching, designing and testing changes to Dataverse's Citation metadatablock and external controlled vocabulary feature.
• The Dataverse UX WG started clarifying the purpose and feasibility of design sprints and clarifying the scope of the first sprint about helping depositors describe the people and organizations associated with their deposits.

[jggautier]

Status: May 2024

• @jggautier, @sbarbosadataverse and @cmbz adjusted the plan for aligning Dataverse with the NIH GREI metadata recommendations. Due to resource constraints, we've replaced the first planned design sprint (about helping depositors describe the people and organizations associated with their deposits) with tasks we're describing in the GitHub issues listed in the "Epics and Issues" section of this tracking issue.

[cmbz]

Status: June 2024

• @jggautier discussed proposal for sending to DataCite more of the metadata that Dataverse repositories already collect, related to Align or merge DataCite metadata exports dataverse#5889. See discussions in Datacite xml improvements dataverse#10615
• @jggautier started detailing and preparing plans for benchmarking the amount of ORCIDs, ROR IDs, and related research object metadata that Harvard Dataverse publishes, in order to measure the success of Harvard Dataverse's implementation of version 1 of the GREI Metadata Recommendations. See Epic: GREI 2 Task 1 - Publish benchmarks for amount of Harvard Dataverse ORCIDs, ROR IDs, and related research object metadata #225
• @jggautier met with the UX working group (see 2024-06-13 meeting notes) to schedule and start the design sprint for improving metadata about people and organizations. See schedule and more details about each stage of the sprint.
• Members of the Dataverse UX WG reviewed the proposal (Proposal: GREI HDV and Dataverse Metadata Support) and related research and discussions
• @jggautier shared initial ideas about which types of users should help test the redesign during the validation stage of the design sprint
• Members of the Dataverse UX WG met (see 2024-06-27 meeting notes) to plan ways to measure success of implemented solutions and started planning for how to share design ideas.

[jggautier]

Status: July 2024

• GREI 2: Task 1 - Propose redesigns of citation metadata block and use and build on controlled vocabulary functionality in order to improve the collection and use of metadata about people and organizations associated with deposits, including use of ROR and ORCID (Sketch stage) #258 (comment)

[cmbz]

Status: December 2024

• Metadata Coordination team decided on a course of action to move the implementation of GREI Metadata Recommendations forward:
  • Deploy 'External Vocabulary' scripts, developed by QDR, to Author and Funding fields on Harvard Dataverse dataverse.harvard.edu#326
  • Feature Request: Add ROR to the citation metadata block author identifier field dataverse#11075
  • GREI 2 Task 1 - Develop citation metadata block improvements punch list (Year 4) #356
  • GREI 2 Task 1: Review punch list of citation metadata block improvements (year 4) #357

[cmbz]

Status: January 2025

• ROR was added as an Author Identifier Type
  • add ROR as an Author Identifier Type dataverse#11118

[cmbz]

Status: February 2025

• We'll consider version 1 of the GREI Metadata Recommendation "implemented" once v6.6 is released and applied to Harvard Dataverse, and the Author and Funding Information fields are changed to use the controlled vocabulary functionality to let users select names from the ORCID and ROR APIs (Deploy 'External Vocabulary' scripts, developed by QDR, to Author and Funding fields on Harvard Dataverse dataverse.harvard.edu#326)

[cmbz]

Status: March 2025

• Dataverse v6.6. was released and applied to Harvard Dataverse. The "post-production" task of applying the redesign to the Author and Funding Information fields is pending and we expect will be done in April 2025.

[cmbz]

Status: April 2025

• Pending