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 commented 8 months ago

Overview

Task 1: Continue to implement version 1 of the GREI Metadata Recommendation across repositories and collaboratively develop an updated version of the Recommendation.

[ ] 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.

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

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

cmbz commented 5 months ago

@sbarbosadataverse, @jggautier, and @cmbz met to discuss the status of https://github.com/IQSS/dataverse.harvard.edu/issues/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 https://github.com/IQSS/dataverse/issues/5889 with a proposal for sending more metadata to DataCite

cmbz commented 4 months ago

@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 commented 4 months ago

@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 commented 3 months ago

@jggautier discussed proposal for sending to DataCite more of the metadata that Dataverse repositories already collect, related to https://github.com/IQSS/dataverse/issues/5889. See discussions in https://github.com/IQSS/dataverse/pull/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 https://github.com/IQSS/dataverse-pm/issues/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 commented 1 month ago