From b1deccb819720959434de91e42ed7b1f076888e6 Mon Sep 17 00:00:00 2001 From: Yaroslav Halchenko Date: Wed, 8 Jul 2026 08:02:23 -0400 Subject: [PATCH] Cite DataLad JOSS paper on first mention Add the DataLad JOSS publication (doi:10.21105/joss.03262) to references.bib and cite it on the first reference to DataLad in data_management.md. While there, fix the mangled markdown in the link label ([Dat*aLad] -> [*DataLad*]) so the intended italic-linked text actually renders. Co-Authored-By: Claude Code 2.1.204 / Claude Opus 4.7 --- book/data_management.md | 2 +- book/references.bib | 13 +++++++++++++ 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/book/data_management.md b/book/data_management.md index 21bef03..bc8c419 100644 --- a/book/data_management.md +++ b/book/data_management.md @@ -953,7 +953,7 @@ However,*git* does not work well for version control on larger datasets using bi ### Using *DataLad* for version control on larger datasets -A solution to this problem is to use a version control tool that is specifically designed for large data. There are several tools that address this problem; we will focus on [Dat*aLad](https://www.datalad.org/), which is a data management system that functions very similarly to git. It is based on a tool called [*git-annex*](https://git-annex.branchable.com/), but provides much greater ease of use for researchers. (Full disclosure: Our group collaborates with the *DataLad* group and our grants have supported some of their development work.) +A solution to this problem is to use a version control tool that is specifically designed for large data. There are several tools that address this problem; we will focus on [*DataLad*](https://www.datalad.org/) [@Halchenko:2021aa], which is a data management system that functions very similarly to git. It is based on a tool called [*git-annex*](https://git-annex.branchable.com/), but provides much greater ease of use for researchers. (Full disclosure: Our group collaborates with the *DataLad* group and our grants have supported some of their development work.) An important note: *DataLad* is quite powerful but has a significant learning curve, and takes a bit of time to get accustomed to. In particular, its use of symbolic links can sometimes confuse new users. Having said that, let's look at some simple examples. diff --git a/book/references.bib b/book/references.bib index 5d1d4e2..2b83431 100644 --- a/book/references.bib +++ b/book/references.bib @@ -1337,3 +1337,16 @@ @article{Open-Science-Collaboration:2015aa volume = {349}, year = {2015}, bdsk-url-1 = {https://doi.org/10.1126/science.aac4716}} + +@article{Halchenko:2021aa, + author = {Halchenko, Yaroslav O. and Meyer, Kyle and Poldrack, Benjamin and Solanky, Debanjum Singh and Wagner, Adina S. and Gors, Jason and MacFarlane, Dave and Pustina, Dorian and Sochat, Vanessa and Ghosh, Satrajit S. and M{\"o}nch, Christian and Markiewicz, Christopher J. and Waite, Laura and Shlyakhter, Ilya and de la Vega, Alejandro and Hayashi, Soichi and H{\"a}usler, Christian Olaf and Poline, Jean-Baptiste and Kadelka, Tobias and Skyt{\'e}n, Kusti and Jarecka, Dorota and Kennedy, David and Strauss, Ted and Cieslak, Matt and Vavra, Peter and Ioanas, Horea-Ioan and Schneider, Robin and Pfl{\"u}ger, Mika and Haxby, James V. and Eickhoff, Simon B. and Hanke, Michael}, + doi = {10.21105/joss.03262}, + journal = {Journal of Open Source Software}, + number = {63}, + pages = {3262}, + publisher = {The Open Journal}, + title = {DataLad: distributed system for joint management of code, data, and their relationship}, + url = {https://doi.org/10.21105/joss.03262}, + volume = {6}, + year = {2021}, + bdsk-url-1 = {https://doi.org/10.21105/joss.03262}}