Hi Bram, yup I see your point and some times I am sure it's useful. Personally I still think its a bad idea, as you easily get into trouble later. In terms of design we are saying that groups are for output/analysis, and data set for data input/capture. So the moment an org unit should belong to a group for analysis (e.g. "CHC") but for some reason should not capture one data set, then you have a conflict / mix of concern...
cheers Lars On Fri, Jul 25, 2014 at 4:15 PM, Bram Piot <[email protected]> wrote: > Hi Lars, > > I can see that this option is confusing to some, but it's very useful to > others so please reconsider removing it - let me explain: in settings with > highly dynamic org units (i.e. new org units are being added on a regular > basis), assigning a data set or a program to one or more org unit groups is > much more efficient and less error-prone than assigning it to org units > directly. When based on groups, one doesn't need to assign the data set or > program to the new org units as the they are automatically included, > provided of course that the new org units are part of the appropriate > group(s). > > Maybe an alternative would be to give the option to assign either directly > to org units, or to groups, but not both at the same time as is currently > the case? > > Are others using the assignment by org unit group or are we (PSI) the only > ones? > > Thanks, > > bram > > > > On 25 July 2014 15:26, Lars Helge Øverland <[email protected]> wrote: > >> >> >> >> On Fri, Jul 25, 2014 at 3:18 PM, Knut Staring <[email protected]> wrote: >> >>> Thanks, I actually had tried that with no effect - but by sheer >>> coincindence, I discovered what was the matter today: >>> >>> I was going to change the icon for an OU group, and noticed that the >>> forms I wanted to get rid of had been assigned to several OU groups (one of >>> which contained most of the OUs in the system). So this functionality is >>> independent of and overriding the dataset assignment - and the result can >>> be very confusing (I spent at least a day trying to fix this issue in the >>> db via other means). >>> >> >> Yes I think that was a bad idea in the first place, we have a blueprint >> to remove it here: >> >> >> https://blueprints.launchpad.net/dhis2/+spec/remove-dataset-orgunit-group-assignments >> >> >> >>> >>> Glad to have finally resolved the issue - but also have a similar issue >>> with sharing: Everything (e.g. maps and PT favorites) are accessible to >>> everyone even though I try to restrict to certain user groups. >>> >>> Knut >>> >>> >>> On Friday, July 25, 2014, Lars Helge Øverland <[email protected]> >>> wrote: >>> >>>> That is hard to say, try deleting the contents from datasetsource and >>>> try again. >>>> >>>> Lars >>>> >>>> >>>> >>>> On Fri, Jul 25, 2014 at 2:41 AM, Knut Staring <[email protected]> wrote: >>>> >>>>> Right, but would you have any idea what causes my problem with dataset >>>>> assignment and how to fix it? >>>>> On Jul 25, 2014 2:16 AM, "Lars Helge Øverland" <[email protected]> >>>>> wrote: >>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Jul 24, 2014 at 7:53 PM, Knut Staring <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> One method to do this is to export the datasets to XML, delete them, >>>>>>> and then reimport. >>>>>>> >>>>>>> This worked well for 3 of my forms, but when trying to Remove the >>>>>>> last form, I got the message below, which I found surprising, since I >>>>>>> didn't think there were any associations between MapViews and Datasets? >>>>>>> >>>>>>> Object not deleted because it is associated by objects of type >>>>>>> MapView >>>>>>> >>>>>> >>>>>> You can render reporting rates for data sets in GIS, hence the >>>>>> MapView > DataSet association. >>>>>> >>>>>> Lars >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Jul 24, 2014 at 7:07 PM, Knut Staring <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> In my 2.15 db my existing forms show up in data entry for all OUs >>>>>>>> even though I've tried to restrict them to just level 4 (they had >>>>>>>> previously been assigned to all OUs by mistake). The >>>>>>>> restriction/assignment >>>>>>>> works for new datasets, but not for the existing ones. >>>>>>>> >>>>>>>> How can make sure the exisiting forms only show up for the OUs in >>>>>>>> the datasetsource table? >>>>>>>> >>>>>>>> -- >>>>>>>> Knut Staring >>>>>>>> Dept. of Informatics, University of Oslo >>>>>>>> +4791880522 >>>>>>>> http://dhis2.org >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Knut Staring >>>>>>> Dept. of Informatics, University of Oslo >>>>>>> +4791880522 >>>>>>> http://dhis2.org >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Mailing list: https://launchpad.net/~dhis2-users >>>>>>> Post to : [email protected] >>>>>>> Unsubscribe : https://launchpad.net/~dhis2-users >>>>>>> More help : https://help.launchpad.net/ListHelp >>>>>>> >>>>>>> >>>>>> >>>> >>> >>> -- >>> Knut Staring >>> Dept. of Informatics, University of Oslo >>> +4791880522 >>> http://dhis2.org >>> >>> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~dhis2-users >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~dhis2-users >> More help : https://help.launchpad.net/ListHelp >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
