dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

2011/9/26 Bob Jolliffe <bobjolliffe@xxxxxxxxx>

> I think maybe its really a UI paradigm twist ...
>
> Currently we only add orgunits to groups in the orgunitgroup editor.
> What we need, in the orgunit edit screen, is to show the
> orgunitgroupsets (attributes) and their corresponding groups (values)
> and have the means to change the value from there.  This will then
> have the same 'look and feel' as editing attributes.
>

We actually allow the users to select groups per group set in the edit
orgunit window today, at least for the two standard group sets "Type" and
"Ownership", so this change is not so radical.
If we can add additional group sets in there dynamically, then I guess we
have what you suggest.

What we still need is the ability to batch assign orgunits to groups like we
have in the edit group today, since no one wants to add 8000 facilities to a
type by opening the edit orgunit window for 8000 orgunits....

Ola
--------


>
> This should also simplify the attribute code as dealing with the coded
> attribute special case seemed a bit awkward.
>
> On 26/09/2011, Lars Helge Øverland <larshelge@xxxxxxxxx> wrote:
> >> How is a coded attribute different from a groupset?  From a
> >> dimensionality perspective they realy seem completely identical to me.
> >>  So should we drop groupsets?  Or implement coded attributes as
> >> groupsets?
> >>
> >
> > Seems you are right. AttributeOption=Group and Attribute=GroupSet.
> > Don't think we want to remove group sets but it seems redundant to
> > have both.
> >
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>