Closed yarikoptic closed 6 years ago
@yarikoptic - so if we have nested git annex repos, we will need to find each one and set metadata explicitly? seems like datalad should do this, since datalad intends to be a bridge across multiple git-annex repos.
Here specifically it is just a matter of replacing one datalad call with another one. Nothing will need to be set manually, nothing will change to the user.
Or are your asking more generic datalad question? Please give use case
@yarikoptic - replacing a datalad call with a git-annex call right? i think in the heudiconv context for the moment it may be fine.
i'm just thinking more generally of datalad datasets, wouldn't there be an api to read and write metadata at any level?
Cherrio!
Datalad 0.10+ will have an API to read arbitrary metadata on any level. The "write" side is not so easy. So far the metadata
command pretended that file-based metadata could be set with it, but that was ultimately only true for annexed files, and only with the limitations of annex (size, and key composition). Datalad 0.10 forcefully ends this dream :(
A generic "write anything, of any size with any structure" is certainly doable, but arguably of less value than adhering to a defined metadata standard -- and I say that without having a good idea on what kind of metadata heudiconv is trying to write...
With @mih we reached an agreement to retract ability to set metadata associated with the files, so currently heudiconv would break if ran with master of datalad:
so fix is needed to manipulate git-annex metada directly via
AnnexRepo.set_metadata
while avoidingdatalad.api.metadata
call