so if I adjust wanted for the remote repo and (re)publish dataset, it would transfer some files, update git-annex on remote but I don't think it would trigger post-update hook... even if it does, parents datasets wouldn't be aware of it and wouldn't update their web meta-data knowledge about some kid pushing more data files. So I guess, in case of publish executed under a sub-dataset, logic could try to ascend hierarchy on the remote end and trigger post-updates to get information updated
today it happened similarly but in a different scenario. I guess that somehow super was published first, so whenever later subdataset was published super's web metadata didn't reflect anything about its kid size
so if I adjust wanted for the remote repo and (re)publish dataset, it would transfer some files, update git-annex on remote but I don't think it would trigger post-update hook... even if it does, parents datasets wouldn't be aware of it and wouldn't update their web meta-data knowledge about some kid pushing more data files. So I guess, in case of publish executed under a sub-dataset, logic could try to ascend hierarchy on the remote end and trigger post-updates to get information updated
today it happened similarly but in a different scenario. I guess that somehow super was published first, so whenever later subdataset was published super's web metadata didn't reflect anything about its kid size