dandi / dandi/dandi-cli

model: should we remove "access" and "repository" for now?

Open
#344 5 comments 0 reactions 0 assignees View on GitHub
schema
Dominant language
Python
Stars
28
Forks
37
Avg merge
1d 17h
Merged PRs (30d)
9

Description

I think we would be better to start with smaller, more manageable metadata record for dandiset, without hard-coding things such as `repository` and `access` (seems to be also a tricky one: #343 ). It would always be easier to extend, or to provide custom mapping (e.g. based on identifier being DANDI we could make claims on `repository` and even `access`). WDYT @satra?

edit 1: I somewhat also dislike them since they are "the defaults" for any `DandiMeta` (which might not even yet was considered to be uploaded to the archive's metadata record).

edit 2: Actually - may be they are ok IF dandi-api server would populate them since it is not client's job since we do not upload dandiset metadata (although #341 is coming to facilitate migration). But first let's figure out #343 and then file an issue or PR for dandi-api to complement https://github.com/dandi/dandi-api/issues/64 and https://github.com/dandi/dandi-api/issues/63

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.