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

services: define and use "scope" #2048

Open
yarikoptic opened this issue Oct 15, 2024 · 0 comments
Open

services: define and use "scope" #2048

yarikoptic opened this issue Oct 15, 2024 · 0 comments
Labels
UX Affects usability of the system

Comments

@yarikoptic
Copy link
Member

Came up in the context of

we could add services not only for assets but also

  • dataset (generic, non-DANDI specific term so could later be reused by others)
  • directory ("folder" is forbidden in BIDS)
  • file (generic, non-DANDI specific)

so then corresponding selection of services could be picked up.

I think it is ok to have scope: str (not a list[str]) since for every scope there would be different URL and potentially descriptive "categories", as per

@yarikoptic yarikoptic added the UX Affects usability of the system label Oct 15, 2024
@yarikoptic yarikoptic changed the title services: define "scope" services: define and use "scope" Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX Affects usability of the system
Projects
None yet
Development

No branches or pull requests

1 participant