backtrackbaba
commented
4 years ago Hi @joe-scotto,
As mentioned in the README, our APIs are built upon data provided by pomber who internally consumes JHU's data. Now, if you see the update frequency of JHU, you'll see that it has reduced to once a day which happens approximately at 00:00 GMT every day. Based on the updation of JHU, I had written automation to update the database a few minutes after they do their update.
The endpoint for the same still exists in the code, but the automation has removed due to the following reasons:
Our project essentially standardizes the data of JHU by using globally accepted ISO standards for the dates as well as the names. The data provided by JHU doesn't have standard country names. If you see this file that I use to standardize includes all the names that JHU has and it's equivalent ISO code.
This can't be automated as there isn't a proper system of naming hence there has to be a human in the process to checks for mapping issues and simply adds it to the JSON.
Ex: Just yesterday they added a ship called MS Zaandam, which is stuck somewhere near the Netherlands. Now, if this would've been automated it would've broken the system as there isn't any country by that name. Hence, I had to manually add an entry for it as MSZ
This is a reason why I update it locally first, to see what are the breaking changes and then trigger the update on prod manually.
Do let me know if you have any better process in mind or if you need any other help with the project
Title pretty much says it all... it seems that you manually trigger updates to the API but what times are these?