writing a scientific literature review

What makes a good enough literature review?

Charles T. Gray true
11-27-2018

At the outset of a literature review, I’ve learnt the hard way to anticipate that you will not be able to cover the entirety of the literature. Perhaps a very pertinant paper did not come up in your journal search. Perhaps you used the wrong search tool, perhaps the keywords of interest are different in different disciplines. At any rate, a best practice literature review could well fall into the category of how long is a piece of string1?

This naturally leads to the question, what is a analogously good enough(Wilson et al. 2017) literature review? My instinctive response, is a literature review that answers the question posed of it, that is, the follows the line of inquiry. But I have a feeling that reading and defining the question are a symbiotic process whereby I refine the question as I read peoples’ thoughts.

For example, I began with

read literature on open science and reproducibiility, what are key concepts?

But the inquiry began to be refined almost immediately as I discovered literature focussing specifically on building a reproducible analysis (Marwick, Boettiger, and Mullen 2018).

what work has been done in statistical open science and reproducibility, and what work needs to be done?

Furthemore, statistical software development is intrinsically linked ot reproducibility for statistics, so it is impossible to consider the above question without investigating tools developed specifically for reproducible data analysis such as workflowr::(Blischak, Carbonetto, and Stephens 2018) and rrtools::(Marwick 2018).

Today I find myself asking,

what does this paper confirm, nuance, or challenge about open and reproducible data analysis?

Perhaps there is more to this, but after taking a look at some lit review guides(uoguelph 2018; writingcenter 2018), and establishing there was little in guidance for the type of literature review I’m writing on google scholar. A cursory look at the generalist guides gives me the impression that this something to use common sense for. A clear message, narrative etc. Find both the question and the present the answer, comparing and contrasing nuances of opinion and so forth.

Finishing this post off, I began to wonder if it was worth writing at all. But then I realised that I feel reassured I’m on the right track now, which absolutely makes it a worthwhile effort. The primary purpose of this blog is to write things down so I feel less anxious about my work. And now I do. :)

Blischak, John, Peter Carbonetto, and Matthew Stephens. 2018. Workflowr: A Framework for Reproducible and Collaborative Data Science. https://CRAN.R-project.org/package=workflowr.

Marwick, Ben. 2018. Rrtools: Creates a Reproducible Research Compendium. https://github.com/benmarwick/rrtools.

Marwick, Ben, Carl Boettiger, and Lincoln Mullen. 2018. “Packaging Data Analytical Work Reproducibly Using R (and Friends).” The American Statistician 72 (1): 80–88. https://doi.org/10.1080/00031305.2017.1375986.

Wilson, Greg, Jennifer Bryan, Karen Cranston, Justin Kitzes, Lex Nederbragt, and Tracy K. Teal. 2017. “Good Enough Practices in Scientific Computing.” Edited by Francis Ouellette. PLOS Computational Biology 13 (6): e1005510. https://doi.org/10.1371/journal.pcbi.1005510.

writingcenter. 2018. “Literature Reviews.” The Writing Center. https://writingcenter.unc.edu/tips-and-tools/literature-reviews/.


  1. Incidentally, how long is a piece of string was said to me in one of the most infuriating moments of my brief and frustring career in bioinformatics.

Citation

For attribution, please cite this work as

Gray (2018, Nov. 27). measured.: writing a scientific literature review. Retrieved from https://fervent-hypatia-7b7343.netlify.com/posts/2018-11-27-scientific-lit-review/

BibTeX citation

@misc{gray2018writing,
  author = {Gray, Charles T.},
  title = {measured.: writing a scientific literature review},
  url = {https://fervent-hypatia-7b7343.netlify.com/posts/2018-11-27-scientific-lit-review/},
  year = {2018}
}