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.
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 <[email protected]> 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 : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
