-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Return/Add validation of dandiset.yaml upon upload? #1427
Comments
the key question is whether you expect to only get dandiset id from dandiset.yaml, or do you expect anything more than that. if the former, then it doesn't matter if the rest is valid or invalid. however, i think the CLI is always an opportunity to inform the user to fix/update something. think |
ATM AFAIK we just care about yes -- client has an opportunity, hence this issue, but there are all those concerns especially about ensuring up-to-dateness of local dandiset.yaml. |
i would still say remote is the keeper of record and cli could tell user locally to update (or just auto update). |
prompted by @satra's question in
ATM:
--upload-dandiset-metadata
but we are not validating.I think, indeed, we should re-approach validation of the dandiset.yaml here.
--upload-dandiset-metadata
option block with the same behavior as we have for assets in terms of--validation
option.dandiset.yaml
might differ from the metadata record on the server.--validation
option)WDYT @satra @jwodder ?
The text was updated successfully, but these errors were encountered: