We have lots of users that have access to the library. The reason is that we do quite specialised analysis of experimental data and a lot of users have to create their own analysis files, so they also need the ability to move around items, delete them etc. to organise their work.
However, this comes at the risk of accidentally deleting important data and because version control is not there yet, this can create lots of trouble. Using permissions certainly helps, but having the possiblity to write protect items in the library would certainly improve the situation. If an item (folder, analysis etc) is write protected, the user would have to actively remove write protection before deleting an item. This way accidental deletion of items would be virtually impossible. The write protection should be on an item level, not only on folder level, but folder level would help a lot already. Write protection should apply irrespective of permissions (even admins etc. would have to remove the flag before deletion), but only users with full control should be able to change the flag I think.
In addition to the above, this would need to take into account the potential overwrites when Library Content is imported into an environment.