Add a is_active field to PointDeCharge table?

[jmaupetit]

Purpose

When a point of charge (PoC) is decommissioned (most of the time when the PoC has a new operator), we should keep this database entry to ensure database consistency (mostly regarding dynamic data). But if this PoC is no longer active, we should be able to flag it as is and adapt database queries or indicator calculations by taking into account this status update.

Proposal

• add a is_active: bool = True field to the PointDeCharge model
• add database migration
• ensure the Statique model does not export this field

Cherry on the cake:

• add a /statique/inactivate/bulk endpoint *
• add a /statique/activate/bulk endpoint (in case we made a mistake) *

* expected payload would be a list of id_pdc_itinerance

[loco-philippe]

I think it's a good idea, but it seems to me that it's better to add the field to the station table.

It may also be useful to discuss with operators to understand what types of operations are required to define operating modes (and possible additional attributes or endpoints).

e.g. is it interesting to separate the creation of an operator, the creation of a station and the association of a station to an operator ?

[loco-philippe]

deactivation / reactivation rule proposal :

• deactivation of pocs:

  • all poc can be deactivated
  • deactivation of a poc is not propagated to the station

• purge of deactivated pocs

  • a deactivated poc without session and without status is included in the data to purge

• reactivation

  • all deactivated pocs (not yet deleted) can be reactivated

Deactivation of a station is equivalent to deactivation of all pocs.
The is_active status of a station can be calculated with the following rule :
- if all pocs of the station are deactivated, the station is deactivated (is_active is False) else is_active is True