Tracker update frequency

[pwalsh]

User story

As an {Administrator}, I want the Tracker to take two updates a year instead of monthly updates as done until now, so that Tracker data is more relevant based on actual data changes.

Notes

• To work, we need this data available from Indaba. If it is not available when work starts, delays in the timeline are to be expected.
• We need some example API queries, with actual data, to understand this.

Tasks

• Write standalone script that talks to the API, and creates a snapshot
  • What a snapshot looks like depends on what our current monthly snapshots look like - please advise if any problems
• The script reads the API and saves the snapshot to a remote fileserver. We can use an S3 bucket for convenience
• S3 bucket should have a naming convention that exposes a "snapshots API" for our code
• Write the logic to display snapshots in the UI
• Write some unit tests

[pwalsh]

@dumyan

• I removed some comments in this thread that were unrelated.
• I updated the tasks list
• I created an S3 bucket and shared shared in our slack channel

Can you please consider the above approach, and estimate time.

[pwalsh]

@dumyan we'll use cron or similar to run this snapshot script - it does not have to be integrated into the web app framework.

[dumyan]

I think 1.5 days will be enough for this, more or less if there aren't any blockers around. I'm not sure if I get "Write the logic to display snapshots in the UI" right, this UI is the tracker, am I right?

[pwalsh]

@dumyan I think so - check where the current snapshots are used pls.