From 2d2e21ef4897db7f9e76a5742ba37d657b86a7ea Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Szczepanik?= Date: Wed, 10 Jan 2024 12:40:19 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Adina Wagner --- docs/source/user/datalad-access.rst | 6 ++++++ docs/source/user/datalad-generate.rst | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/source/user/datalad-access.rst b/docs/source/user/datalad-access.rst index 2072185..c9ded59 100644 --- a/docs/source/user/datalad-access.rst +++ b/docs/source/user/datalad-access.rst @@ -37,6 +37,12 @@ Given the exemplary values above, the pattern would expand to 'datalad-annex::?type=external&externaltype=uncurl&encryption=none&url=file:///data/group/groupname/local_dicom_store/my-study/P000123_{{annex_key}}' +A full ``datalad clone`` command could then look like this: + +.. code-block:: + datalad clone 'datalad-annex::?type=external&externaltype=uncurl&encryption=none&url=file:///tmp/local_dicom_store/dl-Z03/P000624_{{annex_key}}' my_clone + + .. note:: The URL is arguably a bit clunky. A convenience short cut can be provided via configuration item ``datalad.clone.url-substitute.