With Magnolia 5.7 we stop creating the (longtime outdated) workspace dms.
It means: A fresh installation of Magnolia 5.7+ won't install the dms ws anymore,
but
We must provide a recipe how customers can remove the dms workspace manually on installations which has just been upgraded to Magnolia 5.7+ -.
Ideally we can provide a groovy script which operates on the JCR API to delete the workspace independent from the underlying DB which acts as the persistence layer.

The recipe should work to delete any JCR workspace.