{"id":2711,"date":"2015-02-19T13:42:08","date_gmt":"2015-02-19T13:42:08","guid":{"rendered":"https:\/\/blogs.nature.com\/scientificdata\/?p=2711"},"modified":"2015-02-19T13:59:09","modified_gmt":"2015-02-19T13:59:09","slug":"code-sharing-tips","status":"publish","type":"post","link":"https:\/\/blogs.nature.com\/scientificdata\/2015\/02\/19\/code-sharing-tips\/","title":{"rendered":"Code Sharing \u2013 read our tips and share your own"},"content":{"rendered":"\n\n\n
This week we announced an update to our journal policies on code sharing<\/a>. To encourage our authors to share their code, we also added a new code availability section<\/strong> to our article templates<\/a>. This new code availability section focuses mainly on articles that rely on custom code to generate or process data described in our articles. But, almost all modern research employs code or software at some stage. We feel that, ideally, it is best to describe all code or software used in a study<\/strong> in a way that supports reproducible research. What does this mean for our authors who would like to share their code alongside their data? What should be included in the code availability section? Here are some suggestions from our editorial team.<\/td>\n<\/td>\n\"rsz_1scidata_codesharing\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/p>\n