Closed andreped closed 1 year ago
I think currently we don't expose anything to kill it, although we have been working on a new mechanism / way to reimport things, so I'll see if it's possible to expose a way to kill the current import task.
On Tue, May 23, 2023 at 5:06 PM André Pedersen @.***> wrote:
When adding new data to an existing database, occationally I add the wrong data/folder. In that case, it would be great if it was an easy method to stop this transfer.
Is it possible to stop such a job through the web interface?
Right now, we have DSA setup on a stable server where multiple people can access the data added to the database. Hence, it is not of interest to restart the entire service in these scenarios.
— Reply to this email directly, view it on GitHub https://github.com/DigitalSlideArchive/digital_slide_archive/issues/271, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFODTVTANDVS7Q7QKNMQDDXHURGTANCNFSM6AAAAAAYMOBRTE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- David A Gutman, M.D. Ph.D. Associate Professor of Neurology Emory University School of Medicine
Would be of interest :]
BTW: Is there a place where one could start discussions/feature requests (rather than asking questions in Issues, which I believe mostly should be used for bug reports or similar).
In other projects we have started using GitHub Discussions, which then can be accessed from the tab right of Pull Requests
(e.g., see FAST).
I changed the issue to a feature request
.
With the import tracker plugin (https://github.com/DigitalSlideArchive/import-tracker), which is part of our standard deployment, this can be done since https://github.com/DigitalSlideArchive/import-tracker/pull/14
Fantastic, @manthey! This greatly improves the user-experience :] Cheers!
When adding new data to an existing database, occationally I add the wrong data/folder. In that case, it would be great if there exist an easy method to stop this transfer, preferably through the web interface. Is that possible?
Right now, we have DSA setup on a stable server where multiple people can access the data added to the database. Hence, it is not of interest to restart the entire service in these scenarios.