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
With any luck #9888 will be merged and we will have a consistent abstraction (backend plugins, consistent use across upload APIs, consistent use with remote files API, and frontend GUI) to describe sources of files to import into Galaxy from. Adding another method to the interface to write files out and using the folder selection GUI included in that commit would provide a powerful abstraction to export files to in a more robust way than sort of ad hoc interfaces and DB tricks we do now.
We could allow users to write their history exports, collection exports, direct datasets, markdown PDF exports to all the interfaces we can target with that plugin infrastructure - including NFS directories, their library and FTP directories, WebDAV, Dropbox, etc.. (Terra and buckets soon hopefully). This would be a much more robust way to get data out of Galaxy and build archives. It would also give admins hooks to tie into existing infrastructure (SCP, aspera, etc..).
The text was updated successfully, but these errors were encountered:
I think @Slugger70 has the same issue, wanting to send individual/a few datasets through to a file sources backend. Currently they're using a tool for this.
With any luck #9888 will be merged and we will have a consistent abstraction (backend plugins, consistent use across upload APIs, consistent use with remote files API, and frontend GUI) to describe sources of files to import into Galaxy from. Adding another method to the interface to write files out and using the folder selection GUI included in that commit would provide a powerful abstraction to export files to in a more robust way than sort of ad hoc interfaces and DB tricks we do now.
We could allow users to write their history exports, collection exports, direct datasets, markdown PDF exports to all the interfaces we can target with that plugin infrastructure - including NFS directories, their library and FTP directories, WebDAV, Dropbox, etc.. (Terra and buckets soon hopefully). This would be a much more robust way to get data out of Galaxy and build archives. It would also give admins hooks to tie into existing infrastructure (SCP, aspera, etc..).
The text was updated successfully, but these errors were encountered: