Right now the CBRAIN task launching interface will refuse to launch a task when:
- the user has selected a file that they don't own
- the file's
group_writable attribute is set to read-only
- the task doesn't say explicitly that it doesn't modify its inputs
The behavior of point 3 is the default. A task can inform the framework that it doesn't modify its inputs by having either:
task_properties :readonly_input_files in portal/taskname.rb (standard integration)
"custom": { "cbrain:readonly-input-files": true } (Boutiques integration)
Given that often integrators forget to set these properties, the admin should have the ability to override the behavior directly in a ToolConfig (or maybe directly at the Tool level?). This would be provided by a simply checkbox in the ToolConfig form, associated with a new boolean attribute:
[ ] Does not require write-access to inputs