Open shervinsafavi opened 6 years ago
npscience
commented
6 years ago Hi @shervinsafavi - great idea! I've added to your doc:
"A useful resource: https://www.datacite.org/ Including a database of data repositories so you can find the right place to share your data: https://www.re3data.org/"
cartoonist
commented
6 years ago To achieve the main objective there are couple of non-exclusive approaches:
Define data index (d-Index) which can be used:
Assuming that d-index is an effective metric,
We are going to investigate
[*] Data can be raw or processed depends on difficulty in storing and/or processing raw data.
[1] Cameron, B. D. (2005). Trends in the usage of ISI bibliometric data: Uses, abuses, and implications. portal: Libraries and the Academy, 5(1), 105-125.
cartoonist
commented
6 years ago This might be useful: https://pdfs.semanticscholar.org/d53c/594e80ef35b9b3782d86abfcaf402fb0a2df.pdf
Confused? New to Github? Visit the GitHub help page on our site for more information!
[//]: # "======================= Even if you know Github well, we suggest you read this. Anything between these lines you can leave or delete, as they won't display anyway when you post (you can check this via Preview changes). They're here to help you complete issues quickly and in a way that will help other participants. If you're posting a new project, or challenge. We suggest you fill out the Google Forms first. ============================"
At a glance
[//]: # "======================= Please paste the metadata you received after submitting your project or challenge in your Google Form exactly as we sent it to you. You can delete what's there now, it's just there ============================"
Description
[//]: # "======================= Insert a paragraph providing more context for your project or challenge focuses on. For project leads, this is a good place to give some broader context about your project—beyond the scope of the do-a-thon. If you're posting a challenge, this is a good chance to say how the problem arise or why it feels relevant to you. ============================" We all know, making research data open is extremely needed/helpful for reproducibility and advancement of science, medicine and technology, but how might we can make it "a routine"? We need to know what are the caveats in data sharing, what does encourage/demotivate scientists from sharing their research data? Ideally we would like establish the culture of data sharing in all scientific disciplines, therefore appropriate investigations and actions have to be made in field-specific manner. For instance, in the field of machine learning (~ a branch of artificial intelligence) the openness culture is ahead of what I/we observe in the neurosciences therefore what we need to make in the latter is different.
[//]: # "======================= What are we working on during the do-a-thon? What kinds of support do we need? For those leading projects, please give some more information about what type of support you are specifically looking to get done during the do-a-thon day. Note: Challenge leads will not need to fill out this section and can remove it. ============================"
How can others contribute?
[//]: # "======================= Please say what the best way to contribute to the project or challenge is, sometimes that will just be 'lets discuss here' or 'Ive started a Google doc'. If you are a challenge lead, give some context on what design thinking tools you will be using, and how other folks can update their ideas onto the thread. If you are a project lead, and you already have clear ways people can contribute it might be worth linking to them here. Language: If your project is regionally based in a non-English-speaking region, clarify here what language you and contributors will primarily be communicating in. If you're leading a project or challenge participating remotely: Use this space to let people know that this is a remote project and that you are not 'in the room' in Berlin. Let other participants know what the best way to get in touch with you, where the work will happen, and where any updates or outputs will go. If you are at the in-person meeting in Berlin: Be as inclusive as possible to those outside the room. Use this space to give clear instructions to those participating in the do-a-thon remotely on how they can keep up to date and contribute. ============================"
We hope with help of many bright minds we can come up with minimally doable plan in direction of achieving the goal of making data sharing a routine. Given the cultural variability across scientific disciplines we thought we start from a narrow filed. We would suggest non-clinical neuroscience as the start point, since I've already initiated a few informal investigations in this field. But if volunteer from other field are ready to take the lead why not going beyond!
Our raw idea is, the main caveats in data sharing are the following:
We need to have both simultaneity to make data sharing a routine.
To reach this minimal step we need to define multiple doable steps which we need to know your opinion on that. During the Do-A-Thon (as well as after!) We invite anyone to help tackle this challenge. You don’t need to be physically in Berlin (if your are, find us in the Goethe-saal right corner at the end) to share your thoughts and ideas! Either share your ideas in the the Do-A-Thon session at OpenCon 2017 or write them in the following Google document: https://goo.gl/rVwX6k
By the way, this a link to brainstorm on a related topic happened during an unconference duing OpenCon 2016: https://goo.gl/3gqZyL
[//]: # "======================= You're ready to post!!! After posting your issue, the real work begins. Next, you might want to: Tweet a link to this issue with #opencon so others can join in Make another issue to involve people in your work - remember to use your metadata Come back from time to time and update the community on your project. You'll get an email update whenever someone interacts with your issue. ============================"
This post is part of the OpenCon 2017 Do-A-Thon. Not sure what's going on? Head here.