dhis2-devs team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

On 6 June 2011 17:44, jason.p.pickering@xxxxxxxxx <
jason.p.pickering@xxxxxxxxx> wrote:

> KISS. Don't use categories as the model does not fit the use case. Three
> plain old data elements will  work.
>
> Just a thought.
>

Tempting thought ... with a few downsides. Its not just 3.  60 job titles x
3 would be 180 dataelements.  Also the existing sdmx-hd transforms I have
developed map sdmx-hd dimensions onto our dhis categories.  Much though I
might have reason to regret some of this, that is the way it is at the
moment.  And it works ok as long as you don't want to add options to
categories :-(


>
> Sent from my HTC
>
>
> ----- Reply message -----
> From: "Bob Jolliffe" <bobjolliffe@xxxxxxxxx>
> Date: Mon, Jun 6, 2011 18:11
> Subject: [Dhis2-devs] adding categoryoption
> To: "dhis2-devs" <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>
> The folk in Zanzibar have an interesting problem with linking with iHRIS.
> iHRIS has data on staffing usually disaggregated by Male/Female but
> occasionally not.  So they need an extra code Male, Female and Unknown.
>
> Now the Zanzibar database has a Sex category with Male and Female defined.
> But *adding* a new categoryoption seems difficult.  After all there are
> many
> categorycombos using Sex as an axis.  And catoptcombos would need to be
> regenerated etc.  Is there any sensible way to do this?
>
> The alternative is to make a brand new category, say Gender, and fill this
> with the three options though that is far from ideal.  For one thing we
> could not reuse the Male/Female codes so would have to use MALE/FEMALE or
> what have you.
>
> Any thoughts?
>
> Regards
> Bob
>
>
>