@dannon @mvdbeek
We’ve talked about how it would be great if there was a possibility to export CLI runs to a Galaxy instance. The question is how that should be implemented—should we use RO-Crates? If so, we’d likely need to handle: "Add functionality for exporting RO crates #1045".
If not, could we instead use Galaxy’s archiving functionality to export a CLI run to a Galaxy instance? And if we go that route, would a workflow like this make sense?
- Use the
/api/histories/{history_id}/prepare_store_download endpoint to package the history.
- Poll
/api/short_term_storage/{storage_id}/ready to check when the package is available.
- Download the archive from
/api/short_term_storage/{storage_id}.
- Re-upload it to a Galaxy instance using
/api/histories.
Alternatively, could we use the /api/histories/{history_id}/write_store? endpoint for this instead?
@dannon @mvdbeek
We’ve talked about how it would be great if there was a possibility to export CLI runs to a Galaxy instance. The question is how that should be implemented—should we use RO-Crates? If so, we’d likely need to handle: "Add functionality for exporting RO crates #1045".
If not, could we instead use Galaxy’s archiving functionality to export a CLI run to a Galaxy instance? And if we go that route, would a workflow like this make sense?
/api/histories/{history_id}/prepare_store_downloadendpoint to package the history./api/short_term_storage/{storage_id}/readyto check when the package is available./api/short_term_storage/{storage_id}./api/histories.Alternatively, could we use the /api/histories/{history_id}/write_store? endpoint for this instead?