Recover ENEDIS past data lost due to "rolling window" publication strategy
Following #822 (closed)
Description
ENEDIS provider publishes data with a rolling window strategy. The ENEDIS fetcher has not been configured with dataset_update_strategy: merge
in fetchers.yml
. Data has not been accumulated in json-data but is not lost because source-data is versioned (cf source-data history).
Tasks
-
reconstitute enedis-json-data from enedis-source-data by applying "merge" dataset update strategy
Technical notes
- this should be implemented as a script in dbnomics-data-model that takes advantage of the model layer