-
Notifications
You must be signed in to change notification settings - Fork 13
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
References #3
Comments
Related but distinct: Ten Simple Rules for the Care and Feeding of Scientific Data |
Also in the astronomy theme, Reimplementing the Hierarchical Data System using HDF5 has some interesting comments on using different formats for processing, strage, and transport. I can translate jargon if necessary.. |
Hi everyone! This paper from our group may be of interest here: http://arxiv.org/abs/1502.06900 |
New from PLOS one that might have some relevance (I have only looked at abstract): |
Blog post from NatureJobs on how to publish a data paper: http://blogs.nature.com/naturejobs/2014/12/04/how-to-publish-your-data-in-a-data-journal |
Nice webpage from USGS that covers some of the same topics http://www.usgs.gov/datamanagement/plan/dataformats.php |
Closing because paper is now in production. |
Here are some references for us.
Original context of the e-mail.
Hi,
In case you missed it, Daisie Huang wrote a very insightful article
about the differences between scientific coding and software engineering
for the Software Sustainability Institute's blog at
http://www.software.ac.uk/blog/2015-02-06-scientific-coding-and-software-engineering-whats-difference.
I think short pieces like this that we can link to when we're talking to
colleagues (and writing proposals) are really useful, so I would be
grateful if a few of our newer instructors would like to volunteer to
summarize three recent discussions we've been having about:
Where should scientists store their data? swcarpentry/DEPRECATED-site#797
Guide to submitting a 10 simple rules
http://journals.plos.org/ploscollections/article?id=10.1371/journal.pcbi.1003858
The text was updated successfully, but these errors were encountered: