Set environment vars to set vendor-specific dandi-schema used by the DANDI instance#47
Conversation
680b5cd to
1e16bdf
Compare
|
@candleindark should we also ensure that we have at least up to dandi/dandi-archive#2386 pulled into our fork before hitting merge? |
No, this is independent of that one. All this one does is to introduce some env vars, it shouldn't affect the current operation in any way. With that said, I want to wait until dandi#224 is merged before you merge this one though since this repo is a fork of https://github.com/dandi/dandi-infrastructure. |
Sounds good thank you! |
This change is to match the changes in PR dandi#224
|
@NEStock dandi#224 has been approved. It believe it will be merged very soon. It is unlikely to change. You can merge this PR now or continue to wait. But make sure you have this PR merged and released before Stage 2b in dandi/dandi-schema#299 merge and released. |
@candleindark Thank you for the update! We have a few dandi-archive & dand-infrastructure updates to pull into our fork, so ideally we can get those in first (& soon) and then do this next |
dandi/dandi-schema#294 enables vendor-configurable metadata models in dandi-schema.
This PR sets environment variables to configure the metadata models in dandi-schema with EMBER specific info. It is comparable to dandi#224 in https://github.com/dandi/dandi-infrastructure and should be merged after dandi#224 is merged.
TODOs: