4.33. Editor - Delete a site
| Id | 4.33. |
| Description |
As an Editor,
I want to be able to delete a site that has been demolished or entered multiple times with different addresses,
So that I can correct the registry, avoid confusion and improve reliability on the data. |
| Priority | Medium |
| Actors | Editor |
| API Calls | DELETE /sites/<site-id> |
| Linked Processes | |
| Status | Implemented |
Preconditions
- The User must be authenticated and have the Editor role.
- The User has a valid site ID to delete
- The User has selected a reason for deleting the site
Postconditions
- The system returns a confirmation that the site has been marked as “to be deleted”.
Main flow
- The Organisation Editor uses an API call to delete a specific site by ID (DELETE).
- The system validates the input parameters.
- The system marks the site, its blocks and its units as well as their connections as “to be deleted”. WARNING: If the site is already used somewhere in the system, the site gets marked as deleted but is kept in the database.
- The system returns a confirmation that the site has been marked as “to be deleted”
Exceptions
[400 Bad Request] Invalid input:
If mandatory fields are missing or invalid, the system returns an error message.
[404 Not Found] Site not found
Error returned by the system if the site is not found.
[500 Internal Server Error] System Error
If the system fails to save changes due to an internal error, it displays an appropriate message and logs the error for further investigation.