Currently documents on output ports are stored under data/jobs by the framework and the GUI simply shows the files at that location to the user. Copying the files to somewhere else would be better. Basically output ports and output options should be treated the same (the web UI and CLI do this too).
The job form could get a new section called "Outputs" which would include both output options and output ports.
Another solution would be to let the user specify only one output directory, which the Pipeline will then use to store all outputs, sorted in sub-directories, like is currently done also by the CLI.
Currently documents on output ports are stored under data/jobs by the framework and the GUI simply shows the files at that location to the user. Copying the files to somewhere else would be better. Basically output ports and output options should be treated the same (the web UI and CLI do this too).
The job form could get a new section called "Outputs" which would include both output options and output ports.
Another solution would be to let the user specify only one output directory, which the Pipeline will then use to store all outputs, sorted in sub-directories, like is currently done also by the CLI.