Hi Dapo,
I have put my comments on issue
4. Remove all associations between the org unit and data sets.
Please see the trail mail for the reference. hope this will help you.
Regards
Brajesh Murari
P please consider the environment before printing this email
On Friday, 4 April 2014 4:24 PM, Dapo Adejumo <dapo_adej...@yahoo.com> wrote:
Tricky issue – Discussed before. The problem is that the OU attributes that
should control this seem to conflict each other. For instance even if the
closed date is set / Registers Data set to No and datasets are allocated to the
OU – data will still be captured against this OU.
Lars, we may need to review the functionality of closing date for OUs and also
other relevant metadata like dataelements and indicators.
................................................
Regards,
Dapo Adejumo
+2348033683677
skype : dapojorge
From:Dhis2-users
[mailto:dhis2-users-bounces+dapo_adejumo=yahoo....@lists.launchpad.net] On
Behalf Of Lars Helge Øverland
Sent: 04 April 2014 10:38
To: Wilson,Randy
Cc: dhis2-us...@lists.launchpad.net; dhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-users] [Dhis2-devs] Inactive Organisation Unit
4. Remove all associations between the org unit and data sets.
I think association is one of the most oldest inherent feature provided in DHIS
development since DHIS 1,
Perhaps, in OOP methodology, association is week relationship and composition
is strong,
some thing like indicators indicating performance of services provided by
facility associated with
organizationunit represents weak relationship, but composition of dataset for
even a very small
new born organizationunit represents a strong relationship, it does't matter
new born organization
unit is still birth or live birth, reporting with attached dataset with reports
to their parent orgnaisationunits
or not but their association with datasets had been always supported by
various global health
governing system agencies and health systems in most of the developed and under
developed
countries round the globe. This implies that association is week and
composition is strong relationship.
But this does't implies that we should absolutely focused on compositions only,
and loses affirmative and associative services consumptions with other quality
functional multi-threaded, multi-cultural aspect oriented services consumption
provided by old historical attached organizationunit, may be some where on long
distance there would be concept and culture of lion's loosely coupled and weird
but clean relationship, where dataset composition design took-place only after
birth of new born organizationunit, and there could be a culture of multiple
times datasets association-dissociations with orgaisationunit and datasets and
several reforms in datasets hierarchical design.
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-us...@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
