-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project: NIH GREI - Generalist Repository Ecosystem Initiative #124
Comments
Status: December 2024GREI ObjectivesGREI 1GREI 2GREI 3GREI 4GREI 5GREI 6GREI 7GREI 8GREI Re-archTask GroupsReports
|
Hi @cmbz. About October 2024 updates for GREI 1 objectives, I'm not really involved in this objective. In the GitHub issue, "Conduct a comprehensive internal review of the Generalist Repository Comparison Chart to improve clarity, transparency, and usability" I read that a survey is planned to be sent out in early October. @sbarbosadataverse definitely knows more. |
@jggautier Yes, thanks. I was aware of the survey. But I didn't see a message on the GREI Slack that indicated it had gone out. |
Vision
The long-term vision for GREI is to develop collaborative approaches for data management and sharing through inclusion of the generalist repositories in the NIH data ecosystem. GREI also aims to better enable search and discovery of NIH-funded data in the generalist repositories.
Mission
GREI’s mission is twofold. The primary mission is to establish a common set of cohesive and consistent capabilities, services, metrics, and social infrastructure across various generalist repositories. Secondarily, GREI will raise general awareness and help researchers to adopt FAIR principles to better share and reuse data.
See: NIH GREI Announcement
GREI Repositories and Participants
Objectives
Task Group Participation
Active
(Note that QA/QC and #Sensitive Data were combined into one task group during Y3 face to face meeting).
Completed
Grant Supplements
Reports
Timeline
Resources
GREI Program Resources
Harvard GREI Resources
The text was updated successfully, but these errors were encountered: