Is your feature request related to a problem? Please describe.
I use search daily. I can be searching for anything, an accession number (which I always put in metadata) or a given string (yes, it's bad, but I usually use some other filters to narrow the depth of the search). Some times a search is taking forever and then I notice that it won't return anything. The GUI is pretty much toast now and any new searches will not work until the first one finishes.
Describe your use case
I need this feature so I can accomplish doing a search that I know will work, compared to the one that I started and it's killing the DB for no reason - since no results will come out of it (potentially after scanning the whole table)
Describe the solution you'd like
There should be a cancel search button that just kills the whole pipeline going to the DB.
Describe alternatives you've considered
My workaround is to kill the GUI completely and re-launch a new one. ugh!
Is your feature request related to a problem? Please describe.
I use search daily. I can be searching for anything, an accession number (which I always put in metadata) or a given string (yes, it's bad, but I usually use some other filters to narrow the depth of the search). Some times a search is taking forever and then I notice that it won't return anything. The GUI is pretty much toast now and any new searches will not work until the first one finishes.
Describe your use case
I need this feature so I can accomplish doing a search that I know will work, compared to the one that I started and it's killing the DB for no reason - since no results will come out of it (potentially after scanning the whole table)
Describe the solution you'd like
There should be a cancel search button that just kills the whole pipeline going to the DB.
Describe alternatives you've considered
My workaround is to kill the GUI completely and re-launch a new one. ugh!