Here is the documentation for Data Managers: https://galaxyproject.org/admin/tools/data-managers/ https://galaxyproject.org/admin/tools/data-managers/data-manager-xml-syntax/ https://galaxyproject.org/admin/tools/data-managers/data-manager-json-syn... I don't see any reference to removing entries from a Tool Data Table. Is there a technical reason why it can't be done? As I understand it, each Tool Data Table must have one column called 'value' that acts as a unique ID for that row of the table. So the data manager would just need the name of the Tool Data Table and a string to look up in the 'value' table, and it would remove that row if it found a match. In my case, another column in the Tool Data Table stores the path to a kmer database that should be removed from the disk. Will this be possible with the currently-available xml & json syntax? Are there any postgresql database entries that should be cleaned up if a Tool Data Table entry is removed? Is there some reason why this is a bad idea or is there another way of accomplishing this (removing Tool Data Table entries) that I've missed? Thanks Dan On Tue, Mar 27, 2018 at 2:09 PM, Dan Fornika <dfornika.work(a)gmail.com&gt; wrote:

Sorry, I should have been more clear. I'd like to create a Data Manager tool that an Admin can use to remove items from a Tool Data Table. I agree that reproducibility is an important concern and the Admin should keep that in mind when managing the data tables. In our case, MentaLiST is designed to pull MLST schemes from public data sources (pubmlst.org, cgmlst.org, enterobase.warwick.ac.uk), and build kmer databases. Those public datasets are updated periodically, so an Admin may decide to build new versions of the databases at various timepoints. We do stamp the data table entries with the creation date, so each new database gets a new entry in the tool data table. At some point an Admin may want to remove older versions of a database. They might find that there is some sort of error or corruption in one of the existing databases. They might want to free up a bit of storage, or just make the user interface a bit cleaner by removing old entries. I noticed that the galaxy API provides a method to do this and it's also included in bioblend, so I'm curious to know if there's a way to call that method from a Data Manager tool. https://docs.galaxyproject.org/en/master/api/api.html#galaxy.webapps.gala... http://bioblend.readthedocs.io/en/latest/api_docs/galaxy/all.html#bioblen... Dan On Sun, Apr 22, 2018 at 3:16 AM, Björn Grüning <bjoern.gruening(a)gmail.com&gt; wrote: