There is a Docker container that runs the data freshness emailer (https://hub.docker.com/r/mcarans/hdx-data-freshness-emailer/). The code for the implementation is here: https://github.com/OCHA-DAP/hdx- data - freshness - emailer . It has tests with a high level of coverage.It sends an automated mail reminder to data contributors if the update frequency time window for any of their datasets is missed by a certain amount. We would provide the link to the dataset that needs updating and emails to the same individual for multiple datasets are batched into one so they are not bombarded. When a dataset becomes delinquent then HDX administrators are sent an email so that they can follow up. The flow is as shown below:
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Here is the Docker image of the data freshness emailer: https://hub.docker.com/r/mcarans/hdx-data-freshness-emailer/. The code for the implementation is here: https://github.com/OCHA-DAP/hdx-data-freshness-emailer. It has tests with a high level of coverage.
29/11/2017 (60 days of runs since overdue emails sent)
SELECT DISTINCT a.id, c.title FROM dbdatasets a, dbdatasets b, dbinfodatasets c where a.id = b.id AND a.run_number > b.run_number and b.run_number > 149 AND a.fresh = 0 and b.fresh = 2 AND a.id = c.id;
...