Proposal: GREI Harvard Dataverse Repository and Dataverse Software Metadata Support
cmbz opened this issue · comments
Overview
The NIH GREI Metadata and Search Subcommittee developed a set of recommendations for metadata that all GREI repositories should strive to support. See GREI Metadata and Search Subcommittee Recommendations from DataCite schema version 4.4.
@jggautier and @cmbz will develop a proposal describing how Harvard Dataverse repository and the Dataverse software can support the metadata recommendations. Proposed tasks will include identifying relevant current Github issues and relevant documentation. Topics will include specific support for Harvard Dataverse (e.g., metadata blocks, training, support resources) as well as code changes to the Dataverse software that will benefit the wider Dataverse Community.
Proposed Timeline
See the timeline in the proposal
Related
2023/11/27
- @jggautier will update the proposed timeline based on new information/activities that have happened since the issue was created.
Thanks @cmbz. I updated the timeline, mostly accounting for the upcoming holidays and other priorities.
2024/02/01
- I updated the title to reflect the name of the proposal.
Just leaving an update here that the proposed timeline needs to be revised again. I'm continuing to work out how to manage my other work so that I have time to work on this proposal and the timeline will be revised as I learn more about this.
The proposal involves creating a shared understanding of how Dataverse meets these recommendations today (as of v6.1), and what work has been and could be done, including discovery research, defining success, design, implementation and evaluation. To facilitate this shared understanding, @scolapasta and I agreed that I would continue drafting a document that details if and how Dataverse records and sends the metadata in the NIH GREI recommendations.
Status: June 2024
- This proposal is now finalized.
- Implementation will be tracked here: IQSS/dataverse-pm#127
2024/06/06
- Closed as complete, per #230 (comment)