dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #21489
[Branch ~dhis2-documenters/dhis2/dhis2-docbook-docs] Rev 685: Minor
------------------------------------------------------------
revno: 685
committer: Lars Helge Øverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Wed 2013-03-13 14:12:35 +0100
message:
Minor
modified:
src/docbkx/en/dhis2_user_man_sharing.xml
--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs
Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription
=== modified file 'src/docbkx/en/dhis2_user_man_sharing.xml'
--- src/docbkx/en/dhis2_user_man_sharing.xml 2013-03-13 12:39:05 +0000
+++ src/docbkx/en/dhis2_user_man_sharing.xml 2013-03-13 13:12:35 +0000
@@ -63,9 +63,9 @@
<title>Sharing applied</title>
<para>The sharing functionality is useful in several scenarios. One use-case is setting up a
DHIS instance for a global organisation with operations in multiple countries. Typically the
- organisation has a set global indicators and reports which should apply to all countries,
- while all countries will have the need for country-specific indicators and reports. In this
- scenario the following approach could work: </para>
+ organisation has a set of global data sets, indicators and reports which should apply to all
+ countries, while all countries will have the need for country-specific data sets, indicators
+ and reports. In this scenario the following approach could work: </para>
<itemizedlist>
<listitem>
<para>Set up one user group for global personell.</para>
@@ -74,20 +74,28 @@
<para>Set up a user group for personell in each country.</para>
</listitem>
<listitem>
- <para>Create global indicators and reports, make them viewable for everyone and editable for
+ <para>Create global data sets and reports, make them viewable for everyone and editable for
the global user group only.</para>
</listitem>
<listitem>
- <para>Create country-specific indicators and reports, make them viewable and editable for
- the country user group and the global user group.</para>
+ <para>Create country-specific data sets and reports, make them viewable and editable for the
+ country user group and the global user group only.</para>
</listitem>
</itemizedlist>
<para>This way, the global indicators and reports could be viewed and analysed by everyone, but
- maintained by the global user group only. The country-specific indicators and reports could be
- viewed and maintained by the country and global personell, without being visible or impacting
- the system for other countries in the organisation.</para>
+ maintained by the global user group only. The country-specific data sets, indicators and
+ reports could be viewed and maintained by the country and global personell, without being
+ visible or impacting the system for other countries in the organisation.</para>
<para>A similar approach could work for a scenario with a donor, multiple funding agencies and
implemeting partners in a country, where user groups could be set up for each of those
entities.</para>
+ <para>Another use-case is a country department of health with multiple health programs.
+ Typically there is a need for having general reports and charts for the department while
+ allowing the health programs to develop specific reports and charts for internal. This can be
+ achieved by creating user groups for each health program. Later, when developing reports and
+ charts, these can be made viewable and editable to the program user group only. This way the
+ reports will not be visible to other programs and users. This is benecifial because the
+ reports are kept internal to the program and because the visible list of reports of other
+ users are kept shorter and more relevant.</para>
</section>
</chapter>