-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add information in the guide about R-Ladies Zenodo Community #79
Comments
This sound great!! |
Thank you!! Would you be able to make a PR to the guide? |
Sure, I wanted to open an issue before initiating the PR! You both have way more extensive knowledge about the structure of the guide, so thank you again! |
Maybe organizers (https://guide.rladies.org/organization/events/promotion/?) but cross-linked from https://guide.rladies.org/comm/conferences/? (I often have to use the search bar to find things in the guide myself 😂 😭) |
Thanks, this makes more sense now! |
The materials generated from R-Ladies are huge but scattered (and mostly uncitable) - not easily searchable. In order to increase the discoverability, visibility, re-usability and make the materials citable, we recommend creating a Zenodo Community for R-Ladies where they can link not just their materials from GitHub (with two extra clicks) but also slides presentations, PDF and any type of output created by R-Ladies to make it citable. Every entry can be tagged by R-Ladise chapter name, the level of the materials and any other related metadata. You can also add the materials under more than one community (e.g. R-Ladies + another community helped with session (e.g. LatinR) ..) to increase the visibility, if wanted. Zenodo also provide a matric showing the numbers of downloads and views.
After an initial approval in Slack, I created a Zenodo community for R-Ladies and added one entry from a workshop by Allison Horst. However, if we want to proceed with this step, we need instructions to be added to the R-Ladies guidebook, how does this sound?
The wonderful @flor14 is working with me on this as well!
The text was updated successfully, but these errors were encountered: