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

Modify Center_name field of mri_protocol to allow for NULL values #646

Closed
4 tasks done
cmadjar opened this issue Jul 21, 2021 · 0 comments · Fixed by #650
Closed
4 tasks done

Modify Center_name field of mri_protocol to allow for NULL values #646

cmadjar opened this issue Jul 21, 2021 · 0 comments · Fixed by #650

Comments

@cmadjar
Copy link
Collaborator

cmadjar commented Jul 21, 2021

Currently, when an mri_protocol is not being restricted for a specify Center_name, users enter either ZZZZ or AAAA and it is understood that an mri_protocol with Center ZZZZ or AAAA is valid for all centres' scans...

Instead of using that weird hack, we should refactor the code and the database table to allow for the Center_name to be NULL. Ideally, instead of having the Center_name column in the mri_protocol, it should be a CenterID column that links back to the CenterID field of the psc table (foreign key).

TODOs:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants