dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #27292
[Branch ~dhis2-documenters/dhis2/dhis2-docbook-docs] Rev 939: Minor
------------------------------------------------------------
revno: 939
committer: Lars Helge Øverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Fri 2014-01-03 15:22:28 +0100
message:
Minor
modified:
src/docbkx/en/dhis2_user_man_approving_data.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_approving_data.xml'
--- src/docbkx/en/dhis2_user_man_approving_data.xml 2013-12-30 10:26:28 +0000
+++ src/docbkx/en/dhis2_user_man_approving_data.xml 2014-01-03 14:22:28 +0000
@@ -5,6 +5,9 @@
<title>Data approval</title>
<para>DHIS 2 has an optional feature that allows authorized users to approve data that has been entered. It allows data to be reviewed and approved at each level in the organisation unit hierarchy, so the approval follows the structure of the hierarchy from lower levels to higher levels.</para>
<para>Data may be approved for each combination of (a) data set, (b) period and (c) organisation unit. Data may be approved for the organisation unit for which it is entered, as well as for higher-level organisation units to which the data is aggregated. It can be approved for a higher-level organisation unit only after it has been approved for all that organisation unit's children for the same data set and period.</para>
+ <para>After a data set, period and organiasation unit combination has been approved, the form will
+ be locked and any further data entry or modification will be prohibited, unless it is later
+ un-approved.</para>
<para>For example, the following diagram illustrates that data has already been approved for organisation units C and D, for a given data set and period. It may now be approved for organisation unit B for the same data set and period. But it is not ready to be approved for organization unit A. Before it can be approved for organisation unit A, it must be approved for B, and for any other children of organisation unit A, for that data set and period.</para>
<figure>
<title>Approving at organisation units</title>