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 and collaboratively develop an updated version of the Recommendation.

Deliverables

• Deliverable: Continue to iterate individual repository implementation plans to support version 1.
• Deliverable: Draft and publish updated version 2 of Metadata Recommendation that could include support for controlled vocabularies to consider, e.g. MeSH, LCSH.

Epics and Issues

Year 3

This is an ordered list for Year 3. All eight tasks will take between 6 - 12 total weeks.

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
• GREI 2: Task 1 - Create usability testing plan for 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 (Validate stage) #261
• GREI 2: Task 1 - Conduct and summarize results of usability testing of 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 (Validate stage) #262
• GREI 2: Task 1 - Use learnings from usability testing (testing of the 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) in order to adjust the redesign of the citation metadata block and changes to the controlled vocabulary functionality (Validate stage) #263

Software Development

After the Year 3 UX Design and Testing is completed, we can start the software development tasks below

• Epic: GREI 2 Task 1 - Implement redesigned metadata block and external vocabulary scripts to improve collection of ORCIDs and ROR IDs #223
• Spike: Feature Request/Idea: Deprecating metadata fields dataverse#10431
• 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
• Deploy redesigned citation metadata block and adjusted DataCite export code to Harvard Dataverse dataverse.harvard.edu#263
• Resend metadata to PID providers when metadata schema used to register PIDs is modified dataverse#5144

Year 4

• Epic: GREI 2 Task 1 - Publish benchmarks for amount of Harvard Dataverse ORCIDs, ROR IDs, and related research object metadata #225
• Epic: GREI 2 Task 1 - Conduct usability tests of the citation metadata block and recommend improvement #226

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

Resources

• Project: NIH GREI - Generalist Repository Ecosystem Initiative #124
• Epic: GREI 2 - Consistent Metadata #116
• DRAFT: Year 3 Realignment Proposal Plan (Document)

[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)