Hi,
we're currently reviewing how DHIS2 is used for the yearly review here in Ghana, and an issue related to the aggregation came up: during the reviews, which go into February and March, data quality issues with the previous years data are often found, and needs to be corrected. However, since only the last 12 months are aggregated by the scheduled datamart, changes made to the data in January and February are never reflected in the reports for the previous year unless the datamart is run manually.
Perhaps the scheduler could either let
1) set the number of months to aggregate daily/weekly
2) increase the aggregation to for example 14 months instead of 12
??
Good ideas. In the meantime, you may want to have a look at the infamous “Controlling datamart scheduling” thread for an approach for how to schedule the datamart when and how you want it.
You could of course use other things like shell scripts or a Python script to achieve similar things.
Regards,
Jason
···
On Fri, Feb 22, 2013 at 11:54 AM, Olav Poppe olav.poppe@me.com wrote:
Hi,
we’re currently reviewing how DHIS2 is used for the yearly review here in Ghana, and an issue related to the aggregation came up: during the reviews, which go into February and March, data quality issues with the previous years data are often found, and needs to be corrected. However, since only the last 12 months are aggregated by the scheduled datamart, changes made to the data in January and February are never reflected in the reports for the previous year unless the datamart is run manually.
Perhaps the scheduler could either let
set the number of months to aggregate daily/weekly
increase the aggregation to for example 14 months instead of 12
Thanks, setting up a script is an option, but it would be nice if it could be done from within GUI.
Being able to set the time to run it from within DHIS2 would also be good (both if running several instances, or if it needs to be started a bit earlier in order to complete in time), but that is probably an old request.
Olav
···
On Fri, Feb 22, 2013 at 11:54 AM, Olav Poppe olav.poppe@me.com wrote:
Hi,
we’re currently reviewing how DHIS2 is used for the yearly review here in Ghana, and an issue related to the aggregation came up: during the reviews, which go into February and March, data quality issues with the previous years data are often found, and needs to be corrected. However, since only the last 12 months are aggregated by the scheduled datamart, changes made to the data in January and February are never reflected in the reports for the previous year unless the datamart is run manually.
Perhaps the scheduler could either let
set the number of months to aggregate daily/weekly
increase the aggregation to for example 14 months instead of 12