You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
modify the default schema to allow NULL values for the Center_name field of the mri_protocol table
have a patch to modify the Center_name column (might be tricky with the change of center_name into centerID?)
correct the raisin bread dataset to replace AAAA or ZZZZ by NULL if applicable?
Currently, when an mri_protocol is not being restricted for a specify Center_name, users enter either
ZZZZ
orAAAA
and it is understood that an mri_protocol with CenterZZZZ
orAAAA
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 beNULL
. Ideally, instead of having theCenter_name
column in the mri_protocol, it should be aCenterID
column that links back to the CenterID field of the psc table (foreign key).TODOs:
NULL
values for theCenter_name
field of themri_protocol
tableCenter_name
column (might be tricky with the change of center_name into centerID?)AAAA
orZZZZ
byNULL
if applicable?The text was updated successfully, but these errors were encountered: