You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a data repository when adding images to scivision is a fiddly step that image providers are likely to want to avoid. Currently there are these instructions that explain to create a GitHub repo with an intake catalog (config file) called .scivision/data.yml - but this also glosses over the part where you also have to host the data at appropriate url that can be included in the intake catalog - typically we are using Zenodo for this. Getting the urlpath right in the config is a particular hassle.
Can we automate this via the scivision UI? Can we give the following options:
An upload button for images, or a compressed folder of images
A field for the link to a pre-existing url (e.g. Zenodo)
It would need to automate the:
Intake catalog creation (or future scivision data config file if we move away from intake)
Creation of a GH repo or similar that contains the config file (e.g. at .scivision/data.yml)
Maybe there's some sensible alternative such as a default location where scivision datasets and configs get stored.
TODO:
Check if it's possible to have the intake config in Zenodo instead of GitHub
The text was updated successfully, but these errors were encountered:
Creating a data repository when adding images to scivision is a fiddly step that image providers are likely to want to avoid. Currently there are these instructions that explain to create a GitHub repo with an intake catalog (config file) called
.scivision/data.yml
- but this also glosses over the part where you also have to host the data at appropriate url that can be included in the intake catalog - typically we are using Zenodo for this. Getting theurlpath
right in the config is a particular hassle.Can we automate this via the scivision UI? Can we give the following options:
It would need to automate the:
.scivision/data.yml
)Maybe there's some sensible alternative such as a default location where scivision datasets and configs get stored.
TODO:
The text was updated successfully, but these errors were encountered: