-
Notifications
You must be signed in to change notification settings - Fork 18
Export to nwb #7
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
Conversation
Co-authored-by: Dimitri Yatsenko <dimitri@datajoint.com>
Co-authored-by: Dimitri Yatsenko <dimitri@datajoint.com>
The gh action buildtest is failing because there was a change to usernames. If you swap |
@CBroz1 why add a SessionNote table? Wouldn't it be better to just add this as a field of the Session table? |
Arguably, Thinking it through, maybe |
@CBroz1 I don't see what you are gaining by making either session_note or session_directory their own tables. It complicates the schema and necessitates more complex queries. I generally think of tables as handling 1-many and many-many relationships. If you have a 1-1 relationship, such as session to session_note, IMO it is better to make a fatter table with nullable fields than add additional tables. These fields would not be keys, so it should not affect any other tables that link to Session. |
Co-authored-by: Dimitri Yatsenko <dimitri@datajoint.com>
Co-authored-by: Dimitri Yatsenko <dimitri@datajoint.com>
Co-authored-by: Dimitri Yatsenko <dimitri@datajoint.com>
Caught up with other folks on this. The separation of tables here is based on the expected timing of data entry or need to update.
This way, we permit later entry, and avoid cascading deletes or updates to this |
Co-authored-by: Chris Brozdowski <CBrozdowski@yahoo.com>
Co-authored-by: Dimitri Yatsenko <dimitri@datajoint.com>
Co-authored-by: Dimitri Yatsenko <dimitri@datajoint.com>
# Conflicts: # element_session/export/nwb.py
…o_nwb # Conflicts: # element_session/session.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good here. The only piece I would change would be to move the integration test to the test folder of workflow-session. This could be done pretty easily via PR to the CBroz1:nwb
branch which has an open PR we plan to close out this week.
# Conflicts: # element_session/export/nwb.py # element_session/session_with_id.py # requirements.txt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bendichter! Great work. A few minor documentation suggestions above.
Co-authored-by: Kabilar Gunalan <kabilar@datajoint.com>
Co-authored-by: Kabilar Gunalan <kabilar@datajoint.com>
Co-authored-by: Kabilar Gunalan <kabilar@datajoint.com>
Co-authored-by: Kabilar Gunalan <kabilar@datajoint.com>
Co-authored-by: Kabilar Gunalan <kabilar@datajoint.com>
Co-authored-by: Kabilar Gunalan <kabilar@datajoint.com>
Co-authored-by: Kabilar Gunalan <kabilar@datajoint.com>
Co-authored-by: Kabilar Gunalan <kabilar@datajoint.com>
@kabilar all look good. I do not have merge privileges so feel free to merge when you are ready. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bendichter!
No description provided.