Looking for best practices to prevent accidently removing lots of links.
I think there has been improvements in this area.
Scenario delete home node (accidently), popup launches for option for break links dialog. Select remove broken links, thinking deleting another node. Break links takes a while. Cancel delete operation. Job to remove broken links continues in back ground. Later realise lots of links have been removed, and roll back database.
At time was a bug, when deleting a proxy configuration item that didn't refresh UI. And so if went to delete item again, as item already deleted would default to the hone node and delete that instead. (fixed since) Also seen case where content author deleted a large section, and chose remove broken links.
One is education, saying in dialog what actions will be performed, how many items deleting, how many links about to break etc. Defaulting option to not break links.
Other is extending pipeline to prevent mass deletion of items. Recall adding pipeline before to say are you sure you want to delete 100 items etc, and preventing deleting 1000 items in one go.
Other is auditing/alerting that a bulk delete/remive links operation has been requested. Do doesn't go days before realising all links broken in master.
Wondering what best practices are, how others have protected from these scenarios