KBI0013: Merge Data Availability Information #45
Conversation
kbi/0013/index.rst
Outdated
| KBI0013: Merge Data Availability Information | ||
| ============================================ |
There was a problem hiding this comment.
I feel like the title should somehow reflect the context of the text below (splitting a dataset). Right now it is really broad. I am not sure would would be best. Two possible directions
- Split a dataset and reuse data hosting
- Import content availability information on shared annex keys from another dataset
There was a problem hiding this comment.
I agree that "Merge Data Availability Information" was broad.
I'm still not crazy about the current title, but I wasn't able to come up with anything better.
Co-authored-by: Adina Wagner <adina.wagner@t-online.de>
Suggested by: Michael Hanke <michael.hanke@gmail.com>
Show the workflow with 2 files and 2 targets.
Link to the handbook workflow for copy-file instead of to the datalad-docs. Suggested-by: Adina Wagner <adina.wagner@t-online.de>
|
I've made a few updates and chose to keep the focus on splitting datasets. |
There was a problem hiding this comment.
This works for me, thanks for writing it up! I left a few minor suggestions, but feel free to ignore them - when I read this KBI being unfamiliar with the command, I wondered what format this export was in and read it up; the suggestions add rough and short comments about this.
Co-authored-by: Adina Wagner <adina.wagner@t-online.de>
This is a start of a KBI for #28 using @mih's notes from datalad/datalad#600 (comment)
Right now it only covers the use-case of splitting into multiple subdatasets. I plan to come back to this on my next support shift to explore adding a few other examples of how this workflow can be used.