In short, my question is: when running an existing RMarkdown file that was created on another system, I am notified of R package dependencies and provided with an option to install missing packages. Is there a similar process for detecting and resolving data dependencies?
Some background: I am new to R and RMarkdown and attracted to the latter's potential to increase the reproducibility of published research. After exploring some tutorial materials, I wanted to see how RMarkdown is used in the wild. I thus went to medRxiv and searched it for RMarkdown, which yielded 11 results, and the one I tried gave me this issue. It was easily resolved manually by re-running the RMarkdown in a folder containing the relevant data files, but I am wondering whether such data dependencies could be handled in a more (re)user friendly fashion, especially given that it already works smoothly for code dependencies (at least as long as they are in R).