Once dandi/dandi-schema#294, which includes dandi/dandi-schema#323, and dandi/dandi-archive#2430 are merged to the respective repo's master branch, the dandi service-scripts publish-dandiset-version-doi command should be made DANDI instance specific, incorporating the vendor information of a particular DANDI instance, in its execution. In executing the dandi service-scripts publish-dandiset-version-doi command, dandi-cli should fetch vendor info from the api/info/ endpoint of a specified DANDI instance to generate metadata.
Notes
Once dandi/dandi-schema#294, which includes dandi/dandi-schema#323, and dandi/dandi-archive#2430 are merged to the respective repo's master branch, the
dandi service-scripts publish-dandiset-version-doicommand should be made DANDI instance specific, incorporating the vendor information of a particular DANDI instance, in its execution. In executing thedandi service-scripts publish-dandiset-version-doicommand, dandi-cli should fetch vendor info from theapi/info/endpoint of a specified DANDI instance to generate metadata.Notes
dandi service-scripts publish-dandiset-version-doiis not removed in Remove hardcoded vendor specific information #1760 and should be removed in this PR.