Skip to content

Commit

Permalink
Address Open Science 101 suggestion in Issue nasa#831
Browse files Browse the repository at this point in the history
  • Loading branch information
bressler1995 committed Oct 3, 2024
1 parent a89ad40 commit a2d8f26
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Module_4/Lesson_1/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -189,7 +189,7 @@ It is not uncommon for research groups to spend years developing code, writing p

| Fear | Discussion/Mitigation: |
|---|---|
| Scooping: What if someone re-uses my code to publish a result I was working on? | Yes, this can happen. But, in many fields, if it is clear that someone is actively working on a problem, the decision by another scoop may have a short term gain but long-term loss. In the scientific community, reputations serve as a cultural currency and being collaborative generally leads to increased career successes. If you are sharing your code, ensure it has a digital object identifier (DOI) so you get credit. This does not prevent anyone from using it or extending your analysis, but it does ensure you will get credit for your contribution. There is a nice article about this here. |
| Scooping: What if someone re-uses my code to publish a result I was working on? | Yes, this can happen. But, in many fields, if it is clear that someone is actively working on a problem, the decision by another scoop may have a short term gain but long-term loss. In the scientific community, reputations serve as a cultural currency and being collaborative generally leads to increased career successes. If you are sharing your code, ensure it has a digital object identifier (DOI) so you get credit. This does not prevent anyone from using it or extending your analysis, but it does ensure you will get credit for your contribution. There is a nice article about this [here](https://datascience.codata.org/articles/10.5334/dsj-2017-029). |
| Misinterpretation or misuse | Provide sufficient contextual information (documentation) to allow others to understand your code fully to reduce this risk. |
| My code will be used, but not cited | While it is not common for researchers to cite code, data, or other non-published articles, science ethics dictates that you should be cited if your work is used. Remember to appropriately cite the material of others so that you're not adding to the problem. |
| Code is too sensitive to share | User controlled access to help maintain sensitivity and security. |
Expand Down

0 comments on commit a2d8f26

Please sign in to comment.