Currently, the only data available to the romidata REST API, and thus, the visualizer, is the data located in the Visualization directory (as well as the metadata and images directories).
The problem is that this creates a duplication of the data. For exemple, AnglesAndInternodes.json is present in the AnglesAndInternodes_out_somethingsomething as well as in the Visualization directory.
My suggestion to solve this problem would be to keep the Visualization directory, or replace it with a json file, and only store URIs inside of it. That way, the visualizer would have access to the same data, but without duplication.
This solution would also make it easy to give access to certain files to the visualizer, as we would only need to add an entry in the json file.
@jlegrand62
Running "Visualization" task to access a scan and subsequent output is problematic:
a scan cannot be viewed or accessed within the viewer after "data upload";
"Visualization" task duplicates many data;
REST API does not beneficiate from "Visualization" task data pre-processing (not simple enough);
force to re-run "Visualization" task when updates instead of adding "version" check to REST API;
Currently, the only data available to the romidata REST API, and thus, the visualizer, is the data located in the Visualization directory (as well as the metadata and images directories).
The problem is that this creates a duplication of the data. For exemple,
AnglesAndInternodes.jsonis present in the AnglesAndInternodes_out_somethingsomething as well as in the Visualization directory.My suggestion to solve this problem would be to keep the Visualization directory, or replace it with a json file, and only store URIs inside of it. That way, the visualizer would have access to the same data, but without duplication.
This solution would also make it easy to give access to certain files to the visualizer, as we would only need to add an entry in the json file.
@jlegrand62
Running "Visualization" task to access a scan and subsequent output is problematic: