We'd like to have a consistent and safe way for study designers (almost always the implementers, so people with the DEVELOPER role) to delete and remove things as they set up a study. Often out deletes actually remove things from the database, and so those calls are only accessible to administrators for test clean-up.
...
- If item is already logically deleted, throw an EntityNotFoundException
- If item is not marked deleted, mark it as deleted
...
- If item is not in database, throw an EntityNotFoundException
- If item is in database but logically deleted, this should physically delete the item
...
Dependent Objects
Objects that cannot be deleted because they would leave other objects with referential integrity problems:
...