I'm a new instructor (since I'm yet to help in my first workshop, I'm
just new, not quite an instructor even!), but I'd be really keen on
helping too.
I think a good point to adress is how to bridge the gap between local
storage (how to represent data for your analysis), local backup, and
final archival for publication. I think this require to realize that the
exact same dataset can be stored in really different ways as a function
of what you want to do with it.
t
Le 2015-02-13 12:12, Ted Hart a écrit :
I know I'm not a new instructor, but I'd be interested in
collaborating on a 10 simple rules style piece for PLoS on storing
scientific data. I think it's the sort of thing that might be more
beneficial as a paper of those topics listed. Is anyone else
interested in collaborating? The style seems ideal for collaboration
if we could break the rules up among authors.
Ted
On Fri, Feb 13, 2015 at 7:54 AM Greg Wilson
<[email protected]
<mailto:[email protected]>> wrote:
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 scientists should store their data:
https://github.com/swcarpentry/site/issues/797
* what project templates people use, and how:
https://github.com/swcarpentry/site/issues/806
* how to manage the flood of notifications from GitHub (and
information
flood more generally): https://github.com/swcarpentry/site/issues/813
The summary/synthesis wouldn't have to go on the SWC blog - if you
have
a blog of your own and would like to put it there to start bringing in
more readers, we'd be very happy to link to it. And if you'd like
to do
something more ambitious, like a "Ten Simple Rules" article for PLOS
(http://www.ploscollections.org/article/browseIssue.action?issue=info%3Adoi%2F10.1371%2Fissue.pcol.v03.i01),
that would be even better.
Collectively, we know a lot about how to actually do scientific
computing, open research, and a bunch of other things. We won't
ever be
able to teach all of it in our workshops - there's simply not time
- but
we can still help other people by boiling it down and making it easier
to find. If your schedule and other commitments don't allow you to
travel to help teach a workshop, you can still make a valuable
contribution by helping us share our collected wisdom with others. If
you're interested, please mail me directly and we'll get the ball
rolling.
Thanks,
Greg
--
Dr. Greg Wilson | [email protected]
<mailto:[email protected]>
Software Carpentry | http://software-carpentry.org
_______________________________________________
Discuss mailing list
[email protected]
<mailto:[email protected]>
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
--
Timothée Poisot, PhD
Professeur adjoint
Département des sciences biologiques
Université de Montréal
phone : 514 343-7691
web : http://poisotlab.io
twitter: @PoisotLab
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
