dhis2-devs team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 1054
committer: Lars Helge Øverland <larshelge@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Fri 2014-04-25 15:08:46 +0200
message:
  User docs
modified:
  src/docbkx/en/dhis2_user_man_user_management.xml
  src/docbkx/en/dhis2_user_man_web_api.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_user_management.xml'
--- src/docbkx/en/dhis2_user_man_user_management.xml	2014-04-24 16:11:08 +0000
+++ src/docbkx/en/dhis2_user_man_user_management.xml	2014-04-25 13:08:46 +0000
@@ -146,13 +146,15 @@
         </listitem>
         <listitem>
           <para>Users can be assigned to any number of data view organisation units. This controls
-            which organisation units the user can view aggregated data for in analysis modules. Giving access
-            to an organisation unit implicitly gives access to all organisation unit below it in the organisation unit
-            hierarchy.</para>
-          <para>In order for users to be able to enter data for specific organisation units, they
-            must be assigned these units. If a user is responsible for entering data for all
-            facilities for a given district, they should typically be assigned the district, and all
-            of the facilities contained within the district.</para>
+            which organisation units the user can view aggregated data for in analysis modules.
+            Giving access to an organisation unit implicitly gives access to all organisation unit
+            below it in the organisation unit hierarchy. Note that data view organisation units are
+            optional. If you do not specify any, the user will have access to the full organisation
+            unit hierarchy for viewing aggregated data.</para>
+          <para>In several places in the analysis modules one can select "user organisation unit"
+            for the organisation unit dimension. This mechanism will first attempt to use the data
+            view organisation units linked to the current user. If not found, it will use the data
+            capture organisation units.</para>
           <screenshot>
             <screeninfo>User management screen</screeninfo>
             <mediaobject>

=== modified file 'src/docbkx/en/dhis2_user_man_web_api.xml'
--- src/docbkx/en/dhis2_user_man_web_api.xml	2014-04-22 14:58:33 +0000
+++ src/docbkx/en/dhis2_user_man_web_api.xml	2014-04-25 13:08:46 +0000
@@ -4511,7 +4511,7 @@
       include a program query parameter like this:</para>
     <screen>api/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&amp;ou=O6uvpzGd5pu&amp;ouMode=DESCENDANTS&amp;program=ur1Edk5Oe2n</screen>
       <para>To specify program enrollment dates as part of the query you can use this syntax:</para>
-      <screen>api/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&amp;ou=O6uvpzGd5pu&amp;program=ur1Edk5Oe2n&amp;programStartDate=2013-01-01&amp;programEndDate=013-09-01</screen>
+      <screen>api/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&amp;ou=O6uvpzGd5pu&amp;program=ur1Edk5Oe2n&amp;programStartDate=2013-01-01&amp;programEndDate=2013-09-01</screen>
     <para>To constrain the response to instances of a specific tracked entity you can include a
       tracked entity query parameter like this:</para>
     <screen>api/trackedEntityInstances.json?attribute=zHXD5Ve1Efw:EQ:A&amp;ou=O6uvpzGd5pu&amp;ouMode=DESCENDANTS&amp;trackedEntity=cyl5vuJ5ETQ</screen>