You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ChRIS_store backend supports POST request to create and store pipelines (a chain of multiple plugins, with parameters). We need to implement a user interface for creating plugins.
We are debating a new proposal: add a page featuring a drag-and-drop interface where users can design pipelines in the ChRIS_store_ui. If logged in, user should be able to save the pipeline to the ChRIS_store.
Ideally, the widget for this should be coded up as a reusable React component — one day we might want to port it into https://github.com/FNNDSC/ChRIS_ui/
Arguments against the new proposal: user cannot execute test-run of pipelines designed in the ChRIS_store_ui without importing the pipeline into ChRIS first. The feature of designing pipelines should only be available in ChRIS_ui, and the only way to upload pipelines to the ChRIS_store should be via a publish or import/export mechanism invoked from ChRIS.
The ChRIS_store backend supports POST request to create and store pipelines (a chain of multiple plugins, with parameters). We need to implement a user interface for creating plugins.
Easiest solution: allow pipeline JSON to be uploaded. Front-end makes a POST request to
chrisstore.co/api/v1/pipelines/
.Example: https://github.com/FNNDSC/CHRIS_docs/blob/master/pipelines/fetal_brain_reconstruction.sh
We are debating a new proposal: add a page featuring a drag-and-drop interface where users can design pipelines in the ChRIS_store_ui. If logged in, user should be able to save the pipeline to the ChRIS_store.Ideally, the widget for this should be coded up as a reusable React component — one day we might want to port it into https://github.com/FNNDSC/ChRIS_ui/
Arguments against the new proposal: user cannot execute test-run of pipelines designed in the ChRIS_store_ui without importing the pipeline into ChRIS first. The feature of designing pipelines should only be available in ChRIS_ui, and the only way to upload pipelines to the ChRIS_store should be via a publish or import/export mechanism invoked from ChRIS.Regarding above, see FNNDSC/ChRIS_ui#269
The text was updated successfully, but these errors were encountered: