-
Notifications
You must be signed in to change notification settings - Fork 12
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
Separate "Developer User Guide" or just "Developer Guide" and rename into "DANDI Developer Guide"? #125
Comments
Hi @yarikoptic, these instructions would be great. Could they live under the current Developer Guide section? Thank you. |
that's the question on either they should? As far as I see that one is primarily about developing DANDI itself thus somewhat hiding and splitting (Python interface is in "User guide") "development against DANDI". So I wondered if we could get some better organization... worse come to worse we could just add some sections to |
How about adding a separate section below |
We have
User Guide
which is mostly user oriented -- users who aim to access or upload data, not write software to integrate with DANDI.I wonder if we should make more explicit separation here, and have a section for people who are developing based on DANDI, e.g. using API, Python lower level APIs etc.
E.g. ATM in the light of
I was looking a place where to add an advise/requests to use it aiming for efficiency/lower impact on our services, e.g.
glob
for/assets/
listing whenever aiming for specific file types (not to fetch all and filter on the client).and that should possibly be accompanied with examples on how it to be done both in API calls and Python interfaces.
WDYT?
The text was updated successfully, but these errors were encountered: