Support dimensional dataelements

Registered by Jo Størset

Mutlidimensional elements must be flattened into it's individual options

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Ngo Thanh Long
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 0.2
Started by
Ngo Thanh Long
Completed by
Jo Størset

Related branches

Sprints

Whiteboard

We need to support flattening of dimensions.

A dataelement that has dimensions, should be listed like this in the form:

DataElementName (shown as some kind of heading)
===============
CatOptionCombo1
__________
CatOptionCombo2
__________
CatOptionCombo3
__________
=============== (some kind of ending for the dataelement to show that the next element is about to start)

Example (District Stock Monthly, kerala):

0.1 ml (AD) Stock
===
Balance from Previous month
___
Stock received
___
Unusable
___
Stock Distributed
___
Total stock
___
===
0.5 ml (AD) Stock
===

...

I'm not completely sure if we should flatten the dimensions on the server or do that on the client, but I propose that we flatten on the server, so that the list of values in the datavalueset for a dataelement matches the definition of the dataelement.

In that case we could have an optional list of CategoryOptionCombos (I think that is the right term) for a dataelement (with name = a comma-separated list of names), and for datavalues we turn it into a list of values, with the nonmultidimensional datavalues only having a single value?

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.