Live saving archiving and documentation strategies.

What are the best practices in documentation, archiving, publishing of code, data, and other materials? How to keep your file structure organized on your own computers?

This series featured two awesome guests from University of Pennsylvania:

Steven Weissberg (https://stevenmweisberg.com/) from the Chatlab at Upenn (http://ccn.upenn.edu/chatterjee/) talked about OSF and how to use it for open science and archiving (from 5:14).

Giulia Frazetta (https://github.com/gfrazzetta) from Geoffrey Aguirre’s lab at UPenn ( https://github.com/gkaguirrelab) talked about versioning and how to make the best use of github (from 11:39).

 

Quick summary of the most important points:

  1. Always keep future you in mind. And with future, we don’t mean the next few weeks, but the next few years.
  2. Keep your files on your computer tidy. Organize things which you are likely to recycle (e.g. slides, writing, graphics) together. Organize your research material (e.g. data, analysis files, stimuli) in project folders and stay consistent with folder structure and naming.
  3. Don’t panic-save everything. Archive data files at the most important steps in a separate folder (raw, preprocessed, analysis#1, analysis#2, wide format) and use the  copies in your analysis directory for ongoing analyses and trying out things. Overwrite old files when moving on (Don’t panic, you have that safety copy).
  4. Write up the documentation of your study directly into a manuscript file which will later be the basis of a published paper. Writing up the experiment protocols, materials and methods descriptions, analysis steps, and the results right away will save you a lot of time and frustration.
  5. Use OSF (https://osf.io) to archive your materials and data. This is also great for working with multiple people on one project. Keep this as tidy as possible. As soon as you make it public eventually (which we recommend for most projects) this should be the best reflection of your work as a scientist with highest standards.
  6. If your work entails any kind of coding or writing analysis scripts, github is a great way to keep version control and publish your code.
  7. Always work as if a stranger would have to pick up your project at any time and finish it for you.

Published by

Dr Franziska Hartung

Cognitive neuroscientist researching how brains create meaning.

One thought on “Live saving archiving and documentation strategies.”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s
https://academiccrisisline.wordpress.com/2017/10/24/live-saving-archiving-and-documentation-strategies/
academiccrisisline.wordpress.com
crawl=CC-MAIN-2021-25
73265
application/http; msgtype=response
sha1:DHXQPZYRV7WTHJOJLVUT5LGVSBNSC4I2
<urn:uuid:7829b9ab-addf-4cf1-ace0-b2d99178a3e9>
2021-06-24T19:43:20Z
192.0.78.13
text/html
sha1:WFOUMOFMJKH734QZVVE3TQTQ5KZXFH6O
<urn:uuid:11fbe583-b550-411a-90c8-727865ae5893>
https://academiccrisisline.wordpress.com/2017/10/24/live-saving-archiving-and-documentation-strategies/
response
<urn:uuid:8e22374b-b8b3-4b6a-b544-9d6f12179c68>
isPartOf: CC-MAIN-2021-25
publisher: Common Crawl
description: Wide crawl of the web for June 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-168.ec2.internal
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/