Be it coding, or making your manuscript worthy of publication, we all know that a final version just does not exist. But a decent start lets you find your notes when you need them, or get to that methods-related tip your supervisor had given on you second meeting with them, from some 17 months ago, or to be able to just send a link to a place on the internet where others can see what you’ve been working on and can collaborate with minimal effort.
There are a few options out there that solve your starting problem. None of them were quite what I was looking for – a bare minimum setup, that’s independent of the operating system, programming language used in the project, but easy to reuse in different project from another field. Just a basic directory setup that keeps my data separate from the code, article document files separate from the figures, and so on. So, after quickly canvasing the relevant information on the internet, I made one of my own this morning in hopes of using it time and again (because I want to be in academia for a much longer than this one project).
Now I imagine you have some questions.
What exactly is this thing?
It’s a simple directory structure that has specific folders for your data, code, article writing, meeting notes, etc. It’s organized like this -
. ├── README.md ├── code ├── data ├── docs │ ├── article │ ├── notes │ │ └── article_summaries.md │ └── presentation ├── logs │ └── meeting_notes.md ├── results │ └── figures └── scratch >> Treat scratch as a temporary folder to dump all intermediate files, before you move final versions to results.
Looks good. I want it right now.
Well, head over to my github repo and click on that “clone or download” button.
But I’ve never used git before.
That’s fine. Download it as a .zip and use it as your normal directory. =)
Okay, I’ll just use it as a my initial directory setup. What’s with all the .md files?
You don’t have to use the same file. Feel free to replace it with your MS Word file, or a .txt file. .md is for markdown files that make it much much easier for you to just write. Getting the words right is all you need to worry about. Syntax, rules of formatting are all for other programs. I recommend Pandoc.
You can find a detailed overview of such a workflow here at Tooling up for Plain Text Academic Writing in Markdown.
Done. Shouldn’t you be working?
- Git can facilitate greater reproducibility and increased transparency in science, Ram, K. (2013) - article
- Tooling up for Plain Text Academic Writing in Markdown, by Eric J. Ma - blogpost
- PhD Starter Kit, by Achintya Rao - website
- Reproducible Research Project Initialization - github
- Project template, by John Myles White - github, website