chore: autopublish 2024-07-10T21:22:09Z

projects/dhis2-single-page-docs/am_ET/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:31Z
+2024-07-10T21:21:16Z

projects/dhis2-single-page-docs/ar/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:31Z
+2024-07-10T21:21:16Z

projects/dhis2-single-page-docs/cs/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:31Z
+2024-07-10T21:21:16Z

projects/dhis2-single-page-docs/es_419/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:32Z
+2024-07-10T21:21:17Z

projects/dhis2-single-page-docs/fr/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:33Z
+2024-07-10T21:21:17Z

projects/dhis2-single-page-docs/id_ID/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:33Z
+2024-07-10T21:21:18Z

projects/dhis2-single-page-docs/ko/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:34Z
+2024-07-10T21:21:18Z

projects/dhis2-single-page-docs/ko_KR/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:34Z
+2024-07-10T21:21:18Z

projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2022-03-10'
 tags:
-- DHIS core version 2.37
 - 사용
+- DHIS core version 2.37
 template: single.html
 ---
 

projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2023-02-20'
 tags:
-- DHIS core version 2.37
 - 사용
+- DHIS core version 2.37
 template: single.html
 ---
 

projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md

@@ -1,5 +1,5 @@
 ---
-revision_date: '2024-06-26'
+revision_date: '2024-07-04'
 tags:
 - 사용
 - DHIS core version 2.39
@@ -18901,19 +18901,32 @@ system.
     elements to be member of data sets with similar period types to have
     a defined behaviour.
 
-  - Period structure (\_dataperiodstructure)
+  - Date periods structure (\_dateperiodstructure)
 
     This table provides information about all periods and which period
     type they are associated with. For each period type with lower
     frequency than itself, it contains information about which period it
     will fall within.
 
+  - Periods structure (\_periodstructure)
+
+    Similar to `_dateperiodstructure`, containing a scoped set of
+    periods more adapted for aggregated analytics.
+    It's based on `period` and `periodtype` tables.
+
   - Data element category option combinations
     (\_dataelementcategoryoptioncombo)
 
     This table provides a mapping between data elements and all possible
     category option combinations.
 
+  - Data set organisation unit category (\_datasetorganisationunitcategory)
+
+    This table provides information related to data sets, organisation units
+    and its category option combinations associated. If no association is found,
+    it uses the default category option combo.
+
+
 ## Analytics tables management { #data_admin_analytics_tables }
 
 DHIS2 generates database tables which the system then uses as basis for
@@ -19004,7 +19017,6 @@ has been modified directly the application cache needs to be cleared for
 it to take effect.
 
 
-
 # Visualize usage statistics { #using_usage_analytics }
 
 ## About the Usage Analytics app { #about-the-usage-analytics-app } 

projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2024-06-26'
 tags:
-- DHIS core version 2.40
 - 사용
+- DHIS core version 2.40
 template: single.html
 ---
 

projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md

@@ -1,8 +1,8 @@
 ---
-revision_date: '2024-06-26'
+revision_date: '2024-07-04'
 tags:
-- DHIS core version 2.40
 - 사용
+- DHIS core version 2.40
 template: single.html
 ---
 
@@ -19097,19 +19097,32 @@ system.
     elements to be member of data sets with similar period types to have
     a defined behaviour.
 
-  - Period structure (\_dataperiodstructure)
+  - Date periods structure (\_dateperiodstructure)
 
     This table provides information about all periods and which period
     type they are associated with. For each period type with lower
     frequency than itself, it contains information about which period it
     will fall within.
 
+  - Periods structure (\_periodstructure)
+
+    Similar to `_dateperiodstructure`, containing a scoped set of
+    periods more adapted for aggregated analytics.
+    It's based on `period` and `periodtype` tables.
+
   - Data element category option combinations
     (\_dataelementcategoryoptioncombo)
 
     This table provides a mapping between data elements and all possible
     category option combinations.
 
+  - Data set organisation unit category (\_datasetorganisationunitcategory)
+
+    This table provides information related to data sets, organisation units
+    and its category option combinations associated. If no association is found,
+    it uses the default category option combo.
+
+
 ## Analytics tables management { #data_admin_analytics_tables }
 
 DHIS2 generates database tables which the system then uses as basis for
@@ -19200,7 +19213,6 @@ has been modified directly the application cache needs to be cleared for
 it to take effect.
 
 
-
 # Visualize usage statistics { #using_usage_analytics }
 
 ## About the Usage Analytics app { #about-the-usage-analytics-app } 

projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2024-06-26'
 tags:
-- DHIS core version master
 - 사용
+- DHIS core version master
 template: single.html
 ---
 

projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md

@@ -1,8 +1,8 @@
 ---
-revision_date: '2024-06-26'
+revision_date: '2024-07-04'
 tags:
-- DHIS core version master
 - 사용
+- DHIS core version master
 template: single.html
 ---
 
@@ -19144,7 +19144,7 @@ all data integrity issues are resolved. The resource tables are also
 generated automatically, every time the analytics process is run by the
 system.
 
-  - Organisation unit structure (\_orgunitstructure)
+  - Organisation unit structure (analytics_rs_orgunitstructure)
 
     This table should be regenerated any time there have been any
     changes made to the organisational unit hierarchy. This table
@@ -19153,62 +19153,75 @@ system.
     unit level and the organisation unit identifiers for all parents in
     the lineage as values.
 
-  - Data element group set structure (\_dataelementgroupsetstructure)
+  - Data element group set structure (analytics_rs_dataelementgroupsetstructure)
 
     This table provides information about which data elements are
     members of which data element group sets. The table has one row for
     each data element, one column for each data element group set and
     the names of the data element group as values.
 
-  - Indicator group set structure (\_indicatorgroupsetstructure)
+  - Indicator group set structure (analytics_rs_indicatorgroupsetstructure)
 
     This table provides information about which indicators are members
     of which indicator group sets. The table has one row for each
     indicator, one column for each indicator group set and the names of
     the indicator group as values.
 
   - Organisation unit group set structure
-    (\_organisationunitgroupsetstructure)
+    (analytics_rs_organisationunitgroupsetstructure)
 
     This table provides information about which organisation units are
     members of which organisation unit group sets. The table has one row
     for each organisation unit, one column for each organisation unit
     group set and the names of the organisation unit groups as values.
 
-  - Category structure (\_categorystructure)
+  - Category structure (analytics_rs_categorystructure)
 
     This table provides information about which data elements are
     members of which categories. The table has one row for each data
     element, one column for each category and the names of the category
     options as values.
 
-  - Data element category option combo name (\_categoryoptioncomboname)
+  - Data element category option combo name (analytics_rs_categoryoptioncomboname)
 
     This table should be regenerated any time there have been changes
     made to the category combination names. It contains readable names
     for the various combinations of categories.
 
-  - Data element structure (\_dataelementstructure)
+  - Data element structure (analytics_rs_dataelementstructure)
 
     This table provides information about all data elements and which
     period type (frequency) they capture data at. The period type is
     determined through the data set membership and hence relies on data
     elements to be member of data sets with similar period types to have
     a defined behaviour.
 
-  - Period structure (\_dataperiodstructure)
+  - Date periods structure (analytics_rs_dateperiodstructure)
 
     This table provides information about all periods and which period
     type they are associated with. For each period type with lower
     frequency than itself, it contains information about which period it
     will fall within.
 
+  - Periods structure (analytics_rs_periodstructure)
+
+    Similar to `analytics_rs_dateperiodstructure`, containing a scoped set of
+    periods more adapted for aggregated analytics.
+    It's based on `period` and `periodtype` tables.
+
   - Data element category option combinations
-    (\_dataelementcategoryoptioncombo)
+    (analytics_rs_dataelementcategoryoptioncombo)
 
     This table provides a mapping between data elements and all possible
     category option combinations.
 
+  - Data set organisation unit category (analytics_rs_datasetorganisationunitcategory)
+
+    This table provides information related to data sets, organisation units
+    and its category option combinations associated. If no association is found,
+    it uses the default category option combo.
+
+
 ## Analytics tables management { #data_admin_analytics_tables }
 
 DHIS2 generates database tables which the system then uses as basis for
@@ -19304,7 +19317,6 @@ has been modified directly the application cache needs to be cleared for
 it to take effect.
 
 
-
 # Visualize usage statistics { #using_usage_analytics }
 
 ## About the Usage Analytics app { #about-the-usage-analytics-app } 

projects/dhis2-single-page-docs/pt/.cache_timestamp

@@ -1 +1 @@
-2024-07-09T21:21:34Z
+2024-07-10T21:21:26Z

projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2023-01-13'
 tags:
-- DHIS core version 2.37
 - Desenvolver
+- DHIS core version 2.37
 template: single.html
 ---
 

projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2024-07-02'
 tags:
-- Desenvolver
 - DHIS core version 2.39
+- Desenvolver
 template: single.html
 ---
 

projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2024-07-02'
 tags:
-- Desenvolver
 - DHIS core version 2.40
+- Desenvolver
 template: single.html
 ---
 

projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md

@@ -1,5 +1,5 @@
 ---
-revision_date: '2024-07-02'
+revision_date: '2024-07-08'
 tags:
 - DHIS core version master
 - Desenvolver
@@ -20671,7 +20671,8 @@ Organisation units are one of the most fundamental objects in DHIS2. They define
 which a user is allowed to record and/or read data. There are three types of organisation units that
 can be assigned to a user. These are data capture, data view (not used in tracker), and tracker
 search. As the name implies, these organisation units define a scope under which a user is allowed
-to conduct the respective operations.
+to conduct the respective operations. A user can search for data in their search scope and capture 
+scope organisation units.
 
 However, to further fine-tune the scope, DHIS2 Tracker introduces a concept that we call
 **OrganisationUnitSelectionMode**. Such a mode is often used at the time exporting tracker objects.
@@ -20747,14 +20748,19 @@ falls under the user's organisation unit scope (Search/Capture). For Programs th
 with access level  *OPEN* or *AUDITED* , the Owner OrganisationUnit has to be in the user's search
 scope. For Programs that are configured with access level  *PROTECTED* or *CLOSED* , the Owner
 OrganisationUnit has to be in the user's capture scope to be able to access the corresponding
-program data for the specific tracked entity. Irrespective of the program access level, to access
-Tracker objects, the requested organisation unit must always be within the user's search scope. A
-user cannot request objects outside its search scope unless it's using the organisation unit mode
-ALL and has enough privileges to use that mode.
-
-When requesting tracked entities without specifying a program, the response will include only tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and one of the following criteria:
-- The tracked entity is enrolled in at least one program the user has data access to, and the user has access to the owner organisation unit.
-- The tracked entity is not enrolled in any program the user has data access to, but the user has access to the tracked entity registering organisation unit.
+program data for the specific tracked entity. Irrespective of the program access level, to access 
+Tracker objects, the requested organisation unit must always be within either the user's search 
+scope or capture scope. A user cannot request objects outside these two scopes unless they are 
+using the organisation unit mode ALL and have sufficient privileges to use that mode.
+
+When requesting tracked entities without specifying a program, the response will include only 
+tracked entities that satisfy [metadata sharing settings](#webapi_tracker_metadata_sharing) and 
+one of the following criteria:
+
+* The tracked entity is enrolled in at least one program the user has data access to, and the user
+ has access to the owner organisation unit.
+* The tracked entity is not enrolled in any program the user has data access to, but the user has
+ access to the tracked entity registering organisation unit.
 
 #### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override }
 

projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2023-03-22'
 tags:
-- DHIS core version 2.37
 - Gerir
+- DHIS core version 2.37
 template: single.html
 ---
 

projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md

@@ -1,8 +1,8 @@
 ---
 revision_date: '2024-02-16'
 tags:
-- Gerir
 - DHIS core version 2.39
+- Gerir
 template: single.html
 ---