I am not sure if this is the normal behaviour, but seems that Organisation Units do not inherit their ancestors Organisation Unit Groups. In our case, most of the data belongs to leaf instances of our Organisation Units Tree. Therefore, those terminal Organisation Units had to belong to all their ancestors Organisation Unit Groups in order to use those groups as analysis dimensions. Is that correct?
Thanks in advance,
Octavio.
Hi all,
Hi,
It’s true that there is no inheritance (which makes sense if for example you want to make a group like “Districts”). You have to explicitly include every OrgUnit.
What could be quite useful for a case like yours, is to be able to select all children in one go when you assign orgunits to a group. Sounds like a Blueprint to me.
On Fri, Feb 6, 2015 at 4:55 PM, Octavio GLORIO Octavio.GLORIO@barcelona.msf.org wrote:
I am not sure if this is the normal behaviour, but seems that Organisation Units do not inherit their ancestors Organisation Unit Groups. In our case, most of the data belongs to leaf instances of our Organisation Units Tree. Therefore, those terminal Organisation Units had to belong to all their ancestors Organisation Unit Groups in order to use those groups as analysis dimensions. Is that correct?
Thanks in advance,
Octavio.
Hi all,
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar
Oops - I just checked now, and we already have the Select Children button…
On Fri, Feb 6, 2015 at 4:59 PM, Knut Staring knutst@gmail.com wrote:
Hi,
It’s true that there is no inheritance (which makes sense if for example you want to make a group like “Districts”). You have to explicitly include every OrgUnit.
What could be quite useful for a case like yours, is to be able to select all children in one go when you assign orgunits to a group. Sounds like a Blueprint to me.
–
On Fri, Feb 6, 2015 at 4:55 PM, Octavio GLORIO Octavio.GLORIO@barcelona.msf.org wrote:
I am not sure if this is the normal behaviour, but seems that Organisation Units do not inherit their ancestors Organisation Unit Groups. In our case, most of the data belongs to leaf instances of our Organisation Units Tree. Therefore, those terminal Organisation Units had to belong to all their ancestors Organisation Unit Groups in order to use those groups as analysis dimensions. Is that correct?
Thanks in advance,
Octavio.
Hi all,
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar
–
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar
Hi, Thank you for the quick response. We are currently deploying an automatic process for historic data migration. There, our terminal org units are created on demand (because they correspond to services). Therefore, we will have to get ancestors groups and update them.
cheers,
octavio.
Para: Octavio GLORIO Octavio.GLORIO@barcelona.msf.org
De: Knut Staring knutst@gmail.com
Fecha: 06/02/2015 16:59
cc: dhis2-users dhis2-users@lists.launchpad.net
Asunto: Re: [Dhis2-users] Organisation Unit Groups inheritanceHi,
It’s true that there is no inheritance (which makes sense if for example you want to make a group like “Districts”). You have to explicitly include every OrgUnit.
What could be quite useful for a case like yours, is to be able to select all children in one go when you assign orgunits to a group. Sounds like a Blueprint to me.
-----Knut Staring knutst@gmail.com escribió: -----
On Fri, Feb 6, 2015 at 4:55 PM, Octavio GLORIO Octavio.GLORIO@barcelona.msf.org wrote:
I am not sure if this is the normal behaviour, but seems that Organisation Units do not inherit their ancestors Organisation Unit Groups. In our case, most of the data belongs to leaf instances of our Organisation Units Tree. Therefore, those terminal Organisation Units had to belong to all their ancestors Organisation Unit Groups in order to use those groups as analysis dimensions. Is that correct?
Thanks in advance,
Octavio.
Hi all,
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar
Right - so I guess you would have loved it if the WebAPI would automatically assign the orgunit groups of the ancestors - and not just the immediate parent, rather all groups for all levels?
I suppose the WebAPI could be extended to have a YES/NO parameter for this, just wondering if it is a sufficiently general requirement.
Knut
On Fri, Feb 6, 2015 at 5:12 PM, Octavio GLORIO Octavio.GLORIO@barcelona.msf.org wrote:
Hi, Thank you for the quick response. We are currently deploying an automatic process for historic data migration. There, our terminal org units are created on demand (because they correspond to services). Therefore, we will have to get ancestors groups and update them.
cheers,
octavio.
Para: Octavio GLORIO Octavio.GLORIO@barcelona.msf.org
De: Knut Staring knutst@gmail.com
Fecha: 06/02/2015 16:59
cc: dhis2-users dhis2-users@lists.launchpad.net
Asunto: Re: [Dhis2-users] Organisation Unit Groups inheritanceHi,
It’s true that there is no inheritance (which makes sense if for example you want to make a group like “Districts”). You have to explicitly include every OrgUnit.
What could be quite useful for a case like yours, is to be able to select all children in one go when you assign orgunits to a group. Sounds like a Blueprint to me.
-----Knut Staring knutst@gmail.com escribió: -----
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
On Fri, Feb 6, 2015 at 4:55 PM, Octavio GLORIO Octavio.GLORIO@barcelona.msf.org wrote:
I am not sure if this is the normal behaviour, but seems that Organisation Units do not inherit their ancestors Organisation Unit Groups. In our case, most of the data belongs to leaf instances of our Organisation Units Tree. Therefore, those terminal Organisation Units had to belong to all their ancestors Organisation Unit Groups in order to use those groups as analysis dimensions. Is that correct?
Thanks in advance,
Octavio.
Hi all,
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar
Hi Knut,
You are right, had to be a really nice nice feature having a “inherit ancestors groups” flag. Indeed, maybe have some sense considering the inheritance property assigned to the org units groups directly.
Anyway, will be really great to hear some news around this.
cheers,
octavio.
Para: Octavio GLORIO Octavio.GLORIO@barcelona.msf.org
De: Knut Staring knutst@gmail.com
Fecha: 06/02/2015 17:34
cc: dhis2-users dhis2-users@lists.launchpad.net
Asunto: Re: [Dhis2-users] Organisation Unit Groups inheritanceRight - so I guess you would have loved it if the WebAPI would automatically assign the orgunit groups of the ancestors - and not just the immediate parent, rather all groups for all levels?
I suppose the WebAPI could be extended to have a YES/NO parameter for this, just wondering if it is a sufficiently general requirement.
Knut
-----Knut Staring knutst@gmail.com escribió: -----
On Fri, Feb 6, 2015 at 5:12 PM, Octavio GLORIO Octavio.GLORIO@barcelona.msf.org wrote:
Hi, Thank you for the quick response. We are currently deploying an automatic process for historic data migration. There, our terminal org units are created on demand (because they correspond to services). Therefore, we will have to get ancestors groups and update them.
cheers,
octavio.
Para: Octavio GLORIO Octavio.GLORIO@barcelona.msf.org
De: Knut Staring knutst@gmail.com
Fecha: 06/02/2015 16:59
cc: dhis2-users dhis2-users@lists.launchpad.net
Asunto: Re: [Dhis2-users] Organisation Unit Groups inheritanceHi,
It’s true that there is no inheritance (which makes sense if for example you want to make a group like “Districts”). You have to explicitly include every OrgUnit.
What could be quite useful for a case like yours, is to be able to select all children in one go when you assign orgunits to a group. Sounds like a Blueprint to me.
-----Knut Staring knutst@gmail.com escribió: -----
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
On Fri, Feb 6, 2015 at 4:55 PM, Octavio GLORIO Octavio.GLORIO@barcelona.msf.org wrote:
I am not sure if this is the normal behaviour, but seems that Organisation Units do not inherit their ancestors Organisation Unit Groups. In our case, most of the data belongs to leaf instances of our Organisation Units Tree. Therefore, those terminal Organisation Units had to belong to all their ancestors Organisation Unit Groups in order to use those groups as analysis dimensions. Is that correct?
Thanks in advance,
Octavio.
Hi all,
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar
Knut Staring
Dept. of Informatics, University of Oslo
Norway: +4791880522
Skype: knutstar