Default ScannerID should be NULL instead of 0 in mri_protocol when a protocol is valid on all scanners

[cmadjar]

Modify the perl pipeline to reflect the change in the schema for the mri_protocol table. From now on, when a protocol should not be restricted to a specific scanner, instead of using 0 as a value, the field will be set to NULL.

Unless I am mistaken, I believe that most of the code that will need to be changed is located in the following function of MRI.pm:

Loris-MRI/uploadNeuroDB/NeuroDB/MRI.pm

Line 304 in f9df1b7

sub identify_scan_db {

This goes hand in hand with the following issue on the LORIS side: aces/Loris#7476