Open psadil opened 1 year ago
Hey @psadil, sorry for the long silence here! Your ideas are interesting. We're busy with a different development project until the end of May, though, so there is too little time for us this month to discuss or act on this issue. However, as a heads-up, we have scheduled a ria-themed sprint for the month of June, and added this issue to our agenda - thanks for opening it!
@adswa , thanks for the update!
What is the problem?
This started out as a thread on neurostars.org. Now it's a feature request!
My current understanding (from this answer) is that the process for making a 7 zip archive of annexed files in a RIA store involves :
For safety, these steps need to be done while also manually managing locks and ensuring that annexed files are synchronized.
That works, but it would be convenient if there were a way to interact with a RIA store without knowledge of it's internal structure -- to have the annex components be backed by the archive only.
What steps will reproduce the problem?
Create store
Now, when pushing annexed content to the new store, I would like for the ability to have
DataLad
automagically archive the annexed files into a 7 Zippedarchive.7z
.Here are a couple of ways that could look
A new subcommand
A new flag for
export-archive-ora
, making TARGET optionalA flag for
push
(which causes an error if the sibling is not a RIA store)DataLad information
Additional context
datalad/datalad#5059 is related, but I think it had a slightly different target (and was closed without changes).
Have you had any success using DataLad before?
Yes! But the 7 Zip archive process felt awkward and so I left files unarchived.