Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export using FilesSource plugins #9948

Closed
jmchilton opened this issue Jul 1, 2020 · 3 comments
Closed

Export using FilesSource plugins #9948

jmchilton opened this issue Jul 1, 2020 · 3 comments

Comments

@jmchilton
Copy link
Member

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..).

@jmchilton
Copy link
Member Author

backend #10993
frontend #11054

@hexylena
Copy link
Member

hexylena commented Sep 1, 2021

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.

I'm not sure if they use it in workflows

@bgruening
Copy link
Member

related I think: #11613

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants