When preparing the SIARD for browse if the process for some reason gets stuck at preparing for browse state as mentioned by @Laurira in #212 there is no mechanism to start the process over again or delete unless via REST API.
The dbptk-ui should have mechanism to recover from inconsistent states. As it is (version 2.5.1) the only way to delete the database from dbptk is via REST API.
When preparing the SIARD for browse if the process for some reason gets stuck at preparing for browse state as mentioned by @Laurira in #212 there is no mechanism to start the process over again or delete unless via REST API.
The dbptk-ui should have mechanism to recover from inconsistent states. As it is (version 2.5.1) the only way to delete the database from dbptk is via REST API.