add daily iv report

[lagartoverde]

Overview

Made a report about the number of IV created in each admin unit, and the number of those IVs that were synced

connected issues and PRs:

GN-5197

Setup

You will need a user to login into the dashboard

How to test/reproduce

reduce the cron on the ivReport file to make it run soon, verify that the cron is run and that the report generated is correct

Challenges/uncertainties

Waiting for a better translation for the report description and asked Arne if I should check if the synchronization was successful or not

Checks PR readiness

• UI: works on smaller screen sizes
• UI: feedback for any loading/error states
• Check cancel/go-back flows
• Check database state correct when deleting/updating (especially regarding relationships)
• changelog
• no new deprecations

[elpoelma]

Report generation itself works well.
A few questions/remarks though:

• It seems that we always get all historical data, not only scoped per day. Is this what we want? Unfortunately, we of course don't keep track when a meeting has been created...
• Unfortunately, we always only keep track of one 'sync-status' (through a belongsTo relationship), so the sync-count will always be 1 (per meeting). So I'm not sure if that statistic is super helpful. In hindsight (easy to say I know) we probably should have kept this as a hasMany relationship. The sync-status resources themselves are not removed I think, and as they are scoped per 'administrative-unit' graph, you might be able to get a relevant number still.
• Indicating whether the sync was successful or not seems relevant to me

[lagartoverde]

Report generation itself works well. A few questions/remarks though:

• It seems that we always get all historical data, not only scoped per day. Is this what we want? Unfortunately, we of course don't keep track when a meeting has been created...
• Unfortunately, we always only keep track of one 'sync-status' (through a belongsTo relationship), so the sync-count will always be 1 (per meeting). So I'm not sure if that statistic is super helpful. In hindsight (easy to say I know) we probably should have kept this as a hasMany relationship. The sync-status resources themselves are not removed I think, and as they are scoped per 'administrative-unit' graph, you might be able to get a relevant number still.
• Indicating whether the sync was successful or not seems relevant to me

1. My understanding is that we always want to get historical data
2. The sync count will be always 1 in case that meeting was synced, otherwise it will be 0 my intention was to show how many of those IVs were synced
3. How would you do it, make another column indicating if the last sync was an error?

[elpoelma]

Report generation itself works well. A few questions/remarks though:

• It seems that we always get all historical data, not only scoped per day. Is this what we want? Unfortunately, we of course don't keep track when a meeting has been created...
• Unfortunately, we always only keep track of one 'sync-status' (through a belongsTo relationship), so the sync-count will always be 1 (per meeting). So I'm not sure if that statistic is super helpful. In hindsight (easy to say I know) we probably should have kept this as a hasMany relationship. The sync-status resources themselves are not removed I think, and as they are scoped per 'administrative-unit' graph, you might be able to get a relevant number still.
• Indicating whether the sync was successful or not seems relevant to me

1. My understanding is that we always want to get historical data

2. The sync count will be always 1 in case that meeting was synced, otherwise it will be 0 my intention was to show how many of those IVs were synced

3. How would you do it, make another column indicating if the last sync was an error?

I would indeed indicate whether the last sync was an error in a seperate column.