Dear Galaxy Developers,
Because of specific use case, our transfer tool need to keep the datasets in a different location instead of the default location, so we'd like to purge datasets according to its "external_filename" (we found this column in the dataset table in the database). Is there a way or some code to modify so that when we try to purge a dataset or a history in Galaxy, the file located at a dataset's external_filename can also be deleted?
Thanks in advance, Mark Xiao
Hi Mark,
I'm not sure this is something I'd encourage pursuing for most folks, but I understand that custom deployments may need special functionality. To implement this for your Galaxy instance, you'd want to look at the ObjectStore "delete" functions, here: https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/objectstore/__in...
-Dannon
On Thu, Nov 3, 2016 at 12:33 AM, Mark Xiao mustxyk@gmail.com wrote:
Dear Galaxy Developers,
Because of specific use case, our transfer tool need to keep the datasets in a different location instead of the default location, so we'd like to purge datasets according to its "external_filename" (we found this column in the dataset table in the database). Is there a way or some code to modify so that when we try to purge a dataset or a history in Galaxy, the file located at a dataset's external_filename can also be deleted?
Thanks in advance, Mark Xiao
Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
galaxy-dev@lists.galaxyproject.org