Closed jimklo closed 3 years ago
Sadly I don't think those assumptions are at fault here. The real error is being mangled by this: raise ValidationError({'error': f'Invalid CSV file: {str(e)}'})
. I submitted #137 to stop obscuring the useful stack traces, once it's merged you should be able to rebuild and get a more useful error log.
When trying to import sessions from a CSV file; we receive an error in the log and no sessions are actually imported:
Seems like there are some 'hard coded' assumptions when looking at
csvContentToJsonObject
, especially here/fs/storage/XNAT
is a fixed path within the SRI/Stanford XNAT install - may not be the same for other installations. It should be noted that once this path is set for XNAT, there is not mechanism in XNAT to change it's root, meaning this should be a value that is set per installation, and likely should not be hard coded.Related, the Django container configuration specifies:
which is leveraged within the
docker-compose.yml
as:I'm not sure this is the right way we should mount. Our host doesn't locate scans in the same physical location as the XNAT container.