dhis2-users team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

I think (semantically) the correct way is to create a new "Unknown"
option, though it should have a different code and uid from other
unknowns.  The displayed label just happens to be the same but the
underlying concept is different.  That is, they actually represent the
likes of "Unknown age", "Unknown test result", "Unknown sex" etc.
Despite sharing the same text label, they are really quite different
options.

There is a similar issue we have grappled with
categories/categoryOptions which is resolved in a different (also
slightly unsatisfactory) way.

My longer term view is that options should be able to be reused in
different optionsets, but not in a completely free manner.

There is some experience of the problem outside of dhis2 and I believe
the established consensus is that
(i)  codes/options in a controlled vocabulary are contained in a code
list.  Every item in that list should be uniquely identifiable.
(ii)  these items should relate to a specific concept (age, disease,
test result etc)
(ii)  value sets (such as categories and optionsets in dhis2) should
be selected from one and only one codelist.  There can be any number
of valuesets for any one codelist.  This allows for reuse of items but
disallows a valueset with mixed concepts (ie you couldn't construct an
optionset containing 'Malaria','Male','under5','Unknown')

If we do get to re-examine our model in this area, this is the
approach I would advocate.



On 23 May 2016 at 12:35, Lars Helge Øverland <lars@xxxxxxxxx> wrote:
> Hi Lise,
>
> at the moment you must create a new "Unknown" option. You can give it the
> same name and code though as the other Unknowns. The uid will be different.
>
> It is debatable whether this is the right way. We are considering whether to
> change the design to allow for re-use of options.
>
> regards,
>
> Lars
>
>
> On Sun, May 22, 2016 at 6:50 PM, GROUT, Lise <groutl@xxxxxxx> wrote:
>>
>> Dear Markus and Prosper,
>>
>>
>>
>> Thank you for your help!
>>
>>
>>
>> So if I understand correctly, I have to create different options (with
>> different UID and codes) but I can reuse the same option name?
>>
>>
>>
>> Thank you!
>>
>>
>>
>> Lise.
>>
>>
>>
>> From: Prosper BT [mailto:ptb3000@xxxxxxxxx]
>> Sent: 22 May 2016 18:11
>> To: GROUT, Lise; dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Dhis2-users] Option, option set and dataelement
>>
>>
>>
>> Dear Lise
>>
>>
>>
>> We don't have uniqueness in options across different option sets. So it's
>> possible to use same options names in different options sets.
>>
>>
>>
>> Regards
>>
>>  22, 2016, 6:51 PM GROUT, Lise <groutl@xxxxxxx> wrote:
>>
>> Dear all,
>>
>>
>>
>> Sorry for this basic question but I prefer to ask for confirmation.
>>
>>
>>
>> Can we use the same option in different option sets (for example
>> positive/negative in different option Sets) and the same option sets in
>> different dataelements (for example the option sets results for different
>> tests)?
>>
>>
>>
>> Thanks!
>>
>>
>>
>> Lise.
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> lars@xxxxxxxxx
> http://www.dhis2.org
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>