This also reminiscent of other identifiers we encountered in datacite, so we might want to design this one with

ATM we have smth like

id: DANDI-SANDBOX:217838/draft
identifier: DANDI-SANDBOX:217838

(disregard id for this one since versioned!)

and when to upload the same to main dandi archive, we should know what ID there should it be. So I think we should add otherIdentifiers which would be a list where other DANDI instances could be listed with their ids. So if client specifies some other instance to upload to (via -i --instance) -- it would know! note that dandiset.yaml itself is not uploaded, so we have "no problem" of needing to update it somehow on the remote end.

Would fully or partially (analysis todo; may be just a duplicate) address good old

• Need to provide support for different "instances" of DANDI archive #76