Aggregation level boundaries

Registered by Lars Helge Øverland on 2009-03-26

Functionality for defining aggregation start levels / boundaries for data elements. For certain data elements one would like to store overlapping data at different levels. In those cases you would like to confine the data used for aggregation to certain levels.

An example: One stores population data (census) at level 3 and at level 5 (generated). In this case the aggregated value for orgunits at level 1 to 3 should use data from level 3, while orgunits at level 4 to 5 should use data from level 5.

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Lars Helge Øverland
Definition:
New
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2.0.2
Started by
Lars Helge Øverland on 2009-05-22
Completed by
Lars Helge Øverland on 2009-05-28

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.