dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olatitle@xxxxxxxxx>]

Public bug reported:

The system does not pre-generate periods, but instead creates them when
they are needed to store a new value, either via data entry or data
import.

In a system where data is entered or imported monthly only, which is
quite common, there would e.g. be no quarterly periods available in the
database. When you want to use or export aggregated values by quarter
there is no way to select these quarterly periods in either datamart or
report table GUI since they do not appear in the available period lists
in the select boxes, simply because they do not exist.

We need some kind of mechanism to allow "output" modules like datamart
and report tables to create and use periods when generating aggregated
data.

Right now this inconsistency is blocking the users from analysing and
presenting data on aggregated periods.

** Affects: dhis2
     Importance: High
         Status: New


** Tags: aggregation periods

** Changed in: dhis2
   Importance: Undecided => High

** Changed in: dhis2
    Milestone: None => 2.0.1

-- 
Aggregate periods not available in datamart or report tables
https://bugs.launchpad.net/bugs/375989
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS: 2.0.1.

Status in District Health Information Software 2: New

Bug description:
The system does not pre-generate periods, but instead creates them when they are needed to store a new value, either via data entry or data import. 

In a system where data is entered or imported monthly only, which is quite common, there would e.g. be no quarterly periods available in the database. When you want to use or export aggregated values by quarter there is no way to select these quarterly periods in either datamart or report table GUI since they do not appear in the available period lists in the select boxes, simply because they do not exist.

We need some kind of mechanism to allow "output" modules like datamart and report tables to create and use periods when generating aggregated data.

Right now this inconsistency is blocking the users from analysing and presenting data on aggregated periods.