Once an object is deleted, it is deleted for good. There is no trash bin. There is no hidden way to get something back. The only thing you could possibly do is get it from a database backup. 

Thanks Pam. I have no doubt there would be support for a recycle bin/undelete option. After all, most of your users are humans. :-)

I completely agree with your opinion. Even though a baseline was fixed, language-level objects can be deleted easily. We really need the undo delete option.

As the workaround for an accidental object deletion, we export a publication when editing/translating is finished for a document. To avoid disk space shortage, I created a PowerShell script that moves exported publication files to a cheap external storage.

Great idea Naoki Hirai! Right now we're at the authoring stage with most of our content, so we're quite vulnerable.

Undeleting/recycle bin seems like a problem where most use cases have been identified and resolved. We're certainly not the first people to delete with regrets.

Luckily we had recently done a complete content export from prod and imported to our dev and test environments, so accessing a backup wasn't too much of a problem. Otherwise we'd have to knock on the DBA's door with a box of chocolates. :-)

This may not appy, and may be too late, but did anyone the check local storage of the last-modified user? That has saved us when it's a specific topic and someone's been working on it.

Great idea Jennifer. :-)

Thanks Jennifer. In case it helps anyone else who uses oXygen for authoring, our local SDL documents cache is in %userprofile%\Documents\SDL\InfoShare\{serverID}.