-
Notifications
You must be signed in to change notification settings - Fork 28
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
subject_id confusion #78
Comments
#82 will address Re
thus specifying which field (subject_id) and in what file. Could you please copy/paste complaint which you saw? |
@yarikoptic @bendichter has this been addressed in the mean time? can we close this? |
This is fixed
This is still the case. It reports that the file does not have all of the necessary metadata, but does not inform the user specifically that the subject_id is missing. I think it would be a smoother UX for
This is still the case, though I think this would be addressed sufficiently by fixing #2. |
isn't that what it says in
? I would also like to see colors to indicate errors |
oh shoot there it is. OK yeah we can close this |
There are a few issues around
subject_id
:dandi validate
does not enforce thatsubject_id
is present, butdandi organize
requires it.dandi organize
runs on a file that is missingsubject_id
it complains about missing metadata, but does not specify what this missing metadata is.dandi organize
complaining, so a user will just carry on and will be confused when no data is uploaded.This is all exacerbated by the fact that ipfx, the main conversion software for ABF and DAT icephys files out of the Allen Institute, doesn't currently even have a way to add a
Subject
object to the nwb file in the first place (so you can't specifysubject_id
). I have made a pull request to be able to add this information here.The text was updated successfully, but these errors were encountered: