Skip to content
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

Automate data repo creation #471

Closed
1 task
edwardchalstrey1 opened this issue Jan 3, 2023 · 2 comments
Closed
1 task

Automate data repo creation #471

edwardchalstrey1 opened this issue Jan 3, 2023 · 2 comments
Labels
enhancement New feature or request frontend
Milestone

Comments

@edwardchalstrey1
Copy link
Contributor

edwardchalstrey1 commented Jan 3, 2023

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
@edwardchalstrey1 edwardchalstrey1 added enhancement New feature or request frontend labels Jan 3, 2023
@ots22
Copy link
Member

ots22 commented Jan 5, 2023

#64 #445

@ots22
Copy link
Member

ots22 commented Aug 29, 2023

Closing, since preferable to address as part of #480 (linked the discussion from there)

@ots22 ots22 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request frontend
Projects
None yet
Development

No branches or pull requests

3 participants