From c4f2cf276eee5812998b3d0f94be7371b728c981 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Tue, 4 Jun 2024 21:28:47 +0000 Subject: [PATCH] chore: autopublish 2024-06-04T21:28:45Z --- .../am_ET/.cache_timestamp | 2 +- .../ar/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 3064 +------------- .../cs/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 3046 +------------- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-239__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../es_419/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 3064 +------------- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-239__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../fr/.cache_timestamp | 2 +- ...FERENCE__DHIS-CORE-VERSION-232__web-api-md | 136 +- ...FERENCE__DHIS-CORE-VERSION-233__web-api-md | 264 +- ...FERENCE__DHIS-CORE-VERSION-234__web-api-md | 286 +- ...FERENCE__DHIS-CORE-VERSION-235__web-api-md | 288 +- ...ENCE__DHIS-CORE-VERSION-MASTER__web-api-md | 322 +- ...DHIS-CORE-VERSION-233__developer-manual-md | 264 +- ...DHIS-CORE-VERSION-234__developer-manual-md | 28 +- ...DHIS-CORE-VERSION-235__developer-manual-md | 30 +- ...DHIS-CORE-VERSION-236__developer-manual-md | 30 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 410 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 432 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 521 ++- ...DHIS-CORE-VERSION-240__developer-manual-md | 525 ++- ...S-CORE-VERSION-MASTER__developer-manual-md | 3584 ++--------------- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-239__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../id_ID/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 3064 +------------- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-239__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../ko/.cache_timestamp | 2 +- .../ko_KR/.cache_timestamp | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../pt/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 3065 +------------- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-239__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../ru/.cache_timestamp | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../si/.cache_timestamp | 2 +- .../ur_PK/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 3064 +------------- ...ERSION-237__system-administration-guide-md | 2 +- ...ERSION-239__system-administration-guide-md | 2 +- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../zh/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 3063 +------------- ...ION-MASTER__system-administration-guide-md | 2 +- ...CORE-VERSION-237__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-237__dhis2-user-manual-md | 2 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 2 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 2 +- .../zh_CN/.cache_timestamp | 2 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-238__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-239__developer-manual-md | 2 +- ...DHIS-CORE-VERSION-240__developer-manual-md | 2 +- ...S-CORE-VERSION-MASTER__developer-manual-md | 3064 +------------- .../zh_TW/.cache_timestamp | 2 +- projects/docs-full-site/ar/.cache_timestamp | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__analytics-md | 8 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...SION-MASTER__settings-and-configuration-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 347 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- projects/docs-full-site/cs/.cache_timestamp | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__analytics-md | 8 +- ...THE-API__DHIS-CORE-VERSION-MASTER__apps-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-approval-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-entry-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__data-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-store-md | 2 +- ...IS-CORE-VERSION-MASTER__data-validation-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__event-hooks-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__i18n-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__introduction-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__maintenance-md | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__messaging-md | 2 +- ...DHIS-CORE-VERSION-MASTER__metadata-gist-md | 2 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 2 +- ...S-CORE-VERSION-MASTER__org-unit-profile-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__route-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__scheduling-md | 2 +- ...SION-MASTER__settings-and-configuration-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__sharing-md | 2 +- ...-THE-API__DHIS-CORE-VERSION-MASTER__sms-md | 2 +- ...IS-CORE-VERSION-MASTER__synchronization-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 347 +- ...HE-API__DHIS-CORE-VERSION-MASTER__users-md | 2 +- ...HIS-CORE-VERSION-MASTER__visualizations-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-239__audit-md | 2 +- ...ON__DHIS-CORE-VERSION-239__installation-md | 2 +- ...ATION__DHIS-CORE-VERSION-239__upgrading-md | 2 +- ...N-239__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-240__audit-md | 2 +- ...-VERSION-240__debugging-as-another-user-md | 2 +- ...ON__DHIS-CORE-VERSION-240__installation-md | 2 +- ...TION__DHIS-CORE-VERSION-240__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-240__upgrading-md | 2 +- ...N-240__using-gateways-for-sms-reporting-md | 2 +- ...RATION__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...RSION-MASTER__debugging-as-another-user-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__installation-md | 2 +- ...N__DHIS-CORE-VERSION-MASTER__monitoring-md | 2 +- ...ON__DHIS-CORE-VERSION-MASTER__upgrading-md | 2 +- ...ASTER__using-gateways-for-sms-reporting-md | 2 +- ...10__DASHBOARD-AND-DEMO-SERVER__browsing-md | 2 +- ...DASHBOARD-AND-DEMO-SERVER__introduction-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-planning-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-tracking-md | 2 +- ...LLATION-AND-CONFIGURATION__installation-md | 2 +- ...ALLATION-AND-CONFIGURATION__maintenance-md | 2 +- ...-AND-USAGE__analysis-and-interpretation-md | 2 +- ...NTRODUCTION-AND-USAGE__app-architecture-md | 2 +- ...RODUCTION-AND-USAGE__dashboard-and-demo-md | 2 +- ...RODUCTION-AND-USAGE__navigating-the-app-md | 2 +- ...ION-AND-USAGE__visualization-operations-md | 2 +- ...ER-IMPLEMENTATION__adopting-the-bna-app-md | 2 +- ..._USER-IMPLEMENTATION__capacity-building-md | 2 +- ..._USER-IMPLEMENTATION__end-user-training-md | 2 +- ...IMPLEMENTATION__implementation-overview-md | 2 +- ...ER-IMPLEMENTATION__integration-concepts-md | 2 +- ...MENTATION__opportunities-and-challenges-md | 2 +- ...IMPLEMENTATION__planning-and-organising-md | 2 +- ...USER-IMPLEMENTATION__setting-up-the-app-md | 2 +- ...ER-IMPLEMENTATION__support-and-scale-up-md | 2 +- ...22__USER-IMPLEMENTATION__sustainability-md | 2 +- ..._APP-VERSION-140__CONFIGURATION__access-md | 2 +- ...erventions-and-indicators-configuration-md | 2 +- ...N-140__CONFIGURATION__map-configuration-md | 2 +- ...VERSION-140__INSTALLATION__installation-md | 2 +- ...ION-140__INTRODUCTION__about-this-guide-md | 2 +- ...-140__INTRODUCTION__introduction-to-bna-md | 2 +- ..._USAGE__bna-analysis-and-interpretation-md | 2 +- ...APP__APP-VERSION-140__USAGE__bna-layout-md | 2 +- ...__APP-VERSION-140__USAGE__data-analysis-md | 2 +- ...S-APP__APP-VERSION-140__USAGE__map-view-md | 2 +- ...__immunization-analysis-app-user-manual-md | 2 +- ...-APP__APP-VERSION-250__about-this-guide-md | 2 +- ...0__accessing-and-transilating-scorecard-md | 2 +- ...CORECARD-APP__APP-VERSION-250__browsing-md | 2 +- ...PP__APP-VERSION-250__creating-scorecard-md | 2 +- ...-250__introduction-to-the-scorecard-app-md | 2 +- ..._APP-VERSION-250__saving-configurations-md | 2 +- ...VERSION-250__scorecard-app-architecture-md | 2 +- ...ON-250__support-and-maintenance-options-md | 2 +- ...APP__APP-VERSION-250__viewing-scorecard-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...APP-DEMO__architecture-and-installation-md | 2 +- ...ALONE-ACTION-TRACKER-APP-DEMO__browsing-md | 2 +- ...E-ACTION-TRACKER-APP-DEMO__introduction-md | 2 +- ...ON-TRACKER-CONFIGURATION__configuration-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-238__ANALYSING-DATA__dashboards-md | 2 +- ...ON-238__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-238__ANALYSING-DATA__event-reports-md | 2 +- ...N-238__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-238__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-238__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-238__ANALYSING-DATA__reports-md | 2 +- ...ION-238__APPROVING-DATA__approving-data-md | 2 +- ...SION-238__APPROVING-DATA__data-approval-md | 2 +- ...ERSION-238__COLLECTING-DATA__data-entry-md | 2 +- ...SION-238__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-238__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-238__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...SION-238__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-238__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...238__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...8__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...VERSION-239__ANALYSING-DATA__dashboards-md | 2 +- ...ON-239__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-239__ANALYSING-DATA__event-reports-md | 2 +- ...N-239__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-239__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-239__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-239__ANALYSING-DATA__reports-md | 2 +- ...ION-239__APPROVING-DATA__approving-data-md | 2 +- ...SION-239__APPROVING-DATA__data-approval-md | 2 +- ...N-239__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-239__COLLECTING-DATA__data-entry-md | 2 +- ...SION-239__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-239__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-239__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-239__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...239__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-240__ANALYSING-DATA__dashboards-md | 2 +- ...ON-240__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-240__ANALYSING-DATA__event-reports-md | 2 +- ...N-240__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-240__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-240__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-240__ANALYSING-DATA__reports-md | 2 +- ...ION-240__APPROVING-DATA__approving-data-md | 2 +- ...SION-240__APPROVING-DATA__data-approval-md | 2 +- ...N-240__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-240__COLLECTING-DATA__data-entry-md | 2 +- ...SION-240__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-240__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-240__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-240__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-240__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-240__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...240__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- .../docs-full-site/es_419/.cache_timestamp | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__analytics-md | 8 +- ...THE-API__DHIS-CORE-VERSION-MASTER__apps-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-approval-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-entry-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__data-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-store-md | 2 +- ...IS-CORE-VERSION-MASTER__data-validation-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__email-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__event-hooks-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__i18n-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__introduction-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__maintenance-md | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__messaging-md | 2 +- ...DHIS-CORE-VERSION-MASTER__metadata-gist-md | 2 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 2 +- ...S-CORE-VERSION-MASTER__org-unit-profile-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__route-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__scheduling-md | 2 +- ...SION-MASTER__settings-and-configuration-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__sharing-md | 2 +- ...-THE-API__DHIS-CORE-VERSION-MASTER__sms-md | 2 +- ...IS-CORE-VERSION-MASTER__synchronization-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 347 +- ...HE-API__DHIS-CORE-VERSION-MASTER__users-md | 2 +- ...HIS-CORE-VERSION-MASTER__visualizations-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-239__audit-md | 2 +- ...ON__DHIS-CORE-VERSION-239__installation-md | 2 +- ...TION__DHIS-CORE-VERSION-239__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-239__upgrading-md | 2 +- ...N-239__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-240__audit-md | 2 +- ...-VERSION-240__debugging-as-another-user-md | 2 +- ...ON__DHIS-CORE-VERSION-240__installation-md | 2 +- ...TION__DHIS-CORE-VERSION-240__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-240__upgrading-md | 2 +- ...N-240__using-gateways-for-sms-reporting-md | 2 +- ...RATION__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...RSION-MASTER__debugging-as-another-user-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__installation-md | 2 +- ...N__DHIS-CORE-VERSION-MASTER__monitoring-md | 2 +- ...ON__DHIS-CORE-VERSION-MASTER__upgrading-md | 2 +- ...ASTER__using-gateways-for-sms-reporting-md | 2 +- ...10__DASHBOARD-AND-DEMO-SERVER__browsing-md | 2 +- ...DASHBOARD-AND-DEMO-SERVER__introduction-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-planning-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-tracking-md | 2 +- ...LLATION-AND-CONFIGURATION__installation-md | 2 +- ...ALLATION-AND-CONFIGURATION__maintenance-md | 2 +- ...-AND-USAGE__analysis-and-interpretation-md | 2 +- ...NTRODUCTION-AND-USAGE__app-architecture-md | 2 +- ...RODUCTION-AND-USAGE__dashboard-and-demo-md | 2 +- ...RODUCTION-AND-USAGE__navigating-the-app-md | 2 +- ...ION-AND-USAGE__visualization-operations-md | 2 +- ...ER-IMPLEMENTATION__adopting-the-bna-app-md | 2 +- ..._USER-IMPLEMENTATION__capacity-building-md | 2 +- ..._USER-IMPLEMENTATION__end-user-training-md | 2 +- ...IMPLEMENTATION__implementation-overview-md | 2 +- ...ER-IMPLEMENTATION__integration-concepts-md | 2 +- ...MENTATION__opportunities-and-challenges-md | 2 +- ...IMPLEMENTATION__planning-and-organising-md | 2 +- ...USER-IMPLEMENTATION__setting-up-the-app-md | 2 +- ...ER-IMPLEMENTATION__support-and-scale-up-md | 2 +- ...22__USER-IMPLEMENTATION__sustainability-md | 2 +- ..._APP-VERSION-140__CONFIGURATION__access-md | 2 +- ...erventions-and-indicators-configuration-md | 2 +- ...N-140__CONFIGURATION__map-configuration-md | 2 +- ...VERSION-140__INSTALLATION__installation-md | 2 +- ...ION-140__INTRODUCTION__about-this-guide-md | 2 +- ...-140__INTRODUCTION__introduction-to-bna-md | 2 +- ..._USAGE__bna-analysis-and-interpretation-md | 2 +- ...APP__APP-VERSION-140__USAGE__bna-layout-md | 2 +- ...__APP-VERSION-140__USAGE__data-analysis-md | 2 +- ...S-APP__APP-VERSION-140__USAGE__map-view-md | 2 +- ...__immunization-analysis-app-user-manual-md | 2 +- ...-APP__APP-VERSION-250__about-this-guide-md | 2 +- ...0__accessing-and-transilating-scorecard-md | 2 +- ...CORECARD-APP__APP-VERSION-250__browsing-md | 2 +- ...PP__APP-VERSION-250__creating-scorecard-md | 2 +- ...-250__introduction-to-the-scorecard-app-md | 2 +- ..._APP-VERSION-250__saving-configurations-md | 2 +- ...VERSION-250__scorecard-app-architecture-md | 2 +- ...ON-250__support-and-maintenance-options-md | 2 +- ...APP__APP-VERSION-250__viewing-scorecard-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...APP-DEMO__architecture-and-installation-md | 2 +- ...ALONE-ACTION-TRACKER-APP-DEMO__browsing-md | 2 +- ...E-ACTION-TRACKER-APP-DEMO__introduction-md | 2 +- ...ON-TRACKER-CONFIGURATION__configuration-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-238__ANALYSING-DATA__dashboards-md | 2 +- ...ON-238__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-238__ANALYSING-DATA__event-reports-md | 2 +- ...N-238__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-238__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-238__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-238__ANALYSING-DATA__reports-md | 2 +- ...ION-238__APPROVING-DATA__approving-data-md | 2 +- ...SION-238__APPROVING-DATA__data-approval-md | 2 +- ...ERSION-238__COLLECTING-DATA__data-entry-md | 2 +- ...SION-238__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-238__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-238__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...SION-238__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-238__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...238__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...8__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-239__ANALYSING-DATA__dashboards-md | 2 +- ...ON-239__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-239__ANALYSING-DATA__event-reports-md | 2 +- ...N-239__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-239__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-239__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-239__ANALYSING-DATA__reports-md | 2 +- ...ION-239__APPROVING-DATA__approving-data-md | 2 +- ...SION-239__APPROVING-DATA__data-approval-md | 2 +- ...N-239__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-239__COLLECTING-DATA__data-entry-md | 2 +- ...SION-239__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-239__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-239__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-239__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...239__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-240__ANALYSING-DATA__dashboards-md | 2 +- ...ON-240__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-240__ANALYSING-DATA__event-reports-md | 2 +- ...N-240__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-240__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-240__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-240__ANALYSING-DATA__reports-md | 2 +- ...ION-240__APPROVING-DATA__approving-data-md | 2 +- ...SION-240__APPROVING-DATA__data-approval-md | 2 +- ...N-240__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-240__COLLECTING-DATA__data-entry-md | 2 +- ...SION-240__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-240__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-240__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-240__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-240__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-240__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...240__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...0__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...SION-MASTER__ANALYSING-DATA__dashboards-md | 2 +- ...MASTER__ANALYSING-DATA__data-visualizer-md | 2 +- ...N-MASTER__ANALYSING-DATA__event-reports-md | 2 +- ...ASTER__ANALYSING-DATA__event-visualizer-md | 2 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 2 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...VERSION-MASTER__ANALYSING-DATA__reports-md | 2 +- ...-MASTER__APPROVING-DATA__approving-data-md | 2 +- ...N-MASTER__APPROVING-DATA__data-approval-md | 2 +- ...ASTER__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ION-MASTER__COLLECTING-DATA__data-entry-md | 2 +- ...N-MASTER__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...ON-MASTER__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...-MASTER__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...-MASTER__EXCHANGING-DATA__data-exchange-md | 2 +- ...N-MASTER__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...-MASTER__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TER__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...R__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- projects/docs-full-site/fr/.cache_timestamp | 2 +- ...THE-API__DHIS-CORE-VERSION-232__web-api-md | 136 +- ...THE-API__DHIS-CORE-VERSION-233__web-api-md | 264 +- ...THE-API__DHIS-CORE-VERSION-234__web-api-md | 28 +- ...THE-API__DHIS-CORE-VERSION-235__web-api-md | 30 +- ...E-API__DHIS-CORE-VERSION-236__messaging-md | 28 +- ...HE-API__DHIS-CORE-VERSION-236__metadata-md | 2 +- ...API__DHIS-CORE-VERSION-236__new-tracker-md | 2 +- ...E-API__DHIS-CORE-VERSION-237__messaging-md | 318 +- ...HE-API__DHIS-CORE-VERSION-237__metadata-md | 30 +- ...API__DHIS-CORE-VERSION-237__new-tracker-md | 2 +- ...__DHIS-CORE-VERSION-237__visualizations-md | 58 +- ...E-API__DHIS-CORE-VERSION-238__messaging-md | 318 +- ...HE-API__DHIS-CORE-VERSION-238__metadata-md | 30 +- ...API__DHIS-CORE-VERSION-238__new-tracker-md | 2 +- ...__DHIS-CORE-VERSION-238__visualizations-md | 80 +- ...E-API__DHIS-CORE-VERSION-239__messaging-md | 318 +- ...HE-API__DHIS-CORE-VERSION-239__metadata-md | 119 +- ...API__DHIS-CORE-VERSION-239__new-tracker-md | 2 +- ...__DHIS-CORE-VERSION-239__visualizations-md | 80 +- ...E-API__DHIS-CORE-VERSION-240__messaging-md | 318 +- ...HE-API__DHIS-CORE-VERSION-240__metadata-md | 123 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 2 +- ...__DHIS-CORE-VERSION-240__visualizations-md | 80 +- ...HE-API__DHIS-CORE-VERSION-241__metadata-md | 135 +- ...THE-API__DHIS-CORE-VERSION-241__tracker-md | 2 +- ...__DHIS-CORE-VERSION-241__visualizations-md | 80 +- ...PI__DHIS-CORE-VERSION-MASTER__analytics-md | 8 +- ...THE-API__DHIS-CORE-VERSION-MASTER__apps-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-approval-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-entry-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__data-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-store-md | 2 +- ...IS-CORE-VERSION-MASTER__data-validation-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__email-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__event-hooks-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__i18n-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__introduction-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__maintenance-md | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__messaging-md | 320 +- ...DHIS-CORE-VERSION-MASTER__metadata-gist-md | 2 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 137 +- ...__DHIS-CORE-VERSION-MASTER__new-tracker-md | 2 +- ...S-CORE-VERSION-MASTER__org-unit-profile-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__route-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__scheduling-md | 2 +- ...SION-MASTER__settings-and-configuration-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__sharing-md | 2 +- ...-THE-API__DHIS-CORE-VERSION-MASTER__sms-md | 2 +- ...IS-CORE-VERSION-MASTER__synchronization-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 355 +- ...HE-API__DHIS-CORE-VERSION-MASTER__users-md | 2 +- ...HIS-CORE-VERSION-MASTER__visualizations-md | 82 +- ...ISTRATION__DHIS-CORE-VERSION-239__audit-md | 2 +- ...ON__DHIS-CORE-VERSION-239__installation-md | 2 +- ...TION__DHIS-CORE-VERSION-239__monitoring-md | 2 +- ...ATION__DHIS-CORE-VERSION-239__upgrading-md | 2 +- ...N-239__using-gateways-for-sms-reporting-md | 2 +- ...ISTRATION__DHIS-CORE-VERSION-240__audit-md | 2 +- ...-VERSION-240__debugging-as-another-user-md | 2 +- ...ON__DHIS-CORE-VERSION-240__installation-md | 2 +- ...ATION__DHIS-CORE-VERSION-240__upgrading-md | 2 +- ...RATION__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...RSION-MASTER__debugging-as-another-user-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__installation-md | 2 +- ...N__DHIS-CORE-VERSION-MASTER__monitoring-md | 2 +- ...ON__DHIS-CORE-VERSION-MASTER__upgrading-md | 2 +- ...ASTER__using-gateways-for-sms-reporting-md | 2 +- ...10__DASHBOARD-AND-DEMO-SERVER__browsing-md | 2 +- ...DASHBOARD-AND-DEMO-SERVER__introduction-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-planning-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-tracking-md | 2 +- ...LLATION-AND-CONFIGURATION__installation-md | 2 +- ...ALLATION-AND-CONFIGURATION__maintenance-md | 2 +- ...-AND-USAGE__analysis-and-interpretation-md | 2 +- ...NTRODUCTION-AND-USAGE__app-architecture-md | 2 +- ...RODUCTION-AND-USAGE__dashboard-and-demo-md | 2 +- ...RODUCTION-AND-USAGE__navigating-the-app-md | 2 +- ...ION-AND-USAGE__visualization-operations-md | 2 +- ...ER-IMPLEMENTATION__adopting-the-bna-app-md | 2 +- ..._USER-IMPLEMENTATION__capacity-building-md | 2 +- ..._USER-IMPLEMENTATION__end-user-training-md | 2 +- ...IMPLEMENTATION__implementation-overview-md | 2 +- ...ER-IMPLEMENTATION__integration-concepts-md | 2 +- ...MENTATION__opportunities-and-challenges-md | 2 +- ...IMPLEMENTATION__planning-and-organising-md | 2 +- ...USER-IMPLEMENTATION__setting-up-the-app-md | 2 +- ...ER-IMPLEMENTATION__support-and-scale-up-md | 2 +- ...22__USER-IMPLEMENTATION__sustainability-md | 2 +- ..._APP-VERSION-140__CONFIGURATION__access-md | 2 +- ...erventions-and-indicators-configuration-md | 2 +- ...N-140__CONFIGURATION__map-configuration-md | 2 +- ...VERSION-140__INSTALLATION__installation-md | 2 +- ...ION-140__INTRODUCTION__about-this-guide-md | 2 +- ...-140__INTRODUCTION__introduction-to-bna-md | 2 +- ..._USAGE__bna-analysis-and-interpretation-md | 2 +- ...APP__APP-VERSION-140__USAGE__bna-layout-md | 2 +- ...__APP-VERSION-140__USAGE__data-analysis-md | 2 +- ...__immunization-analysis-app-user-manual-md | 2 +- ...-APP__APP-VERSION-250__about-this-guide-md | 2 +- ...0__accessing-and-transilating-scorecard-md | 2 +- ...CORECARD-APP__APP-VERSION-250__browsing-md | 2 +- ...PP__APP-VERSION-250__creating-scorecard-md | 2 +- ...-250__introduction-to-the-scorecard-app-md | 2 +- ..._APP-VERSION-250__saving-configurations-md | 2 +- ...VERSION-250__scorecard-app-architecture-md | 2 +- ...ON-250__support-and-maintenance-options-md | 2 +- ...APP__APP-VERSION-250__viewing-scorecard-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...APP-DEMO__architecture-and-installation-md | 2 +- ...ALONE-ACTION-TRACKER-APP-DEMO__browsing-md | 2 +- ...E-ACTION-TRACKER-APP-DEMO__introduction-md | 2 +- ...ON-TRACKER-CONFIGURATION__configuration-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-238__ANALYSING-DATA__dashboards-md | 2 +- ...ON-238__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-238__ANALYSING-DATA__event-reports-md | 2 +- ...N-238__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-238__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-238__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-238__ANALYSING-DATA__reports-md | 2 +- ...SION-238__APPROVING-DATA__data-approval-md | 2 +- ...ERSION-238__COLLECTING-DATA__data-entry-md | 2 +- ...SION-238__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-238__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-238__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...SION-238__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-238__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...238__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...8__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...ON-239__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-239__ANALYSING-DATA__event-reports-md | 2 +- ...N-239__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-239__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-239__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-239__ANALYSING-DATA__reports-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...ON-240__ANALYSING-DATA__data-visualizer-md | 2 +- ...RSION-240__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-240__ANALYSING-DATA__maps-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...ION-240__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-240__EXCHANGING-DATA__importexport-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-240__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...MASTER__ANALYSING-DATA__data-visualizer-md | 2 +- ...N-MASTER__ANALYSING-DATA__event-reports-md | 2 +- ...ASTER__ANALYSING-DATA__event-visualizer-md | 2 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 2 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...VERSION-MASTER__ANALYSING-DATA__reports-md | 2 +- ...N-MASTER__APPROVING-DATA__data-approval-md | 2 +- ...ION-MASTER__COLLECTING-DATA__data-entry-md | 2 +- ...N-MASTER__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...ON-MASTER__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...-MASTER__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...-MASTER__EXCHANGING-DATA__data-exchange-md | 2 +- ...N-MASTER__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...-MASTER__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TER__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...R__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- projects/docs-full-site/pt/.cache_timestamp | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-238__ANALYSING-DATA__dashboards-md | 2 +- ...ON-238__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-238__ANALYSING-DATA__event-reports-md | 2 +- ...N-238__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-238__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-238__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-238__ANALYSING-DATA__reports-md | 2 +- ...ION-238__APPROVING-DATA__approving-data-md | 2 +- ...SION-238__APPROVING-DATA__data-approval-md | 2 +- ...ERSION-238__COLLECTING-DATA__data-entry-md | 2 +- ...SION-238__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-238__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-238__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...SION-238__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-238__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...238__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...8__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...ION-240__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...240__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...0__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...SION-MASTER__ANALYSING-DATA__dashboards-md | 2 +- ...MASTER__ANALYSING-DATA__data-visualizer-md | 2 +- ...N-MASTER__ANALYSING-DATA__event-reports-md | 2 +- ...ASTER__ANALYSING-DATA__event-visualizer-md | 2 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 2 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...VERSION-MASTER__ANALYSING-DATA__reports-md | 2 +- ...-MASTER__APPROVING-DATA__approving-data-md | 2 +- ...N-MASTER__APPROVING-DATA__data-approval-md | 2 +- ...ASTER__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ION-MASTER__COLLECTING-DATA__data-entry-md | 2 +- ...N-MASTER__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...ON-MASTER__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...-MASTER__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...-MASTER__EXCHANGING-DATA__data-exchange-md | 2 +- ...N-MASTER__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...-MASTER__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TER__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...R__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- projects/docs-full-site/ru/.cache_timestamp | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...10__DASHBOARD-AND-DEMO-SERVER__browsing-md | 2 +- ...DASHBOARD-AND-DEMO-SERVER__introduction-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-planning-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-tracking-md | 2 +- ...LLATION-AND-CONFIGURATION__installation-md | 2 +- ...ALLATION-AND-CONFIGURATION__maintenance-md | 2 +- ...-AND-USAGE__analysis-and-interpretation-md | 2 +- ...NTRODUCTION-AND-USAGE__app-architecture-md | 2 +- ...RODUCTION-AND-USAGE__dashboard-and-demo-md | 2 +- ...RODUCTION-AND-USAGE__navigating-the-app-md | 2 +- ...ION-AND-USAGE__visualization-operations-md | 2 +- ...ER-IMPLEMENTATION__adopting-the-bna-app-md | 2 +- ..._USER-IMPLEMENTATION__capacity-building-md | 2 +- ..._USER-IMPLEMENTATION__end-user-training-md | 2 +- ...IMPLEMENTATION__implementation-overview-md | 2 +- ...ER-IMPLEMENTATION__integration-concepts-md | 2 +- ...MENTATION__opportunities-and-challenges-md | 2 +- ...IMPLEMENTATION__planning-and-organising-md | 2 +- ...USER-IMPLEMENTATION__setting-up-the-app-md | 2 +- ...ER-IMPLEMENTATION__support-and-scale-up-md | 2 +- ...22__USER-IMPLEMENTATION__sustainability-md | 2 +- ..._APP-VERSION-140__CONFIGURATION__access-md | 2 +- ...erventions-and-indicators-configuration-md | 2 +- ...N-140__CONFIGURATION__map-configuration-md | 2 +- ...VERSION-140__INSTALLATION__installation-md | 2 +- ...ION-140__INTRODUCTION__about-this-guide-md | 2 +- ...-140__INTRODUCTION__introduction-to-bna-md | 2 +- ..._USAGE__bna-analysis-and-interpretation-md | 2 +- ...APP__APP-VERSION-140__USAGE__bna-layout-md | 2 +- ...__APP-VERSION-140__USAGE__data-analysis-md | 2 +- ...S-APP__APP-VERSION-140__USAGE__map-view-md | 2 +- ...__immunization-analysis-app-user-manual-md | 2 +- ...-APP__APP-VERSION-250__about-this-guide-md | 2 +- ...0__accessing-and-transilating-scorecard-md | 2 +- ...CORECARD-APP__APP-VERSION-250__browsing-md | 2 +- ...PP__APP-VERSION-250__creating-scorecard-md | 2 +- ...-250__introduction-to-the-scorecard-app-md | 2 +- ..._APP-VERSION-250__saving-configurations-md | 2 +- ...VERSION-250__scorecard-app-architecture-md | 2 +- ...ON-250__support-and-maintenance-options-md | 2 +- ...APP__APP-VERSION-250__viewing-scorecard-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...APP-DEMO__architecture-and-installation-md | 2 +- ...ALONE-ACTION-TRACKER-APP-DEMO__browsing-md | 2 +- ...E-ACTION-TRACKER-APP-DEMO__introduction-md | 2 +- ...ON-TRACKER-CONFIGURATION__configuration-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-238__ANALYSING-DATA__dashboards-md | 2 +- ...ON-238__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-238__ANALYSING-DATA__event-reports-md | 2 +- ...N-238__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-238__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-238__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-238__ANALYSING-DATA__reports-md | 2 +- ...ION-238__APPROVING-DATA__approving-data-md | 2 +- ...SION-238__APPROVING-DATA__data-approval-md | 2 +- ...ERSION-238__COLLECTING-DATA__data-entry-md | 2 +- ...SION-238__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-238__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-238__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-238__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...SION-238__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-238__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...238__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...8__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-239__ANALYSING-DATA__dashboards-md | 2 +- ...ON-239__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-239__ANALYSING-DATA__event-reports-md | 2 +- ...N-239__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-239__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-239__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-239__ANALYSING-DATA__reports-md | 2 +- ...ION-239__APPROVING-DATA__approving-data-md | 2 +- ...SION-239__APPROVING-DATA__data-approval-md | 2 +- ...N-239__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-239__COLLECTING-DATA__data-entry-md | 2 +- ...SION-239__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-239__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-239__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-239__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...239__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-240__ANALYSING-DATA__dashboards-md | 2 +- ...ON-240__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-240__ANALYSING-DATA__event-reports-md | 2 +- ...N-240__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-240__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-240__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-240__ANALYSING-DATA__reports-md | 2 +- ...ION-240__APPROVING-DATA__approving-data-md | 2 +- ...SION-240__APPROVING-DATA__data-approval-md | 2 +- ...N-240__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-240__COLLECTING-DATA__data-entry-md | 2 +- ...SION-240__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-240__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-240__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-240__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-240__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-240__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...240__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...0__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...SION-MASTER__ANALYSING-DATA__dashboards-md | 2 +- ...MASTER__ANALYSING-DATA__data-visualizer-md | 2 +- ...N-MASTER__ANALYSING-DATA__event-reports-md | 2 +- ...ASTER__ANALYSING-DATA__event-visualizer-md | 2 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 2 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...VERSION-MASTER__ANALYSING-DATA__reports-md | 2 +- ...-MASTER__APPROVING-DATA__approving-data-md | 2 +- ...N-MASTER__APPROVING-DATA__data-approval-md | 2 +- ...ASTER__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ION-MASTER__COLLECTING-DATA__data-entry-md | 2 +- ...N-MASTER__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...ON-MASTER__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...-MASTER__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...-MASTER__EXCHANGING-DATA__data-exchange-md | 2 +- ...N-MASTER__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...-MASTER__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...TER__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...R__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- projects/docs-full-site/si/.cache_timestamp | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- projects/docs-full-site/zh/.cache_timestamp | 2 +- ...PI__DHIS-CORE-VERSION-MASTER__analytics-md | 8 +- ...THE-API__DHIS-CORE-VERSION-MASTER__apps-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-approval-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-entry-md | 2 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__data-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__data-store-md | 2 +- ...IS-CORE-VERSION-MASTER__data-validation-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__event-hooks-md | 2 +- ...THE-API__DHIS-CORE-VERSION-MASTER__i18n-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__introduction-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__maintenance-md | 2 +- ...DHIS-CORE-VERSION-MASTER__metadata-gist-md | 2 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 2 +- ...S-CORE-VERSION-MASTER__org-unit-profile-md | 2 +- ...__DHIS-CORE-VERSION-MASTER__query-alias-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__route-md | 2 +- ...I__DHIS-CORE-VERSION-MASTER__scheduling-md | 2 +- ...SION-MASTER__settings-and-configuration-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__sharing-md | 2 +- ...-THE-API__DHIS-CORE-VERSION-MASTER__sms-md | 2 +- ...IS-CORE-VERSION-MASTER__synchronization-md | 2 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 357 +- ...HE-API__DHIS-CORE-VERSION-MASTER__users-md | 2 +- ...HIS-CORE-VERSION-MASTER__visualizations-md | 2 +- ...RATION__DHIS-CORE-VERSION-MASTER__audit-md | 2 +- ...RSION-MASTER__debugging-as-another-user-md | 2 +- ..._DHIS-CORE-VERSION-MASTER__installation-md | 2 +- ...N__DHIS-CORE-VERSION-MASTER__monitoring-md | 2 +- ...ON__DHIS-CORE-VERSION-MASTER__upgrading-md | 2 +- ...ASTER__using-gateways-for-sms-reporting-md | 2 +- ...10__DASHBOARD-AND-DEMO-SERVER__browsing-md | 2 +- ...DASHBOARD-AND-DEMO-SERVER__introduction-md | 2 +- ...0__MAINTENANCE-AND-SUPPORT__maintenance-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-planning-md | 2 +- ...-AND-ANALYZING-ACTIONS__action-tracking-md | 2 +- ...LLATION-AND-CONFIGURATION__installation-md | 2 +- ...ALLATION-AND-CONFIGURATION__maintenance-md | 2 +- ...-AND-USAGE__analysis-and-interpretation-md | 2 +- ...NTRODUCTION-AND-USAGE__app-architecture-md | 2 +- ...RODUCTION-AND-USAGE__dashboard-and-demo-md | 2 +- ...RODUCTION-AND-USAGE__navigating-the-app-md | 2 +- ...ION-AND-USAGE__visualization-operations-md | 2 +- ...ER-IMPLEMENTATION__adopting-the-bna-app-md | 2 +- ..._USER-IMPLEMENTATION__capacity-building-md | 2 +- ..._USER-IMPLEMENTATION__end-user-training-md | 2 +- ...IMPLEMENTATION__implementation-overview-md | 2 +- ...ER-IMPLEMENTATION__integration-concepts-md | 2 +- ...MENTATION__opportunities-and-challenges-md | 2 +- ...IMPLEMENTATION__planning-and-organising-md | 2 +- ...N-239__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-239__COLLECTING-DATA__data-entry-md | 2 +- ...SION-239__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-239__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-239__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-239__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-239__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-239__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-239__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...239__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...9__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-240__ANALYSING-DATA__dashboards-md | 2 +- ...ON-240__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-240__ANALYSING-DATA__event-reports-md | 2 +- ...N-240__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-240__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-240__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-240__ANALYSING-DATA__reports-md | 2 +- ...ION-240__APPROVING-DATA__approving-data-md | 2 +- ...SION-240__APPROVING-DATA__data-approval-md | 2 +- ...N-240__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-240__COLLECTING-DATA__data-entry-md | 2 +- ...SION-240__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-240__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-240__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-240__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-240__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-240__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-240__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...240__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...0__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ATION__dhis2-frequently-asked-questions-md | 2 +- ..._ADDITIONAL-INFORMATION__dhis2-glossary-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...-INFORMATION__release-and-upgrade-notes-md | 2 +- ...VERSION-241__ANALYSING-DATA__dashboards-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...SION-241__ANALYSING-DATA__event-reports-md | 2 +- ...N-241__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 2 +- ...-CORE-VERSION-241__ANALYSING-DATA__maps-md | 2 +- ...RE-VERSION-241__ANALYSING-DATA__reports-md | 2 +- ...ION-241__APPROVING-DATA__approving-data-md | 2 +- ...SION-241__APPROVING-DATA__data-approval-md | 2 +- ...N-241__COLLECTING-DATA__data-entry-beta-md | 2 +- ...ERSION-241__COLLECTING-DATA__data-entry-md | 2 +- ...SION-241__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...RSION-241__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...N-241__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...ION-241__CONFIGURING-THE-SYSTEM__report-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...ION-241__EXCHANGING-DATA__data-exchange-md | 2 +- ...SION-241__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...__MAINTAINING-THE-SYSTEM__configure-sms-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...INTAINING-THE-SYSTEM__datastore-manager-md | 2 +- ...ING-THE-SYSTEM__installing-applications-md | 2 +- ...ION-241__MAINTAINING-THE-SYSTEM__mobile-md | 2 +- ...241__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...-THE-SYSTEM__visualize-usage-statistics-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...NG-INDIVIDUAL-LEVEL-DATA__event-capture-md | 2 +- ...-INDIVIDUAL-LEVEL-DATA__tracker-capture-md | 2 +- ...G-THE-DATA-MODEL__about-data-dimensions-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...DING-THE-DATA-MODEL__relationship-model-md | 2 +- ...1__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- ...R-ACCOUNT__set-user-account-preferences-md | 2 +- ...server-live-package-and-database-design-md | 2 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...SION-MASTER__ANALYSING-DATA__dashboards-md | 2 +- ...MASTER__ANALYSING-DATA__data-visualizer-md | 2 +- ...N-MASTER__ANALYSING-DATA__event-reports-md | 2 +- ...ASTER__ANALYSING-DATA__event-visualizer-md | 2 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 2 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...-MASTER__APPROVING-DATA__approving-data-md | 2 +- ...ASTER__COLLECTING-DATA__data-entry-beta-md | 2 +- ...N-MASTER__COLLECTING-DATA__data-quality-md | 2 +- ...NG-THE-SYSTEM__about-sharing-of-objects-md | 2 +- ...ON-MASTER__CONFIGURING-THE-SYSTEM__maps-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__metadata-md | 2 +- ...ASTER__CONFIGURING-THE-SYSTEM__programs-md | 2 +- ...CONFIGURING-THE-SYSTEM__system-settings-md | 2 +- ...ONFIGURING-THE-SYSTEM__user-authorities-md | 2 +- ...RING-THE-SYSTEM__users-roles-and-groups-md | 2 +- ...-MASTER__EXCHANGING-DATA__data-exchange-md | 2 +- ...N-MASTER__EXCHANGING-DATA__importexport-md | 2 +- ...CHANGING-DATA__metadata-synchronization-md | 2 +- ...TAINING-THE-SYSTEM__data-administration-md | 2 +- ...TER__MAINTAINING-THE-SYSTEM__scheduling-md | 2 +- ...TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md | 2 +- ...-DATA-MODEL__additional-data-dimensions-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- 1606 files changed, 7557 insertions(+), 32066 deletions(-) diff --git a/projects/dhis2-single-page-docs/am_ET/.cache_timestamp b/projects/dhis2-single-page-docs/am_ET/.cache_timestamp index e21bc1b9d..501106780 100644 --- a/projects/dhis2-single-page-docs/am_ET/.cache_timestamp +++ b/projects/dhis2-single-page-docs/am_ET/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:26:54Z \ No newline at end of file +2024-06-04T21:26:49Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ar/.cache_timestamp b/projects/dhis2-single-page-docs/ar/.cache_timestamp index e21bc1b9d..501106780 100644 --- a/projects/dhis2-single-page-docs/ar/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ar/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:26:54Z \ No newline at end of file +2024-06-04T21:26:49Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index b839f9dc6..9b59544a7 100644 --- a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index 67d073ec8..17a3aea74 100644 --- a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 21331d90b..ff27fb945 100644 --- a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index e82657e97..12abc00e1 100644 --- a/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/ar/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - Develop - DHIS core version master @@ -12221,7 +12221,7 @@ Table: Query parameters for event query analytics only | Query parameter | Required | Description | خيارات | |---|---|---|---| -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return events which have coordinates. | false | true | @@ -13128,7 +13128,7 @@ Table: Query parameters for enrollment query endpoint | filter | No | Dimension identifier including data elements, attributes, periods, organisation units and organisation unit group sets. Parameter can be repeated any number of times. Item filters can be applied to a dimension on the format ::. Filter values are case-insensitive. || | programStatus | No | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | No | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return enrollments which have coordinates. | false | true | @@ -17837,20 +17837,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17953,7 +17954,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | No | Yes | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | Yes | No | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | No | Yes | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -18013,9 +18013,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Attributes { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -18030,18 +18032,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -18056,31 +18060,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Notes { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -18091,10 +18095,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -18136,92 +18140,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the working list. Required. || -| description | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Description | Example | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -18230,9 +18149,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -18265,7 +18184,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -18665,7 +18584,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -19111,7 +19030,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -19241,7 +19160,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | لا ينطبق | Undefined error message. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -19251,7 +19170,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -19276,8 +19195,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -19330,7 +19249,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -19386,7 +19305,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -19408,7 +19327,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -19442,7 +19361,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -19494,9 +19413,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -19576,8 +19495,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -19682,7 +19601,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19944,8 +19863,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -20149,8 +20068,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -20445,13 +20364,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -20497,7 +20416,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -20566,13 +20485,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -20584,7 +20503,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -20597,7 +20516,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -20607,7 +20526,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -20637,7 +20556,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -20653,2767 +20572,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Table: Payload -|Tracker Object|Previously|Now| +| Payload values | Description | Example | |---|---|---| -|**Attribute**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Event**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Note**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Relationship**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribute`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes`|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus`|`enrollmentStatus`| -|`query`|Removed - use `filter` instead| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Previously|Now| -|---|---| -|`enrollment`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus`|`status`| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`event`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`lastUpdated`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus`|`enrollmentStatus`| -|`skipEventId`|Removed| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Previously|Now| -|---|---| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity`| - -## Tracker Web API { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### Tracked entity instance management { #webapi_tracked_entity_instance_management } - -Tracked entity instances have full CRUD support in the API. Together -with the API for enrollment most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/trackedEntityInstances - -#### Creating a new tracked entity instance { #webapi_creating_tei } - -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -The field "geometry" accepts a GeoJson object, where the type of the -GeoJson have to match the featureType of the TrackedEntityType -definition. An example GeoJson object looks like this: - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +| name | Name of the working list. Required. || +| description | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Table: Program Stage Query Criteria - /api/trackedEntityInstances +| Criteria values | Description | Example | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +See an example payload below: ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -To push this to the server you can use the cURL command like this: - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -To create multiple instances in one request you can wrap the payload in -an outer array like this and POST to the same resource as above:[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -The system does not allow the creation of a tracked entity instance -(as well as enrollment and event) with a UID that was already used in -the system. That means that UIDs cannot be reused. - -#### Updating a tracked entity instance { #webapi_updating_tei } - -For updating a tracked entity instance, the payload is equal to the -previous section. The difference is that you must use the HTTP *PUT* -method for the request when sending the payload. You will also need to -append the person identifier to the *trackedEntityInstances* resource in -the URL like this, where `` should -be replaced by the identifier of the tracked entity instance: - - /api/trackedEntityInstances/ - -The payload has to contain all, even non-modified, attributes and -relationships. Attributes or relationships that were present before and -are not present in the current payload any more will be removed from the -system. This means that if attributes/relationships are empty in the -current payload, all existing attributes/relationships will be deleted -from the system. From 2.31, it is possible to ignore empty -attributes/relationships in the current payload. A request parameter of -`ignoreEmptyCollection` set to `true` can be used in case you do not -wish to send in any attributes/relationships and also do not want them -to be deleted from the system. - -It is not allowed to update an already deleted tracked entity instance. -Also, it is not allowed to mark a tracked entity instance as deleted via -an update request. The same rules apply to enrollments and events. - -#### Deleting a tracked entity instance { #webapi_deleting_tei } - -In order to delete a tracked entity instance, make a request to the URL -identifying the tracked entity instance with the *DELETE* -method. The URL is equal to the one above used for update. - -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } - -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Complete example of payload including: tracked entity instance, enrollment and event { #webapi_create_enroll_tei_create_event } - -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute":"cejWyOfXge6", - "value":"Male" - } - ], - "enrollments":[ - { - "orgUnit":"DiszpKrYNg8", - "program":"ur1Edk5Oe2n", - "enrollmentDate":"2017-09-15", - "incidentDate":"2017-09-15", - "events":[ - { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues": [ - { - "dataElement":"qrur9Dvnyt5", - "value":"22" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Male" - } - ] - }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues":[ - { - "dataElement":"qrur9Dvnyt5", - "value":"26" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Female" - } - ] - } - ] - } - ] + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Generated tracked entity instance attributes { #webapi_generate_tei_attributes } - -Tracked entity instance attributes that are using automatic generation of -unique values have three endpoints that are used by apps. The endpoints -are all used for generating and reserving values. - -In 2.29 we introduced TextPattern for defining and generating these -patterns. All existing patterns will be converted to a valid TextPattern -when upgrading to 2.29. - -> **Note** -> -> As of 2.29, all these endpoints will require you to include any -> variables reported by the `requiredValues` endpoint listed as -> required. Existing patterns, consisting of only `#`, will be upgraded -> to the new TextPattern syntax `RANDOM()`. The RANDOM -> segment of the TextPattern is not a required variable, so this -> endpoint will work as before for patterns defined before 2.29. - -##### Finding required values { #finding-required-values } - -A TextPattern can contain variables that change based on different -factors. Some of these factors will be unknown to the server, so the -values for these variables have to be supplied when generating and -reserving values. - -This endpoint will return a map of required and optional values, that -the server will inject into the TextPattern when generating new values. -Required variables have to be supplied for the generation, but optional -variables should only be supplied if you know what you are doing. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### Generate value endpoint { #webapi_generate_values } - -Online web apps and other clients that want to generate a value that -will be used right away can use the simple generate endpoint. This -endpoint will generate a value that is guaranteed to be unique at the -time of generation. The value is also guaranteed not to be reserved. As -of 2.29, this endpoint will also reserve the value generated for 3 days. - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } - -The generate and reserve endpoint is used by offline clients that need -to be able to register tracked entities with unique ids. They will -reserve a number of unique ids that this device will then use when -registering new tracked entity instances. The endpoint is called to -retrieve a number of tracked entity instance reserved values. An -optional parameter numberToReserve specifies how many ids to generate -(default is 1). - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -Similar to the /generate endpoint, this endpoint can also specify the -expiration time in the same way. By adding the `?expiration=` -you can override the default 60 days. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### Reserved values { #reserved-values } - -Reserved values are currently not accessible through the api, however, they -are returned by the `generate` and `generateAndReserve` endpoints. The -following table explains the properties of the reserved value object: - -##### - - - -Table: Reserved values - -| Property | Description | -|---|---| -| ownerObject | The metadata type referenced when generating and reserving the value. Currently only TRACKEDENTITYATTRIBUTE is supported. | -| ownerUid | The uid of the metadata object referenced when generating and reserving the value. | -| key | A partially generated value where generated segments are not yet added. | -| value | The fully resolved value reserved. This is the value you send to the server when storing data. | -| created | The timestamp when the reservation was made | -| expiryDate | The timestamp when the reservation will no longer be reserved | - -Expired reservations are removed daily. If a pattern changes, values -that were already reserved will be accepted when storing data, even if -they don't match the new pattern, as long as the reservation has not -expired. - -#### Image attributes { #image-attributes } - -Working with image attributes is a lot like working with file data -values. The value of an attribute with the image value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///image` -endpoint will return the actual image. The optional height and width -parameters can be used to specify the dimensions of the image. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } - -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. - - /api/33/trackedEntityInstances - -##### Request syntax { #webapi_tei_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Description | -|---|---| -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Indicates whether to include soft deleted teis or not. It is false by default. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | The selected organisation units and the immediate children, i.e. the organisation units at the level below. | -| DESCENDANTS | The selected organisation units and all children, i.e. all organisation units in the sub-hierarchy. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| ALL | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -The available assigned user modes are explained in the following table. - - - -Table: Assigned user modes - -| Mode | Description | -|---|---| -| CURRENT | Includes events assigned to the current logged in user. | -| PROVIDED | Includes events assigned to the user provided in the request. | -| NONE | Includes unassigned events only. | -| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendant organisation unit query mode: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a filter: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an *IN* filter: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - &filter=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&page=2&pageSize=3 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Description | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### Tracked entity instance grid query { #webapi_tracked_entity_instance_grid_query } - -To query for tracked entity instances you can interact with the -*/api/trackedEntityInstances/grid* resource. There are two types of -queries: One where a *query* query parameter and optionally *attribute* -parameters are defined, and one where *attribute* and *filter* -parameters are defined. This endpoint uses a more compact "grid" format, -and is an alternative to the query in the previous section. - - /api/33/trackedEntityInstances/query - -##### Request syntax { #webapi_tei_grid_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Description | -|---|---| -| query | Query string. Attribute query parameter can be used to define which attributes to include in the response. If no attributes but a program is defined, the attributes from the program will be used. If no program is defined, all attributes will be used. There are two formats. The first is a plan query string. The second is on the format :. Operators can be EQ | LIKE. EQ implies exact matches on words, LIKE implies partial matches on words. The query will be split on space, where each word will form a logical AND query. | -| attribute | Attributes to be included in the response. Can also be used as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. Filters can be omitted in order to simply include the attribute in the response without any constraints. | -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| eventStatus | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Start date of event associated with the given program and event status. | -| eventEndDate | End date of event associated with the given program and event status. | -| programStage | The programStage for which the event related filters should be applied to. If not provided all stages will be considered. | -| skipMeta | Indicates whether meta data for the response should be included. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| CAPTURE | The data capture organisation units associated with the current user and all children, i.e. all organisation units in the sub-hierarchy. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -Note that you can specify "attribute" with filters or directly using the "filter" params for constraining the -instances to return. - -Certain rules apply to which attributes are returned. - - - If "query" is specified without any attributes or program, then all attributes that - are marked as "Display in List without Program" is included in the response. - - - If program is specified, all the attributes linked to the program will - be included in the response. - - - If tracked entity type is specified, then all tracked entity type attributes - will be included in the response. - -You can specify queries with words separated by space - in that -situation the system will query for each word independently and return -records where each word is contained in any attribute. A query item can -be specified once as an attribute and once as a filter if needed. The -query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - If *eventStatus* is specified then *eventStartDate* and - *eventEndDate* must also be specified. - - - A query cannot be specified together with filters. - - - Attribute items can only be specified once. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -A query on all attributes for a specific value and organisation unit, -using an exact word match: - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -A query on all attributes for a specific value, using a partial word -match: - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -You can query on multiple words separated by the URL character for -space which is %20, will use a logical AND query for each - word: - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -A query where the attributes to include in the response are specified: - - /api/33/trackedEntityInstances/query.json?query=isabel - &attribute=dv3nChNSIxy&attribute=AMpUYgxuCaE&ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendants organisation unit query mode: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &attribute=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a - filter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an IN - filter: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - &attribute=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&program=ur1Edk5Oe2n&programStartDate=2013-01-01 - &programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -To query for instances which have events of a given status within a -given time span: - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Description | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_grid_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - - - csv (application/csv) - - - xls (application/vnd.ms-excel) - -The response in JSON comes is in a tabular format and can look like the -following. The *headers* section describes the content of each column. -The instance, created, last updated, org unit and tracked entity columns -are always present. The following columns correspond to attributes -specified in the query. The *rows* section contains one row per -instance. - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### Tracked entity instance filters { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - /api/33/trackedEntityInstanceFilters - -##### Create and update a tracked entity instance filter definition { #create-and-update-a-tracked-entity-instance-filter-definition } - -For creating and updating a tracked entity instance filter in the -system, you will be working with the *trackedEntityInstanceFilters* -resource. The tracked entity instance filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the filter. Required. || -| description | A description of the filter. || -| sortOrder | The sort order of the filter. Used in Tracker Capture to order the filters in the program dashboard. || -| style | Object containing css style. | ( "color": "blue", "icon": "fa fa-calendar"} | -| program | Object containing the id of the program. Required. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Table: Entity Query Criteria definition - -|||| -|---|---|---| -| attributeValueFilters | A list of attributeValueFilters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| enrollmentStatus | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | When this parameter is true, the filter only returns TEIs that have an enrollment with status followup. || -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayColumnOrder | To specify the output ordering of columns | "displayOrderColumns": ["enrollmentDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus | Any valid EventStatus | "eventStatus": "COMPLETED" | -| programStage | To specify a programStage uid to filter on. TEIs will be filtered based on presence of enrollment in the specified program stage.| "programStage"="a3kGcGDCuk6" | -| trackedEntityType | To specify a trackedEntityType filter TEIs on. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | To specify a list of trackedEntityInstances to use when querying TEIs. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod object date filtering based on enrollment incident date. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod object date filtering based on enrollment created date. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Table: Event filters definition - -|||| -|---|---|---| -| programStage | Which programStage the TEI needs an event in to be returned. | "eaDH9089uMp" | -| eventStatus | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT (events assigned to current user)| PROVIDED (events assigned to users provided in "assignedUsers" list) | NONE (events assigned to no one) | ANY (events assigned to anyone). If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -Table: Period definition - -|||| -|---|---|---| -| periodFrom | Number of days from current day. Can be positive or negative integer. | -15 | -| periodTo | Number of days from current day. Must be bigger than periodFrom. Can be positive or negative integer. | 15 | - -##### Tracked entity instance filters query { #tracked-entity-instance-filters-query } - -To query for tracked entity instance filters in the system, you can -interact with the */api/trackedEntityInstanceFilters* resource. - - - -Table: Tracked entity instance filters query parameters - -| Query parameter | Description | -|---|---| -| program | Program identifier. Restricts filters to the given program. | - -### Enrollment management { #webapi_enrollment_management } - -Enrollments have full CRUD support in the API. Together with the API -for tracked entity instances most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/enrollments - -#### Enrolling a tracked entity instance into a program { #webapi_enrolling_tei } - -For enrolling persons into a program, you will need to first get the -identifier of the person from the *trackedEntityInstances* resource. -Then, you will need to get the program identifier from the *programs* -resource. A template payload can be seen below: - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -This payload should be used in a *POST* request to the enrollments -resource identified by the following URL: - - /api/33/enrollments - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - /api/33/enrollments//cancelled - -For completing an enrollment for a tracked entity instance you can make a -*PUT* request to the following URL: - - /api/33/enrollments//completed - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - /api/33/enrollments/ - -#### Enrollment instance query { #webapi_enrollment_instance_query } - -To query for enrollments you can interact with the */api/enrollments* -resource. - - /api/33/enrollments - -##### Request syntax { #webapi_enrollment_query_request_syntax } - - - -Table: Enrollment query parameters - -| Query parameter | Description | -|---|---| -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| trackedEntityInstance | Tracked entity instance identifier. Should not be used together with trackedEntity. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| includeDeleted | Indicates whether to include soft deleted enrollments or not. It is false by default. | - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request (default). | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - -A query for all enrollments associated with a specific organisation unit -can look like this: - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -To constrain the response to enrollments which are part of a specific -program you can include a program query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the - query: - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - &programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to enrollments of a specific tracked entity -you can include a tracked entity query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -To constrain the response to enrollments of a specific tracked entity -instance you can include a tracked entity instance query parameter, in -this case we have restricted it to available enrollments viewable for -current - user: - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -By default the enrollments are returned in pages of size 50, to change -this you can use the page and pageSize query - parameters: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### Response format { #webapi_enrollment_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### Events { #webapi_events } - -This section is about sending and reading events. - - /api/33/events - -The different status of an event are: - -* **ACTIVE**: If a event has ACTIVE status, it is possible to edit the event details. COMPLETED events can be turned ACTIVE again and vice versa. -* **COMPLETED**: An event change the status to COMPLETED only when a user clicks the complete button. If a event has COMPLETED status, it is not possible to edit the event details. ACTIVE events can be turned COMPLETED again and vice versa. -* **SKIPPED**: Scheduled events that no longer need to happen. In Tracker Capture, there is a button for that. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### Sending events { #webapi_sending_events } - -DHIS2 supports three kinds of events: single events with no registration -(also referred to as anonymous events), single event with registration -and multiple events with registration. Registration implies that the -data is linked to a tracked entity instance which is identified using -some sort of identifier. - -To send events to DHIS2 you must interact with the *events* resource. -The approach to sending events is similar to sending aggregate data -values. You will need a *program* which can be looked up using the -*programs* resource, an *orgUnit* which can be looked up using the -*organisationUnits* resource, and a list of valid data element -identifiers which can be looked up using the *dataElements* resource. -For events with registration, a *tracked entity instance* identifier is -required, read about how to get this in the section about the -*trackedEntityInstances* resource. For sending events to programs with -multiple stages, you will need to also include the *programStage* -identifier, the identifiers for programStages can be found in the -*programStages* resource. - -A simple single event with no registration example payload in XML format -where we send events from the "Inpatient morbidity and mortality" -program for the "Ngelehun CHC" facility in the demo database can be seen -below: - -```xml - - - - - - - - - -``` - -To perform some testing we can save the XML payload as a file -called *event.xml* and send it as a POST request to the events resource -in the API using curl with the following command: - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -The same payload in JSON format looks like this: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -To send this you can save it to a file called *event.json* and use curl -like this: - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -We also support sending multiple events at the same time. A payload in -XML format might look like this: - -```xml - - - - - - - - - - - - - - - - - -``` - -You will receive an import summary with the response which can be -inspected in order to get information about the outcome of the request, -like how many values were imported successfully. The payload in JSON -format looks like this: - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -You can also use GeoJson to store any kind of geometry on your event. An example payload using GeoJson instead of the former latitude and longitude properties can be seen here: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -As part of the import summary you will also get the identifier -*reference* to the event you just sent, together with a *href* element -which points to the server location of this event. The table below -describes the meaning of each element. - - - -Table: Events resource format - -| Parameter | Type | Required | Options (default first) | Description | -|---|---|---|---|---| -| program | string | true || Identifier of the single event with no registration program | -| orgUnit | string | true || Identifier of the organisation unit where the event took place | -| eventDate | date | true || The date of when the event occurred | -| completedDate | date | false || The date of when the event is completed. If not provided, the current date is selected as the event completed date | -| status | enum | false | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Whether the event is complete or not | -| storedBy | string | false | Defaults to current user | Who stored this event (can be username, system-name, etc) | -| coordinate | double | false || Refers to where the event took place geographically (latitude and longitude) | -| dataElement | string | true || Identifier of data element | -| value | string | true || Data value or measure for this event | - -##### OrgUnit matching { #orgunit-matching } - -By default the orgUnit parameter will match on the -ID, you can also select the orgUnit id matching scheme by using the -parameter orgUnitIdScheme=SCHEME, where the options are: *ID*, *UID*, -*UUID*, *CODE*, and *NAME*. There is also the *ATTRIBUTE:* scheme, which -matches on a *unique* metadata attribute value. - -#### Updating events { #webapi_updating_events } - -To update an existing event, the format of the payload is the same, but -the URL you are posting to must add the identifier to the end of the URL -string and the request must be PUT. - -The payload has to contain all, even non-modified, attributes. -Attributes that were present before and are not present in the current -payload any more will be removed by the system. - -It is not allowed to update an already deleted event. The same applies -to tracked entity instance and enrollment. - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### Deleting events { #webapi_deleting_events } - -To delete an existing event, all you need is to send a DELETE request -with an identifier reference to the server you are using. - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### Assigning user to events { #webapi_user_assign_event } - -A user can be assigned to an event. This can be done by including the appropriate property in the payload when updating or creating the event. - - "assignedUser": "" - -The id refers to the if of the user. Only one user can be assigned to an event at a time. - -User assignment must be enabled in the program stage before users can be assigned to events. -#### Getting events { #webapi_getting_events } - -To get an existing event you can issue a GET request including the -identifier like this: - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### Querying and reading events { #webapi_querying_reading_events } - -This section explains how to read out the events that have been stored -in the DHIS2 instance. For more advanced uses of the event data, please -see the section on event analytics. The output format from the -`/api/events` endpoint will match the format that is used to send events -to it (which the analytics event api does not support). Both XML and -JSON are supported, either through adding .json/.xml or by setting the -appropriate *Accept* header. The query is paged by default and the -default page size is 50 events, *field* filtering works as it does for -metadata, add the *fields* parameter and include your wanted properties, -i.e. *?fields=program,status*. - - - -Table: Events resource query parameters - -| Key | Type | Required | Description | -|---|---|---|---| -| program | identifier | true (if not programStage is provided) | Identifier of program | -| programStage | identifier | false | Identifier of program stage | -| programStatus | enum | false | Status of event in program, ca be ACTIVE | COMPLETED | CANCELLED | -| followUp | boolean | false | Whether event is considered for follow up in program, can be true | false or omitted. | -| trackedEntityInstance | identifier | false | Identifier of tracked entity instance | -| orgUnit | identifier | true | Identifier of organisation unit | -| ouMode | enum | false | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| startDate | date | false | Only events newer than this date | -| endDate | date | false | Only events older than this date | -| status | enum | false | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | date | false | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | date | false | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | string | false | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta | boolean | false | Exclude the meta data part of response (improves performance) | -| page | integer | false | Page number | -| pageSize | integer | false | Number of items in each page | -| totalPages | boolean | false | Indicates whether to include the total number of pages in the paging response. | -| skipPaging | boolean | false | Indicates whether to skip paging in the query and return all events. | -| dataElementIdScheme | string | false | Data element ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme | string | false | Category Option Combo ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| orgUnitIdScheme | string | false | Organisation Unit ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programIdScheme | string | false | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programStageIdScheme | string | false | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| idScheme | string | false | Allows to set id scheme for data element, category option combo, orgUnit, program and program stage at once. | -| order | string | false | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| event | comma delimited string | false | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | boolean | false | Skips event identifiers in the response | -| attributeCc (\*\*) | string | false | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | string | false | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | false | true | false | Indicates whether the import should be done asynchronous or synchronous. | -| includeDeleted | boolean | false | When true, soft deleted events will be included in your query result. | -| assignedUserMode | enum | false | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | comma delimited strings | false | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> **Note** -> -> If the query contains neither `attributeCC` nor `attributeCos`, the server returns events for all attribute option combos where the user has read access. - -##### Examples { #examples } - -Query for all events with children of a certain organisation unit: - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -Query for all events with all descendants of a certain organisation -unit, implying all organisation units in the sub-hierarchy: - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -Query for all events with a certain program and organisation unit: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -Query for all events with a certain program and organisation unit, -sorting by due date - ascending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -Query for the 10 events with the newest event date in a certain program -and organisation unit - by paging and ordering by due date descending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &order=eventDate:desc&pageSize=10&page=1 - -Query for all events with a certain program and organisation unit for a -specific tracked entity instance: - - /api/33/events.json?orgUnit=DiszpKrYNg8 - &program=eBAyeGv0exc&trackedEntityInstance=gfVxE3ALA9m - -Query for all events with a certain program and organisation unit older -or equal to - 2014-02-03: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -Query for all events with a certain program stage, organisation unit and -tracked entity instance in the year 2014: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &trackedEntityInstance=gfVxE3ALA9m&startDate=2014-01-01&endDate=2014-12-31 - -Query files associated with event data values. In the specific case of fetching an image file an -additional parameter can be provided to fetch the image with different dimensions. If dimension is -not provided, the system will return the original image. The parameter will be ignored in case of -fetching non-image files e.g pdf. Possible dimension values are *small(254 x 254), -medium(512 x 512), large(1024 x 1024) or original*. Any value other than those mentioned will be -discarded and the original image will be returned. - - /api/33/events/files?eventUid=hcmcWlYkg9u&dataElementUid=C0W4aFuVm4P&dimension=small - -Retrieve events with specified Organisation unit and Program, and use _Attribute:Gq0oWTf2DtN_ as -identifier scheme - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for -orgUnits, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as identifier -scheme for the rest of the metadata with assigned attribute. - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=Code - -#### Event grid query { #event-grid-query } - -In addition to the above event query end point, there is an event grid -query end point where a more compact "grid" format of events are -returned. This is possible by interacting with -/api/events/query.json|xml|xls|csv endpoint. - - /api/33/events/query - -Most of the query parameters mentioned in event querying and reading -section above are valid here. However, since the grid to be returned -comes with specific set of columns that apply to all rows (events), it -is mandatory to specify a program stage. It is not possible to mix -events from different programs or program stages in the return. - -Returning events from a single program stage, also opens up for new -functionality - for example sorting and searching events based on their -data element values. api/events/query has support for this. Below are -some examples - -A query to return an event grid containing only selected data elements -for a program stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &dataElement=qrur9Dvnyt5,fWIAEtYVEGk,K6uUAvq500H&order=lastUpdated:desc - &pageSize=50&page=1&totalPages=true - -A query to return an event grid containing all data elements of a -program - stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &includeAllDataElements=true - -A query to filter events based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50 - -In addition to the filtering, the above example also illustrates one -thing: the fact that there are no data elements mentioned to be returned -in the grid. When this happens, the system defaults back to return only -those data elements marked "Display in report" under program stage -configuration. - -We can also extend the above query to return us a grid sorted (asc|desc) -based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50&order=qrur9Dvnyt5:desc - -#### Event filters { #webapi_event_filters } - -To create, read, update and delete event filters you -can interact with the `/api/eventFilters` resource. - - /api/33/eventFilters - -##### Create and update an event filter definition { #create-and-update-an-event-filter-definition } - -For creating and updating an event filter in the -system, you will be working with the *eventFilters* -resource. *POST* is used to create and *PUT* method is used to update. The event filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Request Payload - -| Request Property | Description | Example | -|---|---|---| -| name | Name of the filter. | "name":"My working list" | -| description | A description of the filter. | "description":"for listing all events assigned to me". | -| program | The uid of the program. | "program" : "a3kGcGDCuk6" | -| programStage | The uid of the program stage. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Object containing parameters for querying, sorting and filtering events. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Table: Event Query Criteria definition - -|||| -|---|---|---| -| followUp | Used to filter events based on enrollment followUp flag. Possible values are true|false. | "followUp": true | -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | To specify the output ordering of columns | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| dataFilters | To specify filters to be applied when listing events | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| status | Any valid EventStatus | "eventStatus": "COMPLETED" | -| events | To specify list of events | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod object date filtering based on completed date. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod object date filtering based on due date. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -The available assigned user selection modes are explained in the -following table. - - - -Table: Assigned user selection modes (event assignment) - -| Mode | Description | -|---|---| -| CURRENT | Assigned to the current logged in user | -| PROVIDED | Assigned to the users provided in the "assignedUser" parameter | -| NONE | Assigned to no users. | -| ANY | Assigned to any users. | - -A sample payload that can be used to create/update an eventFilter is shown below. - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### Retrieving and deleting event filters { #retrieving-and-deleting-event-filters } - -A specific event filter can be retrieved by using the following api - - GET /api/33/eventFilters/{uid} - -All event filters can be retrieved by using the following api. - - GET /api/33/eventFilters?fields=* - -All event filters for a specific program can be retrieved by using the following api - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -An event filter can be deleted by using the following api - - DELETE /api/33/eventFilters/{uid} - -### Relationships { #relationships } -Relationships are links between two entities in tracker. These entities can be tracked entity instances, enrollments and events. - -There are multiple endpoints that allow you to see, create, delete and update relationships. The most common is the /api/trackedEntityInstances endpoint, where you can include relationships in the payload to create, update or deleting them if you omit them - Similar to how you work with enrollments and events in the same endpoint. All the tracker endpoints, /api/trackedEntityInstances, /api/enrollments and /api/events also list their relationships if requested in the field filter. - -The standard endpoint for relationships is, however, /api/relationships. This endpoint provides all the normal CRUD operations for relationships. - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -This request will return a list of any relationship you have access to see that includes the trackedEntityInstance, enrollment or event you specified. Each relationship is represented with the following JSON: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -You can also view specified relationships using the following endpoint: - - GET /api/relationships/ - -To create or update a relationship, you can use the following endpoints: - - POST /api/relationships - PUT /api/relationships - -And use the following payload structure: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -To delete a relationship, you can use this endpoint: - - DELETE /api/relationships/ - -In our example payloads, we use a relationship between trackedEntityInstances. Because of this, the "from" and "to" properties of our payloads include "trackedEntityInstance" objects. If your relationship includes other entities, you can use the following properties: - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### Update strategies { #webapi_tei_update_strategies } - -Two update strategies for all 3 tracker endpoints are supported: -enrollment and event creation. This is useful when you have generated an -identifier on the client side and are not sure if it was created or not -on the server. - - - -Table: Available tracker strategies - -| Parameter | Description | -|---|---| -| CREATE | Create only, this is the default behavior. | -| CREATE_AND_UPDATE | Try and match the ID, if it exist then update, if not create. | - -To change the parameter, please use the strategy parameter: - - POST /api/33/trackedEntityInstances?strategy=CREATE_AND_UPDATE - -### Tracker bulk deletion { #webapi_tracker_bulk_deletion } - -Bulk deletion of tracker objects work in a similar fashion to adding and -updating tracker objects, the only difference is that the -`importStrategy` is *DELETE*. - -*Example: Bulk deletion of tracked entity instances:* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*Example: Bulk deletion of enrollments:* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*Example: Bulk deletion of events:* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### Identifier reuse and item deletion via POST and PUT methods { #webapi_updating_and_deleting_items } - -Tracker endpoints */trackedEntityInstances*, */enrollments*, */events* -support CRUD operations. The system keeps track of used identifiers. -Therefore, an item which has been created and then deleted (e.g. events, -enrollments) cannot be created or updated again. If attempting to delete -an already deleted item, the system returns a success response as -deletion of an already deleted item implies no change. - -The system does not allow to delete an item via an update (*PUT*) or -create (*POST*) method. Therefore, an attribute *deleted* is ignored in -both *PUT* and *POST* methods, and in *POST* method it is by default set -to *false*. - -### Import parameters { #webapi_import_parameters } - -The import process can be customized using a set of import parameters: - - - -Table: Import parameters - -| Parameter | Values (default first) | Description | -|---|---|---| -| dataElementIdScheme | id | name | code | attribute:ID | Property of the data element object to use to map the data values. | -| orgUnitIdScheme | id | name | code | attribute:ID | Property of the org unit object to use to map the data values. | -| idScheme | id | name | code| attribute:ID | Property of all objects including data elements, org units and category option combos, to use to map the data values. | -| dryRun | false | true | Whether to save changes on the server or just return the import summary. | -| strategy | CREATE | UPDATE | CREATE_AND_UPDATE | DELETE | Save objects of all, new or update import status on the server. | -| skipNotifications | true | false | Indicates whether to send notifications for completed events. | -| skipFirst | true | false | Relevant for CSV import only. Indicates whether CSV file contains a header row which should be skipped. | -| importReportMode | FULL, ERRORS, DEBUG | Sets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes *ObjectReports* for object which has errors. `FULL` returns an *ObjectReport* for all objects imported, and `DEBUG` returns the same plus a name for the object (if available). | - -#### CSV Import / Export { #webapi_events_csv_import_export } - -In addition to XML and JSON for event import/export, in DHIS2.17 we -introduced support for the CSV format. Support for this format builds on -what was described in the last section, so here we will only write about -what the CSV specific parts are. - -To use the CSV format you must either use the `/api/events.csv` -endpoint, or add *content-type: text/csv* for import, and *accept: -text/csv* for export when using the `/api/events` endpoint. - -The order of column in the CSV which are used for both export and import -is as follows: - - - -Table: CSV column - -| Index | Key | Type | Description | -|---|---|---|---| -| 1 | event | identifier | Identifier of event | -| 2 | status | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | program | identifier | Identifier of program | -| 4 | programStage | identifier | Identifier of program stage | -| 5 | enrollment | identifier | Identifier of enrollment (program instance) | -| 6 | orgUnit | identifier | Identifier of organisation unit | -| 7 | eventDate | date | Event date | -| 8 | dueDate | date | Due Date | -| 9 | latitude | double | Latitude where event happened | -| 10 | longitude | double | Longitude where event happened | -| 11 | dataElement | identifier | Identifier of data element | -| 12 | value | string | Value / measure of event | -| 13 | storedBy | string | Event was stored by (defaults to current user) | -| 14 | providedElsewhere | boolean | Was this value collected somewhere else | -| 14 | completedDate | date | Completed date of event | -| 14 | completedBy | string | Username of user who completed event | - -*Example of 2 events with 2 different data value - each:* - -```csv -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,1,, -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,2,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,3,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,4,, -``` - -#### Import strategy: SYNC { #webapi_sync_import_strategy } - -The import strategy SYNC should be used only by internal synchronization -task and not for regular import. The SYNC strategy allows all 3 -operations: CREATE, UPDATE, DELETE to be present in the payload at the -same time. - -### Tracker Ownership Management { #webapi_tracker_ownership_management } - -A new concept called Tracker Ownership is introduced from 2.30. There -will now be one owner organisation unit for a tracked entity instance in -the context of a program. Programs that are configured with an access -level of *PROTECTED* or *CLOSED* will adhere to the ownership -privileges. Only those users belonging to the owning org unit for a -tracked entity-program combination will be able to access the data -related to that program for that tracked entity. - -#### Tracker Ownership Override : Break the Glass { #webapi_tracker_ownership_override_api } - -It is possible to temporarily override this ownership privilege for a -program that is configured with an access level of *PROTECTED*. Any user -will be able to temporarily gain access to the program related data, if -the user specifies a reason for accessing the tracked entity-program -data. This act of temporarily gaining access is termed as *breaking the -glass*. Currently, the temporary access is granted for 3 hours. DHIS2 -audits breaking the glass along with the reason specified by the user. -It is not possible to gain temporary access to a program that has been -configured with an access level of *CLOSED*. To break the glass for a -tracked entity program combination, you can issue a POST request as -shown: - - /api/33/tracker/ownership/override?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care - -#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer_api } - -It is possible to transfer the ownership of a tracked entity-program -from one org unit to another. This will be useful in case of patient -referrals or migrations. Only an owner (or users who have broken the -glass) can transfer the ownership. To transfer ownership of a tracked -entity-program to another organisation unit, you can issue a PUT request -as shown: - - /api/33/tracker/ownership/transfer?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&ou=EJNxP3WreNP - - -## Potential Duplicates { #potential-duplicates } - -Potential duplicates are records we work with in the data deduplication feature. Due to the nature of the deduplication feature, this API endpoint is somewhat restricted. - -A potential duplicate represents a pair of records which are suspected to be a duplicate. - -The payload of a potential duplicate looks like this: - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -You can retrieve a list of potential duplicates using the following endpoint: - - GET /api/potentialDuplicates - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| teis | List of tracked entity instances | List of string (separated by comma)| existing tracked entity instance id | -| status | Potential duplicate status | string | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Status code | Description -|---|---| -| 400 | Invalid input status - -You can inspect individual potential duplicate records: - - GET /api/potentialDuplicates/ - -| Status code | Description -|---|---| -| 404 | Potential duplicate not found - -To create a new potential duplicate, you can use this endpoint: - - POST /api/potentialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Status code | Description -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -To update a potential duplicate status: - - PUT /api/potentialDuplicates/ - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| status | Potential duplicate status | string | `OPEN`, `INVALID`, `MERGED` | - -| Status code | Description -|---|---| -| 400 | You can't update a potential duplicate to MERGED as this is possible only by a merging request -| 400 | You can't update a potential duplicate that is already in a MERGED status - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -To merge a Potential Duplicate, or the two tracked entity instances the Potential Duplicate represents, the following endpoint can be used: - - POST /api/potentialDuplicates//merge - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| mergeStrategy | Strategy to use for merging the potentialDuplicate | enum | AUTO(default) or MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- The same attribute has different values in each tracked entity instance -- Both tracked entity instances are enrolled in the same program -- Tracked entity instances have different types - -If any conflict is encountered, an errormessage is returned to the user. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -When requesting an automatic merge like this, a payload is not required and will be ignored. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Relationship cannot be between the original and the duplicate (This results in an invalid self-referencing relationship) -- Relationship cannot be of the same type and to the same object in both tracked entity instances (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) - -There are two ways to do a manual merge: With and without a payload. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -Otherwise, if a manual merge is requested with a payload, the payload refers to what data should be moved from the duplicate to the original. The payload looks like this: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -The fields are explained in the following table. - - -Table: Program Notification Template payload - -| Field | Required | Description | Values | -|---|---|---|---| -| name | Yes | name of Program Notification Template | case-notification-alert | -| notificationTrigger | Yes | When notification should be triggered. Possible values are ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| ENROLLMENT | -| subjectTemplate | No | Subject template string | Case notification V{org_unit_name} | -| messageTemplate | Yes | Message template string | Case notification A{h5FuguPFF2j} | -| notificationRecipient | YES | Who is going to receive notification. Possible values are USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | No | Which channel should be used for this notification. It can be either SMS, EMAIL or HTTP | SMS | -| sendRepeatable | No | Whether notification should be sent multiple times | false | - -NOTE: WEB_HOOK notificationRecipient is used only to POST http request to an external system. Make sure to choose HTTP delivery channel when using WEB_HOOK. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -The list of Program Notification Templates can be retrieved using GET. - - GET /api/programNotificationTemplates - -For one particular Program Notification Template. - - GET /api/33/programNotificationTemplates/{uid} - -To get filtered list of Program Notification Templates - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Program Notification Template can be deleted using DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -Program message lets you send messages to tracked entity instances, -contact addresses associated with organisation units, phone numbers and -email addresses. You can send messages through the `messages` resource. - - /api/33/messages - -### Sending program messages { #sending-program-messages } - -Program messages can be sent using two delivery channels: - - - SMS (SMS) - - - Email address (EMAIL) - -Program messages can be sent to various recipients: - - - Tracked entity instance: The system will look up attributes of value - type PHONE_NUMBER or EMAIL (depending on the specified delivery - channels) and use the corresponding attribute values. - - - Organisation unit: The system will use the phone number or email - information registered for the organisation unit. - - - List of phone numbers: The system will use the explicitly defined - phone numbers. - - - List of email addresses: The system will use the explicitly defined - email addresses. - -Below is a sample JSON payload for sending messages using POST requests. -Note that message resource accepts a wrapper object named -`programMessages` which can contain any number of program messages. - - POST /api/33/messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -The fields are explained in the following table. - - - -Table: Program message payload - -| Field | Required | Description | Values | -|---|---|---|---| -| recipients | Yes | Recipients of the program message. At least one recipient must be specified. Any number of recipients / types can be specified for a message. | Can be trackedEntityInstance, organisationUnit, an array of phoneNumbers or an array of emailAddresses. | -| programInstance | Either this or programStageInstance required | The program instance / enrollment. | Enrollment ID. | -| programStageInstance | Either this or programInstance required | The program stage instance / event. | Event ID. | -| deliveryChannels | Yes | Array of delivery channels. | SMS | EMAIL | -| subject | No | The message subject. Not applicable for SMS delivery channel. | Text. | -| text | Yes | The message text. | Text. | -| storeCopy | No | Whether to store a copy of the program message in DHIS2. | false (default) | true | - -A minimalistic example for sending a message over SMS to a tracked -entity instance looks like this: - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### Retrieving and deleting program messages { #retrieving-and-deleting-program-messages } - -The list of messages can be retrieved using GET. - - GET /api/33/messages - -To get the list of sent tracker messages, the below endpoint can be used. ProgramInstance or ProgramStageInstance uid has to be provided. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -To get the list of all scheduled message - - GET /api/33/messages/scheduled - GET /api/33/messages/scheduled?scheduledAt=2020-12-12 - -One particular message can also be retrieved using GET. - - GET /api/33/messages/{uid} - -Message can be deleted using DELETE. - - DELETE /api/33/messages/{uid} - - -### Querying program messages { #querying-program-messages } - -The program message API supports program message queries based on -request parameters. Messages can be filtered based on below mentioned -query parameters. All requests should use the GET HTTP verb for -retrieving information. - - - -Table: Query program messages API - -| Parameter | URL | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # Email { #email } diff --git a/projects/dhis2-single-page-docs/cs/.cache_timestamp b/projects/dhis2-single-page-docs/cs/.cache_timestamp index f71ec932f..278776bf1 100644 --- a/projects/dhis2-single-page-docs/cs/.cache_timestamp +++ b/projects/dhis2-single-page-docs/cs/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:27:02Z \ No newline at end of file +2024-06-04T21:27:05Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index da543b3ea..f5fe4446d 100644 --- a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2023-01-13' tags: -- DHIS core verze 2.37 - Vývoj +- DHIS core verze 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index a6375340f..734e999fa 100644 --- a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index 0ef20c81a..b118ea9d9 100644 --- a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 946fa83f1..ce893996e 100644 --- a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 55cafbfe3..7d119e47f 100644 --- a/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/cs/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - Vývoj - Hlavní verze jádra DHIS @@ -12120,7 +12120,7 @@ Tabulka: Parametry dotazu pouze pro analýzu dotazů událostí | Parametr dotazu | Požadované | Popis | Možnosti | |---|---|---|---| -| ouMode | Ne | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | Ne | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Ne | Dimenze, které mají být seřazeny vzestupně, mohou odkazovat na datum události, název a kód organizační jednotky a jakékoli identifikátory položek. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Ne | Dimenze, které mají být seřazeny sestupně, mohou odkazovat na datum události, název a kód organizační jednotky a jakékoli identifikátory položek. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | Ne | Zda se mají vrátit pouze události, které mají souřadnice. | false | true | @@ -13012,7 +13012,7 @@ Tabulka: Parametry dotazu pro koncový bod dotazu registrace | filtr | Ne | Identifikátor dimenze zahrnující datové prvky, atributy, období, organizační jednotky a sady skupin organizačních jednotek. Parametr lze opakovat libovolněkrát. Filtry položek lze použít na dimenzi ve formátu : : . Hodnoty filtru nerozlišují malá a velká písmena. || | programStatus | Ne | Zadejte stav zápisu zápisů, které chcete zahrnout. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | řetězec | Ne | Identifikátor data, např.: "2016-01-01". Přepíše počáteční datum relativního období | -| ouMode | Ne | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | Ne | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Ne | Dimenze, které mají být seřazeny vzestupně, mohou odkazovat na datum registrace, datum incidentu, název a kód organizační jednotky. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Ne | Dimenze, které mají být seřazeny sestupně, mohou odkazovat na datum registrace, datum incidentu, název a kód organizační jednotky. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | Ne | Zda se mají vrátit pouze zápisy, které mají souřadnice. | false | true | @@ -17685,20 +17685,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Objekty Trasovače { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17801,7 +17802,6 @@ point out any exceptional cases between these two. | program | Pouze pro čtení dat. Typ programu, který má registrace, která událost vlastní. | Ne | Ano | String:Uid | ABCDEF12345 | | trackedEntity | Pouze pro čtení dat. Trasovaná entita, která událost vlastní. ***Neplatí pro `PROGRAM AKCE`*** | Ne | Ne | String:Uid | ABCDEF12345 | | status | Stav události. AKTIVNÍ, pokud není součástí dodávky. | Ne | Ne | Výčet | AKTIVNÍ, DOKONČENÉ, NAVŠTÍVENÉ, PLÁNOVANÉ, PO TERMÍNU, PŘESKOČENO | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | Ne | Ne | Výčet | AKTIVNÍ, DOKONČENO, ZRUŠENO | | orgUnit | Organizační jednotka, kde uživatel zaregistroval událost. | Ano | Ne | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | Ne | Ano | Date:ISO 8601 | RRRR-MM-DDThh:mm:ss | | createdAtClient | Časové razítko, kdy uživatel vytvořil událost na klientovi | Ne | Ne | Date:ISO 8601 | RRRR-MM-DDThh:mm:ss | @@ -17861,9 +17861,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Atributy { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Vlastnictví | Popis | Požadované | Neměnný | Typ | Příklad | |---|---|---|---|---|---| @@ -17878,18 +17880,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -Zatímco `Attributes` popisuje `trasovanou entitu` nebo `zápis`, `datové hodnoty` popisují `událost`. Hlavní rozdíl spočívá v tom, že `atributy` mohou mít pro danou `trasovanou entitu` pouze jednu hodnotu. Naproti tomu `datové hodnoty` mohou mít mnoho různých hodnot pro různé `události` - i když všechny `události` patří ke stejnému `zápisu` nebo `trasované entitě`. +While attributes describe a tracked entity, data values describe an event. | Vlastnictví | Popis | Požadované | Neměnný | Typ | Příklad | |---|---|---|---|---|---| @@ -17904,31 +17908,31 @@ Zatímco `Attributes` popisuje `trasovanou entitu` nebo `zápis`, `datové hodno > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Poznámky { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -17939,10 +17943,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -17984,92 +17988,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Tabulka: Datový obsah - -| Hodnoty datového obsahu | Popis | Příklad | -|---|---|---| -| název | Name of the working list. Required. || -| popis | A description of the working list. || -| program | Objekt obsahující id programu. Požadované. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Popis | Příklad | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| řazení | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Import trackeru (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -18078,9 +17997,9 @@ to import i.e. create, update and delete * **Zápisy** * **Události** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -18113,7 +18032,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -18513,7 +18432,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Souhrn importu { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -18959,7 +18878,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Kódy chyb { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -19089,7 +19008,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | Nedostupné | Nedefinovaná chybová zpráva. | -### Ověření { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -19099,7 +19018,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -19124,8 +19043,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -19178,7 +19097,7 @@ Some examples of configurable validations: Tyto konfigurace dále změní způsob provádění ověřování během importu. -### Pravidla programu { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -19234,7 +19153,7 @@ information about side effects can be found in the following section. > > Programová pravidla lze během importu přeskočit pomocí parametru `skipProgramRules`. -### Vedlejší účinky { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -19256,7 +19175,7 @@ V současné době jsou podporovány následující vedlejší účinky: > > Určité konfigurace mohou řídit provádění vedlejších účinků. Během importu lze nastavit příznak `skipSideEffects`, aby se vedlejší efekty zcela vynechaly. Tento parametr může být užitečný, pokud například importujete něco, na co nechcete spouštět upozornění. -### Přiřadit uživatele k událostem { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -19290,7 +19209,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -19342,9 +19261,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -19424,8 +19343,8 @@ Koncový bod vrátí seznam trasovaných entit, které odpovídají parametrům |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -19529,7 +19448,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19791,8 +19710,8 @@ Vrátí seznam událostí na základě filtrů. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| |`program`|`String`|`uid`| Identifikátor programu| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -19996,8 +19915,8 @@ Vrátí seznam událostí na základě poskytnutých filtrů. |`followUp`|`boolean`| `true`|`false` | Zda je událost zvažována pro pokračování v programu. Výchozí hodnota je `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifikátor organizační jednotky| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Stav události| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filtrujte události, které nastaly po tomto datu.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filtrujte události, které nastaly do tohoto data.| @@ -20292,13 +20211,13 @@ Následující pravidla platí pro parametry dotazu. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Sdílení metadat { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -20344,7 +20263,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -20413,13 +20332,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -20431,7 +20350,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Přepsání vlastnictví trasovače: Rozbijte sklo { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -20444,7 +20363,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Převod vlastnictví trasovače { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -20454,7 +20373,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Úroveň přístupu { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -20484,7 +20403,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -20500,2747 +20419,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Tabulka: Datový obsah -|Objekt trasování|Dříve|Nyní| +| Hodnoty datového obsahu | Popis | Příklad | |---|---|---| -|**Atribut**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Zápis**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Událost**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Poznámka**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Vztah**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Dříve|Nyní| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribute`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes`|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Odebráno – zastaralé, viz
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus`|`enrollmentStatus`| -|`query`|Removed - use `filter` instead| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Dříve|Nyní| -|---|---| -|`enrollment`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus`|`status`| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Dříve|Nyní| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`event`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`lastUpdated`|Odebráno - zastaralé, viz:
  • `01cupdatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus`|`enrollmentStatus`| -|`skipEventId`|Removed| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Dříve|Nyní| -|---|---| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity`| - -## Web API Trasovače { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### Správa instance trasované entity { #webapi_tracked_entity_instance_management } - -Tracked entity instances have full CRUD support in the API. Together -with the API for enrollment most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/trackedEntityInstances - -#### Vytváření nové instance trasované entity { #webapi_creating_tei } - -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -The field "geometry" accepts a GeoJson object, where the type of the -GeoJson have to match the featureType of the TrackedEntityType -definition. An example GeoJson object looks like this: - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +| název | Name of the working list. Required. || +| popis | A description of the working list. || +| program | Objekt obsahující id programu. Požadované. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Table: Program Stage Query Criteria - /api/trackedEntityInstances +| Criteria values | Popis | Příklad | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| řazení | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +See an example payload below: ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -Chcete-li to odeslat na server, můžete použít příkaz cURL takto: - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -To create multiple instances in one request you can wrap the payload in -an outer array like this and POST to the same resource as above:[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -The system does not allow the creation of a tracked entity instance -(as well as enrollment and event) with a UID that was already used in -the system. That means that UIDs cannot be reused. - -#### Aktualizace instance trasované entity { #webapi_updating_tei } - -For updating a tracked entity instance, the payload is equal to the -previous section. The difference is that you must use the HTTP *PUT* -method for the request when sending the payload. You will also need to -append the person identifier to the *trackedEntityInstances* resource in -the URL like this, where `` should -be replaced by the identifier of the tracked entity instance: - - /api/trackedEntityInstances/ - -The payload has to contain all, even non-modified, attributes and -relationships. Attributes or relationships that were present before and -are not present in the current payload any more will be removed from the -system. This means that if attributes/relationships are empty in the -current payload, all existing attributes/relationships will be deleted -from the system. From 2.31, it is possible to ignore empty -attributes/relationships in the current payload. A request parameter of -`ignoreEmptyCollection` set to `true` can be used in case you do not -wish to send in any attributes/relationships and also do not want them -to be deleted from the system. - -It is not allowed to update an already deleted tracked entity instance. -Also, it is not allowed to mark a tracked entity instance as deleted via -an update request. The same rules apply to enrollments and events. - -#### Odstranění instance trasované entity { #webapi_deleting_tei } - -In order to delete a tracked entity instance, make a request to the URL -identifying the tracked entity instance with the *DELETE* -method. The URL is equal to the one above used for update. - -#### Vytvářejte a zapisujte instance trasovaných entit { #webapi_create_enroll_tei } - -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Kompletní příklad datového obsahu včetně: instance trasované entity, registrace a události { #webapi_create_enroll_tei_create_event } - -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "cejWyOfXge6", - "value": "Male" - } - ], - "enrollments": [ - { - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollmentDate": "2017-09-15", - "incidentDate": "2017-09-15", - "events": [ - { - "program": "ur1Edk5Oe2n", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2017-10-17", - "status": "COMPLETED", - "storedBy": "admin", - "programStage": "EPEcjy3FWmI", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "ur1Edk5Oe2n", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2017-10-17", - "status": "COMPLETED", - "storedBy": "admin", - "programStage": "EPEcjy3FWmI", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } - ] - } - ] + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ + { + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Vygenerované atributy instance trasované entity { #webapi_generate_tei_attributes } - -Tracked entity instance attributes that are using automatic generation of -unique values have three endpoints that are used by apps. The endpoints -are all used for generating and reserving values. - -In 2.29 we introduced TextPattern for defining and generating these -patterns. All existing patterns will be converted to a valid TextPattern -when upgrading to 2.29. - -> **Note** -> -> As of 2.29, all these endpoints will require you to include any -> variables reported by the `requiredValues` endpoint listed as -> required. Existing patterns, consisting of only `#`, will be upgraded -> to the new TextPattern syntax `RANDOM()`. The RANDOM -> segment of the TextPattern is not a required variable, so this -> endpoint will work as before for patterns defined before 2.29. - -##### Nalezení požadovaných hodnot { #finding-required-values } - -A TextPattern can contain variables that change based on different -factors. Some of these factors will be unknown to the server, so the -values for these variables have to be supplied when generating and -reserving values. - -This endpoint will return a map of required and optional values, that -the server will inject into the TextPattern when generating new values. -Required variables have to be supplied for the generation, but optional -variables should only be supplied if you know what you are doing. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### Generovat koncový bod hodnoty { #webapi_generate_values } - -Online web apps and other clients that want to generate a value that -will be used right away can use the simple generate endpoint. This -endpoint will generate a value that is guaranteed to be unique at the -time of generation. The value is also guaranteed not to be reserved. As -of 2.29, this endpoint will also reserve the value generated for 3 days. - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### Generovat a rezervovat koncový bod hodnoty { #webapi_generate_reserve_values } - -The generate and reserve endpoint is used by offline clients that need -to be able to register tracked entities with unique ids. They will -reserve a number of unique ids that this device will then use when -registering new tracked entity instances. The endpoint is called to -retrieve a number of tracked entity instance reserved values. An -optional parameter numberToReserve specifies how many ids to generate -(default is 1). - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -Similar to the /generate endpoint, this endpoint can also specify the -expiration time in the same way. By adding the `?expiration=` -you can override the default 60 days. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### Rezervované hodnoty { #reserved-values } - -Reserved values are currently not accessible through the api, however, they -are returned by the `generate` and `generateAndReserve` endpoints. The -following table explains the properties of the reserved value object: - -##### - - - -Tabulka: Rezervované hodnoty - -| Vlastnictví | Popis | -|---|---| -| ownerObject | Typ metadat odkazovaný při generování a rezervaci hodnoty. V současné době je podporován pouze TRACKEDENTITYATTRIBUTE. | -| ownerUid | Uid objektu metadat odkazovaného při generování a rezervaci hodnoty. | -| key | Částečně generovaná hodnota, kde generované segmenty ještě nejsou přidány. | -| value | Plně vyřešená hodnota vyhrazena. Toto je hodnota, kterou odesíláte na server při ukládání dat. | -| created | Časové razítko, kdy byla rezervace provedena | -| expiryDate | Časové razítko, kdy rezervace již nebude rezervována | - -Expired reservations are removed daily. If a pattern changes, values -that were already reserved will be accepted when storing data, even if -they don't match the new pattern, as long as the reservation has not -expired. - -#### Atributy obrázku { #image-attributes } - -Working with image attributes is a lot like working with file data -values. The value of an attribute with the image value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///image` -endpoint will return the actual image. The optional height and width -parameters can be used to specify the dimensions of the image. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### Dotaz na instanci trasované entity { #webapi_tracked_entity_instance_query } - -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. - - /api/33/trackedEntityInstances - -##### Požádat o syntaxi { #webapi_tei_query_request_syntax } - - - -Tabulka: Parametry dotazu instancí trasovaných entit - -| Parametr dotazu | Popis | -|---|---| -| filtr | Atributy, které se mají použít jako filtr pro dotaz. Parametr lze opakovat libovolněkrát. Filtry lze použít na rozměr ve formátu ::[::]. Hodnoty filtru nerozlišují velká a malá písmena a lze je spolu s operátorem opakovat libovolněkrát. Operátory mohou být EQ | GT | GE | LT | LE | NE | LIKE | V. | -| ou | Identifikátory organizační jednotky oddělené „;“. | -| ouMode | Režim výběru organizačních jednotek lze SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Výchozí hodnota je SELECTED, což se týká pouze vybraných vybraných organizačních jednotek. Vysvětlení viz tabulka níže. | -| program | Identifikátor programu. Omezuje instance na přihlášení do daného programu. | -| programStatus | Stav instance pro daný program. Může být AKTIVNÍ | DOKONČENO | ZRUŠENO. | -| followUp | Sledovat stav instance pro daný program. Může to být true | false nebo omitted. | -| programStartDate | Datum zahájení zápisu v daném programu pro instanci trasované entity. | -| programEndDate | Datum ukončení zápisu v daném programu pro instanci trasované entity. | -| trackedEntity | Identifikátor trasované entity. Omezuje instance na daný typ trasované instance. | -| strana | Číslo stránky. Výchozí stránka je 1. | -| pageSize | Velikost stránky. Výchozí velikost je 50 řádků na stránku. | -| totalPages | Označuje, zda se má do odpovědi stránkování zahrnout celkový počet stránek (znamená delší dobu odezvy). | -| skipPaging | Označuje, zda má být stránkování ignorováno a mají být vráceny všechny řádky. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Označuje, zda zahrnout měkké odstraněné TEI nebo ne. Ve výchozím nastavení je fase. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Tabulka: Režimy výběru organizační jednotky - -| Režim | Popis | -|---|---| -| SELECTED | Organizační jednotky definované v požadavku. | -| CHILDREN | Vybrané organizační jednotky a bezprostřední podřazené, tedy organizační jednotky na níže uvedené úrovni. | -| DESCENDANTS | Vybrané organizační jednotky a všechny podřazené, tedy všechny organizační jednotky v podhierarchii. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| VŠE | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -The available assigned user modes are explained in the following table. - - - -Tabulka: Přiřazené uživatelské režimy - -| Režim | Popis | -|---|---| -| CURRENT | Zahrnuje události přiřazené aktuálně přihlášenému uživateli. | -| PROVIDED | Includes events assigned to the user provided in the request. | -| NONE | Includes unassigned events only. | -| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | - -V dotazu se nerozlišují velká a malá písmena. Pro parametry dotazu platí následující pravidla. - - - Alespoň jedna organizační jednotka musí být specifikována pomocí *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Může být pouze jeden z parametrů *program* a *trackedEntity* - specifikováno (nula nebo jedna). - - - If *programStatus* is specified then *program* must also be - specifikováno. - - - Je-li zadáno *followUp*, musí být zadáno také *program*. - - - Pokud je zadáno *programStartDate* nebo *programEndDate*, pak - musí být také specifikován *program*. - - - Položky filtru lze zadat pouze jednou. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendant organisation unit query mode: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a filter: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an *IN* filter: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - &filter=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -Chcete-li zadat data zápisu programu jako součást dotazu: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&page=2&pageSize=3 - -K filtrování můžete použít řadu operátorů: - - - -Tabulka: Operátory filtrů - -| Operátor | Popis | -|---|---| -| EQ | Rovno | -| GT | Větší než | -| GE | Větší než nebo rovno | -| LT | Menší než | -| LE | Menší nebo rovno | -| NE | Nerovná se | -| LIKE | Shoda volného textu (obsahuje) | -| SW | Začíná s | -| EW | Končí s | -| IN | Rovná se jedné z více hodnot oddělených ";" | - -##### Formát odpovědi { #webapi_tei_query_response_format } - -Tento zdroj podporuje zdroj JSON, JSONP, XLS a CSV -reprezentace. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### Databázový dotaz na mřížku instance trasované entity { #webapi_tracked_entity_instance_grid_query } - -To query for tracked entity instances you can interact with the -*/api/trackedEntityInstances/grid* resource. There are two types of -queries: One where a *query* query parameter and optionally *attribute* -parameters are defined, and one where *attribute* and *filter* -parameters are defined. This endpoint uses a more compact "grid" format, -and is an alternative to the query in the previous section. - - /api/33/trackedEntityInstances/query - -##### Požádat o syntaxi { #webapi_tei_grid_query_request_syntax } - - - -Tabulka: Parametry dotazu instancí trasovaných entit - -| Parametr dotazu | Popis | -|---|---| -| query | Řetězec dotazu. Parametr dotazu na atributy lze použít k definování atributů, které se mají zahrnout do odpovědi. Pokud nejsou definovány žádné atributy, ale program, použijí se atributy z programu. Pokud není definován žádný program, použijí se všechny atributy. Existují dva formáty. První je řetězec dotazu plánu. Druhý je ve formátu : . Operátory mohou být EQ | JAKO. EQ znamená přesné shody slov, LIKE znamená částečné shody slov. Dotaz bude rozdělen na mezeru, kde každé slovo bude tvořit logický dotaz AND. | -| attribute | Atributy, které mají být zahrnuty do odpovědi. Lze také použít jako filtr pro dotaz. Parametr lze opakovat libovolněkrát. Filtry lze použít na rozměr ve formátu ::[::]. Hodnoty filtru nerozlišují velká a malá písmena a lze je spolu s operátorem opakovat libovolněkrát. Operátory mohou být EQ | GT | GE | LT | LE | NE | LIKE | V. Filtry lze vynechat, aby bylo možné atribut jednoduše zahrnout do odpovědi bez jakýchkoli omezení. | -| filtr | Atributy, které se mají použít jako filtr pro dotaz. Parametr lze opakovat libovolněkrát. Filtry lze použít na rozměr ve formátu ::[::]. Hodnoty filtru nerozlišují velká a malá písmena a lze je spolu s operátorem opakovat libovolněkrát. Operátory mohou být EQ | GT | GE | LT | LE | NE | LIKE | V. | -| ou | Identifikátory organizační jednotky oddělené „;“. | -| ouMode | Režim výběru organizačních jednotek může být SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Výchozí hodnota je SELECTED, což se týká pouze vybraných organizačních jednotek. Vysvětlení viz tabulka níže. | -| program | Identifikátor programu. Omezuje instance na přihlášení do daného programu. | -| programStatus | Stav instance pro daný program. Může být AKTIVNÍ | DOKONČENO | ZRUŠENO. | -| followUp | Sledovat stav instance pro daný program. Může to být true | false nebo omitted. | -| programStartDate | Datum zahájení zápisu v daném programu pro instanci trasované entity. | -| programEndDate | Datum ukončení zápisu v daném programu pro instanci trasované entity. | -| trackedEntity | Identifikátor trasované entity. Omezuje instance na daný typ trasované instance. | -| eventStatus | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Datum zahájení akce spojené s daným programem a stav akce. | -| eventEndDate | Datum ukončení události spojené s daným programem a stavem události. | -| programStage | ProgramStage, pro kterou by se měly použít filtry související s událostmi. Pokud nebudou poskytnuty, budou zváženy všechny fáze. | -| skipMeta | Označuje, zda by měla být zahrnuta metadata pro odpověď. | -| strana | Číslo stránky. Výchozí stránka je 1. | -| pageSize | Velikost stránky. Výchozí velikost je 50 řádků na stránku. | -| totalPages | Označuje, zda se má do odpovědi stránkování zahrnout celkový počet stránek (znamená delší dobu odezvy). | -| skipPaging | Označuje, zda má být stránkování ignorováno a mají být vráceny všechny řádky. | -| assignedUserMode | Omezuje výsledek na tei s událostmi přiřazenými na základě přiřazeného režimu výběru uživatele, může být CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Tabulka: Režimy výběru organizační jednotky - -| Režim | Popis | -|---|---| -| SELECTED | Organizační jednotky definované v požadavku. | -| CHILDREN | Bezprostřední podřazené, tedy pouze první úroveň níže, organizačních jednotek definovaných v požadavku. | -| DESCENDANTS | Všechny podřazení, tedy pouze na nižších úrovních, např. včetně podřazených do druhé úrovně organizačních jednotek definovaných v požadavku. | -| ACCESSIBLE | Všichni podřazení organizačních jednotek zobrazení dat přidružení k aktuálnímu uživateli. Pokud první není definován, vrátí se zpět k organizačním jednotkám sběru dat přidruženým k aktuálnímu uživateli. | -| CAPTURE | Data zachycují organizační jednotky spojené s aktuálním uživatelem a všemi potomky, tj. všemi organizačními jednotkami v podhierarchii. | -| VŠE | All organisation units in the system. Requires `ALL` authority. | - -Note that you can specify "attribute" with filters or directly using the "filter" params for constraining the -instances to return. - -Pro vrácení atributů platí určitá pravidla. - - - If "query" is specified without any attributes or program, then all attributes that - are marked as "Display in List without Program" is included in the response. - - - Pokud je zadán program, budou všechny atributy spojené s programem - be included in the response. - - - If tracked entity type is specified, then all tracked entity type attributes - will be included in the response. - -You can specify queries with words separated by space - in that -situation the system will query for each word independently and return -records where each word is contained in any attribute. A query item can -be specified once as an attribute and once as a filter if needed. The -query is case insensitive. The following rules apply to the query -parameters. - - - Alespoň jedna organizační jednotka musí být specifikována pomocí *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Může být pouze jeden z parametrů *program* a *trackedEntity* - specifikováno (nula nebo jedna). - - - If *programStatus* is specified then *program* must also be - specifikováno. - - - Je-li zadáno *followUp*, musí být zadáno také *program*. - - - Pokud je zadáno *programStartDate* nebo *programEndDate*, pak - musí být také specifikován *program*. - - - If *eventStatus* is specified then *eventStartDate* and - *eventEndDate* must also be specified. - - - Spolu s filtry nelze zadat dotaz. - - - Položky atributů lze zadat pouze jednou. - - - Položky filtru lze zadat pouze jednou. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -A query on all attributes for a specific value and organisation unit, -using an exact word match: - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -A query on all attributes for a specific value, using a partial word -match: - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -You can query on multiple words separated by the URL character for -space which is %20, will use a logical AND query for each - word: - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -Dotaz, kde jsou specifikovány atributy, které mají být zahrnuty v odpovědi: - - /api/33/trackedEntityInstances/query.json?query=isabel - &attribute=dv3nChNSIxy&attribute=AMpUYgxuCaE&ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendants organisation unit query mode: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &attribute=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a - filter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an IN - filter: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - &attribute=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -Chcete-li zadat data zápisu programu jako součást dotazu: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&program=ur1Edk5Oe2n&programStartDate=2013-01-01 - &programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -To query for instances which have events of a given status within a -given time span: - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -K filtrování můžete použít řadu operátorů: - - - -Tabulka: Operátory filtrů - -| Operátor | Popis | -|---|---| -| EQ | Rovno | -| GT | Větší než | -| GE | Větší než nebo rovno | -| LT | Menší než | -| LE | Menší nebo rovno | -| NE | Nerovná se | -| LIKE | Shoda volného textu (obsahuje) | -| SW | Začíná s | -| EW | Končí s | -| IN | Rovná se jedné z více hodnot oddělených ";" | - -##### Formát odpovědi { #webapi_tei_grid_query_response_format } - -Tento zdroj podporuje zdroj JSON, JSONP, XLS a CSV -reprezentace. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - - - csv (application/csv) - - - xls (application/vnd.ms-excel) - -The response in JSON comes is in a tabular format and can look like the -following. The *headers* section describes the content of each column. -The instance, created, last updated, org unit and tracked entity columns -are always present. The following columns correspond to attributes -specified in the query. The *rows* section contains one row per -instance. - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### Filtry instance trasované entity { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - /api/33/trackedEntityInstanceFilters - -##### Vytvořte a aktualizujte definici filtru instance trasované entity { #create-and-update-a-tracked-entity-instance-filter-definition } - -For creating and updating a tracked entity instance filter in the -system, you will be working with the *trackedEntityInstanceFilters* -resource. The tracked entity instance filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Tabulka: Datový obsah - -| Hodnoty datového obsahu | Popis | Příklad | -|---|---|---| -| název | Název filtru. Požadované. || -| popis | Popis filtru. || -| sortOrder | Pořadí řazení filtru. Používá se v aplikaci Tracker Capture k uspořádání filtrů na ovládacím panelu programu. || -| styl | Objekt obsahující styl css. | ( "color": "blue", "icon": "fa fa-calendar"} | -| program | Objekt obsahující id programu. Požadované. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Tabulka: Definice kritérií dotazu entity - -|||| -|---|---|---| -| attributeValueFilters | Seznam FilterValueFilters. To se používá ke specifikaci filtrů pro hodnoty atributů při výpisu instancí sledovaných entit | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| enrollmentStatus | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | Když je tento parametr pravdivý, filtr vrátí pouze TEI, které mají registraci s následným sledováním stavu. || -| organisationUnit | Chcete-li zadat uid organizační jednotky | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | Chcete-li určit režim výběru OU. Možné hodnoty jsou VYBRANÉ| PŘÍSTUPNÉ DĚTI|POTOMCI|ZAJIŠTĚNÍ VŠECH | "ouMode": "SELECTED" | -| assignedUserMode | Chcete-li určit režim výběru přiřazeného uživatele pro události. Možné hodnoty jsou CURRENT| PROVIDED| NONE | ANY. Podívejte se do tabulky níže, abyste pochopili, co jednotlivé hodnoty znamenají. Je-li hodnota PROVIDED (nebo null), budou v datovém obsahu zohledněni neprázdní přiřazení uživatelé. | "assignedUserMode": "PROVIDED" | -| assignedUsers | Chcete-li zadat seznam přiřazených uživatelů pro události. K použití spolu s výše uvedeným režimem PROVIDEDassignedUserMode. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayColumnOrder | Chcete-li určit výstupní pořadí sloupců | "displayOrderColumns": ["enrollmentDate", "program"] | -| řazení | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus | Jakýkoli platný EventStatus | "eventStatus": "COMPLETED" | -| programStage | Chcete-li zadat uid programuStage, podle kterého se má filtrovat. TEI budou filtrovány na základě přítomnosti zapsaných ve specifikované fázi programu.| "programStage"="a3kGcGDCuk6" | -| trackedEntityType | Chcete-li určit TEI filtru trackedEntityType na. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | Chcete-li zadat seznam trackedEntityInstance, který se má použít při dotazování na TEI. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod filtrování data objektu na základě data incidentu registrace. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod filtrování data objektu na základě data události. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod filtrování data objektu na základě data vytvoření registrace. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod filtrování data objektu na základě data poslední aktualizace. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Tabulka: Definice filtrů událostí - -|||| -|---|---|---| -| programStage | Ve které fázi programu TEI potřebuje událost, aby byla vrácena. | "eaDH9089uMp" | -| eventStatus | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| assignedUserMode | Chcete-li určit režim výběru přiřazeného uživatele pro události. Možné hodnoty jsou CURRENT (události přiřazené aktuálnímu uživateli)| PROVIDED (události přiřazené uživatelům v seznamu „assignedUsers“) | ŽÁDNÉ (události přiřazené nikomu) | JAKÉKOLI (události přiřazené komukoli). Je-li POSKYTNUTO (nebo null), budou zohledněni neprázdní přiřazení uživatelé v užitečné zátěži. | "assignedUserMode": "PROVIDED" | -| assignedUsers | Chcete-li zadat seznam přiřazených uživatelů pro události. K použití spolu s výše uvedeným režimem PROVIDEDassignedUserMode. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Tabulka: Definice objektu DateFilterPeriod - -|||| -|---|---|---| -| typ | Určete, zda je typ období typu ABSOLUTE | RELATIVNÍ | "type" : "RELATIVE" | -| period | Určete, zda se má použít období definované relativním systémem. Použitelné pouze tehdy, když je "typ" RELATIVNÍ. (podporovaná relativní období viz [Relativní období](#webapi_date_relative_period_values)) | "period" : "THIS_WEEK" | -| startDate | Absolutní datum zahájení. Použitelné pouze tehdy, když je "typ" ABSOLUTNÍ | "startDate":"2014-05-01" | -| endDate | Absolutní datum ukončení. Použitelné pouze tehdy, když je "typ" ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relativní vlastní datum zahájení. Použitelné pouze tehdy, když je "typ" RELATIVNÍ | "startBuffer":-10 | -| endBuffer | Relativní vlastní datum ukončení. Použitelné pouze tehdy, když je "typ" RELATIVNÍ | "startDate":+10 | - -Tabulka: Definice období - -|||| -|---|---|---| -| periodFrom | Počet dní od aktuálního dne. Může být kladné nebo záporné celé číslo. | -15 | -| periodTo | Počet dní od aktuálního dne. Musí být větší než období od. Může být kladné nebo záporné celé číslo. | 15 | - -##### Dotaz na filtry instance trasované entity { #tracked-entity-instance-filters-query } - -Chcete-li se dotazovat na filtry instancí sledovaných entit v systému, můžete komunikovat se zdrojem */api/trackedEntityInstanceFilters*. - - - -Tabulka: Instance sledované entity filtruje parametry dotazu - -| Parametr dotazu | Popis | -|---|---| -| program | Identifikátor programu. Omezí filtry na daný program. | - -### Správa zápisů { #webapi_enrollment_management } - -Zápisy mají v rozhraní API plnou podporu CRUD. Společně s API pro trasované instance entit většina operací potřebných pro práci s trasovanými instancemi entit a programy jsou podporovány. - - /api/33/enrollments - -#### Registrace instance trasované entity do programu { #webapi_enrolling_tei } - -For enrolling persons into a program, you will need to first get the -identifier of the person from the *trackedEntityInstances* resource. -Then, you will need to get the program identifier from the *programs* -resource. A template payload can be seen below: - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -Tento datový obsah by měl být použit v požadavku *POST* na zápis -identifikovaný následující adresou URL: - - /api/33/enrollments - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - /api/33/enrollments//cancelled - -For completing an enrollment for a tracked entity instance you can make a -*PUT* request to the following URL: - - /api/33/enrollments//completed - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - /api/33/enrollments/ - -#### Databázový dotaz na zápis instance { #webapi_enrollment_instance_query } - -Chcete-li se zeptat na zápisy, můžete komunikovat se zdrojem */api/enrollments*. - - /api/33/enrollments - -##### Požádat o syntaxi { #webapi_enrollment_query_request_syntax } - - - -Tabulka: Parametry dotazu zápisu - -| Parametr dotazu | Popis | -|---|---| -| ou | Identifikátory organizační jednotky oddělené „;“. | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Identifikátor programu. Omezuje instance na přihlášení do daného programu. | -| programStatus | Stav instance pro daný program. Může být AKTIVNÍ | DOKONČENO | ZRUŠENO. | -| followUp | Sledovat stav instance pro daný program. Může to být true | false nebo omitted. | -| programStartDate | Datum zahájení zápisu v daném programu pro instanci trasované entity. | -| programEndDate | Datum ukončení zápisu v daném programu pro instanci trasované entity. | -| lastUpdatedDuration | Zahrňte pouze položky, které jsou aktualizovány během daného trvání. Formát je , kde podporované časové jednotky jsou „d“ (dny), „h“ (hodiny), „m“ (minuty) a „s“ (sekundy). | -| trackedEntity | Identifikátor trasované entity. Omezuje instance na daný typ trasované instance. | -| trackedEntityInstance | Identifikátor instance trasované entity. Nemělo by se používat společně s trackedEntity. | -| strana | Číslo stránky. Výchozí stránka je 1. | -| pageSize | Velikost stránky. Výchozí velikost je 50 řádků na stránku. | -| totalPages | Označuje, zda se má do odpovědi stránkování zahrnout celkový počet stránek (znamená delší dobu odezvy). | -| skipPaging | Označuje, zda má být stránkování ignorováno a mají být vráceny všechny řádky. | -| includeDeleted | Označuje, zda se mají zahrnout měkké smazané zápisy nebo ne. Ve výchozím nastavení je nepravda. | - -The available organisation unit selection modes are explained in the -following table. - - - -Tabulka: Režimy výběru organizační jednotky - -| Režim | Popis | -|---|---| -| SELECTED | Organizační jednotky definované v požadavku (výchozí). | -| CHILDREN | Bezprostřední podřazené, tedy pouze první úroveň níže, organizačních jednotek definovaných v požadavku. | -| DESCENDANTS | Všechny podřazení, tedy pouze na nižších úrovních, např. včetně podřazených do druhé úrovně organizačních jednotek definovaných v požadavku. | -| ACCESSIBLE | Všichni podřazení organizačních jednotek zobrazení dat přidružení k aktuálnímu uživateli. Pokud první není definován, vrátí se zpět k organizačním jednotkám sběru dat přidruženým k aktuálnímu uživateli. | -| VŠE | All organisation units in the system. Requires `ALL` authority. | - -V dotazu se nerozlišují velká a malá písmena. Pro parametry dotazu platí následující pravidla. - - - Alespoň jedna organizační jednotka musí být specifikována pomocí *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Může být pouze jeden z parametrů *program* a *trackedEntity* - specifikováno (nula nebo jedna). - - - If *programStatus* is specified then *program* must also be - specifikováno. - - - Je-li zadáno *followUp*, musí být zadáno také *program*. - - - Pokud je zadáno *programStartDate* nebo *programEndDate*, pak - musí být také specifikován *program*. - -A query for all enrollments associated with a specific organisation unit -can look like this: - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -To constrain the response to enrollments which are part of a specific -program you can include a program query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -Chcete-li zadat data zápisu programu jako součást dotazu: - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - &programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to enrollments of a specific tracked entity -you can include a tracked entity query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -To constrain the response to enrollments of a specific tracked entity -instance you can include a tracked entity instance query parameter, in -this case we have restricted it to available enrollments viewable for -current - user: - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -By default the enrollments are returned in pages of size 50, to change -this you can use the page and pageSize query - parameters: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### Formát odpovědi { #webapi_enrollment_query_response_format } - -Tento zdroj podporuje zdroj JSON, JSONP, XLS a CSV -reprezentace. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### Události { #webapi_events } - -Tato část je o odesílání a čtení událostí. - - /api/33/events - -Různé stavy události jsou: - -* **AKTIVNÍ**: Pokud má událost stav AKTIVNÍ, je možné upravit podrobnosti události. DOKONČENÉ události lze znovu přepnout na AKTIVNÍ a naopak. -* **DOKONČENO**: Událost změní stav na DOKONČENO pouze tehdy, když uživatel klikne na tlačítko dokončení. Pokud má událost stav DOKONČENO, není možné upravit podrobnosti události. AKTIVNÍ události lze znovu změnit na DOKONČENÉ a naopak. -* **SKIPPED**: Naplánované události, které se již nemusí konat. V Tracker Capture je na to tlačítko. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### Odesílání událostí { #webapi_sending_events } - -DHIS2 supports three kinds of events: single events with no registration -(also referred to as anonymous events), single event with registration -and multiple events with registration. Registration implies that the -data is linked to a tracked entity instance which is identified using -some sort of identifier. - -To send events to DHIS2 you must interact with the *events* resource. -The approach to sending events is similar to sending aggregate data -values. You will need a *program* which can be looked up using the -*programs* resource, an *orgUnit* which can be looked up using the -*organisationUnits* resource, and a list of valid data element -identifiers which can be looked up using the *dataElements* resource. -For events with registration, a *tracked entity instance* identifier is -required, read about how to get this in the section about the -*trackedEntityInstances* resource. For sending events to programs with -multiple stages, you will need to also include the *programStage* -identifier, the identifiers for programStages can be found in the -*programStages* resource. - -A simple single event with no registration example payload in XML format -where we send events from the "Inpatient morbidity and mortality" -program for the "Ngelehun CHC" facility in the demo database can be seen -below: - -```xml - - - - - - - - - -``` - -To perform some testing we can save the XML payload as a file -called *event.xml* and send it as a POST request to the events resource -in the API using curl with the following command: - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -Stejný datový obsah ve formátu JSON vypadá takto: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -To send this you can save it to a file called *event.json* and use curl -like this: - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -We also support sending multiple events at the same time. A payload in -XML format might look like this: - -```xml - - - - - - - - - - - - - - - - - -``` - -You will receive an import summary with the response which can be -inspected in order to get information about the outcome of the request, -like how many values were imported successfully. The payload in JSON -format looks like this: - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -GeoJson můžete také použít k uložení jakéhokoli druhu geometrie vaší události. Zde můžete vidět příklad datového obsahu pomocí GeoJson namísto dřívějších vlastností zeměpisné šířky a délky: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -As part of the import summary you will also get the identifier -*reference* to the event you just sent, together with a *href* element -which points to the server location of this event. The table below -describes the meaning of each element. - - - -Tabulka: Formát zdroje událostí - -| Parametr | Typ | Požadované | Možnosti (nejprve výchozí) | Popis | -|---|---|---|---|---| -| program | řetězec | true || Identifikátor jedné události bez registračního programu | -| orgUnit | řetězec | true || Identifikátor organizační jednotky, kde se akce konala | -| eventDate | datum | true || Datum, kdy k události došlo | -| completedDate | datum | false || Datum, kdy je akce dokončena. Pokud není zadáno, je jako datum dokončení události vybráno aktuální datum | -| status | enum | false | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Zda je akce dokončena nebo ne | -| storedBy | řetězec | false | Výchozí nastavení pro aktuálního uživatele | Kdo uložil tuto událost (může to být uživatelské jméno, název systému atd.) | -| souřadnice | dvojnásobek | false || Odkazuje na místo, kde se událost geograficky odehrála (zeměpisná šířka a délka) | -| dataElement | řetězec | true || Identifikátor datového prvku | -| value | řetězec | true || Hodnota nebo míra dat pro tuto událost | - -##### Shoda OrgUnit { #orgunit-matching } - -By default the orgUnit parameter will match on the -ID, you can also select the orgUnit id matching scheme by using the -parameter orgUnitIdScheme=SCHEME, where the options are: *ID*, *UID*, -*UUID*, *CODE*, and *NAME*. There is also the *ATTRIBUTE:* scheme, which -matches on a *unique* metadata attribute value. - -#### Aktualizace událostí { #webapi_updating_events } - -To update an existing event, the format of the payload is the same, but -the URL you are posting to must add the identifier to the end of the URL -string and the request must be PUT. - -The payload has to contain all, even non-modified, attributes. -Attributes that were present before and are not present in the current -payload any more will be removed by the system. - -It is not allowed to update an already deleted event. The same applies -to tracked entity instance and enrollment. - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### Mazání událostí { #webapi_deleting_events } - -To delete an existing event, all you need is to send a DELETE request -with an identifier reference to the server you are using. - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### Přiřazení uživatele k událostem { #webapi_user_assign_event } - -K události lze přiřadit uživatele. To lze provést zahrnutím příslušné vlastnosti do datového obsahu při aktualizaci nebo vytváření události. - - "assignedUser": "" - -ID odkazuje na if uživatele. K události lze najednou přiřadit pouze jednoho uživatele. - -Přiřazení uživatele musí být povoleno ve fázi programu, než mohou být uživatelé přiřazeni k událostem. -#### Získávání událostí { #webapi_getting_events } - -To get an existing event you can issue a GET request including the -identifier like this: - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### Dotazování a čtení událostí { #webapi_querying_reading_events } - -This section explains how to read out the events that have been stored -in the DHIS2 instance. For more advanced uses of the event data, please -see the section on event analytics. The output format from the -`/api/events` endpoint will match the format that is used to send events -to it (which the analytics event api does not support). Both XML and -JSON are supported, either through adding .json/.xml or by setting the -appropriate *Accept* header. The query is paged by default and the -default page size is 50 events, *field* filtering works as it does for -metadata, add the *fields* parameter and include your wanted properties, -i.e. *?fields=program,status*. - - - -Tabulka: Parametry dotazu na zdroj událostí - -| Klíč | Typ | Požadované | Popis | -|---|---|---|---| -| program | identifikátor | true (pokud není poskytnut programStage) | Identifikátor programu | -| programStage | identifikátor | false | Identifikátor fáze programu | -| programStatus | enum | false | Stav události v programu, může být ACTIVE | COMPLETED | CANCELLED | -| followUp | boolean | false | Zda je událost zvažována pro pokračování v programu, může být pravda | nepravdivé nebo vynechané. | -| trackedEntityInstance | identifikátor | false | Identifikátor instance trasované entity | -| orgUnit | identifikátor | true | Identifikátor organizační jednotky | -| ouMode | enum | false | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| startDate | datum | false | Pouze události novější než toto datum | -| endDate | datum | false | Pouze události starší než toto datum | -| status | enum | false | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | datum | false | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | datum | false | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | řetězec | false | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta | boolean | false | Vyloučí metadatovou část odpovědi (zlepšuje výkon) | -| strana | celé číslo | false | Číslo stránky | -| pageSize | celé číslo | false | Počet položek na každé stránce | -| totalPages | boolean | false | Označuje, zda se má do odpovědi stránkování zahrnout celkový počet stránek. | -| skipPaging | boolean | false | Označuje, zda se má přeskočit stránkování v dotazu a vrátit všechny události. | -| dataElementIdScheme | řetězec | false | Schéma ID datového prvku pro export, platné možnosti jsou UID, CODE a ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme | řetězec | false | ID schéma Možnost kombinace kategorií pro export, platné možnosti jsou UID, CODE a ATRIBUTE:{ID} | -| orgUnitIdScheme | řetězec | false | Schéma ID organizační jednotky pro export, platné možnosti jsou UID, CODE a ATTRIBUTE:{ID} | -| programIdScheme | řetězec | false | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programStageIdScheme | řetězec | false | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| idScheme | řetězec | false | Umožňuje nastavit id schéma pro datový prvek, kombinaci možností kategorie, orgUnit, program a fázi programu najednou. | -| řazení | řetězec | false | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| událost | čárkou oddělený řetězec | false | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | boolean | false | Přeskočí identifikátory událostí v odpovědi | -| atributCc (\*\*) | řetězec | false | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | řetězec | false | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | false | true | false | Označuje, zda má být import proveden asynchronně nebo synchronně. | -| includeDeleted | boolean | false | Když je true, budou do výsledku dotazu zahrnuty měkké odstraněné události. | -| assignedUserMode | enum | false | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | čárkou oddělené řetězce | false | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> **Poznámka** -> -> Pokud dotaz neobsahuje ani `attributeCC`, ani `attributeCos`, vrátí server události pro všechna komba voleb atributů, kde má uživatel přístup ke čtení. - -##### Příklady { #examples } - -Dotaz na všechny události s podřazenými určité organizační jednotky: - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -Dotaz na všechny události se všemi potomky určité organizační jednotky, což znamená všechny organizační jednotky v subhierarchii: - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -Dotaz na všechny události s určitou programovou a organizační jednotkou: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -Query for all events with a certain program and organisation unit, -sorting by due date - ascending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -Query for the 10 events with the newest event date in a certain program -and organisation unit - by paging and ordering by due date descending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &order=eventDate:desc&pageSize=10&page=1 - -Query for all events with a certain program and organisation unit for a -specific tracked entity instance: - - /api/33/events.json?orgUnit=DiszpKrYNg8 - &program=eBAyeGv0exc&trackedEntityInstance=gfVxE3ALA9m - -Query for all events with a certain program and organisation unit older -or equal to - 2014-02-03: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -Query for all events with a certain program stage, organisation unit and -tracked entity instance in the year 2014: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &trackedEntityInstance=gfVxE3ALA9m&startDate=2014-01-01&endDate=2014-12-31 - -Query files associated with event data values. In the specific case of fetching an image file an -additional parameter can be provided to fetch the image with different dimensions. If dimension is -not provided, the system will return the original image. The parameter will be ignored in case of -fetching non-image files e.g pdf. Possible dimension values are *small(254 x 254), -medium(512 x 512), large(1024 x 1024) or original*. Any value other than those mentioned will be -discarded and the original image will be returned. - - /api/33/events/files?eventUid=hcmcWlYkg9u&dataElementUid=C0W4aFuVm4P&dimension=small - -Retrieve events with specified Organisation unit and Program, and use _Attribute:Gq0oWTf2DtN_ as -identifier scheme - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for -orgUnits, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as identifier -scheme for the rest of the metadata with assigned attribute. - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=Code - -#### Dotaz na mřížku událostí { #event-grid-query } - -In addition to the above event query end point, there is an event grid -query end point where a more compact "grid" format of events are -returned. This is possible by interacting with -/api/events/query.json|xml|xls|csv endpoint. - - /api/33/events/query - -Most of the query parameters mentioned in event querying and reading -section above are valid here. However, since the grid to be returned -comes with specific set of columns that apply to all rows (events), it -is mandatory to specify a program stage. It is not possible to mix -events from different programs or program stages in the return. - -Vracení událostí z jedné fáze programu také otevírá nové funkce - například třídění a vyhledávání událostí na základě hodnot jejich datových prvků. api/events/query to podporuje. Níže je uvedeno několik příkladů - -A query to return an event grid containing only selected data elements -for a program stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &dataElement=qrur9Dvnyt5,fWIAEtYVEGk,K6uUAvq500H&order=lastUpdated:desc - &pageSize=50&page=1&totalPages=true - -A query to return an event grid containing all data elements of a -program - stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &includeAllDataElements=true - -A query to filter events based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50 - -In addition to the filtering, the above example also illustrates one -thing: the fact that there are no data elements mentioned to be returned -in the grid. When this happens, the system defaults back to return only -those data elements marked "Display in report" under program stage -configuration. - -We can also extend the above query to return us a grid sorted (asc|desc) -based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50&order=qrur9Dvnyt5:desc - -#### Filtry událostí { #webapi_event_filters } - -To create, read, update and delete event filters you -can interact with the `/api/eventFilters` resource. - - /api/33/eventFilters - -##### Vytvořte a aktualizujte definici filtru událostí { #create-and-update-an-event-filter-definition } - -For creating and updating an event filter in the -system, you will be working with the *eventFilters* -resource. *POST* is used to create and *PUT* method is used to update. The event filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Tabulka: Požadavek na užitečné zatížení - -| Vlastnost požadavku | Popis | Příklad | -|---|---|---| -| název | Název filtru. | "name":"Můj pracovní seznam" | -| popis | Popis filtru. | "description":"pro výpis všech událostí, které mi byly přiřazeny". | -| program | Uid programu. | "program" : "a3kGcGDCuk6" | -| programStage | Uid fáze programu. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Objekt obsahující parametry pro dotazování, řazení a filtrování událostí. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Tabulka: Definice kritérií dotazu na událost - -|||| -|---|---|---| -| followUp | Používá se k filtrování událostí na základě příznaku sledování registrace. Možné hodnoty jsou true|false. | "followUp": true | -| organisationUnit | Chcete-li zadat uid organizační jednotky | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | Chcete-li určit režim výběru OU. Možné hodnoty jsou VYBRANÉ| PŘÍSTUPNÉ DĚTI|POTOMCI|ZAJIŠTĚNÍ VŠECH | "ouMode": "SELECTED" | -| assignedUserMode | Chcete-li určit režim výběru přiřazeného uživatele pro události. Možné hodnoty jsou CURRENT| PROVIDED| NONE | ANY. Podívejte se do tabulky níže, abyste pochopili, co jednotlivé hodnoty znamenají. Je-li hodnota PROVIDED (nebo null), budou v datovém obsahu zohledněni neprázdní přiřazení uživatelé. | "assignedUserMode": "PROVIDED" | -| assignedUsers | Chcete-li zadat seznam přiřazených uživatelů pro události. K použití spolu s výše uvedeným režimem PROVIDEDassignedUserMode. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | Chcete-li určit výstupní pořadí sloupců | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| řazení | Specifikovat řazení/třídění polí a jejich směry v hodnotách oddělených čárkami. Jedna položka v objednávce má tvar "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| dataFilters | Chcete-li určit filtry, které se mají použít při vypisování událostí | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| status | Jakýkoli platný EventStatus | "eventStatus": "COMPLETED" | -| Události | Chcete-li specifikovat seznam událostí | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod filtrování data objektu na základě data dokončení. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod filtrování data objektu na základě data události. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod filtrování data objektu na základě data platnosti. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod filtrování data objektu na základě data poslední aktualizace. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Tabulka: Definice objektu DateFilterPeriod - -|||| -|---|---|---| -| typ | Určete, zda je typ období typu ABSOLUTE | RELATIVNÍ | "type" : "RELATIVE" | -| period | Určete, zda se má použít období definované relativním systémem. Použitelné pouze tehdy, když je "typ" RELATIVNÍ. (podporovaná relativní období viz [Relativní období](#webapi_date_relative_period_values)) | "period" : "THIS_WEEK" | -| startDate | Absolutní datum zahájení. Použitelné pouze tehdy, když je "typ" ABSOLUTNÍ | "startDate":"2014-05-01" | -| endDate | Absolutní datum ukončení. Použitelné pouze tehdy, když je "typ" ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relativní vlastní datum zahájení. Použitelné pouze tehdy, když je "typ" RELATIVNÍ | "startBuffer":-10 | -| endBuffer | Relativní vlastní datum ukončení. Použitelné pouze tehdy, když je "typ" RELATIVNÍ | "startDate":+10 | - -The available assigned user selection modes are explained in the -following table. - - - -Tabulka: Režimy výběru přiřazených uživatelů (přiřazení události) - -| Režim | Popis | -|---|---| -| CURRENT | Přiřazeno aktuálně přihlášenému uživateli | -| PROVIDED | Přiřazeno uživatelům uvedeným v parametru „assignedUser“. | -| NONE | Nepřiřazeno žádným uživatelům. | -| ANY | Přiděleno všem uživatelům. | - -Ukázkový datový obsah, který lze použít k vytvoření / aktualizaci eventFilter, je uveden níže. - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### Načítání a mazání filtrů událostí { #retrieving-and-deleting-event-filters } - -Filtr konkrétních událostí lze načíst pomocí následujícího rozhraní API - - GET /api/33/eventFilters/{uid} - -Všechny filtry událostí lze načíst pomocí následujícího rozhraní API. - - GET /api/33/eventFilters?fields=* - -Všechny filtry událostí pro konkrétní program lze načíst pomocí následujícího rozhraní API - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -Filtr událostí lze odstranit pomocí následujícího rozhraní API - - DELETE /api/33/eventFilters/{uid} - -### Vztahy { #relationships } -Vztahy jsou vazby mezi dvěma entitami v trasovači. Tyto entity mohou být instance trasovaných entit, zápisy a události. - -Existuje několik koncových bodů, které vám umožňují zobrazit, vytvořit, odstranit a aktualizovat vztahy. Nejběžnější je /api/trackedEntityInstances koncový bod, kde můžete zahrnout vztahy v datovém obsahu, abyste je mohli vytvořit, aktualizovat nebo odstranit, pokud je vynecháte - podobně jako při práci se zápisy a událostmi ve stejném koncovém bodě. Všechny koncové body trasovače, /api/trackedEntityInstances, /api/enrollments a /api/events také uvedou jejich vztahy, pokud je to požadováno ve filtru pole. - -Standardní koncový bod pro vztahy je však /api/relationships. Tento koncový bod poskytuje všechny normální operace CRUD pro vztahy. - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -Tento požadavek vrátí seznam všech vztahů, ke kterým máte přístup, a který obsahuje trasovanou entitu, zápis, nebo událost, kterou jste zadali. Každý vztah je reprezentován následujícím JSON: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -Můžete také zobrazit zadané vztahy pomocí následujícího koncového bodu: - - GET /api/relationships/ - -Chcete-li vytvořit nebo aktualizovat vztah, můžete použít následující koncové body: - - POST /api/relationships - PUT /api/relationships - -A použijte následující strukturu datového obsahu: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -Chcete-li odstranit vztah, můžete použít tento koncový bod: - - DELETE /api/relationships/ - -V našem příkladu datového obsahu používáme vztah mezi trackedEntityInstances. Z tohoto důvodu vlastnosti „od“ a „do“ našich užitečných dat zahrnují objekty „trackedEntityInstance“. Pokud váš vztah zahrnuje další entity, můžete použít následující vlastnosti: - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### Strategie aktualizací { #webapi_tei_update_strategies } - -Two update strategies for all 3 tracker endpoints are supported: -enrollment and event creation. This is useful when you have generated an -identifier on the client side and are not sure if it was created or not -on the server. - - - -Tabulka: Dostupné strategie sledování - -| Parametr | Popis | -|---|---| -| VYTVOŘIT | Pouze vytvořit, toto je výchozí chování. | -| CREATE_AND_UPDATE | Zkuste a porovnejte ID, pokud existuje, aktualizujte, pokud ne vytvořte. | - -Chcete-li změnit parametr, použijte parametr strategie: - - POST /api/33/trackedEntityInstances?strategy=CREATE_AND_UPDATE - -### Hromadné mazání trasovače { #webapi_tracker_bulk_deletion } - -Bulk deletion of tracker objects work in a similar fashion to adding and -updating tracker objects, the only difference is that the -`importStrategy` is *DELETE*. - -*Example: Bulk deletion of tracked entity instances:* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*Příklad: Hromadné mazání zápisů:* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*Příklad: Hromadné mazání událostí:* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### Opětovné použití identifikátoru a odstranění položky metodami POST a PUT { #webapi_updating_and_deleting_items } - -Tracker endpoints */trackedEntityInstances*, */enrollments*, */events* -support CRUD operations. The system keeps track of used identifiers. -Therefore, an item which has been created and then deleted (e.g. events, -enrollments) cannot be created or updated again. If attempting to delete -an already deleted item, the system returns a success response as -deletion of an already deleted item implies no change. - -The system does not allow to delete an item via an update (*PUT*) or -create (*POST*) method. Therefore, an attribute *deleted* is ignored in -both *PUT* and *POST* methods, and in *POST* method it is by default set -to *false*. - -### Import parametrů { #webapi_import_parameters } - -Proces importu lze přizpůsobit pomocí sady parametrů importu: - - - -Tabulka: Parametry importu - -| Parametr | Hodnoty (výchozí první) | Popis | -|---|---|---| -| dataElementIdScheme | id | jméno | kód | atribut:ID | Vlastnost objektu datového prvku, který se má použít k mapování hodnot dat. | -| orgUnitIdScheme | id | jméno | kód | atribut:ID | Vlastnost objektu organizační jednotky, která se má použít k mapování datových hodnot. | -| idScheme | id | name | code| attribute:ID | Vlastnost všech objektů včetně datových prvků, organizačních jednotek a kombinací možností kategorií, které se mají použít k mapování datových hodnot. | -| dryRun | false | true | Zda uložit změny na serveru nebo jen vrátit souhrn importu. | -| strategie | CREATE | UPDATE | CREATE_AND_UPDATE | DELETE | Uložit objekty všech, nový nebo aktualizovat stav importu na server. | -| skipNotifications | true | false | Označuje, zda se mají odesílat upozornění na dokončené události. | -| skipFirst | true | false | Relevantní pouze pro import CSV. Označuje, zda soubor CSV obsahuje řádek záhlaví, který by měl být přeskočen. | -| importReportMode | FULL, ERRORS, DEBUG | Sets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes *ObjectReports* for object which has errors. `FULL` returns an *ObjectReport* for all objects imported, and `DEBUG` returns the same plus a name for the object (if available). | - -#### CSV Import / Export { #webapi_events_csv_import_export } - -In addition to XML and JSON for event import/export, in DHIS2.17 we -introduced support for the CSV format. Support for this format builds on -what was described in the last section, so here we will only write about -what the CSV specific parts are. - -To use the CSV format you must either use the `/api/events.csv` -endpoint, or add *content-type: text/csv* for import, and *accept: -text/csv* for export when using the `/api/events` endpoint. - -The order of column in the CSV which are used for both export and import -is as follows: - - - -Tabulka: Sloupec CSV - -| Index | Klíč | Typ | Popis | -|---|---|---|---| -| 1 | událost | identifikátor | Identifikátor události | -| 2 | status | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | program | identifikátor | Identifikátor programu | -| 4 | programStage | identifikátor | Identifikátor fáze programu | -| 5 | zápis | identifikátor | Identifikátor zápisu (instance programu) | -| 6 | orgUnit | identifikátor | Identifikátor organizační jednotky | -| 7 | eventDate | datum | Datum události | -| 8 | dueDate | datum | Datum splatnosti | -| 9 | latitude | dvojnásobek | Zeměpisná šířka, kde se událost stala | -| 10 | longitude | dvojnásobek | Zeměpisná délka, kde se událost stala | -| 11 | dataElement | identifikátor | Identifikátor datového prvku | -| 12 | value | řetězec | Hodnota / míra události | -| 13 | storedBy | řetězec | Událost byla uložena uživatelem (výchozí nastavení pro aktuálního uživatele) | -| 14 | providedElsewhere | boolean | Byla tato hodnota shromážděna někde jinde | -| 14 | completedDate | datum | Dokončený termín akce | -| 14 | completedBy | řetězec | Uživatelské jméno uživatele, který dokončil událost | - -*Example of 2 events with 2 different data value - each:* - -```csv -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,1,, -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,2,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,3,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,4,, -``` - -#### Strategie importu: SYNC { #webapi_sync_import_strategy } - -Strategie importu SYNC by měla být používána pouze interní synchronizační úlohou a ne pro běžný import. Strategie SYNC umožňuje, aby všechny 3 operace: CREATE, UPDATE, DELETE byly přítomny současně i v datovém obsahu. - -### Správa vlastnictví trasovače { #webapi_tracker_ownership_management } - -A new concept called Tracker Ownership is introduced from 2.30. There -will now be one owner organisation unit for a tracked entity instance in -the context of a program. Programs that are configured with an access -level of *PROTECTED* or *CLOSED* will adhere to the ownership -privileges. Only those users belonging to the owning org unit for a -tracked entity-program combination will be able to access the data -related to that program for that tracked entity. - -#### Přepsání vlastnictví trasovače: Rozbijte sklo { #webapi_tracker_ownership_override_api } - -It is possible to temporarily override this ownership privilege for a -program that is configured with an access level of *PROTECTED*. Any user -will be able to temporarily gain access to the program related data, if -the user specifies a reason for accessing the tracked entity-program -data. This act of temporarily gaining access is termed as *breaking the -glass*. Currently, the temporary access is granted for 3 hours. DHIS2 -audits breaking the glass along with the reason specified by the user. -It is not possible to gain temporary access to a program that has been -configured with an access level of *CLOSED*. To break the glass for a -tracked entity program combination, you can issue a POST request as -shown: - - /api/33/tracker/ownership/override?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care - -#### Převod vlastnictví trasovače { #webapi_tracker_ownership_transfer_api } - -Je možné převést vlastnictví sledovaného subjektu - programu z jedné organizační jednotky na druhou. To bude užitečné v případě předávání pacientů nebo migrace. Vlastnictví může převést pouze vlastník (nebo uživatelé, kteří rozbili sklo). Chcete-li převést vlastnictví sledované entity-programu na jinou organizační jednotku, můžete vystavit požadavek PUT, jak je znázorněno na obrázku: - - /api/33/tracker/ownership/transfer?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&ou=EJNxP3WreNP - - -## Potenciální duplikáty { #potential-duplicates } - -Potenciální duplikáty jsou záznamy, se kterými pracujeme ve funkci deduplikace dat. Vzhledem k povaze funkce deduplikace je tento koncový bod API poněkud omezen. - -Potenciální duplikát představuje dvojici záznamů, u kterých existuje podezření, že jsou duplikáty. - -Datový obsah potenciálního duplikátu vypadá takto: - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -Seznam potenciálních duplikátů můžete načíst pomocí následujícího koncového bodu: - - GET /api/potentialDuplicates - -| Název parametru | Popis | Typ | Povolené hodnoty | -|---|---|---|---| -| tei | Seznam instancí trasovaných entit | Seznam řetězců (oddělených čárkou)| ID existující instance trasované entity | -| status | Potenciální duplicitní stav | řetězec | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Stavový kód | Popis -|---|---| -| 400 | Neplatný stav vstupu - -Jednotlivé potenciální duplicitní záznamy můžete zkontrolovat: - - GET /api/potentialDuplicates/ - -| Stavový kód | Popis -|---|---| -| 404 | Potenciální duplikát nebyl nalezen - -Chcete-li vytvořit nový potenciální duplikát, můžete použít tento koncový bod: - - POST /api/potentialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Stavový kód | Popis -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -Chcete-li aktualizovat potenciální duplicitní stav: - - PUT /api/potentialDuplicates/ - -| Název parametru | Popis | Typ | Povolené hodnoty | -|---|---|---|---| -| status | Potenciální duplicitní stav | řetězec | `OPEN`, `INVALID`, `MERGED` | - -| Stavový kód | Popis -|---|---| -| 400 | Potenciální duplikát nemůžete aktualizovat na MERGED, protože to je možné pouze na základě žádosti o sloučení -| 400 | Nelze aktualizovat potenciální duplikát, který je již ve stavu MERGED - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -Ke sloučení potenciálního duplikátu nebo dvou instancí trasovaných entit, které potenciální duplikát představuje, lze použít následující koncový bod: - - POST /api/potentialDuplicates//merge - -| Název parametru | Popis | Typ | Povolené hodnoty | -|---|---|---|---| -| mergeStrategy | Strategie, která se má použít pro sloučení potenciálního duplikátu | enum | AUTO (výchozí) nebo MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- Stejný atribut má v každé instanci trasované entity různé hodnoty -- Obě instance trasovaných entit jsou zapsány do stejného programu -- Instance trasovaných entit mají různé typy - -Pokud dojde ke konfliktu, uživateli se vrátí chybová zpráva. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -Při požadavku na automatické sloučení, jako je tento, není datový obsah vyžadován a bude ignorován. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Vztah nemůže být mezi originálem a duplikátem (To má za následek neplatný vztah odkazující na sebe) -- Vztah nemůže být stejného typu a ke stejnému objektu v obou instancích trasované entity (např. mezi původní a jinou a duplicitní a jinou; výsledkem by byl duplicitní vztah) - -Existují dva způsoby, jak provést ruční sloučení: S a bez datového obsahu. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -V opačném případě, pokud je požadováno ruční sloučení s datovou částí, datová část odkazuje na to, jaká data by měla být přesunuta z duplikátu do originálu. Datový obsah vypadá takto: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -Pole jsou vysvětlena v následující tabulce. - - -Tabulka: Datový obsah šablony oznámení programu - -| Pole | Požadované | Popis | Hodnoty | -|---|---|---|---| -| název | Ano | name of Program Notification Template | case-notification-alert | -| notificationTrigger | Ano | Kdy má být spuštěno oznámení. Možné hodnoty jsou ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| ZÁPIS | -| subjectTemplate | Ne | Šablona řetězce předmětu | Case notification V{org_unit_name} | -| messageTemplate | Ano | Řetězec šablony zprávy | Oznámení o případu A{h5FuguPFF2j} | -| notificationRecipient | ANO | Kdo bude dostávat oznámení. Možné hodnoty jsou USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | Ne | Který kanál by měl být použit pro toto oznámení. Může to být buď SMS, EMAIL nebo HTTP | SMS | -| sendRepeatable | Ne | Zda má být oznámení odesláno vícekrát | false | - -POZNÁMKA: WEB_HOOK notificationRecipient se používá pouze k POST http požadavku na externí systém. Při použití WEB_HOOK se ujistěte, že jste zvolili doručovací kanál HTTP. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -Seznam šablon oznámení programu lze získat pomocí GET. - - GET /api/programNotificationTemplates - -Pro jednu konkrétní šablonu oznámení programu. - - GET /api/33/programNotificationTemplates/{uid} - -Chcete-li získat filtrovaný seznam šablon oznámení programu - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Šablonu oznámení programu lze odstranit pomocí DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -Program message lets you send messages to tracked entity instances, -contact addresses associated with organisation units, phone numbers and -email addresses. You can send messages through the `messages` resource. - - /api/33/messages - -### Odesílání zpráv programu { #sending-program-messages } - -Programové zprávy lze odesílat pomocí dvou doručovacích kanálů: - - - SMS (SMS) - - - E-mailová adresa (EMAIL) - -Zprávy programu lze zasílat různým příjemcům: - - - Tracked entity instance: The system will look up attributes of value - type PHONE_NUMBER or EMAIL (depending on the specified delivery - channels) and use the corresponding attribute values. - - - Organisation unit: The system will use the phone number or email - information registered for the organisation unit. - - - List of phone numbers: The system will use the explicitly defined - phone numbers. - - - List of email addresses: The system will use the explicitly defined - email addresses. - -Below is a sample JSON payload for sending messages using POST requests. -Note that message resource accepts a wrapper object named -`programMessages` which can contain any number of program messages. - - POST /api/33/messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -Pole jsou vysvětlena v následující tabulce. - - - -Tabulka: Datový obsah zprávy programu - -| Pole | Požadované | Popis | Hodnoty | -|---|---|---|---| -| příjemci | Ano | Příjemci programové zprávy. Musí být uveden alespoň jeden příjemce. Pro zprávu lze zadat libovolný počet příjemců / typů. | Lze sledovat EntityInstance, OrganizationUnit, řadu telefonních čísel nebo řadu e-mailových adres. | -| programInstance | Je vyžadováno buď toto, nebo programStageInstance | Instance programu / zápisu. | ID zápisu. | -| programStageInstance | Vyžaduje se buď toto, nebo programInstance | Instance / událost fáze programu. | Event ID. | -| deliveryChannels | Ano | Pole doručovacích kanálů. | SMS | EMAIL | -| předmět | Ne | Předmět zprávy. Neplatí pro kanál doručování SMS. | Text. | -| text | Ano | Text zprávy. | Text. | -| storeCopy | Ne | Zda uložit kopii zprávy programu v DHIS2. | false (default) | true | - -Minimalistický příklad pro odeslání zprávy přes SMS na instanci trasované entity vypadá takto: - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### Načítání a mazání zpráv programu { #retrieving-and-deleting-program-messages } - -Seznam zpráv lze načíst pomocí GET. - - GET /api/33/messages - -Chcete-li získat seznam odeslaných zpráv trasování, můžete použít níže uvedený koncový bod. Musí být poskytnuto uid ProgramInstance nebo ProgramStageInstance. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -Chcete-li získat seznam všech naplánovaných zpráv - - GET /api/33/messages/scheduled - GET /api/33/messages/scheduled?scheduledAt=2020-12-12 - -Jednu konkrétní zprávu lze také načíst pomocí GET. - - GET /api/33/messages/{uid} - -Zprávu lze smazat pomocí DELETE. - - DELETE /api/33/messages/{uid} - - -### Dotazování na zprávy programu { #querying-program-messages } - -The program message API supports program message queries based on -request parameters. Messages can be filtered based on below mentioned -query parameters. All requests should use the GET HTTP verb for -retrieving information. - - - -Tabulka: API zpráv dotazovacího programu - -| Parametr | URL | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # E-mail { #email } diff --git a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index ea9770944..f646d136b 100644 --- a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- Správa - DHIS core verze 2.37 +- Správa template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md index 9c9ab2245..35e15915f 100644 --- a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- Správa - DHIS základní verze 2.39 +- Správa template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index e1347ae4a..34cb9d4a0 100644 --- a/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/cs/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- Správa - Hlavní verze jádra DHIS +- Správa template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index 00a723103..095f9746c 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2022-03-10' tags: -- DHIS core verze 2.37 - Použití +- DHIS core verze 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index 6540bebf6..706ac7dce 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2023-02-20' tags: -- DHIS core verze 2.37 - Použití +- DHIS core verze 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index d29d3d150..5ec98a88a 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS základní verze 2.39 - Použití +- DHIS základní verze 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 61bbdc597..abd1cf358 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS základní verze 2.39 - Použití +- DHIS základní verze 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/.cache_timestamp b/projects/dhis2-single-page-docs/es_419/.cache_timestamp index 5b9fb2cdd..b6ed94d48 100644 --- a/projects/dhis2-single-page-docs/es_419/.cache_timestamp +++ b/projects/dhis2-single-page-docs/es_419/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:27:13Z \ No newline at end of file +2024-06-04T21:27:13Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index df3b05d94..542389c7c 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2023-01-13' tags: -- DHIS core version 2.37 - Desarrollar +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index 5fff9b3cf..35dc67f1d 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index b53fc3068..1da455d51 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index cb5fa9578..2d14c6c89 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 6142720a6..c9c2f26c5 100644 --- a/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/es_419/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - Desarrollar - DHIS core version master @@ -12217,7 +12217,7 @@ Table: Query parameters for event query analytics only | Query parameter | Requerido | Descripción | Options | |---|---|---|---| -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return events which have coordinates. | falso | verdadero | @@ -13124,7 +13124,7 @@ Table: Query parameters for enrollment query endpoint | filter | No | Dimension identifier including data elements, attributes, periods, organisation units and organisation unit group sets. Parameter can be repeated any number of times. Item filters can be applied to a dimension on the format ::. Filter values are case-insensitive. || | programStatus | No | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | No | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return enrollments which have coordinates. | falso | verdadero | @@ -17833,20 +17833,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17949,7 +17950,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | No | Sí | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | Sí | No | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -18009,9 +18009,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Attributes { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | Descripción | Requerido | Immutable | Tipo | Example | |---|---|---|---|---|---| @@ -18026,18 +18028,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | Descripción | Requerido | Immutable | Tipo | Example | |---|---|---|---|---|---| @@ -18052,31 +18056,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Notes { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -18087,10 +18091,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -18132,92 +18136,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | Descripción | Example | -|---|---|---| -| name | Name of the working list. Required. || -| Descripción | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Descripción | Example | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -18226,9 +18145,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -18261,7 +18180,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -18661,7 +18580,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -19107,7 +19026,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -19237,7 +19156,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | N/A | Undefined error message. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -19247,7 +19166,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -19272,8 +19191,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -19326,7 +19245,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -19382,7 +19301,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -19404,7 +19323,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -19438,7 +19357,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -19490,9 +19409,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -19572,8 +19491,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -19678,7 +19597,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19940,8 +19859,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -20145,8 +20064,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -20441,13 +20360,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -20493,7 +20412,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -20562,13 +20481,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -20580,7 +20499,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -20593,7 +20512,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -20603,7 +20522,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -20633,7 +20552,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -20649,2767 +20568,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Table: Payload -|Tracker Object|Previously|Now| +| Payload values | Descripción | Example | |---|---|---| -|**Attribute**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Inscripción**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Evento**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Nota**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Relationship**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribute`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes`|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus`|`enrollmentStatus`| -|`query`|Removed - use `filter` instead| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Previously|Now| -|---|---| -|`enrollment`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus`|`status`| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`event`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`lastUpdated`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus`|`enrollmentStatus`| -|`skipEventId`|Removed| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Previously|Now| -|---|---| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity`| - -## Tracker Web API { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### Tracked entity instance management { #webapi_tracked_entity_instance_management } - -Tracked entity instances have full CRUD support in the API. Together -with the API for enrollment most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/trackedEntityInstances - -#### Creating a new tracked entity instance { #webapi_creating_tei } - -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -The field "geometry" accepts a GeoJson object, where the type of the -GeoJson have to match the featureType of the TrackedEntityType -definition. An example GeoJson object looks like this: - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +| name | Name of the working list. Required. || +| Descripción | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Table: Program Stage Query Criteria - /api/trackedEntityInstances +| Criteria values | Descripción | Example | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +See an example payload below: ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -To push this to the server you can use the cURL command like this: - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -To create multiple instances in one request you can wrap the payload in -an outer array like this and POST to the same resource as above:[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -The system does not allow the creation of a tracked entity instance -(as well as enrollment and event) with a UID that was already used in -the system. That means that UIDs cannot be reused. - -#### Updating a tracked entity instance { #webapi_updating_tei } - -For updating a tracked entity instance, the payload is equal to the -previous section. The difference is that you must use the HTTP *PUT* -method for the request when sending the payload. You will also need to -append the person identifier to the *trackedEntityInstances* resource in -the URL like this, where `` should -be replaced by the identifier of the tracked entity instance: - - /api/trackedEntityInstances/ - -The payload has to contain all, even non-modified, attributes and -relationships. Attributes or relationships that were present before and -are not present in the current payload any more will be removed from the -system. This means that if attributes/relationships are empty in the -current payload, all existing attributes/relationships will be deleted -from the system. From 2.31, it is possible to ignore empty -attributes/relationships in the current payload. A request parameter of -`ignoreEmptyCollection` set to `true` can be used in case you do not -wish to send in any attributes/relationships and also do not want them -to be deleted from the system. - -It is not allowed to update an already deleted tracked entity instance. -Also, it is not allowed to mark a tracked entity instance as deleted via -an update request. The same rules apply to enrollments and events. - -#### Deleting a tracked entity instance { #webapi_deleting_tei } - -In order to delete a tracked entity instance, make a request to the URL -identifying the tracked entity instance with the *DELETE* -method. The URL is equal to the one above used for update. - -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } - -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Complete example of payload including: tracked entity instance, enrollment and event { #webapi_create_enroll_tei_create_event } - -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute":"cejWyOfXge6", - "value":"Male" - } - ], - "enrollments":[ - { - "orgUnit":"DiszpKrYNg8", - "program":"ur1Edk5Oe2n", - "enrollmentDate":"2017-09-15", - "incidentDate":"2017-09-15", - "events":[ - { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues": [ - { - "dataElement":"qrur9Dvnyt5", - "value":"22" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Male" - } - ] - }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues":[ - { - "dataElement":"qrur9Dvnyt5", - "value":"26" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Female" - } - ] - } - ] - } - ] + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Generated tracked entity instance attributes { #webapi_generate_tei_attributes } - -Tracked entity instance attributes that are using automatic generation of -unique values have three endpoints that are used by apps. The endpoints -are all used for generating and reserving values. - -In 2.29 we introduced TextPattern for defining and generating these -patterns. All existing patterns will be converted to a valid TextPattern -when upgrading to 2.29. - -> **Note** -> -> As of 2.29, all these endpoints will require you to include any -> variables reported by the `requiredValues` endpoint listed as -> required. Existing patterns, consisting of only `#`, will be upgraded -> to the new TextPattern syntax `RANDOM()`. The RANDOM -> segment of the TextPattern is not a required variable, so this -> endpoint will work as before for patterns defined before 2.29. - -##### Finding required values { #finding-required-values } - -A TextPattern can contain variables that change based on different -factors. Some of these factors will be unknown to the server, so the -values for these variables have to be supplied when generating and -reserving values. - -This endpoint will return a map of required and optional values, that -the server will inject into the TextPattern when generating new values. -Required variables have to be supplied for the generation, but optional -variables should only be supplied if you know what you are doing. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### Generate value endpoint { #webapi_generate_values } - -Online web apps and other clients that want to generate a value that -will be used right away can use the simple generate endpoint. This -endpoint will generate a value that is guaranteed to be unique at the -time of generation. The value is also guaranteed not to be reserved. As -of 2.29, this endpoint will also reserve the value generated for 3 days. - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } - -The generate and reserve endpoint is used by offline clients that need -to be able to register tracked entities with unique ids. They will -reserve a number of unique ids that this device will then use when -registering new tracked entity instances. The endpoint is called to -retrieve a number of tracked entity instance reserved values. An -optional parameter numberToReserve specifies how many ids to generate -(default is 1). - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -Similar to the /generate endpoint, this endpoint can also specify the -expiration time in the same way. By adding the `?expiration=` -you can override the default 60 days. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### Reserved values { #reserved-values } - -Reserved values are currently not accessible through the api, however, they -are returned by the `generate` and `generateAndReserve` endpoints. The -following table explains the properties of the reserved value object: - -##### - - - -Table: Reserved values - -| Property | Descripción | -|---|---| -| ownerObject | The metadata type referenced when generating and reserving the value. Currently only TRACKEDENTITYATTRIBUTE is supported. | -| ownerUid | The uid of the metadata object referenced when generating and reserving the value. | -| key | A partially generated value where generated segments are not yet added. | -| value | The fully resolved value reserved. This is the value you send to the server when storing data. | -| created | The timestamp when the reservation was made | -| expiryDate | The timestamp when the reservation will no longer be reserved | - -Expired reservations are removed daily. If a pattern changes, values -that were already reserved will be accepted when storing data, even if -they don't match the new pattern, as long as the reservation has not -expired. - -#### Image attributes { #image-attributes } - -Working with image attributes is a lot like working with file data -values. The value of an attribute with the image value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///image` -endpoint will return the actual image. The optional height and width -parameters can be used to specify the dimensions of the image. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } - -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. - - /api/33/trackedEntityInstances - -##### Request syntax { #webapi_tei_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Descripción | -|---|---| -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Indicates whether to include soft deleted teis or not. It is false by default. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Descripción | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | The selected organisation units and the immediate children, i.e. the organisation units at the level below. | -| DESCENDANTS | The selected organisation units and all children, i.e. all organisation units in the sub-hierarchy. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| ALL | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -The available assigned user modes are explained in the following table. - - - -Table: Assigned user modes - -| Mode | Descripción | -|---|---| -| CURRENT | Includes events assigned to the current logged in user. | -| PROVIDED | Includes events assigned to the user provided in the request. | -| NONE | Includes unassigned events only. | -| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendant organisation unit query mode: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a filter: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an *IN* filter: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - &filter=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&page=2&pageSize=3 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Descripción | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### Tracked entity instance grid query { #webapi_tracked_entity_instance_grid_query } - -To query for tracked entity instances you can interact with the -*/api/trackedEntityInstances/grid* resource. There are two types of -queries: One where a *query* query parameter and optionally *attribute* -parameters are defined, and one where *attribute* and *filter* -parameters are defined. This endpoint uses a more compact "grid" format, -and is an alternative to the query in the previous section. - - /api/33/trackedEntityInstances/query - -##### Request syntax { #webapi_tei_grid_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Descripción | -|---|---| -| query | Query string. Attribute query parameter can be used to define which attributes to include in the response. If no attributes but a program is defined, the attributes from the program will be used. If no program is defined, all attributes will be used. There are two formats. The first is a plan query string. The second is on the format :. Operators can be EQ | LIKE. EQ implies exact matches on words, LIKE implies partial matches on words. The query will be split on space, where each word will form a logical AND query. | -| attribute | Attributes to be included in the response. Can also be used as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. Filters can be omitted in order to simply include the attribute in the response without any constraints. | -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| eventStatus | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Start date of event associated with the given program and event status. | -| eventEndDate | End date of event associated with the given program and event status. | -| programStage | The programStage for which the event related filters should be applied to. If not provided all stages will be considered. | -| skipMeta | Indicates whether meta data for the response should be included. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Descripción | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| CAPTURE | The data capture organisation units associated with the current user and all children, i.e. all organisation units in the sub-hierarchy. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -Note that you can specify "attribute" with filters or directly using the "filter" params for constraining the -instances to return. - -Certain rules apply to which attributes are returned. - - - If "query" is specified without any attributes or program, then all attributes that - are marked as "Display in List without Program" is included in the response. - - - If program is specified, all the attributes linked to the program will - be included in the response. - - - If tracked entity type is specified, then all tracked entity type attributes - will be included in the response. - -You can specify queries with words separated by space - in that -situation the system will query for each word independently and return -records where each word is contained in any attribute. A query item can -be specified once as an attribute and once as a filter if needed. The -query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - If *eventStatus* is specified then *eventStartDate* and - *eventEndDate* must also be specified. - - - A query cannot be specified together with filters. - - - Attribute items can only be specified once. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -A query on all attributes for a specific value and organisation unit, -using an exact word match: - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -A query on all attributes for a specific value, using a partial word -match: - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -You can query on multiple words separated by the URL character for -space which is %20, will use a logical AND query for each - word: - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -A query where the attributes to include in the response are specified: - - /api/33/trackedEntityInstances/query.json?query=isabel - &attribute=dv3nChNSIxy&attribute=AMpUYgxuCaE&ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendants organisation unit query mode: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &attribute=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a - filter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an IN - filter: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - &attribute=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&program=ur1Edk5Oe2n&programStartDate=2013-01-01 - &programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -To query for instances which have events of a given status within a -given time span: - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Descripción | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_grid_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - - - csv (application/csv) - - - xls (application/vnd.ms-excel) - -The response in JSON comes is in a tabular format and can look like the -following. The *headers* section describes the content of each column. -The instance, created, last updated, org unit and tracked entity columns -are always present. The following columns correspond to attributes -specified in the query. The *rows* section contains one row per -instance. - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### Tracked entity instance filters { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - /api/33/trackedEntityInstanceFilters - -##### Create and update a tracked entity instance filter definition { #create-and-update-a-tracked-entity-instance-filter-definition } - -For creating and updating a tracked entity instance filter in the -system, you will be working with the *trackedEntityInstanceFilters* -resource. The tracked entity instance filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Payload - -| Payload values | Descripción | Example | -|---|---|---| -| name | Name of the filter. Required. || -| Descripción | A description of the filter. || -| sortOrder | The sort order of the filter. Used in Tracker Capture to order the filters in the program dashboard. || -| style | Object containing css style. | ( "color": "blue", "icon": "fa fa-calendar"} | -| program | Object containing the id of the program. Required. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Table: Entity Query Criteria definition - -|||| -|---|---|---| -| attributeValueFilters | A list of attributeValueFilters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| enrollmentStatus | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | When this parameter is true, the filter only returns TEIs that have an enrollment with status followup. || -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayColumnOrder | To specify the output ordering of columns | "displayOrderColumns": ["enrollmentDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus | Any valid EventStatus | "eventStatus": "COMPLETED" | -| programStage | To specify a programStage uid to filter on. TEIs will be filtered based on presence of enrollment in the specified program stage.| "programStage"="a3kGcGDCuk6" | -| trackedEntityType | To specify a trackedEntityType filter TEIs on. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | To specify a list of trackedEntityInstances to use when querying TEIs. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod object date filtering based on enrollment incident date. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod object date filtering based on enrollment created date. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Table: Event filters definition - -|||| -|---|---|---| -| programStage | Which programStage the TEI needs an event in to be returned. | "eaDH9089uMp" | -| eventStatus | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT (events assigned to current user)| PROVIDED (events assigned to users provided in "assignedUsers" list) | NONE (events assigned to no one) | ANY (events assigned to anyone). If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -Table: Period definition - -|||| -|---|---|---| -| periodFrom | Number of days from current day. Can be positive or negative integer. | -15 | -| periodTo | Number of days from current day. Must be bigger than periodFrom. Can be positive or negative integer. | 15 | - -##### Tracked entity instance filters query { #tracked-entity-instance-filters-query } - -To query for tracked entity instance filters in the system, you can -interact with the */api/trackedEntityInstanceFilters* resource. - - - -Table: Tracked entity instance filters query parameters - -| Query parameter | Descripción | -|---|---| -| program | Program identifier. Restricts filters to the given program. | - -### Enrollment management { #webapi_enrollment_management } - -Enrollments have full CRUD support in the API. Together with the API -for tracked entity instances most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/enrollments - -#### Enrolling a tracked entity instance into a program { #webapi_enrolling_tei } - -For enrolling persons into a program, you will need to first get the -identifier of the person from the *trackedEntityInstances* resource. -Then, you will need to get the program identifier from the *programs* -resource. A template payload can be seen below: - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -This payload should be used in a *POST* request to the enrollments -resource identified by the following URL: - - /api/33/enrollments - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - /api/33/enrollments//cancelled - -For completing an enrollment for a tracked entity instance you can make a -*PUT* request to the following URL: - - /api/33/enrollments//completed - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - /api/33/enrollments/ - -#### Enrollment instance query { #webapi_enrollment_instance_query } - -To query for enrollments you can interact with the */api/enrollments* -resource. - - /api/33/enrollments - -##### Request syntax { #webapi_enrollment_query_request_syntax } - - - -Table: Enrollment query parameters - -| Query parameter | Descripción | -|---|---| -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| trackedEntityInstance | Tracked entity instance identifier. Should not be used together with trackedEntity. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| includeDeleted | Indicates whether to include soft deleted enrollments or not. It is false by default. | - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Descripción | -|---|---| -| SELECTED | Organisation units defined in the request (default). | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - -A query for all enrollments associated with a specific organisation unit -can look like this: - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -To constrain the response to enrollments which are part of a specific -program you can include a program query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the - query: - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - &programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to enrollments of a specific tracked entity -you can include a tracked entity query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -To constrain the response to enrollments of a specific tracked entity -instance you can include a tracked entity instance query parameter, in -this case we have restricted it to available enrollments viewable for -current - user: - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -By default the enrollments are returned in pages of size 50, to change -this you can use the page and pageSize query - parameters: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### Response format { #webapi_enrollment_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### Events { #webapi_events } - -This section is about sending and reading events. - - /api/33/events - -The different status of an event are: - -* **ACTIVE**: If a event has ACTIVE status, it is possible to edit the event details. COMPLETED events can be turned ACTIVE again and vice versa. -* **COMPLETED**: An event change the status to COMPLETED only when a user clicks the complete button. If a event has COMPLETED status, it is not possible to edit the event details. ACTIVE events can be turned COMPLETED again and vice versa. -* **SKIPPED**: Scheduled events that no longer need to happen. In Tracker Capture, there is a button for that. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### Sending events { #webapi_sending_events } - -DHIS2 supports three kinds of events: single events with no registration -(also referred to as anonymous events), single event with registration -and multiple events with registration. Registration implies that the -data is linked to a tracked entity instance which is identified using -some sort of identifier. - -To send events to DHIS2 you must interact with the *events* resource. -The approach to sending events is similar to sending aggregate data -values. You will need a *program* which can be looked up using the -*programs* resource, an *orgUnit* which can be looked up using the -*organisationUnits* resource, and a list of valid data element -identifiers which can be looked up using the *dataElements* resource. -For events with registration, a *tracked entity instance* identifier is -required, read about how to get this in the section about the -*trackedEntityInstances* resource. For sending events to programs with -multiple stages, you will need to also include the *programStage* -identifier, the identifiers for programStages can be found in the -*programStages* resource. - -A simple single event with no registration example payload in XML format -where we send events from the "Inpatient morbidity and mortality" -program for the "Ngelehun CHC" facility in the demo database can be seen -below: - -```xml - - - - - - - - - -``` - -To perform some testing we can save the XML payload as a file -called *event.xml* and send it as a POST request to the events resource -in the API using curl with the following command: - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -The same payload in JSON format looks like this: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -To send this you can save it to a file called *event.json* and use curl -like this: - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -We also support sending multiple events at the same time. A payload in -XML format might look like this: - -```xml - - - - - - - - - - - - - - - - - -``` - -You will receive an import summary with the response which can be -inspected in order to get information about the outcome of the request, -like how many values were imported successfully. The payload in JSON -format looks like this: - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -You can also use GeoJson to store any kind of geometry on your event. An example payload using GeoJson instead of the former latitude and longitude properties can be seen here: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -As part of the import summary you will also get the identifier -*reference* to the event you just sent, together with a *href* element -which points to the server location of this event. The table below -describes the meaning of each element. - - - -Table: Events resource format - -| Parámetros | Tipo | Requerido | Options (default first) | Descripción | -|---|---|---|---|---| -| program | string | verdadero || Identifier of the single event with no registration program | -| orgUnit | string | verdadero || Identifier of the organisation unit where the event took place | -| eventDate | date | verdadero || The date of when the event occurred | -| completedDate | date | falso || The date of when the event is completed. If not provided, the current date is selected as the event completed date | -| status | enum | falso | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Whether the event is complete or not | -| storedBy | string | falso | Defaults to current user | Who stored this event (can be username, system-name, etc) | -| coordinate | double | falso || Refers to where the event took place geographically (latitude and longitude) | -| dataElement | string | verdadero || Identifier of data element | -| value | string | verdadero || Data value or measure for this event | - -##### OrgUnit matching { #orgunit-matching } - -By default the orgUnit parameter will match on the -ID, you can also select the orgUnit id matching scheme by using the -parameter orgUnitIdScheme=SCHEME, where the options are: *ID*, *UID*, -*UUID*, *CODE*, and *NAME*. There is also the *ATTRIBUTE:* scheme, which -matches on a *unique* metadata attribute value. - -#### Updating events { #webapi_updating_events } - -To update an existing event, the format of the payload is the same, but -the URL you are posting to must add the identifier to the end of the URL -string and the request must be PUT. - -The payload has to contain all, even non-modified, attributes. -Attributes that were present before and are not present in the current -payload any more will be removed by the system. - -It is not allowed to update an already deleted event. The same applies -to tracked entity instance and enrollment. - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### Deleting events { #webapi_deleting_events } - -To delete an existing event, all you need is to send a DELETE request -with an identifier reference to the server you are using. - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### Assigning user to events { #webapi_user_assign_event } - -A user can be assigned to an event. This can be done by including the appropriate property in the payload when updating or creating the event. - - "assignedUser": "" - -The id refers to the if of the user. Only one user can be assigned to an event at a time. - -User assignment must be enabled in the program stage before users can be assigned to events. -#### Getting events { #webapi_getting_events } - -To get an existing event you can issue a GET request including the -identifier like this: - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### Querying and reading events { #webapi_querying_reading_events } - -This section explains how to read out the events that have been stored -in the DHIS2 instance. For more advanced uses of the event data, please -see the section on event analytics. The output format from the -`/api/events` endpoint will match the format that is used to send events -to it (which the analytics event api does not support). Both XML and -JSON are supported, either through adding .json/.xml or by setting the -appropriate *Accept* header. The query is paged by default and the -default page size is 50 events, *field* filtering works as it does for -metadata, add the *fields* parameter and include your wanted properties, -i.e. *?fields=program,status*. - - - -Table: Events resource query parameters - -| Clave | Tipo | Requerido | Descripción | -|---|---|---|---| -| program | identifier | true (if not programStage is provided) | Identifier of program | -| programStage | identifier | falso | Identifier of program stage | -| programStatus | enum | falso | Status of event in program, ca be ACTIVE | COMPLETED | CANCELLED | -| followUp | boolean | falso | Whether event is considered for follow up in program, can be true | false or omitted. | -| trackedEntityInstance | identifier | falso | Identifier of tracked entity instance | -| orgUnit | identifier | verdadero | Identifier of organisation unit | -| ouMode | enum | falso | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| startDate | date | falso | Only events newer than this date | -| endDate | date | falso | Only events older than this date | -| status | enum | falso | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | date | falso | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | date | falso | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | string | falso | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta | boolean | falso | Exclude the meta data part of response (improves performance) | -| page | entero | falso | Page number | -| pageSize | entero | falso | Number of items in each page | -| totalPages | boolean | falso | Indicates whether to include the total number of pages in the paging response. | -| skipPaging | boolean | falso | Indicates whether to skip paging in the query and return all events. | -| dataElementIdScheme | string | falso | Data element ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme | string | falso | Category Option Combo ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| orgUnitIdScheme | string | falso | Organisation Unit ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programIdScheme | string | falso | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programStageIdScheme | string | falso | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| idScheme | string | falso | Allows to set id scheme for data element, category option combo, orgUnit, program and program stage at once. | -| order | string | falso | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| event | comma delimited string | falso | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | boolean | falso | Skips event identifiers in the response | -| attributeCc (\*\*) | string | falso | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | string | falso | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | falso | verdadero | falso | Indicates whether the import should be done asynchronous or synchronous. | -| includeDeleted | boolean | falso | When true, soft deleted events will be included in your query result. | -| assignedUserMode | enum | falso | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | comma delimited strings | falso | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> **Note** -> -> If the query contains neither `attributeCC` nor `attributeCos`, the server returns events for all attribute option combos where the user has read access. - -##### Examples { #examples } - -Query for all events with children of a certain organisation unit: - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -Query for all events with all descendants of a certain organisation -unit, implying all organisation units in the sub-hierarchy: - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -Query for all events with a certain program and organisation unit: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -Query for all events with a certain program and organisation unit, -sorting by due date - ascending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -Query for the 10 events with the newest event date in a certain program -and organisation unit - by paging and ordering by due date descending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &order=eventDate:desc&pageSize=10&page=1 - -Query for all events with a certain program and organisation unit for a -specific tracked entity instance: - - /api/33/events.json?orgUnit=DiszpKrYNg8 - &program=eBAyeGv0exc&trackedEntityInstance=gfVxE3ALA9m - -Query for all events with a certain program and organisation unit older -or equal to - 2014-02-03: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -Query for all events with a certain program stage, organisation unit and -tracked entity instance in the year 2014: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &trackedEntityInstance=gfVxE3ALA9m&startDate=2014-01-01&endDate=2014-12-31 - -Query files associated with event data values. In the specific case of fetching an image file an -additional parameter can be provided to fetch the image with different dimensions. If dimension is -not provided, the system will return the original image. The parameter will be ignored in case of -fetching non-image files e.g pdf. Possible dimension values are *small(254 x 254), -medium(512 x 512), large(1024 x 1024) or original*. Any value other than those mentioned will be -discarded and the original image will be returned. - - /api/33/events/files?eventUid=hcmcWlYkg9u&dataElementUid=C0W4aFuVm4P&dimension=small - -Retrieve events with specified Organisation unit and Program, and use _Attribute:Gq0oWTf2DtN_ as -identifier scheme - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for -orgUnits, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as identifier -scheme for the rest of the metadata with assigned attribute. - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=Code - -#### Event grid query { #event-grid-query } - -In addition to the above event query end point, there is an event grid -query end point where a more compact "grid" format of events are -returned. This is possible by interacting with -/api/events/query.json|xml|xls|csv endpoint. - - /api/33/events/query - -Most of the query parameters mentioned in event querying and reading -section above are valid here. However, since the grid to be returned -comes with specific set of columns that apply to all rows (events), it -is mandatory to specify a program stage. It is not possible to mix -events from different programs or program stages in the return. - -Returning events from a single program stage, also opens up for new -functionality - for example sorting and searching events based on their -data element values. api/events/query has support for this. Below are -some examples - -A query to return an event grid containing only selected data elements -for a program stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &dataElement=qrur9Dvnyt5,fWIAEtYVEGk,K6uUAvq500H&order=lastUpdated:desc - &pageSize=50&page=1&totalPages=true - -A query to return an event grid containing all data elements of a -program - stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &includeAllDataElements=true - -A query to filter events based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50 - -In addition to the filtering, the above example also illustrates one -thing: the fact that there are no data elements mentioned to be returned -in the grid. When this happens, the system defaults back to return only -those data elements marked "Display in report" under program stage -configuration. - -We can also extend the above query to return us a grid sorted (asc|desc) -based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50&order=qrur9Dvnyt5:desc - -#### Event filters { #webapi_event_filters } - -To create, read, update and delete event filters you -can interact with the `/api/eventFilters` resource. - - /api/33/eventFilters - -##### Create and update an event filter definition { #create-and-update-an-event-filter-definition } - -For creating and updating an event filter in the -system, you will be working with the *eventFilters* -resource. *POST* is used to create and *PUT* method is used to update. The event filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Request Payload - -| Request Property | Descripción | Example | -|---|---|---| -| name | Name of the filter. | "name":"My working list" | -| Descripción | A description of the filter. | "description":"for listing all events assigned to me". | -| program | The uid of the program. | "program" : "a3kGcGDCuk6" | -| programStage | The uid of the program stage. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Object containing parameters for querying, sorting and filtering events. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Table: Event Query Criteria definition - -|||| -|---|---|---| -| followUp | Used to filter events based on enrollment followUp flag. Possible values are true|false. | "followUp": true | -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | To specify the output ordering of columns | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| dataFilters | To specify filters to be applied when listing events | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| status | Any valid EventStatus | "eventStatus": "COMPLETED" | -| events | To specify list of events | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod object date filtering based on completed date. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod object date filtering based on due date. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -The available assigned user selection modes are explained in the -following table. - - - -Table: Assigned user selection modes (event assignment) - -| Mode | Descripción | -|---|---| -| CURRENT | Assigned to the current logged in user | -| PROVIDED | Assigned to the users provided in the "assignedUser" parameter | -| NONE | Assigned to no users. | -| ANY | Assigned to any users. | - -A sample payload that can be used to create/update an eventFilter is shown below. - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### Retrieving and deleting event filters { #retrieving-and-deleting-event-filters } - -A specific event filter can be retrieved by using the following api - - GET /api/33/eventFilters/{uid} - -All event filters can be retrieved by using the following api. - - GET /api/33/eventFilters?fields=* - -All event filters for a specific program can be retrieved by using the following api - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -An event filter can be deleted by using the following api - - DELETE /api/33/eventFilters/{uid} - -### Relationships { #relationships } -Relationships are links between two entities in tracker. These entities can be tracked entity instances, enrollments and events. - -There are multiple endpoints that allow you to see, create, delete and update relationships. The most common is the /api/trackedEntityInstances endpoint, where you can include relationships in the payload to create, update or deleting them if you omit them - Similar to how you work with enrollments and events in the same endpoint. All the tracker endpoints, /api/trackedEntityInstances, /api/enrollments and /api/events also list their relationships if requested in the field filter. - -The standard endpoint for relationships is, however, /api/relationships. This endpoint provides all the normal CRUD operations for relationships. - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -This request will return a list of any relationship you have access to see that includes the trackedEntityInstance, enrollment or event you specified. Each relationship is represented with the following JSON: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -You can also view specified relationships using the following endpoint: - - GET /api/relationships/ - -To create or update a relationship, you can use the following endpoints: - - POST /api/relationships - PUT /api/relationships - -And use the following payload structure: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -To delete a relationship, you can use this endpoint: - - DELETE /api/relationships/ - -In our example payloads, we use a relationship between trackedEntityInstances. Because of this, the "from" and "to" properties of our payloads include "trackedEntityInstance" objects. If your relationship includes other entities, you can use the following properties: - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### Update strategies { #webapi_tei_update_strategies } - -Two update strategies for all 3 tracker endpoints are supported: -enrollment and event creation. This is useful when you have generated an -identifier on the client side and are not sure if it was created or not -on the server. - - - -Table: Available tracker strategies - -| Parámetros | Descripción | -|---|---| -| CREATE | Create only, this is the default behavior. | -| CREATE_AND_UPDATE | Try and match the ID, if it exist then update, if not create. | - -To change the parameter, please use the strategy parameter: - - POST /api/33/trackedEntityInstances?strategy=CREATE_AND_UPDATE - -### Tracker bulk deletion { #webapi_tracker_bulk_deletion } - -Bulk deletion of tracker objects work in a similar fashion to adding and -updating tracker objects, the only difference is that the -`importStrategy` is *DELETE*. - -*Example: Bulk deletion of tracked entity instances:* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*Example: Bulk deletion of enrollments:* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*Example: Bulk deletion of events:* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### Identifier reuse and item deletion via POST and PUT methods { #webapi_updating_and_deleting_items } - -Tracker endpoints */trackedEntityInstances*, */enrollments*, */events* -support CRUD operations. The system keeps track of used identifiers. -Therefore, an item which has been created and then deleted (e.g. events, -enrollments) cannot be created or updated again. If attempting to delete -an already deleted item, the system returns a success response as -deletion of an already deleted item implies no change. - -The system does not allow to delete an item via an update (*PUT*) or -create (*POST*) method. Therefore, an attribute *deleted* is ignored in -both *PUT* and *POST* methods, and in *POST* method it is by default set -to *false*. - -### Import parameters { #webapi_import_parameters } - -The import process can be customized using a set of import parameters: - - - -Table: Import parameters - -| Parámetros | Values (default first) | Descripción | -|---|---|---| -| dataElementIdScheme | id | name | code | attribute:ID | Property of the data element object to use to map the data values. | -| orgUnitIdScheme | id | name | code | attribute:ID | Property of the org unit object to use to map the data values. | -| idScheme | id | name | code| attribute:ID | Property of all objects including data elements, org units and category option combos, to use to map the data values. | -| dryRun | falso | verdadero | Whether to save changes on the server or just return the import summary. | -| strategy | CREATE | UPDATE | CREATE_AND_UPDATE | DELETE | Save objects of all, new or update import status on the server. | -| skipNotifications | true | false | Indicates whether to send notifications for completed events. | -| skipFirst | true | false | Relevant for CSV import only. Indicates whether CSV file contains a header row which should be skipped. | -| importReportMode | FULL, ERRORS, DEBUG | Sets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes *ObjectReports* for object which has errors. `FULL` returns an *ObjectReport* for all objects imported, and `DEBUG` returns the same plus a name for the object (if available). | - -#### CSV Import / Export { #webapi_events_csv_import_export } - -In addition to XML and JSON for event import/export, in DHIS2.17 we -introduced support for the CSV format. Support for this format builds on -what was described in the last section, so here we will only write about -what the CSV specific parts are. - -To use the CSV format you must either use the `/api/events.csv` -endpoint, or add *content-type: text/csv* for import, and *accept: -text/csv* for export when using the `/api/events` endpoint. - -The order of column in the CSV which are used for both export and import -is as follows: - - - -Table: CSV column - -| Index | Clave | Tipo | Descripción | -|---|---|---|---| -| 1 | event | identifier | Identifier of event | -| 2 | status | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | program | identifier | Identifier of program | -| 4 | programStage | identifier | Identifier of program stage | -| 5 | enrollment | identifier | Identifier of enrollment (program instance) | -| 6 | orgUnit | identifier | Identifier of organisation unit | -| 7 | eventDate | date | Event date | -| 8 | dueDate | date | Due Date | -| 9 | latitude | double | Latitude where event happened | -| 10 | longitude | double | Longitude where event happened | -| 11 | dataElement | identifier | Identifier of data element | -| 12 | value | string | Value / measure of event | -| 13 | storedBy | string | Event was stored by (defaults to current user) | -| 14 | providedElsewhere | boolean | Was this value collected somewhere else | -| 14 | completedDate | date | Completed date of event | -| 14 | completedBy | string | Username of user who completed event | - -*Example of 2 events with 2 different data value - each:* - -```csv -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,1,, -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,2,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,3,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,4,, -``` - -#### Import strategy: SYNC { #webapi_sync_import_strategy } - -The import strategy SYNC should be used only by internal synchronization -task and not for regular import. The SYNC strategy allows all 3 -operations: CREATE, UPDATE, DELETE to be present in the payload at the -same time. - -### Tracker Ownership Management { #webapi_tracker_ownership_management } - -A new concept called Tracker Ownership is introduced from 2.30. There -will now be one owner organisation unit for a tracked entity instance in -the context of a program. Programs that are configured with an access -level of *PROTECTED* or *CLOSED* will adhere to the ownership -privileges. Only those users belonging to the owning org unit for a -tracked entity-program combination will be able to access the data -related to that program for that tracked entity. - -#### Tracker Ownership Override : Break the Glass { #webapi_tracker_ownership_override_api } - -It is possible to temporarily override this ownership privilege for a -program that is configured with an access level of *PROTECTED*. Any user -will be able to temporarily gain access to the program related data, if -the user specifies a reason for accessing the tracked entity-program -data. This act of temporarily gaining access is termed as *breaking the -glass*. Currently, the temporary access is granted for 3 hours. DHIS2 -audits breaking the glass along with the reason specified by the user. -It is not possible to gain temporary access to a program that has been -configured with an access level of *CLOSED*. To break the glass for a -tracked entity program combination, you can issue a POST request as -shown: - - /api/33/tracker/ownership/override?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care - -#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer_api } - -It is possible to transfer the ownership of a tracked entity-program -from one org unit to another. This will be useful in case of patient -referrals or migrations. Only an owner (or users who have broken the -glass) can transfer the ownership. To transfer ownership of a tracked -entity-program to another organisation unit, you can issue a PUT request -as shown: - - /api/33/tracker/ownership/transfer?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&ou=EJNxP3WreNP - - -## Potential Duplicates { #potential-duplicates } - -Potential duplicates are records we work with in the data deduplication feature. Due to the nature of the deduplication feature, this API endpoint is somewhat restricted. - -A potential duplicate represents a pair of records which are suspected to be a duplicate. - -The payload of a potential duplicate looks like this: - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -You can retrieve a list of potential duplicates using the following endpoint: - - GET /api/potentialDuplicates - -| Parameter name | Descripción | Tipo | Allowed values | -|---|---|---|---| -| teis | List of tracked entity instances | List of string (separated by comma)| existing tracked entity instance id | -| status | Potential duplicate status | string | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Status code | Descripción -|---|---| -| 400 | Invalid input status - -You can inspect individual potential duplicate records: - - GET /api/potentialDuplicates/ - -| Status code | Descripción -|---|---| -| 404 | Potential duplicate not found - -To create a new potential duplicate, you can use this endpoint: - - POST /api/potentialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Status code | Descripción -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -To update a potential duplicate status: - - PUT /api/potentialDuplicates/ - -| Parameter name | Descripción | Tipo | Allowed values | -|---|---|---|---| -| status | Potential duplicate status | string | `OPEN`, `INVALID`, `MERGED` | - -| Status code | Descripción -|---|---| -| 400 | You can't update a potential duplicate to MERGED as this is possible only by a merging request -| 400 | You can't update a potential duplicate that is already in a MERGED status - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -To merge a Potential Duplicate, or the two tracked entity instances the Potential Duplicate represents, the following endpoint can be used: - - POST /api/potentialDuplicates//merge - -| Parameter name | Descripción | Tipo | Allowed values | -|---|---|---|---| -| mergeStrategy | Strategy to use for merging the potentialDuplicate | enum | AUTO(default) or MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- The same attribute has different values in each tracked entity instance -- Both tracked entity instances are enrolled in the same program -- Tracked entity instances have different types - -If any conflict is encountered, an errormessage is returned to the user. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -When requesting an automatic merge like this, a payload is not required and will be ignored. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Relationship cannot be between the original and the duplicate (This results in an invalid self-referencing relationship) -- Relationship cannot be of the same type and to the same object in both tracked entity instances (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) - -There are two ways to do a manual merge: With and without a payload. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -Otherwise, if a manual merge is requested with a payload, the payload refers to what data should be moved from the duplicate to the original. The payload looks like this: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -The fields are explained in the following table. - - -Table: Program Notification Template payload - -| Field | Requerido | Descripción | Values | -|---|---|---|---| -| name | Sí | name of Program Notification Template | case-notification-alert | -| notificationTrigger | Sí | When notification should be triggered. Possible values are ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| ENROLLMENT | -| subjectTemplate | No | Subject template string | Case notification V{org_unit_name} | -| messageTemplate | Sí | Message template string | Case notification A{h5FuguPFF2j} | -| notificationRecipient | YES | Who is going to receive notification. Possible values are USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | No | Which channel should be used for this notification. It can be either SMS, EMAIL or HTTP | SMS | -| sendRepeatable | No | Whether notification should be sent multiple times | falso | - -NOTE: WEB_HOOK notificationRecipient is used only to POST http request to an external system. Make sure to choose HTTP delivery channel when using WEB_HOOK. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -The list of Program Notification Templates can be retrieved using GET. - - GET /api/programNotificationTemplates - -For one particular Program Notification Template. - - GET /api/33/programNotificationTemplates/{uid} - -To get filtered list of Program Notification Templates - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Program Notification Template can be deleted using DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -Program message lets you send messages to tracked entity instances, -contact addresses associated with organisation units, phone numbers and -email addresses. You can send messages through the `messages` resource. - - /api/33/messages - -### Sending program messages { #sending-program-messages } - -Program messages can be sent using two delivery channels: - - - SMS (SMS) - - - Email address (EMAIL) - -Program messages can be sent to various recipients: - - - Tracked entity instance: The system will look up attributes of value - type PHONE_NUMBER or EMAIL (depending on the specified delivery - channels) and use the corresponding attribute values. - - - Organisation unit: The system will use the phone number or email - information registered for the organisation unit. - - - List of phone numbers: The system will use the explicitly defined - phone numbers. - - - List of email addresses: The system will use the explicitly defined - email addresses. - -Below is a sample JSON payload for sending messages using POST requests. -Note that message resource accepts a wrapper object named -`programMessages` which can contain any number of program messages. - - POST /api/33/messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -The fields are explained in the following table. - - - -Table: Program message payload - -| Field | Requerido | Descripción | Values | -|---|---|---|---| -| recipients | Sí | Recipients of the program message. At least one recipient must be specified. Any number of recipients / types can be specified for a message. | Can be trackedEntityInstance, organisationUnit, an array of phoneNumbers or an array of emailAddresses. | -| programInstance | Either this or programStageInstance required | The program instance / enrollment. | Enrollment ID. | -| programStageInstance | Either this or programInstance required | The program stage instance / event. | Event ID. | -| deliveryChannels | Sí | Array of delivery channels. | SMS | EMAIL | -| subject | No | The message subject. Not applicable for SMS delivery channel. | Text. | -| texto | Sí | The message text. | Text. | -| storeCopy | No | Whether to store a copy of the program message in DHIS2. | false (default) | true | - -A minimalistic example for sending a message over SMS to a tracked -entity instance looks like this: - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### Retrieving and deleting program messages { #retrieving-and-deleting-program-messages } - -The list of messages can be retrieved using GET. - - GET /api/33/messages - -To get the list of sent tracker messages, the below endpoint can be used. ProgramInstance or ProgramStageInstance uid has to be provided. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -To get the list of all scheduled message - - GET /api/33/messages/scheduled - GET /api/33/messages/scheduled?scheduledAt=2020-12-12 - -One particular message can also be retrieved using GET. - - GET /api/33/messages/{uid} - -Message can be deleted using DELETE. - - DELETE /api/33/messages/{uid} - - -### Querying program messages { #querying-program-messages } - -The program message API supports program message queries based on -request parameters. Messages can be filtered based on below mentioned -query parameters. All requests should use the GET HTTP verb for -retrieving information. - - - -Table: Query program messages API - -| Parámetros | URL | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # Email { #email } diff --git a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index 97531c80e..537fa465d 100644 --- a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- Gestionar - DHIS core version 2.37 +- Gestionar template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md index 377547181..6e6bd3dbe 100644 --- a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- Gestionar - DHIS core version 2.39 +- Gestionar template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index 2b338b2bb..40c2e087b 100644 --- a/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/es_419/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- Gestionar - DHIS core version master +- Gestionar template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index 9fe3844e4..96375e077 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/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 - Uso +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index 5eff71af1..db2eec76e 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/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 - Uso +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 082a808ad..bc94ae262 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - Uso +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 6f40491c0..d3065e841 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - Uso +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/.cache_timestamp b/projects/dhis2-single-page-docs/fr/.cache_timestamp index bc7c1b9c5..228d7473c 100644 --- a/projects/dhis2-single-page-docs/fr/.cache_timestamp +++ b/projects/dhis2-single-page-docs/fr/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:27:24Z \ No newline at end of file +2024-06-04T21:27:22Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-232__web-api-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-232__web-api-md index 89fde61a4..3d7fc65ba 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-232__web-api-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-232__web-api-md @@ -4748,7 +4748,7 @@ programRuleVariable model. \-coming- -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } @@ -6371,7 +6371,7 @@ Get all audits for data approval workflow RwNpkAM7Hw7: /api/27/audits/dataApproval?wf=RwNpkAM7Hw7 -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } @@ -6391,17 +6391,17 @@ a message to the *Mobile* user. We will then pretend to be the mobile user and read our new message. Following this we will manage the admin user inbox by marking and removing messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : This is the subject @@ -6413,8 +6413,8 @@ the following XML format for sending to multiple users: -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : This is the subject @@ -6426,8 +6426,8 @@ use: -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : This is the subject @@ -6500,16 +6500,16 @@ that we receive a *Location*HTTP header which value informs us of the URL of the newly created message conversation resource - this can be used by a consumer to perform further action. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : curl "https://play.dhis2.org/demo/api/26/messageConversations" -H "Accept:application/xml" -u mobile:district -X GET -v -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : @@ -6532,9 +6532,9 @@ are now able to construct a URL for sending our reply: "https://play.dhis2.org/demo/api/26/messageConversations/ZjHHSjyyeJ2" -H "Content-Type:text/plain" -u mobile:district -X POST -v -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? @@ -6542,7 +6542,7 @@ The filter searches for matches in subject, messages' text and messages' senders for message conversations. The default query operator is token due to better text search, but you can supply your own operator. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } @@ -6570,14 +6570,14 @@ with id *xE7jOejl9FI* from the conversation with id *jMe43trzrdi*: curl https://play.dhis2.org/demo/api/26/messageConversations/jMe43 -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. { "removed" : ["xE7jOejl9FI"] } -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. { "message" : "No user with uid: dMV6G0tPAEa" } @@ -6600,17 +6600,17 @@ behalf of another user by giving an optional user id curl "https://play.dhis2.org/demo/api/26/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. Marking messages read or unread follows similar semantics as batch removals, and also supports batch operations. To mark messages as read @@ -6620,13 +6620,13 @@ unread we issue an identical request to the *messageConversations/unread* resource. As is the case for removals, an optional *user* request parameter can be given. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : curl "https://play.dhis2.org/dev/api/messageConversations/read" -d '["ZrKML5WiyFm","Gc03smoTm6q"]' -X POST -H "Content-Type: application/json" -u admin:district -v -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : { "markedRead" : [ "ZrKML5WiyFm", "Gc03smoTm6q" ] } @@ -6636,8 +6636,8 @@ message conversation. The resource is located https://play.dhis2.org/demo/api/30/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ``` { @@ -6663,22 +6663,22 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. curl -F file=@attachment.png -u admin:district https://play.dhis2.org/demo/api/messageConversations/attachments -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. { "created":"2018-07-20T16:54:18.210", @@ -6702,8 +6702,8 @@ attachment with the message. "id":"fTpI4GOmujz" } -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ``` { @@ -6735,8 +6735,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. curl -d "Yes the Mortality data set has been reported" "https://play.dhis2.org/demo/api/26/messageConversations/ZjHHSjyyeJ2?attachments=fTpI4GOmujz,h2ZsOxMFMfq" @@ -6752,7 +6752,7 @@ Where \ is the *messageConversation* ID, \ is the ID of the *message* that contains the attachment, and \ is the ID of the specific *messageAttachment*. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } @@ -6765,15 +6765,15 @@ a status and a priority to a ticket. To do this, use these POST https://play.dhis2.org/demo/api/26/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. @@ -6807,9 +6807,9 @@ group.
A list of valid status and priority values
-You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: curl -d "This is an internal message" "https://play.dhis2.org/demo/api/26/messageConversations/ZjHHSjyyeJ2?internal=true" @@ -19268,7 +19268,7 @@ An example curl command looks like this: -d "https://dhis2.org/metadata-repo/221/trainingland-org-units/metadata.json" -H "Content-Type:text/plain" -u admin:district -v -## Icons { #webapi_icons } +## Icônes { #webapi_icons } diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-233__web-api-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-233__web-api-md index fe49ff43c..3180afcd1 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-233__web-api-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-233__web-api-md @@ -4933,7 +4933,7 @@ programRuleVariable model. - TODO Coming - -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } @@ -6624,42 +6624,42 @@ Get all audits for data approval workflow RwNpkAM7Hw7: /api/33/audits/dataApproval?wf=RwNpkAM7Hw7 -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6668,13 +6668,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6683,13 +6683,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6708,25 +6708,25 @@ whether she has reported data for January 2014: ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -6758,23 +6758,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -6799,9 +6799,9 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? @@ -6809,7 +6809,7 @@ The filter searches for matches in subject, text, and senders for message conversations. The default query operator is *token*, however other operators can be defined in the query. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } @@ -6819,26 +6819,26 @@ have a look at managing a user's message inbox by removing and marking conversations through the Web-API. We will do so by performing some maintenance in the inbox of the "DHIS Administrator" user. -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -6846,8 +6846,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -6855,38 +6855,38 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. Marking messages read or unread follows similar semantics as batch removals, and also supports batch operations. To mark messages as read @@ -6896,7 +6896,7 @@ unread we issue an identical request to the `messageConversations/unread` resource. As is the case for removals, an optional *user* request parameter can be given. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -6904,7 +6904,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -6912,12 +6912,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -6943,25 +6943,25 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -6987,8 +6987,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -7019,8 +7019,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7028,38 +7028,36 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. @@ -7093,9 +7091,9 @@ group.
A list of valid status and priority values
-You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -20098,7 +20096,7 @@ curl "localhost:8080/api/synchronization/metadataPull" -X POST -H "Content-Type:text/plain" -u admin:district ``` -## Icons { #webapi_icons } +## Icônes { #webapi_icons } diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-234__web-api-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-234__web-api-md index c24028c38..8b5608827 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-234__web-api-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-234__web-api-md @@ -1789,8 +1789,7 @@ listed below. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -1827,10 +1826,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -5159,7 +5155,7 @@ programRuleVariable model. - TODO Coming - -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } @@ -6896,42 +6892,42 @@ Get all audits for data approval workflow RwNpkAM7Hw7: /api/33/audits/dataApproval?wf=RwNpkAM7Hw7 -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6940,13 +6936,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6955,13 +6951,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6980,25 +6976,25 @@ whether she has reported data for January 2014: ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -7030,23 +7026,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7071,9 +7067,9 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? @@ -7081,36 +7077,36 @@ The filter searches for matches in subject, text, and senders for message conversations. The default query operator is *token*, however other operators can be defined in the query. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. - -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. - -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». + +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. + +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -7118,8 +7114,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -7127,38 +7123,38 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. Marking messages read or unread follows similar semantics as batch removals, and also supports batch operations. To mark messages as read @@ -7168,7 +7164,7 @@ unread we issue an identical request to the `messageConversations/unread` resource. As is the case for removals, an optional *user* request parameter can be given. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -7176,7 +7172,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -7184,12 +7180,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -7215,25 +7211,25 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -7259,8 +7255,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -7291,8 +7287,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7300,38 +7296,36 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. @@ -7365,9 +7359,9 @@ group.
A list of valid status and priority values
-You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -21298,7 +21292,7 @@ curl "localhost:8080/api/synchronization/metadataPull" -X POST -H "Content-Type:text/plain" -u admin:district ``` -## Icons { #webapi_icons } +## Icônes { #webapi_icons } diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-235__web-api-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-235__web-api-md index a4722c2b0..f4362b0e5 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-235__web-api-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-235__web-api-md @@ -1789,8 +1789,7 @@ listed below. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -1827,10 +1826,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -3344,7 +3340,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -5212,7 +5208,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } @@ -6953,42 +6949,42 @@ Get all audits for data approval workflow RwNpkAM7Hw7: /api/33/audits/dataApproval?wf=RwNpkAM7Hw7 -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6997,13 +6993,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7012,13 +7008,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7037,25 +7033,25 @@ whether she has reported data for January 2014: ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -7087,23 +7083,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7128,9 +7124,9 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? @@ -7138,36 +7134,36 @@ The filter searches for matches in subject, text, and senders for message conversations. The default query operator is *token*, however other operators can be defined in the query. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. - -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. - -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». + +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. + +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -7175,8 +7171,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -7184,38 +7180,38 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. Marking messages read or unread follows similar semantics as batch removals, and also supports batch operations. To mark messages as read @@ -7225,7 +7221,7 @@ unread we issue an identical request to the `messageConversations/unread` resource. As is the case for removals, an optional *user* request parameter can be given. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -7233,7 +7229,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -7241,12 +7237,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -7272,25 +7268,25 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -7316,8 +7312,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -7348,8 +7344,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7357,38 +7353,36 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. @@ -7422,9 +7416,9 @@ group.
A list of valid status and priority values
-You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -21708,7 +21702,7 @@ curl "localhost:8080/api/synchronization/metadataPull" -X POST -H "Content-Type:text/plain" -u admin:district ``` -## Icons { #webapi_icons } +## Icônes { #webapi_icons } diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-MASTER__web-api-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-MASTER__web-api-md index 1a33484f4..d0b0b34b8 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-MASTER__web-api-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DEVELOPER-REFERENCE__DHIS-CORE-VERSION-MASTER__web-api-md @@ -1784,8 +1784,7 @@ Le point d'extrémité de l'importation des métadonnées prend en charge une va -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -1822,10 +1821,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1988,7 +1984,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } @@ -3178,7 +3174,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } @@ -4392,7 +4388,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -8108,42 +8104,42 @@ Get all audits for data approval workflow RwNpkAM7Hw7: # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -8152,13 +8148,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -8167,13 +8163,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -8182,35 +8178,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -8242,23 +8238,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -8283,46 +8279,46 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. - -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. - -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». + +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. + +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -8330,8 +8326,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -8339,48 +8335,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -8388,7 +8384,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -8396,12 +8392,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -8427,25 +8423,25 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -8471,8 +8467,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -8503,8 +8499,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -8512,38 +8508,36 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. @@ -8577,9 +8571,9 @@ group.
A list of valid status and priority values
-You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-233__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-233__developer-manual-md index fe49ff43c..3180afcd1 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-233__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-233__developer-manual-md @@ -4933,7 +4933,7 @@ programRuleVariable model. - TODO Coming - -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } @@ -6624,42 +6624,42 @@ Get all audits for data approval workflow RwNpkAM7Hw7: /api/33/audits/dataApproval?wf=RwNpkAM7Hw7 -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6668,13 +6668,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6683,13 +6683,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6708,25 +6708,25 @@ whether she has reported data for January 2014: ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -6758,23 +6758,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -6799,9 +6799,9 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? @@ -6809,7 +6809,7 @@ The filter searches for matches in subject, text, and senders for message conversations. The default query operator is *token*, however other operators can be defined in the query. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } @@ -6819,26 +6819,26 @@ have a look at managing a user's message inbox by removing and marking conversations through the Web-API. We will do so by performing some maintenance in the inbox of the "DHIS Administrator" user. -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -6846,8 +6846,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -6855,38 +6855,38 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. Marking messages read or unread follows similar semantics as batch removals, and also supports batch operations. To mark messages as read @@ -6896,7 +6896,7 @@ unread we issue an identical request to the `messageConversations/unread` resource. As is the case for removals, an optional *user* request parameter can be given. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -6904,7 +6904,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -6912,12 +6912,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -6943,25 +6943,25 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -6987,8 +6987,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -7019,8 +7019,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7028,38 +7028,36 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. @@ -7093,9 +7091,9 @@ group.
A list of valid status and priority values
-You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -20098,7 +20096,7 @@ curl "localhost:8080/api/synchronization/metadataPull" -X POST -H "Content-Type:text/plain" -u admin:district ``` -## Icons { #webapi_icons } +## Icônes { #webapi_icons } diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-234__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-234__developer-manual-md index 66e29610f..1e2a148e0 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-234__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-234__developer-manual-md @@ -6121,8 +6121,8 @@ The resource we need to interact with when sending and reading messages is the _ ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6135,8 +6135,8 @@ For sending to all users contained in one or more user groups, we can use: ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6149,8 +6149,8 @@ For sending to all users connected to one or more organisation units, we can use ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6163,8 +6163,8 @@ Since we want to send a message to our friend the mobile user we need to look up ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? @@ -6178,7 +6178,7 @@ curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -6219,7 +6219,7 @@ curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml /status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-235__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-235__developer-manual-md index b2002803a..4ff1909e0 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-235__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-235__developer-manual-md @@ -2923,7 +2923,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | --- | --- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -6178,8 +6178,8 @@ The resource we need to interact with when sending and reading messages is the _ ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6192,8 +6192,8 @@ For sending to all users contained in one or more user groups, we can use: ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6206,8 +6206,8 @@ For sending to all users connected to one or more organisation units, we can use ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6220,8 +6220,8 @@ Since we want to send a message to our friend the mobile user we need to look up ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? @@ -6235,7 +6235,7 @@ curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -6276,7 +6276,7 @@ curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml /status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-236__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-236__developer-manual-md index 04d7937e4..dda752e7a 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-236__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-236__developer-manual-md @@ -3817,7 +3817,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | --- | --- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -7832,8 +7832,8 @@ The resource we need to interact with when sending and reading messages is the _ ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7846,8 +7846,8 @@ For sending to all users contained in one or more user groups, we can use: ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7860,8 +7860,8 @@ For sending to all users connected to one or more organisation units, we can use ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7874,8 +7874,8 @@ Since we want to send a message to our friend the mobile user we need to look up ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? @@ -7889,7 +7889,7 @@ curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -7930,7 +7930,7 @@ curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml /status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index 892404e9e..b02be131e 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2023-01-13' tags: -- DHIS core version 2.37 - Développement +- DHIS core version 2.37 template: single.html --- @@ -1376,19 +1376,18 @@ Tableau : Paramètres d'importation | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | | ~~mergeMode~~ (mode de fusion) | ~~REPLACE, MERGE~~ (remplacer, fusionner) | ~~Définit le mode de fusion. Lors des mises à jour nous avons deux façons de fusionner l'ancien objet avec le nouveau. Le mode `MERGE` ne remplacera l'ancienne propriété que si la nouvelle n'est pas nulle. Pour le mode `REPLACE`, toutes les propriétés sont remplacées qu'elles soient nulles ou non.~~ (*) | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | > (*) Currently the `mergeMode=MERGE` option of the import service has limitations and doesn't support all objects. It doesn't work with some object types such as Embedded objects, or objects which are saved as JSONB format in database ( sharing, attributeValues, etc...). Fixing those issues are complicated and would just cause new issues. Therefore, this `mergedMode=MERGE` is deprecated and currently is not recommended to use. The update mode should always be mergedMode=REPLACE. We have developed a new [JSON Patch API](#webapi_partial_updates) which can be used as an alternative approach. This feature is introduced in 2.37 release. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -1425,10 +1424,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1501,7 +1497,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons @@ -1639,7 +1635,7 @@ Table: Style properties | Propriété | Description | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -1962,7 +1958,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -2021,7 +2017,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2354,7 +2350,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -2882,7 +2878,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -6641,38 +6637,38 @@ Get all audits for data approval workflow RwNpkAM7Hw7: # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6681,13 +6677,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6696,13 +6692,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6711,35 +6707,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -6771,23 +6767,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -6812,44 +6808,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -6857,8 +6853,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -6866,48 +6862,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -6915,7 +6911,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -6923,12 +6919,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -6954,23 +6950,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -6996,8 +6992,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -7028,8 +7024,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7037,51 +7033,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -7406,29 +7400,29 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | -| reportingParams | Object used to define boolean attributes related to reporting. | +| reportingParams (Paramètres de déclaration) | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | | rowSubTotals | Displays (or not) the row sub-totals. Boolean value. | @@ -8708,7 +8702,7 @@ Table: Pivot table configuration | Type d'agrégation | chaîne | Non | "SUM" |"AVERAGE" | "AVERAGE_SUM_ORG_UNIT"|"LAST"|"LAST_AVERAGE_ORG_UNIT"| "COUNT" | "STDDEV" | "VARIANCE" | "MIN" | "MAX" | Override the data element's default aggregation type | | displayDensity (afficher la densité) | chaîne | Non | "NORMAL" | "COMFORTABLE" | "COMPACT" | The amount of space inside table cells | | fontSize (taille de la police) | chaîne | Non | "NORMAL" | "LARGE" | "SMALL" | Table font size | -| digitGroupSeparator | chaîne | Non | "SPACE" | "COMMA" | "NONE" | How values are formatted: 1 000 | 1,000 | 1000 | +| digitGroupSeparator (Séparateur de groupes de chiffres) | chaîne | Non | "SPACE" | "COMMA" | "NONE" | How values are formatted: 1 000 | 1,000 | 1000 | | legendSet (ensemble de légende) | object | Non || Color the values in the table according to the legend set | | userOrgUnit (unité d'organisation d'utilisateur) | string / array | Non || Organisation unit identifiers, overrides organisation units associated with curretn user, single or array | | relativePeriodDate (Date de la période relative) | chaîne | Non || Identifiant de date, par exemple : "2016-01-01". Il remplace la date de début de la période relative | @@ -8856,16 +8850,16 @@ Table: Chart configuration | showValues | booléen | Non | faux | vrai | Whether to display data values on the chart | | hideEmptyRows (cacher les lignes vides) | booléen | Non | faux | vrai | Whether to hide empty categories | | completedOnly | booléen | Non | faux | vrai | Whether to only show completed events | -| regressionType | chaîne | Non | "NONE" | "LINEAR" | Show trend lines | -| targetLineValue | nombre | Non || Display a target line with this value | +| regressionType (type de régression) | chaîne | Non | "NONE" | "LINEAR" | Show trend lines | +| targetLineValue (valeur de la ligne cible) | nombre | Non || Display a target line with this value | | targetLineTitle | chaîne | Non || Display a title on the target line (does not apply without a target line value) | -| baseLineValue | nombre | Non || Display a base line with this value | +| baseLineValue (Valeur de la ligne de base) | nombre | Non || Display a base line with this value | | baseLineTitle | chaîne | Non || Display a title on the base line (does not apply without a base line value) | | rangeAxisTitle | nombre | Non || Title to be displayed along the range axis | -| rangeAxisMaxValue | nombre | Non || Max value for the range axis to display | -| rangeAxisMinValue | nombre | Non || Min value for the range axis to display | -| rangeAxisSteps | nombre | Non || Number of steps for the range axis to display | -| rangeAxisDecimals | nombre | Non || Bumber of decimals for the range axis to display | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | nombre | Non || Max value for the range axis to display | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | nombre | Non || Min value for the range axis to display | +| rangeAxisSteps (Étapes de l'axe de la plage) | nombre | Non || Number of steps for the range axis to display | +| rangeAxisDecimals (Décimales de l'axe de la plage) | nombre | Non || Bumber of decimals for the range axis to display | | domainAxisTitle | nombre | Non || Title to be displayed along the domain axis | | Type d'agrégation | chaîne | Non | "SUM" |"AVERAGE" | "AVERAGE_SUM_ORG_UNIT"|"LAST"|"LAST_AVERAGE_ORG_UNIT"| "COUNT" | "STDDEV" | "VARIANCE" | "MIN" | "MAX" | Override the data element's default aggregation type | | hideLegend | booléen | Non | faux | vrai | Whether to hide the series legend | @@ -16104,7 +16098,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma de l'identifiant d'option de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NAME`, `ATTRIBUTE`, `AUTO` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être ignoré, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `IGNORER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index d86c2ebeb..c539e277c 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 template: single.html --- @@ -1412,19 +1412,18 @@ Tableau : Paramètres d'importation | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | | ~~mergeMode~~ (mode de fusion) | ~~REPLACE, MERGE~~ (remplacer, fusionner) | ~~Définit le mode de fusion. Lors des mises à jour nous avons deux façons de fusionner l'ancien objet avec le nouveau. Le mode `MERGE` ne remplacera l'ancienne propriété que si la nouvelle n'est pas nulle. Pour le mode `REPLACE`, toutes les propriétés sont remplacées qu'elles soient nulles ou non.~~ (*) | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | > (*) Currently the `mergeMode=MERGE` option of the import service has limitations and doesn't support all objects. It doesn't work with some object types such as Embedded objects, or objects which are saved as JSONB format in database ( sharing, attributeValues, etc...). Fixing those issues are complicated and would just cause new issues. Therefore, this `mergedMode=MERGE` is deprecated and currently is not recommended to use. The update mode should always be mergedMode=REPLACE. We have developed a new [JSON Patch API](#webapi_partial_updates) which can be used as an alternative approach. This feature is introduced in 2.37 release. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -1461,10 +1460,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1537,7 +1533,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons @@ -1676,7 +1672,7 @@ Table: Style properties | Propriété | Description | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -1999,7 +1995,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -2058,7 +2054,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2397,7 +2393,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -2925,7 +2921,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -7217,38 +7213,38 @@ Get all audits for data approval workflow RwNpkAM7Hw7: # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7257,13 +7253,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7272,13 +7268,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7287,35 +7283,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -7347,23 +7343,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7388,44 +7384,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -7433,8 +7429,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -7442,48 +7438,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -7491,7 +7487,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -7499,12 +7495,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -7530,23 +7526,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -7572,8 +7568,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -7604,8 +7600,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7613,51 +7609,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -7993,29 +7987,29 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | -| reportingParams | Object used to define boolean attributes related to reporting. | +| reportingParams (Paramètres de déclaration) | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | | rowSubTotals | Displays (or not) the row sub-totals. Boolean value. | @@ -8545,25 +8539,25 @@ Tableau : Attributs de la visualisation d'événements | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | @@ -17428,7 +17422,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index 3f7a79d0e..8797d2a5b 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 template: single.html --- @@ -1522,19 +1522,18 @@ Tableau : Paramètres d'importation | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | | ~~mergeMode~~ (mode de fusion) | ~~REPLACE, MERGE~~ (remplacer, fusionner) | ~~Définit le mode de fusion. Lors des mises à jour nous avons deux façons de fusionner l'ancien objet avec le nouveau. Le mode `MERGE` ne remplacera l'ancienne propriété que si la nouvelle n'est pas nulle. Pour le mode `REPLACE`, toutes les propriétés sont remplacées qu'elles soient nulles ou non.~~ (*) | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | > (*) Currently the `mergeMode=MERGE` option of the import service has limitations and doesn't support all objects. It doesn't work with some object types such as Embedded objects, or objects which are saved as JSONB format in database ( sharing, attributeValues, etc...). Fixing those issues are complicated and would just cause new issues. Therefore, this `mergedMode=MERGE` is deprecated and currently is not recommended to use. The update mode should always be mergedMode=REPLACE. We have developed a new [JSON Patch API](#webapi_partial_updates) which can be used as an alternative approach. This feature is introduced in 2.37 release. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -1571,10 +1570,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1629,40 +1625,33 @@ ignored: ## GeoJSON import { #geojson-import } -The GeoJSON import is used to attach geometry data to organisation units. +L'importation GeoJSON est utilisée pour relier les données géométriques aux unités d'organisation. -For a bulk import a GeoJSON file with a feature collection is expected. -Each feature in the collection requires a reference to the organisation unit it -should be linked to. +Pour une importation en masse, il faut un fichier GeoJSON avec une collection d'éléments. +Chaque élément de la collection a besoin d'une référence à l'unité d'organisation à laquelle il doit être relié. -By default, the geometry from the file is stored as the `geometry` property of -an organisation unit. To store additional geometries attributes of type -`GEOJSON` can be created. When attributes are use all geometries from a file -are stored for the same attribute which is provided with an additional -parameter `attributeId`. +Par défaut, la géométrie du fichier est stockée en tant que propriété `geometry` d'une unité d'organisation. Pour stocker des géométries supplémentaires, des attributs de type `GEOJSON` peuvent être créés. Lorsque des attributs sont utilisés, toutes les géométries d'un fichier sont stockées pour le même attribut qui est fourni avec un paramètre supplémentaire `attributeId`. -### GeoJSON Bulk Data Import { #webapi_geojson_bulk_import } +### Importation de données en masse avec GeoJSON { #webapi_geojson_bulk_import } -Table: Import Parameters +Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| -| `geoJsonId` | `booléen` | `vrai` | When `true` the `id` property of the GeoJSON features is expected to hold the organisation unit identifier | -| `geoJsonProperty` | `Chaîne` | _undefined_ | If `geoJsonId` is `false` this parameter names the property in the GeoJSON feature's `properties` that holds the organisation unit identifier | -| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | The property of the organisation unit that is referred to by the identifiers used in the GeoJSON file | -| `attributeId` | `Chaîne` | _undefined_ | When set the geometry is stored as value of the attribute referenced by ID | -| `dryRun` | `booléen` | `faux` | When `true` the import is processed without actually updating the organisation units | -| `async` | `booléen` | `faux` | When `true` the import is processed asnychronously | +| `geoJsonId` | `booléen` | `vrai` | Si le paramètre est défini sur `true`, la propriété `id` des éléments GeoJSON est censée contenir l'identifiant de l'unité d'organisation. | +| `geoJsonProperty` | `Chaîne` | _undefined_ | Si `geoJsonId` est défini sur `false`, ce paramètre nomme la propriété dans les `properties` de l'élément GeoJSON qui contient l'identifiant de l'unité d'organisation. | +| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | La propriété de l'unité d'organisation à laquelle se réfèrent les identifiants utilisés dans le fichier GeoJSON. | +| `attributeId` | `Chaîne` | _undefined_ | Lorsqu'elle est définie, la géométrie est stockée en tant que valeur de l'attribut référencé par l'ID. | +| `dryRun` | `booléen` | `faux` | Si le paramètre est défini sur `true`, l'importation est traitée sans que les unités d'organisation ne soient mis à jour. | +| `async` | `booléen` | `faux` | Lorsque le paramètre est défini sur `true`, l'importation est traitée de manière asynchrone. | Uasge: POST /api/organisationUnits/geometry -The post body is the GeoJSON file. Content type should be `application/json` or -`application/geo+json`. The file may be `.zip` or `.gzip` compressed. +Le corps du message est le fichier GeoJSON. Le type de contenu doit être `application/json` ou `application/geo+json`. Le fichier peut être compressé en `.zip` ou `.gzip`. -For example, a default file where `id` is used to refer to an organisation unit -id has this structure: +Par exemple, un fichier par défaut dans lequel `id` est utilisé pour faire référence à l'identifiant d'une unité d'organisation a la structure suivante : ```json { @@ -1678,8 +1667,7 @@ id has this structure: } ``` -A file where a feature property is used to refer to the organisation unit code -would have this structure: +Un fichier dans lequel une propriété d'élément est utilisée pour faire référence au code de l'unité d'organisation devrait avoir la structure suivante : ```json { @@ -1694,62 +1682,55 @@ would have this structure: ] } ``` -A `geometry` may also be `null` to effectively clear or delete the geometry -for specific organisation units. There is a special bulk deletion API that is -described in the next section. +Une `geometry` peut également être `null` pour effacer ou supprimer efficacement la géométrie pour des unités d'organisation spécifiques. Il existe une API spéciale de suppression en masse ; elle est décrite dans la section suivante. -When run synchronously an import report is returned directly. -The HTTP status code is always `OK`, the `status` in the message payload -indicates if all rows were imported successfully. -The import counts statistics contained in the report give further information: +Lorsqu'elle est exécutée de manière synchrone, un rapport d'importation est renvoyé directement. +Le code de statut HTTP est toujours `OK`, le `status` dans le message indique si toutes les lignes ont été importées avec succès. +Les statistiques sur le nombre de lignes importées, contenues dans le rapport donnent des informations supplémentaires : -* `imported`: number of organisation units that were successfully updated with a geometry that did not have one before for the updated property -* `updated`: number of organisation units that were successfully updated with a geometry that did have value for the updated property already -* `ignored`: number of organisation units that failed to update -* `deleted`: number of organisation units that where successfully update with a _empty_ geometry +* `imported` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui n'en avait pas pour la propriété mise à jour. +* `updated` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui avait déjà une valeur pour la propriété mise à jour. +* `ignored` : nombre d'unités d'organisation qui n'ont pas été mises à jour +* `deleted` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie _vide_. -When the import is run asynchronous the request returns immediately with status -`OK` and job configuration response that contains a relative reference to -the task endpoint that allows to track the status of the asynchronous import. -For example: +Lorsque l'importation est exécutée de manière asynchrone, la requête renvoie immédiatement le statut `OK` de même que la réponse de configuration de la tâche qui contient une référence relative au point d'extrémité de la tâche qui permet de suivre le statut de l'importation asynchrone. Voici un exemple : /api/system/tasks/GEOJSON_IMPORT/{job-id} -The summary that is returned directly for synchronous execution is available at +Le récapitulatif renvoyé directement pour une exécution synchrone est disponible à l'adresse suivante : /api/system/taskSummaries/GEOJSON_IMPORT/{job-id} -once the import is finished. +dès que l'importation est terminée. -### GeoJSON Bulk Data Deletion { #webapi_geojson_bulk_deletion } -To clear or unset the `geometry` data for all organisation units use: +### Suppression de données en masse avec GeoJSON { #webapi_geojson_bulk_deletion } +Pour effacer ou désactiver les données `geometry` pour toutes les unités d'organisation, utilisez : DELETE /api/organisationUnits/geometry -To clear or unset the geometry data for a specific `GEOJSON` attribute for -all organisation units use: +Pour effacer ou désactiver les données géométriques d'un attribut `GEOJSON` spécifique pour toutes les unités d'organisation : DELETE /api/organisationUnits/geometry?attributeId={attr-id} -Clearing is always synchronous and returns a similar report as the bulk import. -It does not support any other parameters. No `dry-run` can be performed. -Bulk clearing requires the `F_PERFORM_MAINTENANCE` authority. +Le nettoyage se fait toujours de façon synchrone et renvoie un rapport similaire à celui de l'importation en masse. +Il ne prend en charge aucun autre paramètre. Aucun `essai` ne peut être effectué. +Pour effectuer un nettoyage en masse, l'utilisateur doit disposer de l'autorité `F_PERFORM_MAINTENANCE`. -### GeoJSON Single Data Import { #webapi_geojson_single_import } -The single import allows to update the geometry of a single organisation unit. +### Importation de données à titre individuel avec GeoJSON { #webapi_geojson_single_import } +L'importation unique permet de mettre à jour la géométrie d'une seule unité d'organisation. POST /api/organisationUnits/{id}/geometry -The post body only contains the GeoJSON `geometry` value, for example: +Le corps du message ne contient que la valeur GeoJSON `geometry`, par exemple : ```json { "type": "Polygon", "coordinates": [...] } ``` -Single import only supports `attributeId` and `dryRun` parameters. +L'importation unique ne prend en charge que les paramètres `attributeId` et `dryRun`. -### GeoJSON Single Data Deletion { #webapi_geojson_single_deletion } +### Suppression de données uniques avec GeoJSON { #webapi_geojson_single_deletion } To clear the `geometry` GeoJSON data of an individual organisation unit use: DELETE /api/organisationUnits/{id}/geometry @@ -1784,7 +1765,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons @@ -1923,7 +1904,7 @@ Table: Style properties | Propriété | Description | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -2246,7 +2227,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -2305,7 +2286,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2644,7 +2625,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -3177,7 +3158,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -7500,38 +7481,38 @@ Exaple: Get audits between `2021-01-01` and `2022-01-01` for org unit `DiszpKrYN # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7540,13 +7521,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7555,13 +7536,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7570,35 +7551,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -7630,23 +7611,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7671,44 +7652,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -7716,8 +7697,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -7725,48 +7706,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -7774,7 +7755,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -7782,12 +7763,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -7813,23 +7794,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -7855,8 +7836,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -7887,8 +7868,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7896,51 +7877,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -8279,29 +8258,29 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | -| reportingParams | Object used to define boolean attributes related to reporting. | +| reportingParams (Paramètres de déclaration) | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | | rowSubTotals | Displays (or not) the row sub-totals. Boolean value. | @@ -8829,25 +8808,25 @@ Tableau : Attributs de la visualisation d'événements | périodes relatives | Un objet représentant les périodes relatives utilisées dans la requête analytique. | | légende | An object representing the definitions for the legend and legend set, display style (FILL or TEXT) and display strategy (FIXED or BY_DATA_ITEM). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | @@ -18232,7 +18211,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 2616d7757..9340e4a41 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 template: single.html --- @@ -1493,19 +1493,18 @@ Tableau : Paramètres d'importation | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | | ~~mergeMode~~ (mode de fusion) | ~~REPLACE, MERGE~~ (remplacer, fusionner) | ~~Définit le mode de fusion. Lors des mises à jour nous avons deux façons de fusionner l'ancien objet avec le nouveau. Le mode `MERGE` ne remplacera l'ancienne propriété que si la nouvelle n'est pas nulle. Pour le mode `REPLACE`, toutes les propriétés sont remplacées qu'elles soient nulles ou non.~~ (*) | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | > (*) Currently the `mergeMode=MERGE` option of the import service has limitations and doesn't support all objects. It doesn't work with some object types such as Embedded objects, or objects which are saved as JSONB format in database ( sharing, attributeValues, etc...). Fixing those issues are complicated and would just cause new issues. Therefore, this `mergedMode=MERGE` is deprecated and currently is not recommended to use. The update mode should always be mergedMode=REPLACE. We have developed a new [JSON Patch API](#webapi_partial_updates) which can be used as an alternative approach. This feature is introduced in 2.37 release. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -1542,10 +1541,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1600,40 +1596,33 @@ ignored: ## GeoJSON import { #geojson-import } -The GeoJSON import is used to attach geometry data to organisation units. +L'importation GeoJSON est utilisée pour relier les données géométriques aux unités d'organisation. -For a bulk import a GeoJSON file with a feature collection is expected. -Each feature in the collection requires a reference to the organisation unit it -should be linked to. +Pour une importation en masse, il faut un fichier GeoJSON avec une collection d'éléments. +Chaque élément de la collection a besoin d'une référence à l'unité d'organisation à laquelle il doit être relié. -By default, the geometry from the file is stored as the `geometry` property of -an organisation unit. To store additional geometries attributes of type -`GEOJSON` can be created. When attributes are use all geometries from a file -are stored for the same attribute which is provided with an additional -parameter `attributeId`. +Par défaut, la géométrie du fichier est stockée en tant que propriété `geometry` d'une unité d'organisation. Pour stocker des géométries supplémentaires, des attributs de type `GEOJSON` peuvent être créés. Lorsque des attributs sont utilisés, toutes les géométries d'un fichier sont stockées pour le même attribut qui est fourni avec un paramètre supplémentaire `attributeId`. -### GeoJSON Bulk Data Import { #webapi_geojson_bulk_import } +### Importation de données en masse avec GeoJSON { #webapi_geojson_bulk_import } -Table: Import Parameters +Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| -| `geoJsonId` | `booléen` | `vrai` | When `true` the `id` property of the GeoJSON features is expected to hold the organisation unit identifier | -| `geoJsonProperty` | `Chaîne` | _undefined_ | If `geoJsonId` is `false` this parameter names the property in the GeoJSON feature's `properties` that holds the organisation unit identifier | -| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | The property of the organisation unit that is referred to by the identifiers used in the GeoJSON file | -| `attributeId` | `Chaîne` | _undefined_ | When set the geometry is stored as value of the attribute referenced by ID | -| `dryRun` | `booléen` | `faux` | When `true` the import is processed without actually updating the organisation units | -| `async` | `booléen` | `faux` | When `true` the import is processed asnychronously | +| `geoJsonId` | `booléen` | `vrai` | Si le paramètre est défini sur `true`, la propriété `id` des éléments GeoJSON est censée contenir l'identifiant de l'unité d'organisation. | +| `geoJsonProperty` | `Chaîne` | _undefined_ | Si `geoJsonId` est défini sur `false`, ce paramètre nomme la propriété dans les `properties` de l'élément GeoJSON qui contient l'identifiant de l'unité d'organisation. | +| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | La propriété de l'unité d'organisation à laquelle se réfèrent les identifiants utilisés dans le fichier GeoJSON. | +| `attributeId` | `Chaîne` | _undefined_ | Lorsqu'elle est définie, la géométrie est stockée en tant que valeur de l'attribut référencé par l'ID. | +| `dryRun` | `booléen` | `faux` | Si le paramètre est défini sur `true`, l'importation est traitée sans que les unités d'organisation ne soient mis à jour. | +| `async` | `booléen` | `faux` | Lorsque le paramètre est défini sur `true`, l'importation est traitée de manière asynchrone. | Uasge: POST /api/organisationUnits/geometry -The post body is the GeoJSON file. Content type should be `application/json` or -`application/geo+json`. The file may be `.zip` or `.gzip` compressed. +Le corps du message est le fichier GeoJSON. Le type de contenu doit être `application/json` ou `application/geo+json`. Le fichier peut être compressé en `.zip` ou `.gzip`. -For example, a default file where `id` is used to refer to an organisation unit -id has this structure: +Par exemple, un fichier par défaut dans lequel `id` est utilisé pour faire référence à l'identifiant d'une unité d'organisation a la structure suivante : ```json { @@ -1649,8 +1638,7 @@ id has this structure: } ``` -A file where a feature property is used to refer to the organisation unit code -would have this structure: +Un fichier dans lequel une propriété d'élément est utilisée pour faire référence au code de l'unité d'organisation devrait avoir la structure suivante : ```json { @@ -1665,65 +1653,58 @@ would have this structure: ] } ``` -The `coordinates` in a `geometry` may be pairs or triplets. -If a third dimension is present it is stripped during the import. +Les `coordonnées` d'une `géométrie` peuvent être des paires ou des triplets. +Si une troisième dimension est présente, elle est supprimée lors de l'importation. -A `geometry` may also be `null` to effectively clear or delete the geometry -for specific organisation units. There is a special bulk deletion API that is -described in the next section. +Une `geometry` peut également être `null` pour effacer ou supprimer efficacement la géométrie pour des unités d'organisation spécifiques. Il existe une API spéciale de suppression en masse ; elle est décrite dans la section suivante. -When run synchronously an import report is returned directly. -The HTTP status code is always `OK`, the `status` in the message payload -indicates if all rows were imported successfully. -The import counts statistics contained in the report give further information: +Lorsqu'elle est exécutée de manière synchrone, un rapport d'importation est renvoyé directement. +Le code de statut HTTP est toujours `OK`, le `status` dans le message indique si toutes les lignes ont été importées avec succès. +Les statistiques sur le nombre de lignes importées, contenues dans le rapport donnent des informations supplémentaires : -* `imported`: number of organisation units that were successfully updated with a geometry that did not have one before for the updated property -* `updated`: number of organisation units that were successfully updated with a geometry that did have value for the updated property already -* `ignored`: number of organisation units that failed to update -* `deleted`: number of organisation units that where successfully update with a _empty_ geometry +* `imported` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui n'en avait pas pour la propriété mise à jour. +* `updated` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui avait déjà une valeur pour la propriété mise à jour. +* `ignored` : nombre d'unités d'organisation qui n'ont pas été mises à jour +* `deleted` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie _vide_. -When the import is run asynchronous the request returns immediately with status -`OK` and job configuration response that contains a relative reference to -the task endpoint that allows to track the status of the asynchronous import. -For example: +Lorsque l'importation est exécutée de manière asynchrone, la requête renvoie immédiatement le statut `OK` de même que la réponse de configuration de la tâche qui contient une référence relative au point d'extrémité de la tâche qui permet de suivre le statut de l'importation asynchrone. Voici un exemple : /api/system/tasks/GEOJSON_IMPORT/{job-id} -The summary that is returned directly for synchronous execution is available at +Le récapitulatif renvoyé directement pour une exécution synchrone est disponible à l'adresse suivante : /api/system/taskSummaries/GEOJSON_IMPORT/{job-id} -once the import is finished. +dès que l'importation est terminée. -### GeoJSON Bulk Data Deletion { #webapi_geojson_bulk_deletion } -To clear or unset the `geometry` data for all organisation units use: +### Suppression de données en masse avec GeoJSON { #webapi_geojson_bulk_deletion } +Pour effacer ou désactiver les données `geometry` pour toutes les unités d'organisation, utilisez : DELETE /api/organisationUnits/geometry -To clear or unset the geometry data for a specific `GEOJSON` attribute for -all organisation units use: +Pour effacer ou désactiver les données géométriques d'un attribut `GEOJSON` spécifique pour toutes les unités d'organisation : DELETE /api/organisationUnits/geometry?attributeId={attr-id} -Clearing is always synchronous and returns a similar report as the bulk import. -It does not support any other parameters. No `dry-run` can be performed. -Bulk clearing requires the `F_PERFORM_MAINTENANCE` authority. +Le nettoyage se fait toujours de façon synchrone et renvoie un rapport similaire à celui de l'importation en masse. +Il ne prend en charge aucun autre paramètre. Aucun `essai` ne peut être effectué. +Pour effectuer un nettoyage en masse, l'utilisateur doit disposer de l'autorité `F_PERFORM_MAINTENANCE`. -### GeoJSON Single Data Import { #webapi_geojson_single_import } -The single import allows to update the geometry of a single organisation unit. +### Importation de données à titre individuel avec GeoJSON { #webapi_geojson_single_import } +L'importation unique permet de mettre à jour la géométrie d'une seule unité d'organisation. POST /api/organisationUnits/{id}/geometry -The post body only contains the GeoJSON `geometry` value, for example: +Le corps du message ne contient que la valeur GeoJSON `geometry`, par exemple : ```json { "type": "Polygon", "coordinates": [...] } ``` -Single import only supports `attributeId` and `dryRun` parameters. +L'importation unique ne prend en charge que les paramètres `attributeId` et `dryRun`. -### GeoJSON Single Data Deletion { #webapi_geojson_single_deletion } +### Suppression de données uniques avec GeoJSON { #webapi_geojson_single_deletion } To clear the `geometry` GeoJSON data of an individual organisation unit use: DELETE /api/organisationUnits/{id}/geometry @@ -1758,7 +1739,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons @@ -1897,7 +1878,7 @@ Table: Style properties | Propriété | Description | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -2220,7 +2201,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -2279,7 +2260,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2618,7 +2599,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -3180,7 +3161,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -7701,38 +7682,38 @@ Exaple: Get audits between `2021-01-01` and `2022-01-01` for org unit `DiszpKrYN # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7741,13 +7722,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7756,13 +7737,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -7771,35 +7752,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -7831,23 +7812,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7872,44 +7853,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -7917,8 +7898,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -7926,48 +7907,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -7975,7 +7956,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -7983,12 +7964,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -8014,23 +7995,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -8056,8 +8037,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -8088,8 +8069,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -8097,51 +8078,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -8480,29 +8459,29 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | -| reportingParams | Object used to define boolean attributes related to reporting. | +| reportingParams (Paramètres de déclaration) | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | | rowSubTotals | Displays (or not) the row sub-totals. Boolean value. | @@ -9030,25 +9009,25 @@ Tableau : Attributs de la visualisation d'événements | périodes relatives | Un objet représentant les périodes relatives utilisées dans la requête analytique. | | légende | An object representing the definitions for the legend and legend set, display style (FILL or TEXT) and display strategy (FIXED or BY_DATA_ITEM). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | @@ -15887,7 +15866,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 1c2d1ddc7..94f096d24 100644 --- a/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/fr/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - Développement - Version Master de DHIS2 Central @@ -650,7 +650,7 @@ Pour que le résultat soit ordonné selon une propriété spécifique : /api/indicators.json?order=shortName:desc -To order the result based on created datetime property first (descending order) and then by name property (ascending order): +Pour que le résultat soit d'abord ordonné selon la propriété créée "date et heure" (ordre décroissant), puis selon la propriété "nom" (ordre croissant) : /api/indicators.json?order=created:desc,name:asc @@ -1507,19 +1507,18 @@ Tableau : Paramètres d'importation | preheatMode (mode préchauffage) | REFERENCE, ALL, NONE (référence, tous, aucun) | Définit le mode de préchauffage ; il est utilisé pour signaler si le préchauffage doit être fait pour `TOUS` (comme c'était le cas auparavant avec *preheatCache=true*) ou faire un scan plus intelligent des objets pour voir ce qu'il faut préchauffer (actuellement le paramètre par défaut). Il n'est pas recommandé de le définir sur `AUCUN`. | | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | -> **NOTE** When updating objects, all property values will be overwritten even if the new values are `null`. Please use [JSON Patch API](#webapi_partial_updates) in case you want do partial update to an object. +> **REMARQUE** Lors de la mise à jour des objets, toutes les valeurs des propriétés seront écrasées même si les nouvelles valeurs sont `null`. Veuillez utiliser [JSON Patch API](#webapi_partial_updates) si vous voulez faire une mise à jour partielle d'un objet. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -1556,10 +1555,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1613,40 +1609,33 @@ ignored: ## GeoJSON import { #geojson-import } -The GeoJSON import is used to attach geometry data to organisation units. +L'importation GeoJSON est utilisée pour relier les données géométriques aux unités d'organisation. -For a bulk import a GeoJSON file with a feature collection is expected. -Each feature in the collection requires a reference to the organisation unit it -should be linked to. +Pour une importation en masse, il faut un fichier GeoJSON avec une collection d'éléments. +Chaque élément de la collection a besoin d'une référence à l'unité d'organisation à laquelle il doit être relié. -By default, the geometry from the file is stored as the `geometry` property of -an organisation unit. To store additional geometries attributes of type -`GEOJSON` can be created. When attributes are use all geometries from a file -are stored for the same attribute which is provided with an additional -parameter `attributeId`. +Par défaut, la géométrie du fichier est stockée en tant que propriété `geometry` d'une unité d'organisation. Pour stocker des géométries supplémentaires, des attributs de type `GEOJSON` peuvent être créés. Lorsque des attributs sont utilisés, toutes les géométries d'un fichier sont stockées pour le même attribut qui est fourni avec un paramètre supplémentaire `attributeId`. -### GeoJSON Bulk Data Import { #webapi_geojson_bulk_import } +### Importation de données en masse avec GeoJSON { #webapi_geojson_bulk_import } -Table: Import Parameters +Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| -| `geoJsonId` | `booléen` | `vrai` | When `true` the `id` property of the GeoJSON features is expected to hold the organisation unit identifier | -| `geoJsonProperty` | `Chaîne` | _undefined_ | If `geoJsonId` is `false` this parameter names the property in the GeoJSON feature's `properties` that holds the organisation unit identifier | -| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | The property of the organisation unit that is referred to by the identifiers used in the GeoJSON file | -| `attributeId` | `Chaîne` | _undefined_ | When set the geometry is stored as value of the attribute referenced by ID | -| `dryRun` | `booléen` | `faux` | When `true` the import is processed without actually updating the organisation units | -| `async` | `booléen` | `faux` | When `true` the import is processed asnychronously | +| `geoJsonId` | `booléen` | `vrai` | Si le paramètre est défini sur `true`, la propriété `id` des éléments GeoJSON est censée contenir l'identifiant de l'unité d'organisation. | +| `geoJsonProperty` | `Chaîne` | _undefined_ | Si `geoJsonId` est défini sur `false`, ce paramètre nomme la propriété dans les `properties` de l'élément GeoJSON qui contient l'identifiant de l'unité d'organisation. | +| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | La propriété de l'unité d'organisation à laquelle se réfèrent les identifiants utilisés dans le fichier GeoJSON. | +| `attributeId` | `Chaîne` | _undefined_ | Lorsqu'elle est définie, la géométrie est stockée en tant que valeur de l'attribut référencé par l'ID. | +| `dryRun` | `booléen` | `faux` | Si le paramètre est défini sur `true`, l'importation est traitée sans que les unités d'organisation ne soient mis à jour. | +| `async` | `booléen` | `faux` | Lorsque le paramètre est défini sur `true`, l'importation est traitée de manière asynchrone. | Uasge: POST /api/organisationUnits/geometry -The post body is the GeoJSON file. Content type should be `application/json` or -`application/geo+json`. The file may be `.zip` or `.gzip` compressed. +Le corps du message est le fichier GeoJSON. Le type de contenu doit être `application/json` ou `application/geo+json`. Le fichier peut être compressé en `.zip` ou `.gzip`. -For example, a default file where `id` is used to refer to an organisation unit -id has this structure: +Par exemple, un fichier par défaut dans lequel `id` est utilisé pour faire référence à l'identifiant d'une unité d'organisation a la structure suivante : ```json { @@ -1662,8 +1651,7 @@ id has this structure: } ``` -A file where a feature property is used to refer to the organisation unit code -would have this structure: +Un fichier dans lequel une propriété d'élément est utilisée pour faire référence au code de l'unité d'organisation devrait avoir la structure suivante : ```json { @@ -1678,65 +1666,58 @@ would have this structure: ] } ``` -The `coordinates` in a `geometry` may be pairs or triplets. -If a third dimension is present it is stripped during the import. +Les `coordonnées` d'une `géométrie` peuvent être des paires ou des triplets. +Si une troisième dimension est présente, elle est supprimée lors de l'importation. -A `geometry` may also be `null` to effectively clear or delete the geometry -for specific organisation units. There is a special bulk deletion API that is -described in the next section. +Une `geometry` peut également être `null` pour effacer ou supprimer efficacement la géométrie pour des unités d'organisation spécifiques. Il existe une API spéciale de suppression en masse ; elle est décrite dans la section suivante. -When run synchronously an import report is returned directly. -The HTTP status code is always `OK`, the `status` in the message payload -indicates if all rows were imported successfully. -The import counts statistics contained in the report give further information: +Lorsqu'elle est exécutée de manière synchrone, un rapport d'importation est renvoyé directement. +Le code de statut HTTP est toujours `OK`, le `status` dans le message indique si toutes les lignes ont été importées avec succès. +Les statistiques sur le nombre de lignes importées, contenues dans le rapport donnent des informations supplémentaires : -* `imported`: number of organisation units that were successfully updated with a geometry that did not have one before for the updated property -* `updated`: number of organisation units that were successfully updated with a geometry that did have value for the updated property already -* `ignored`: number of organisation units that failed to update -* `deleted`: number of organisation units that where successfully update with a _empty_ geometry +* `imported` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui n'en avait pas pour la propriété mise à jour. +* `updated` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui avait déjà une valeur pour la propriété mise à jour. +* `ignored` : nombre d'unités d'organisation qui n'ont pas été mises à jour +* `deleted` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie _vide_. -When the import is run asynchronous the request returns immediately with status -`OK` and job configuration response that contains a relative reference to -the task endpoint that allows to track the status of the asynchronous import. -For example: +Lorsque l'importation est exécutée de manière asynchrone, la requête renvoie immédiatement le statut `OK` de même que la réponse de configuration de la tâche qui contient une référence relative au point d'extrémité de la tâche qui permet de suivre le statut de l'importation asynchrone. Voici un exemple : /api/system/tasks/GEOJSON_IMPORT/{job-id} -The summary that is returned directly for synchronous execution is available at +Le récapitulatif renvoyé directement pour une exécution synchrone est disponible à l'adresse suivante : /api/system/taskSummaries/GEOJSON_IMPORT/{job-id} -once the import is finished. +dès que l'importation est terminée. -### GeoJSON Bulk Data Deletion { #webapi_geojson_bulk_deletion } -To clear or unset the `geometry` data for all organisation units use: +### Suppression de données en masse avec GeoJSON { #webapi_geojson_bulk_deletion } +Pour effacer ou désactiver les données `geometry` pour toutes les unités d'organisation, utilisez : DELETE /api/organisationUnits/geometry -To clear or unset the geometry data for a specific `GEOJSON` attribute for -all organisation units use: +Pour effacer ou désactiver les données géométriques d'un attribut `GEOJSON` spécifique pour toutes les unités d'organisation : DELETE /api/organisationUnits/geometry?attributeId={attr-id} -Clearing is always synchronous and returns a similar report as the bulk import. -It does not support any other parameters. No `dry-run` can be performed. -Bulk clearing requires the `F_PERFORM_MAINTENANCE` authority. +Le nettoyage se fait toujours de façon synchrone et renvoie un rapport similaire à celui de l'importation en masse. +Il ne prend en charge aucun autre paramètre. Aucun `essai` ne peut être effectué. +Pour effectuer un nettoyage en masse, l'utilisateur doit disposer de l'autorité `F_PERFORM_MAINTENANCE`. -### GeoJSON Single Data Import { #webapi_geojson_single_import } -The single import allows to update the geometry of a single organisation unit. +### Importation de données à titre individuel avec GeoJSON { #webapi_geojson_single_import } +L'importation unique permet de mettre à jour la géométrie d'une seule unité d'organisation. POST /api/organisationUnits/{id}/geometry -The post body only contains the GeoJSON `geometry` value, for example: +Le corps du message ne contient que la valeur GeoJSON `geometry`, par exemple : ```json { "type": "Polygon", "coordinates": [...] } ``` -Single import only supports `attributeId` and `dryRun` parameters. +L'importation unique ne prend en charge que les paramètres `attributeId` et `dryRun`. -### GeoJSON Single Data Deletion { #webapi_geojson_single_deletion } +### Suppression de données uniques avec GeoJSON { #webapi_geojson_single_deletion } To clear the `geometry` GeoJSON data of an individual organisation unit use: DELETE /api/organisationUnits/{id}/geometry @@ -1771,7 +1752,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. There are two different kind of icons: @@ -1989,7 +1970,7 @@ Table: Style properties | Propriété | Description ; | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -2225,7 +2206,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2321,9 +2302,9 @@ Sample error response looks like: } ``` -## Indicator Types { #webapi_indicator_types} +## Types d'indicateurs { #webapi_indicator_types} -### Merge indicator types { #webapi_indicator_type_merge} +### Fusionner les types d'indicateurs { #webapi_indicator_type_merge} The indicator type merge endpoint allows you to merge a number of indicator types into a target indicator type. @@ -2352,7 +2333,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2550,7 +2531,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -2609,7 +2590,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2948,7 +2929,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -3518,7 +3499,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -8528,38 +8509,38 @@ Exaple: Get audits between `2021-01-01` and `2022-01-01` for org unit `DiszpKrYN # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -8568,13 +8549,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -8583,13 +8564,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -8598,35 +8579,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -8658,23 +8639,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -8699,44 +8680,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -8744,8 +8725,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -8753,48 +8734,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -8802,7 +8783,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -8810,12 +8791,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -8841,23 +8822,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -8883,8 +8864,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -8915,8 +8896,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -8924,51 +8905,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -9307,29 +9286,29 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | -| reportingParams | Object used to define boolean attributes related to reporting. | +| reportingParams (Paramètres de déclaration) | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | | rowSubTotals | Displays (or not) the row sub-totals. Boolean value. | @@ -9857,25 +9836,25 @@ Tableau : Attributs de la visualisation d'événements | périodes relatives | Un objet représentant les périodes relatives utilisées dans la requête analytique. | | légende | An object representing the definitions for the legend and legend set, display style (FILL or TEXT) and display strategy (FIXED or BY_DATA_ITEM). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | @@ -11557,7 +11536,7 @@ Tableau : Paramètres de requête pour l'analyse des requêtes d'événement un | Paramètre de requête | Obligatoire | Description ; | Options | |---|---|---|---| -| ouMode (Mode d'unité d'organisation) | Non | Il s'git du mode de sélection des unités d'organisation. La valeur par défaut est DESCENDANTS (descendants), c'est-à-dire toutes les sous-unités dans la hiérarchie. CHILDREN (subordonnées) fait référence aux unités qui se trouvent directement en dessous de l'unité de référence dans la hiérarchie ; SELECTED (sélectionnées) fait référence aux unités d'organisation sélectionnées uniquement. Vous trouverez plus de détails [ici].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode (Mode d'unité d'organisation) | Non | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Non | Permet de trier les dimensions par ordre croissant ; peut concerner la date de l'événement, le nom et le code de l'unité d'organisation et tout identifiant d'élément. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Non | Permet de trier les dimensions par ordre décroissant ; peut concerner la date de l'événement, le nom et le code de l'unité d'organisation et tout identifiant d'élément. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly (coordonnées uniquement) | Non | Indique s'il faut uniquement renvoyer les événements qui ont des coordonnées. | faux | vrai | @@ -12366,7 +12345,7 @@ Tableau : Paramètres de requête pour le point d'extrémité de la requête d' | filtre | Non | L'identifiant de dimension comprend les éléments de données, les attributs, les périodes, les unités d'organisation et les ensembles de groupes d'unités d'organisation. Le paramètre peut être répété autant de fois que nécessaire. Des filtres d'éléments peuvent être appliqués à une dimension selon le format ::. Les valeurs des filtres ne sont pas sensibles à la casse. || | programStatus (statut de programme) | Non | Spécifie le statut d’inscription des inscriptions à inclure. | ACTIF | TERMINÉ | ANNULÉ | | relativePeriodDate (Date de la période relative) | chaîne | Non | Identifiant de date, par exemple : "2016-01-01". Il remplace la date de début de la période relative | -| ouMode (Mode d'unité d'organisation) | Non | Il s'git du mode de sélection des unités d'organisation. La valeur par défaut est DESCENDANTS (descendants), c'est-à-dire toutes les sous-unités dans la hiérarchie. CHILDREN (subordonnées) fait référence aux unités qui se trouvent directement en dessous de l'unité de référence dans la hiérarchie ; SELECTED (sélectionnées) fait référence aux unités d'organisation sélectionnées uniquement. Vous trouverez plus de détails [ici].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode (Mode d'unité d'organisation) | Non | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Non | Permet de trier les dimensions par ordre croissant ; peut concerner la date d'inscription, la date d'incident, le nom et le code de l'unité d'organisation. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Non | Permet de trier les dimensions dans l'ordre décroissant ; peut concerner la date d'inscription, la date d'incident, le nom et le code de l'unité d'organisation. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly (coordonnées uniquement) | Non | Indique s'il faut uniquement renvoyer les inscriptions qui ont des coordonnées. | faux | vrai | @@ -16994,20 +16973,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Objets du Tracker { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17110,7 +17090,6 @@ point out any exceptional cases between these two. | programme | Uniquement pour lire les données. Il s'agit du type de programme de l'inscription qui possède l'événement. | Non | Oui | Chaîne : Uid | ABCDEF12345 | | Entité suivie | Uniquement pour lire les données. Il s'agit de l'entité suivie propriétaire de l'événement. Ceci ***ne s'applique pas au `PROGRAMME D'ÉVÉNEMENT`*** | Non | Non | Chaîne : Uid | ABCDEF12345 | | statut | Statut de l'évènement. Il est ACTIF au cas où n'est pas fourni. | Non | Non | Énumération | ACTIF, EFFECTUÉ, VISITÉ, HORAIRE, EN RETARD, SAUTÉ | -| Statut de l'inscription | Uniquement pour lire les données. Il s'agit du statut de l'inscription propriétaire de l'événement. Ceci ***ne s'applique pas au `PROGRAMME D'ÉVÉNEMENT`*** | Non | Non | Énumération | ACTIF, EFFECTUÉ, ANNULÉ | | orgUnit (Unité d'organisation) | Il s'agit de l'unité d'organisation dans laquelle l'utilisateur a enregistré l'événement. | Oui | Non | Chaîne : Uid | ABCDEF12345 | | créé à | Only for reading data. Timestamp when the user created the event. Set on the server. | Non | Oui | Date : ISO 8601 | AAAA-MM-JJThh:mm:ss | | crééAtClient (Création au niveau du client) | Date et heure à laquelle l'utilisateur a créé l'évènement au niveau du client | Non | Non | Date : ISO 8601 | AAAA-MM-JJThh:mm:ss | @@ -17170,9 +17149,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Les attributs { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Propriété | Description ; | Obligatoire | Immuable | Type | Exemple | |---|---|---|---|---|---| @@ -17187,18 +17168,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Valeurs de données { #data-values } -Alors que les `Attributs` décrivent une `entité suivie` ou une `inscription`, les `valeurs de données` décrivent un `évènement`. La différence majeure est que les `attributs ` ne peuvent avoir qu'une seule valeur pour une `entité suivie` donnée. En revanche, les `valeurs de données` peuvent avoir plusieurs valeurs différentes selon les `événements` - même si les `événements` appartiennent tous à la même `inscription` ou à la même `entité suivie`. +While attributes describe a tracked entity, data values describe an event. | Propriété | Description ; | Obligatoire | Immuable | Type | Exemple | |---|---|---|---|---|---| @@ -17213,31 +17196,31 @@ Alors que les `Attributs` décrivent une `entité suivie` ou une `inscription`, > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Remarques { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -17248,10 +17231,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -17293,92 +17276,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Charge utile pour les opérations CRUD sur les listes de tâches des étapes de programme{ #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Tableau : Charge utile - -| Valeurs de charge utile | Description ; | Exemple | -|---|---|---| -| nom | Nom de la liste de tâches. Obligatoire. || -| Description | Il s'agit d'une description de la liste de tâches. || -| programme | Objet contenant l'identifiant du programme. Obligatoire. | {"id" : "uy2gU8kTjF"} | -| Étape du programme | Objet contenant l'identifiant de l'étape de programme. Obligatoire. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria (Critères de requête de l'étape de programme) | Un objet représentant diverses valeurs de filtrage possibles. Voir le tableau de définition des *Critères de requête de l'étape de programme* ci-dessous. - -Tableau : Critères de requête de l'étape de programme - -| Valeurs des critères | Description ; | Exemple | -|---|---|---| -| statut | Il s'agit du statut de l'événement. Les valeurs possibles sont ACTIF, EFFECTUÉ, VISITÉ, PROGRAMMÉ, EN RETARD, SAUTÉ et VISITÉ. | "statut": "VISITÉ" | -| Évènement créé à | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date de création de l'événement. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt (programmé à) | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date de programmation de l'événement. | {"type":"RELATIVE","period":"TODAY"} | -| Statut de l'inscription | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "Statut de l'inscription": "EFFECTUÉ" | -| Suivi | Indique s'il faut filtrer ou non les inscriptions marquées pour le suivi | "suivi": vrai | -| inscrit à | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date d'inscription de l'événement. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| Inscription effectué à | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit (Unité d'organisation) | Un UID d'unité d'organisation valide | "orgUnit": "Rp268JB6Ne4" | -| ouMode (Mode d'unité d'organisation) | Un mode de sélection d'unités d'organisation valide | "ouMode": "SELECTED" | -| Mode d'utilisateur assigné | Il s'agit d'un mode de sélection d'utilisateur valide pour les événements. Les valeurs possibles sont ACTUEL, FOURNI, AUCUN, TOUT et TOUS. S’il est FOURNI (ou nul), il sera attendu dans la charge utile des utilisateurs assignés non vides. | "Mode d'utilisateur assigné" : "FOURNI" | -| assignedUser (Utilisateur assigné) | Une liste des utilisateurs assignés aux événements. À utiliser avec le mode d'utilisateur assigné, fourni ci-dessus. | "Utilisateurs assignés":["DXyJmlo9rge"] | -| Ordre | Liste des champs et de leurs directions en valeurs séparées par des virgules, les résultats seront triés en fonction de cette liste. Un seul élément dans l'ordre est de la forme « orderDimension:direction ». | "ordre": "w75KJ2mc4zz:asc" | -| Ordre d'affichage des colonnes | Ordre de sortie des colonnes | "Ordre de sortie des colonnes":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| Filtres de données | Une liste d'éléments contenant les filtres à utiliser lors de requêtes d'événements | "Filtres de données":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| Filtres des valeurs d'attributs | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "Filtres de valeurs d'attribut":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -Ci-dessous, un exemple de charge : - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Importation Tracker (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -17387,9 +17285,9 @@ to import i.e. create, update and delete * **Inscriptions** * **Événements** * **Relations** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Paramètres de requête { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -17398,16 +17296,16 @@ The tracker importer supports the following parameters: | async | Indique si l’importation doit avoir lieu de manière asynchrone ou synchrone. | Booléen | `VRAI`, `FAUX` | | Mode de rapport | Uniquement lors d'une importation synchrone. Voir le "Récapitulatif de l'importation" pour plus d’informations. | Énumération | `COMPLET`, `ERREURS`, `AVERTISSEMENTS` | | Mode d'importation | Can either be `VALIDATE` which will report errors in the payload without making changes to the database or `COMMIT` (default) which will validate the payload and make changes to the database. | Énumération | `VALIDER`, `COMMITER` | -| idScheme (schéma d'identifiants) | Indique le 'schéma d'identification' global à utiliser pour les références de métadonnées lors de l'importation. La valeur par défaut est UID. Elle peut être remplacée pour des métadonnées spécifiques (voir la liste ci-dessous). | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | +| idScheme (schéma d'identification) | Indique le 'schéma d'identification' global à utiliser pour les références de métadonnées lors de l'importation. La valeur par défaut est UID. Elle peut être remplacée pour des métadonnées spécifiques (voir la liste ci-dessous). | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | dataElementIdScheme (Schéma d'identification de l'élément de données) | Indique le schéma d'identification à utiliser pour les éléments de données lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | -| orgUnitIdScheme (Schéma de l'identifiant de l'unité d'organisation) | Indique le schéma d'identification à utiliser pour les unités d'organisation lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | +| orgUnitIdScheme (Schéma d'identification de l'unité d'organisation) | Indique le schéma d'identification à utiliser pour les unités d'organisation lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | programIdScheme (Schéma d'identification des programmes) | Indique le schéma d'identification à utiliser pour les programmes lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | programmeStageIdScheme (Schéma d'identification des étapes de programme) | Indique le schéma d'identification à utiliser pour les étapes de programme lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | -| categoryOptionComboIdScheme (Schéma d'identification des combinaisons d'options de catégorie) | Indique le schéma d'identification à utiliser pour les combinaisons d'options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | +| categoryOptionComboIdScheme (Schéma d'identification de la combinaison d'options de catégorie) | Indique le schéma d'identification à utiliser pour les combinaisons d'options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | @@ -17422,7 +17320,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -17822,7 +17720,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Récapitulatif des importations { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -18268,7 +18166,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Codes d'erreur { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -18398,7 +18296,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | N/A | Message d'erreur non défini. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -18408,7 +18306,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -18433,8 +18331,8 @@ on which property has a wrong format. Some examples of properties that are valid #### Accès des utilisateurs { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -18487,7 +18385,7 @@ Some examples of configurable validations: Ces configurations apporteront des modifications supplémentaires à la manière dont la validation est effectuée lors de l'importation. -### Règles de programme { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -18543,7 +18441,7 @@ information about side effects can be found in the following section. > > Les règles de programme peuvent être ignorées lors de l'importation à l'aide du paramètre `skipProgramRules` (ignorer les règles de programme). -### Effets secondaires { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -18565,7 +18463,7 @@ Voici donc les effets secondaires actuellement pris en charge : > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assigner un utilisateur à des événements { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -18599,7 +18497,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Exportation Tracker { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Les points d'extrémité de l'exportation Tracker vous permettent de récupérer les objets précédemment importés, à savoir : @@ -18651,9 +18549,9 @@ Le point d'extrémité suivant prend en charge les paramètres normalisés pour The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Paramètre de requête pour filtrer les réponses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } Tous les points d'extrémité d'exportation acceptent un paramètre `fields` (champs) qui contrôle les champs qui seront renvoyés dans la réponse JSON. Le paramètre `fields` accepte une liste de noms de champs ou de modèles séparés par des virgules. Quelques filtres `fields` possibles sont présentés ci-dessous. Consultez la section [filtre de champ de métadonnées (#webapi_metadata_field_filter)] pour obtenir un guide plus complet sur l'utilisation du paramètre `fields`. @@ -18730,8 +18628,8 @@ Le point d'extrémité renvoie une liste d'entités suivies qui correspondent au |`filtre`|`Chaîne`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`Chaîne`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`Chaîne`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| |`programme`|`Chaîne`|`UID` de programme|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`Chaîne`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage` (étape de programme)|`Chaîne`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -18835,7 +18733,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19097,8 +18995,8 @@ Renvoie une liste d'événements en fonction des filtres. |---|---|---|---| |`orgUnits`|`Chaîne`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`Chaîne`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| |`programme`|`Chaîne`|`uid`| Identifiant de programme| |`programStatus` **deprecated for removal in version 43 use `status`**|`Chaîne`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`statut`|`Chaîne`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -19302,8 +19200,8 @@ Renvoie une liste d'événements en fonction des filtres fournis. |`followUp` (suivi)|`booléen`| `vrai`, `faux` | Détermine si l'événement est pris en compte pour un suivi dans le programme. La valeur par défaut est `vrai`| |`trackedEntity` (entité suivie)|`Chaîne`|`uid`|Identifier of tracked entity| |`orgUnit` (unité d'organisation)|`Chaîne`|`uid`|Identifiant de l'unité d'organisation| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| |`statut`|`Chaîne`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Statut de l'événement| |`occurredAfter` (survenu après)|`DateTime` (date et heure)|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filtre pour les événements survenus après cette date.| |`occurredBefore` (survenu avant)|`DateTime` (date et heure)| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filtre pour les événements survenus jusqu'à cette date.| @@ -19598,13 +19496,13 @@ Les règles suivantes s'appliquent aux paramètres de requête. } ``` -## Contrôle de l'accès au Tracker { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Partage de métadonnées { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -19650,7 +19548,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -19719,13 +19617,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Propriété du programme Tracker { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -19737,7 +19635,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Annulation de la propriété du Tracker : Briser la glace { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -19750,7 +19648,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Transfert de la propriété du Tracker { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -19760,7 +19658,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Niveau d'accès { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -19790,7 +19688,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -19806,2746 +19704,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Tableau : Charge utile -|Tracker Object|Previously|Now| +| Valeurs de charge utile | Description ; | Exemple | |---|---|---| -|**Attribute**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Manifestation**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Remarque**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Relationship**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Previously|Now| -|---|---| -|`assignedUser` (utilisateur assigné)|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribut`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes` (inclure tous les attributs)|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus` (statut de programme)|`enrollmentStatus`| -|`requête`|Removed - use `filter` instead| -|`skipMeta` (ignorer les métadonnées)|Removed| -|`skipPaging` (ignorer la pagination)|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Previously|Now| -|---|---| -|`inscription`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus` (statut de programme)|`statut`| -|`skipPaging` (ignorer la pagination)|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity` (entité suivie)| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Previously|Now| -|---|---| -|`assignedUser` (utilisateur assigné)|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`événement`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus` (statut de programme)|`enrollmentStatus`| -|`skipEventId` (ignorer l'identifiant de l'élément)|Removed| -|`skipMeta` (ignorer les métadonnées)|Removed| -|`skipPaging` (ignorer la pagination)|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity` (entité suivie)| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Previously|Now| -|---|---| -|`skipPaging` (ignorer la pagination)|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity` (entité suivie)| - -## Tracker Web API { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### Tracked entity instance management { #webapi_tracked_entity_instance_management } - -Tracked entity instances have full CRUD support in the API. Together -with the API for enrollment most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/trackedEntityInstances - -#### Creating a new tracked entity instance { #webapi_creating_tei } - -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -The field "geometry" accepts a GeoJson object, where the type of the -GeoJson have to match the featureType of the TrackedEntityType -definition. An example GeoJson object looks like this: - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +| nom | Nom de la liste de tâches. Obligatoire. || +| Description | Il s'agit d'une description de la liste de tâches. || +| programme | Objet contenant l'identifiant du programme. Obligatoire. | {"id" : "uy2gU8kTjF"} | +| Étape du programme | Objet contenant l'identifiant de l'étape de programme. Obligatoire. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria (Critères de requête de l'étape de programme) | Un objet représentant diverses valeurs de filtrage possibles. Voir le tableau de définition des *Critères de requête de l'étape de programme* ci-dessous. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Tableau : Critères de requête de l'étape de programme - /api/trackedEntityInstances +| Valeurs des critères | Description ; | Exemple | +|---|---|---| +| eventStatus (statut d'événement) | Il s'agit du statut de l'événement. Les valeurs possibles sont ACTIF, EFFECTUÉ, VISITÉ, PROGRAMMÉ, EN RETARD, SAUTÉ et VISITÉ. | "statut": "VISITÉ" | +| Évènement créé à | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date de création de l'événement. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date de programmation de l'événement. | {"type":"RELATIVE","period":"TODAY"} | +| Statut de l'inscription | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "Statut de l'inscription": "EFFECTUÉ" | +| Suivi | Indique s'il faut filtrer ou non les inscriptions marquées pour le suivi | "suivi": vrai | +| inscrit à | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date d'inscription de l'événement. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| Inscription effectué à | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit (Unité d'organisation) | Un UID d'unité d'organisation valide | "orgUnit": "Rp268JB6Ne4" | +| ouMode (Mode d'unité d'organisation) | Un mode de sélection d'unités d'organisation valide | "ouMode": "SELECTED" | +| Mode d'utilisateur assigné | Il s'agit d'un mode de sélection d'utilisateur valide pour les événements. Les valeurs possibles sont ACTUEL, FOURNI, AUCUN, TOUT et TOUS. S’il est FOURNI (ou nul), il sera attendu dans la charge utile des utilisateurs assignés non vides. | "Mode d'utilisateur assigné" : "FOURNI" | +| assignedUser (Utilisateur assigné) | Une liste des utilisateurs assignés aux événements. À utiliser avec le mode d'utilisateur assigné, fourni ci-dessus. | "Utilisateurs assignés":["DXyJmlo9rge"] | +| Ordre | Liste des champs et de leurs directions en valeurs séparées par des virgules, les résultats seront triés en fonction de cette liste. Un seul élément dans l'ordre est de la forme « orderDimension:direction ». | "ordre": "w75KJ2mc4zz:asc" | +| Ordre d'affichage des colonnes | Ordre de sortie des colonnes | "Ordre de sortie des colonnes":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| Filtres de données | Une liste d'éléments contenant les filtres à utiliser lors de requêtes d'événements | "Filtres de données":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| Filtres des valeurs d'attributs | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "Filtres de valeurs d'attribut":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Ci-dessous, un exemple de charge : ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -To push this to the server you can use the cURL command like this: - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -To create multiple instances in one request you can wrap the payload in -an outer array like this and POST to the same resource as above:[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -The system does not allow the creation of a tracked entity instance -(as well as enrollment and event) with a UID that was already used in -the system. That means that UIDs cannot be reused. - -#### Updating a tracked entity instance { #webapi_updating_tei } - -For updating a tracked entity instance, the payload is equal to the -previous section. The difference is that you must use the HTTP *PUT* -method for the request when sending the payload. You will also need to -append the person identifier to the *trackedEntityInstances* resource in -the URL like this, where `` should -be replaced by the identifier of the tracked entity instance: - - /api/trackedEntityInstances/ - -The payload has to contain all, even non-modified, attributes and -relationships. Attributes or relationships that were present before and -are not present in the current payload any more will be removed from the -system. This means that if attributes/relationships are empty in the -current payload, all existing attributes/relationships will be deleted -from the system. From 2.31, it is possible to ignore empty -attributes/relationships in the current payload. A request parameter of -`ignoreEmptyCollection` set to `true` can be used in case you do not -wish to send in any attributes/relationships and also do not want them -to be deleted from the system. - -It is not allowed to update an already deleted tracked entity instance. -Also, it is not allowed to mark a tracked entity instance as deleted via -an update request. The same rules apply to enrollments and events. - -#### Deleting a tracked entity instance { #webapi_deleting_tei } - -In order to delete a tracked entity instance, make a request to the URL -identifying the tracked entity instance with the *DELETE* -method. The URL is equal to the one above used for update. - -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } - -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Complete example of payload including: tracked entity instance, enrollment and event { #webapi_create_enroll_tei_create_event } - -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute":"cejWyOfXge6", - "value":"Male" - } - ], - "enrollments":[ - { - "orgUnit":"DiszpKrYNg8", - "program":"ur1Edk5Oe2n", - "enrollmentDate":"2017-09-15", - "incidentDate":"2017-09-15", - "events":[ - { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues": [ - { - "dataElement":"qrur9Dvnyt5", - "value":"22" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Male" - } - ] - }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues":[ - { - "dataElement":"qrur9Dvnyt5", - "value":"26" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Female" - } - ] - } - ] - } - ] + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Generated tracked entity instance attributes { #webapi_generate_tei_attributes } - -Tracked entity instance attributes that are using automatic generation of -unique values have three endpoints that are used by apps. The endpoints -are all used for generating and reserving values. - -In 2.29 we introduced TextPattern for defining and generating these -patterns. All existing patterns will be converted to a valid TextPattern -when upgrading to 2.29. - -> **Note** -> -> As of 2.29, all these endpoints will require you to include any -> variables reported by the `requiredValues` endpoint listed as -> required. Existing patterns, consisting of only `#`, will be upgraded -> to the new TextPattern syntax `RANDOM()`. The RANDOM -> segment of the TextPattern is not a required variable, so this -> endpoint will work as before for patterns defined before 2.29. - -##### Finding required values { #finding-required-values } - -A TextPattern can contain variables that change based on different -factors. Some of these factors will be unknown to the server, so the -values for these variables have to be supplied when generating and -reserving values. - -This endpoint will return a map of required and optional values, that -the server will inject into the TextPattern when generating new values. -Required variables have to be supplied for the generation, but optional -variables should only be supplied if you know what you are doing. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### Generate value endpoint { #webapi_generate_values } - -Online web apps and other clients that want to generate a value that -will be used right away can use the simple generate endpoint. This -endpoint will generate a value that is guaranteed to be unique at the -time of generation. The value is also guaranteed not to be reserved. As -of 2.29, this endpoint will also reserve the value generated for 3 days. - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } - -The generate and reserve endpoint is used by offline clients that need -to be able to register tracked entities with unique ids. They will -reserve a number of unique ids that this device will then use when -registering new tracked entity instances. The endpoint is called to -retrieve a number of tracked entity instance reserved values. An -optional parameter numberToReserve specifies how many ids to generate -(default is 1). - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -Similar to the /generate endpoint, this endpoint can also specify the -expiration time in the same way. By adding the `?expiration=` -you can override the default 60 days. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### Reserved values { #reserved-values } - -Reserved values are currently not accessible through the api, however, they -are returned by the `generate` and `generateAndReserve` endpoints. The -following table explains the properties of the reserved value object: - -##### - - - -Table: Reserved values - -| Propriété | Description ; | -|---|---| -| ownerObject | The metadata type referenced when generating and reserving the value. Currently only TRACKEDENTITYATTRIBUTE is supported. | -| ownerUid | The uid of the metadata object referenced when generating and reserving the value. | -| clé | A partially generated value where generated segments are not yet added. | -| valeur | The fully resolved value reserved. This is the value you send to the server when storing data. | -| créés | The timestamp when the reservation was made | -| expiryDate | The timestamp when the reservation will no longer be reserved | - -Expired reservations are removed daily. If a pattern changes, values -that were already reserved will be accepted when storing data, even if -they don't match the new pattern, as long as the reservation has not -expired. - -#### Image attributes { #image-attributes } - -Working with image attributes is a lot like working with file data -values. The value of an attribute with the image value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///image` -endpoint will return the actual image. The optional height and width -parameters can be used to specify the dimensions of the image. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } - -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. - - /api/33/trackedEntityInstances - -##### Request syntax { #webapi_tei_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Paramètre de requête | Description ; | -|---|---| -| filtre | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode (Mode d'unité d'organisation) | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected selected organisation units only. See table below for explanations. | -| programme | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus (statut de programme) | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| Suivi | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| Entité suivie | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| page | Il s'agit du numéro de page. La page par défaut est 1. | -| taille de la page | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration (durée de la dernière mise à jour) | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| Mode d'utilisateur assigné | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser (Utilisateur assigné) | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Indicates whether to include soft deleted teis or not. It is false by default. | -| potentialDuplicate | Il est possible de filtrer le résultat en supposant qu'une TEI soit un doublon potentiel. true: renvoie les TEI marqués comme doublons potentiels. false: renvoie les TEI NON marqués comme doublons potentiels. En cas d'omission, nous ne vérifions pas si une TEI est un doublon potentiel ou pas.| - -Les modes de sélection d'unités d'organisation disponibles sont expliqués dans le tableau suivant. - - - -Table: Organisation unit selection modes - -| Mode | Description ; | -|---|---| -| SELECTED | Unités d'organisation définies dans la requête. | -| CHILDREN | The selected organisation units and the immediate children, i.e. the organisation units at the level below. | -| DESCENDANTS | The selected organisation units and all children, i.e. all organisation units in the sub-hierarchy. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| ALL | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -Les modes d'utilisateur assigné disponibles sont expliqués dans le tableau suivant. - - - -Tableau : Modes d'utilisateur assigné - -| Mode | Description ; | -|---|---| -| ACTUEL | Inclut les événements attribués à l’utilisateur actuellement connecté. | -| FOURNI | Inclut les événements attribués à l’utilisateur fourni dans la requête. | -| AUCUN | Inclut uniquement les événements non attribués. | -| TOUT | Inclut tous les événements attribués, peu importe à qui ils sont attribués. | - -La requête n'est pas sensible à la casse. Les règles suivantes s'appliquent aux paramètres de la requête. - - - At least one organisation unit must be specified using the *ou* - (un ou plusieurs), ou *ouMode=ALL* doit être spécifié. - - - Un seul des paramètres *program* et *trackedEntity* peut être - spécifié (zéro ou un). - - - If *programStatus* is specified then *program* must also be - spécifié. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - Les éléments du filtre ne peuvent être spécifiés qu'une seule fois. - -Une requête pour toutes les instances associées à une unité d'organisation spécifique peut ressembler à ceci : - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -Pour lancer une requête sur des instances à l'aide d'un attribut avec filtre et d'un attribut sans filtre, avec une unité d'organisation en utilisant le mode de requête de l'unité d'organisation subordonnée, utilisez ceci : - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a filter: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -Une requête dans laquelle plusieurs opérandes et filtres sont spécifiés pour un élément de filtre : - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -Pour lancer une requête sur un attribut en utilisant plusieurs valeurs dans un filtre *IN* : - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - &filter=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -Pour limiter la réponse aux instances qui font partie d'un programme spécifique, vous pouvez inclure un paramètre de requête de programme : - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -Pour spécifier les dates d'inscription au programme dans la requête : - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&programStartDate=2013-01-01&programEndDate=2013-09-01 - -Pour limiter la réponse aux instances d'une entité suivie spécifique, vous pouvez inclure un paramètre de requête d'entité suivie : - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -Par défaut, les instances sont renvoyées dans des pages de taille 50. Pour modifier cela, vous pouvez utiliser les paramètres de requête de page et de taille de page (pageSize) : - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&page=2&pageSize=3 - -Vous pouvez utiliser une gamme d'opérateurs pour effectuer le filtrage : - - - -Tableau : Opérateurs de filtre - -| Opérateur | Description ; | -|---|---| -| EQ | Egal à | -| GT | Supérieur à | -| GE | Supérieur ou égal à | -| LT | Inférieur à | -| LE | inférieur ou égal à | -| NE | Pas égal à | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Égal à l'une des multiples valeurs séparées par ";" | - -##### Response format { #webapi_tei_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### Tracked entity instance grid query { #webapi_tracked_entity_instance_grid_query } - -To query for tracked entity instances you can interact with the -*/api/trackedEntityInstances/grid* resource. There are two types of -queries: One where a *query* query parameter and optionally *attribute* -parameters are defined, and one where *attribute* and *filter* -parameters are defined. This endpoint uses a more compact "grid" format, -and is an alternative to the query in the previous section. - - /api/33/trackedEntityInstances/query - -##### Request syntax { #webapi_tei_grid_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Paramètre de requête | Description ; | -|---|---| -| requête | Query string. Attribute query parameter can be used to define which attributes to include in the response. If no attributes but a program is defined, the attributes from the program will be used. If no program is defined, all attributes will be used. There are two formats. The first is a plan query string. The second is on the format :. Operators can be EQ | LIKE. EQ implies exact matches on words, LIKE implies partial matches on words. The query will be split on space, where each word will form a logical AND query. | -| attribut | Attributes to be included in the response. Can also be used as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. Filters can be omitted in order to simply include the attribute in the response without any constraints. | -| filtre | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode (Mode d'unité d'organisation) | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| programme | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus (statut de programme) | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| Suivi | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| Entité suivie | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| eventStatus (statut d'événement) | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Start date of event associated with the given program and event status. | -| eventEndDate | End date of event associated with the given program and event status. | -| Étape du programme | The programStage for which the event related filters should be applied to. If not provided all stages will be considered. | -| skipMeta (ignorer les métadonnées) | Indicates whether meta data for the response should be included. | -| page | Il s'agit du numéro de page. La page par défaut est 1. | -| taille de la page | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| Mode d'utilisateur assigné | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser (Utilisateur assigné) | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Il est possible de filtrer le résultat en supposant qu'une TEI soit un doublon potentiel. true: renvoie les TEI marqués comme doublons potentiels. false: renvoie les TEI NON marqués comme doublons potentiels. En cas d'omission, nous ne vérifions pas si une TEI est un doublon potentiel ou pas.| - -Les modes de sélection d'unités d'organisation disponibles sont expliqués dans le tableau suivant. - - - -Table: Organisation unit selection modes - -| Mode | Description ; | -|---|---| -| SELECTED | Unités d'organisation définies dans la requête. | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| CAPTURE | The data capture organisation units associated with the current user and all children, i.e. all organisation units in the sub-hierarchy. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -Note that you can specify "attribute" with filters or directly using the "filter" params for constraining the -instances to return. - -Certain rules apply to which attributes are returned. - - - If "query" is specified without any attributes or program, then all attributes that - are marked as "Display in List without Program" is included in the response. - - - If program is specified, all the attributes linked to the program will - be included in the response. - - - If tracked entity type is specified, then all tracked entity type attributes - will be included in the response. - -You can specify queries with words separated by space - in that -situation the system will query for each word independently and return -records where each word is contained in any attribute. A query item can -be specified once as an attribute and once as a filter if needed. The -query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - (un ou plusieurs), ou *ouMode=ALL* doit être spécifié. - - - Un seul des paramètres *program* et *trackedEntity* peut être - spécifié (zéro ou un). - - - If *programStatus* is specified then *program* must also be - spécifié. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - If *eventStatus* is specified then *eventStartDate* and - *eventEndDate* must also be specified. - - - A query cannot be specified together with filters. - - - Attribute items can only be specified once. - - - Les éléments du filtre ne peuvent être spécifiés qu'une seule fois. - -Une requête pour toutes les instances associées à une unité d'organisation spécifique peut ressembler à ceci : - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -A query on all attributes for a specific value and organisation unit, -using an exact word match: - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -A query on all attributes for a specific value, using a partial word -match: - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -You can query on multiple words separated by the URL character for -space which is %20, will use a logical AND query for each - word: - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -A query where the attributes to include in the response are specified: - - /api/33/trackedEntityInstances/query.json?query=isabel - &attribute=dv3nChNSIxy&attribute=AMpUYgxuCaE&ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendants organisation unit query mode: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &attribute=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a - filter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -Une requête dans laquelle plusieurs opérandes et filtres sont spécifiés pour un élément de filtre : - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an IN - filter: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - &attribute=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -Pour limiter la réponse aux instances qui font partie d'un programme spécifique, vous pouvez inclure un paramètre de requête de programme : - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -Pour spécifier les dates d'inscription au programme dans la requête : - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&program=ur1Edk5Oe2n&programStartDate=2013-01-01 - &programEndDate=2013-09-01 - -Pour limiter la réponse aux instances d'une entité suivie spécifique, vous pouvez inclure un paramètre de requête d'entité suivie : - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -Par défaut, les instances sont renvoyées dans des pages de taille 50. Pour modifier cela, vous pouvez utiliser les paramètres de requête de page et de taille de page (pageSize) : - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -To query for instances which have events of a given status within a -given time span: - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -Vous pouvez utiliser une gamme d'opérateurs pour effectuer le filtrage : - - - -Tableau : Opérateurs de filtre - -| Opérateur | Description ; | -|---|---| -| EQ | Egal à | -| GT | Supérieur à | -| GE | Supérieur ou égal à | -| LT | Inférieur à | -| LE | inférieur ou égal à | -| NE | Pas égal à | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Égal à l'une des multiples valeurs séparées par ";" | - -##### Response format { #webapi_tei_grid_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - - - csv (application/csv) - - - xls (application/vnd.ms-excel) - -The response in JSON comes is in a tabular format and can look like the -following. The *headers* section describes the content of each column. -The instance, created, last updated, org unit and tracked entity columns -are always present. The following columns correspond to attributes -specified in the query. The *rows* section contains one row per -instance. - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### Tracked entity instance filters { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - /api/33/trackedEntityInstanceFilters - -##### Create and update a tracked entity instance filter definition { #create-and-update-a-tracked-entity-instance-filter-definition } - -For creating and updating a tracked entity instance filter in the -system, you will be working with the *trackedEntityInstanceFilters* -resource. The tracked entity instance filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Tableau : Charge utile - -| Valeurs de charge utile | Description ; | Exemple | -|---|---|---| -| nom | Name of the filter. Required. || -| Description | A description of the filter. || -| sortOrder (ordre de tri) | The sort order of the filter. Used in Tracker Capture to order the filters in the program dashboard. || -| style | Object containing css style. | ( "color": "blue", "icon": "fa fa-calendar"} | -| programme | Objet contenant l'identifiant du programme. Obligatoire. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Table: Entity Query Criteria definition - -|||| -|---|---|---| -| Filtres des valeurs d'attributs | A list of attributeValueFilters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| Statut de l'inscription | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | When this parameter is true, the filter only returns TEIs that have an enrollment with status followup. || -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode (Mode d'unité d'organisation) | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| Mode d'utilisateur assigné | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUser (Utilisateur assigné) | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| Ordre d'affichage des colonnes | To specify the output ordering of columns | "displayOrderColumns": ["enrollmentDate", "program"] | -| Ordre | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus (statut d'événement) | Any valid EventStatus | "eventStatus": "COMPLETED" | -| Étape du programme | To specify a programStage uid to filter on. TEIs will be filtered based on presence of enrollment in the specified program stage.| "programStage"="a3kGcGDCuk6" | -| TrackedEntityType (Type d'entité suivie) | To specify a trackedEntityType filter TEIs on. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | To specify a list of trackedEntityInstances to use when querying TEIs. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod object date filtering based on enrollment incident date. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate (date de l'événement) | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod object date filtering based on enrollment created date. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Table: Event filters definition - -|||| -|---|---|---| -| Étape du programme | Which programStage the TEI needs an event in to be returned. | "eaDH9089uMp" | -| eventStatus (statut d'événement) | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| Mode d'utilisateur assigné | To specify the assigned user selection mode for events. Possible values are CURRENT (events assigned to current user)| PROVIDED (events assigned to users provided in "assignedUsers" list) | NONE (events assigned to no one) | ANY (events assigned to anyone). If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUser (Utilisateur assigné) | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| période | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| date de début | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| date de fin | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -Table: Period definition - -|||| -|---|---|---| -| periodFrom | Number of days from current day. Can be positive or negative integer. | -15 | -| periodTo | Number of days from current day. Must be bigger than periodFrom. Can be positive or negative integer. | 15 | - -##### Tracked entity instance filters query { #tracked-entity-instance-filters-query } - -To query for tracked entity instance filters in the system, you can -interact with the */api/trackedEntityInstanceFilters* resource. - - - -Table: Tracked entity instance filters query parameters - -| Paramètre de requête | Description ; | -|---|---| -| programme | Program identifier. Restricts filters to the given program. | - -### Enrollment management { #webapi_enrollment_management } - -Enrollments have full CRUD support in the API. Together with the API -for tracked entity instances most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/enrollments - -#### Enrolling a tracked entity instance into a program { #webapi_enrolling_tei } - -For enrolling persons into a program, you will need to first get the -identifier of the person from the *trackedEntityInstances* resource. -Then, you will need to get the program identifier from the *programs* -resource. A template payload can be seen below: - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -This payload should be used in a *POST* request to the enrollments -resource identified by the following URL: - - /api/33/enrollments - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - /api/33/enrollments//cancelled - -For completing an enrollment for a tracked entity instance you can make a -*PUT* request to the following URL: - - /api/33/enrollments//completed - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - /api/33/enrollments/ - -#### Enrollment instance query { #webapi_enrollment_instance_query } - -To query for enrollments you can interact with the */api/enrollments* -resource. - - /api/33/enrollments - -##### Request syntax { #webapi_enrollment_query_request_syntax } - - - -Table: Enrollment query parameters - -| Paramètre de requête | Description ; | -|---|---| -| ou | Organisation unit identifiers, separated by ";". | -| ouMode (Mode d'unité d'organisation) | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| programme | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus (statut de programme) | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| Suivi | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| lastUpdatedDuration (durée de la dernière mise à jour) | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). | -| Entité suivie | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| trackedEntityInstance | Tracked entity instance identifier. Should not be used together with trackedEntity. | -| page | Il s'agit du numéro de page. La page par défaut est 1. | -| taille de la page | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| includeDeleted | Indicates whether to include soft deleted enrollments or not. It is false by default. | - -Les modes de sélection d'unités d'organisation disponibles sont expliqués dans le tableau suivant. - - - -Table: Organisation unit selection modes - -| Mode | Description ; | -|---|---| -| SELECTED | Organisation units defined in the request (default). | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -La requête n'est pas sensible à la casse. Les règles suivantes s'appliquent aux paramètres de la requête. - - - At least one organisation unit must be specified using the *ou* - (un ou plusieurs), ou *ouMode=ALL* doit être spécifié. - - - Un seul des paramètres *program* et *trackedEntity* peut être - spécifié (zéro ou un). - - - If *programStatus* is specified then *program* must also be - spécifié. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - -Une requête pour toutes les inscriptions associées à une unité d'organisation spécifique peut ressembler à ceci : - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -To constrain the response to enrollments which are part of a specific -program you can include a program query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the - query: - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - &programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to enrollments of a specific tracked entity -you can include a tracked entity query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -To constrain the response to enrollments of a specific tracked entity -instance you can include a tracked entity instance query parameter, in -this case we have restricted it to available enrollments viewable for -current - user: - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -By default the enrollments are returned in pages of size 50, to change -this you can use the page and pageSize query - parameters: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### Response format { #webapi_enrollment_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### Événements { #webapi_events } - -This section is about sending and reading events. - - /api/33/events - -The different status of an event are: - -* **ACTIVE**: If a event has ACTIVE status, it is possible to edit the event details. COMPLETED events can be turned ACTIVE again and vice versa. -* **COMPLETED**: An event change the status to COMPLETED only when a user clicks the complete button. If a event has COMPLETED status, it is not possible to edit the event details. ACTIVE events can be turned COMPLETED again and vice versa. -* **SKIPPED**: Scheduled events that no longer need to happen. In Tracker Capture, there is a button for that. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### Sending events { #webapi_sending_events } - -DHIS2 supports three kinds of events: single events with no registration -(also referred to as anonymous events), single event with registration -and multiple events with registration. Registration implies that the -data is linked to a tracked entity instance which is identified using -some sort of identifier. - -To send events to DHIS2 you must interact with the *events* resource. -The approach to sending events is similar to sending aggregate data -values. You will need a *program* which can be looked up using the -*programs* resource, an *orgUnit* which can be looked up using the -*organisationUnits* resource, and a list of valid data element -identifiers which can be looked up using the *dataElements* resource. -For events with registration, a *tracked entity instance* identifier is -required, read about how to get this in the section about the -*trackedEntityInstances* resource. For sending events to programs with -multiple stages, you will need to also include the *programStage* -identifier, the identifiers for programStages can be found in the -*programStages* resource. - -A simple single event with no registration example payload in XML format -where we send events from the "Inpatient morbidity and mortality" -program for the "Ngelehun CHC" facility in the demo database can be seen -below: - -```xml - - - - - - - - - -``` - -To perform some testing we can save the XML payload as a file -called *event.xml* and send it as a POST request to the events resource -in the API using curl with the following command: - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -The same payload in JSON format looks like this: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -To send this you can save it to a file called *event.json* and use curl -like this: - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -We also support sending multiple events at the same time. A payload in -XML format might look like this: - -```xml - - - - - - - - - - - - - - - - - -``` - -You will receive an import summary with the response which can be -inspected in order to get information about the outcome of the request, -like how many values were imported successfully. The payload in JSON -format looks like this: - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -You can also use GeoJson to store any kind of geometry on your event. An example payload using GeoJson instead of the former latitude and longitude properties can be seen here: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -As part of the import summary you will also get the identifier -*reference* to the event you just sent, together with a *href* element -which points to the server location of this event. The table below -describes the meaning of each element. - - - -Table: Events resource format - -| Paramètre | Type | Obligatoire | Options (par défaut en premier) | Description ; | -|---|---|---|---|---| -| programme | chaîne | vrai || Identifier of the single event with no registration program | -| orgUnit (Unité d'organisation) | chaîne | vrai || Identifier of the organisation unit where the event took place | -| eventDate (date de l'événement) | date | vrai || The date of when the event occurred | -| completedDate | date | faux || The date of when the event is completed. If not provided, the current date is selected as the event completed date | -| statut | enum | faux | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Whether the event is complete or not | -| storedBy (Stockée par) | chaîne | faux | Defaults to current user | Who stored this event (can be username, system-name, etc) | -| coordinate | double | faux || Refers to where the event took place geographically (latitude and longitude) | -| élément de données | chaîne | vrai || Identifier of data element | -| valeur | chaîne | vrai || Data value or measure for this event | - -##### OrgUnit matching { #orgunit-matching } - -By default the orgUnit parameter will match on the -ID, you can also select the orgUnit id matching scheme by using the -parameter orgUnitIdScheme=SCHEME, where the options are: *ID*, *UID*, -*UUID*, *CODE*, and *NAME*. There is also the *ATTRIBUTE:* scheme, which -matches on a *unique* metadata attribute value. - -#### Updating events { #webapi_updating_events } - -To update an existing event, the format of the payload is the same, but -the URL you are posting to must add the identifier to the end of the URL -string and the request must be PUT. - -The payload has to contain all, even non-modified, attributes. -Attributes that were present before and are not present in the current -payload any more will be removed by the system. - -It is not allowed to update an already deleted event. The same applies -to tracked entity instance and enrollment. - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### Deleting events { #webapi_deleting_events } - -To delete an existing event, all you need is to send a DELETE request -with an identifier reference to the server you are using. - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### Assigning user to events { #webapi_user_assign_event } - -A user can be assigned to an event. This can be done by including the appropriate property in the payload when updating or creating the event. - - "assignedUser": "" - -The id refers to the if of the user. Only one user can be assigned to an event at a time. - -User assignment must be enabled in the program stage before users can be assigned to events. -#### Getting events { #webapi_getting_events } - -To get an existing event you can issue a GET request including the -identifier like this: - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### Querying and reading events { #webapi_querying_reading_events } - -This section explains how to read out the events that have been stored -in the DHIS2 instance. For more advanced uses of the event data, please -see the section on event analytics. The output format from the -`/api/events` endpoint will match the format that is used to send events -to it (which the analytics event api does not support). Both XML and -JSON are supported, either through adding .json/.xml or by setting the -appropriate *Accept* header. The query is paged by default and the -default page size is 50 events, *field* filtering works as it does for -metadata, add the *fields* parameter and include your wanted properties, -i.e. *?fields=program,status*. - - - -Table: Events resource query parameters - -| Clé | Type | Obligatoire | Description ; | -|---|---|---|---| -| programme | identifiant | true (if not programStage is provided) | Identifiant de programme | -| Étape du programme | identifiant | faux | Identifiant de l'étape de programme | -| programStatus (statut de programme) | enum | faux | Status of event in program, ca be ACTIVE | COMPLETED | CANCELLED | -| Suivi | booléen | faux | Whether event is considered for follow up in program, can be true | false or omitted. | -| trackedEntityInstance | identifiant | faux | Identifiant de l'instance d'entité suivie | -| orgUnit (Unité d'organisation) | identifiant | vrai | Identifiant de l'unité d'organisation | -| ouMode (Mode d'unité d'organisation) | enum | faux | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| date de début | date | faux | Only events newer than this date | -| date de fin | date | faux | Only events older than this date | -| statut | enum | faux | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | date | faux | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | date | faux | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration (durée de la dernière mise à jour) | chaîne | faux | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta (ignorer les métadonnées) | booléen | faux | Exclut la partie métadonnées de la réponse (améliore les performances) | -| page | entier | faux | Numéro de page | -| taille de la page | entier | faux | Number of items in each page | -| totalPages | booléen | faux | Indicates whether to include the total number of pages in the paging response. | -| skipPaging | booléen | faux | Indicates whether to skip paging in the query and return all events. | -| dataElementIdScheme (Schéma d'identification de l'élément de données) | chaîne | faux | Data element ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme (Schéma d'identification de la combinaison d'options de catégorie) | chaîne | faux | Category Option Combo ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| orgUnitIdScheme (Schéma d'identification de l'unité d'organisation) | chaîne | faux | Organisation Unit ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programIdScheme (Schéma d'identification des programmes) | chaîne | faux | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programmeStageIdScheme (Schéma d'identification des étapes de programme) | chaîne | faux | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| idScheme (schéma d'identification) | chaîne | faux | Permet de définir le schéma d'identification à la fois pour l'élément de données, la combinaison d'options de catégorie, l'unité d'organisation, le programme et l'étape de programme. | -| Ordre | chaîne | faux | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| événement | comma delimited string | faux | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | booléen | faux | Ignore les identifiants d'événement dans la réponse | -| attributeCc (\*\*) | chaîne | faux | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | chaîne | faux | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | faux | vrai | faux | Indicates whether the import should be done asynchronous or synchronous. | -| includeDeleted | booléen | faux | S'il est défini sur "vrai", les événements supprimés de façon réversible seront inclus dans le résultat de votre requête. | -| Mode d'utilisateur assigné | enum | faux | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser (Utilisateur assigné) | comma delimited strings | faux | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> **Note** -> -> If the query contains neither `attributeCC` nor `attributeCos`, the server returns events for all attribute option combos where the user has read access. - -##### Exemples { #examples } - -Query for all events with children of a certain organisation unit: - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -Query for all events with all descendants of a certain organisation -unit, implying all organisation units in the sub-hierarchy: - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -La requête pour tous les événements disposant d'un programme et d'une unité d'organisation : - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -Query for all events with a certain program and organisation unit, -sorting by due date - ascending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -La requête pour les 10 événements avec la date d'événement la plus récente dans un programme et une unité d'organisation - par pagination et ordonnés par date d'échéance en ordre décroissant : - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &order=eventDate:desc&pageSize=10&page=1 - -La requête pour tous les événements avec un programme et une unité d'organisation pour une instance d'entité suivie donnée : - - /api/33/events.json?orgUnit=DiszpKrYNg8 - &program=eBAyeGv0exc&trackedEntityInstance=gfVxE3ALA9m - -Query for all events with a certain program and organisation unit older -or equal to - 2014-02-03: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -La requête pour tous les événements avec une étape de programme, une unité d'organisation et une instance d'entité suivie de l'an 2014 : - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &trackedEntityInstance=gfVxE3ALA9m&startDate=2014-01-01&endDate=2014-12-31 - -Query files associated with event data values. In the specific case of fetching an image file an -additional parameter can be provided to fetch the image with different dimensions. If dimension is -not provided, the system will return the original image. The parameter will be ignored in case of -fetching non-image files e.g pdf. Possible dimension values are *small(254 x 254), -medium(512 x 512), large(1024 x 1024) or original*. Any value other than those mentioned will be -discarded and the original image will be returned. - - /api/33/events/files?eventUid=hcmcWlYkg9u&dataElementUid=C0W4aFuVm4P&dimension=small - -Retrieve events with specified Organisation unit and Program, and use _Attribute:Gq0oWTf2DtN_ as -identifier scheme - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for -orgUnits, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as identifier -scheme for the rest of the metadata with assigned attribute. - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=Code - -#### Event grid query { #event-grid-query } - -In addition to the above event query end point, there is an event grid -query end point where a more compact "grid" format of events are -returned. This is possible by interacting with -/api/events/query.json|xml|xls|csv endpoint. - - /api/33/events/query - -Most of the query parameters mentioned in event querying and reading -section above are valid here. However, since the grid to be returned -comes with specific set of columns that apply to all rows (events), it -is mandatory to specify a program stage. It is not possible to mix -events from different programs or program stages in the return. - -Returning events from a single program stage, also opens up for new -functionality - for example sorting and searching events based on their -data element values. api/events/query has support for this. Below are -some examples - -A query to return an event grid containing only selected data elements -for a program stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &dataElement=qrur9Dvnyt5,fWIAEtYVEGk,K6uUAvq500H&order=lastUpdated:desc - &pageSize=50&page=1&totalPages=true - -A query to return an event grid containing all data elements of a -program - stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &includeAllDataElements=true - -A query to filter events based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50 - -In addition to the filtering, the above example also illustrates one -thing: the fact that there are no data elements mentioned to be returned -in the grid. When this happens, the system defaults back to return only -those data elements marked "Display in report" under program stage -configuration. - -We can also extend the above query to return us a grid sorted (asc|desc) -based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50&order=qrur9Dvnyt5:desc - -#### Event filters { #webapi_event_filters } - -To create, read, update and delete event filters you -can interact with the `/api/eventFilters` resource. - - /api/33/eventFilters - -##### Create and update an event filter definition { #create-and-update-an-event-filter-definition } - -For creating and updating an event filter in the -system, you will be working with the *eventFilters* -resource. *POST* is used to create and *PUT* method is used to update. The event filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Request Payload - -| Request Property | Description ; | Exemple | -|---|---|---| -| nom | Name of the filter. | "name":"My working list" | -| Description | A description of the filter. | "description":"for listing all events assigned to me". | -| programme | The uid of the program. | "program" : "a3kGcGDCuk6" | -| Étape du programme | The uid of the program stage. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Object containing parameters for querying, sorting and filtering events. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Table: Event Query Criteria definition - -|||| -|---|---|---| -| Suivi | Used to filter events based on enrollment followUp flag. Possible values are true|false. | "followUp": true | -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode (Mode d'unité d'organisation) | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| Mode d'utilisateur assigné | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUser (Utilisateur assigné) | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | To specify the output ordering of columns | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| Ordre | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| Filtres de données | To specify filters to be applied when listing events | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| statut | Any valid EventStatus | "eventStatus": "COMPLETED" | -| événements | To specify list of events | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod object date filtering based on completed date. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate (date de l'événement) | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod object date filtering based on due date. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| période | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| date de début | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| date de fin | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -The available assigned user selection modes are explained in the -following table. - - - -Table: Assigned user selection modes (event assignment) - -| Mode | Description ; | -|---|---| -| ACTUEL | Assigned to the current logged in user | -| FOURNI | Assigned to the users provided in the "assignedUser" parameter | -| AUCUN | Assigned to no users. | -| TOUT | Assigned to any users. | - -A sample payload that can be used to create/update an eventFilter is shown below. - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### Retrieving and deleting event filters { #retrieving-and-deleting-event-filters } - -A specific event filter can be retrieved by using the following api - - GET /api/33/eventFilters/{uid} - -All event filters can be retrieved by using the following api. - - GET /api/33/eventFilters?fields=* - -All event filters for a specific program can be retrieved by using the following api - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -An event filter can be deleted by using the following api - - DELETE /api/33/eventFilters/{uid} - -### Relationships { #relationships } -Relationships are links between two entities in tracker. These entities can be tracked entity instances, enrollments and events. - -There are multiple endpoints that allow you to see, create, delete and update relationships. The most common is the /api/trackedEntityInstances endpoint, where you can include relationships in the payload to create, update or deleting them if you omit them - Similar to how you work with enrollments and events in the same endpoint. All the tracker endpoints, /api/trackedEntityInstances, /api/enrollments and /api/events also list their relationships if requested in the field filter. - -The standard endpoint for relationships is, however, /api/relationships. This endpoint provides all the normal CRUD operations for relationships. - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -This request will return a list of any relationship you have access to see that includes the trackedEntityInstance, enrollment or event you specified. Each relationship is represented with the following JSON: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -You can also view specified relationships using the following endpoint: - - GET /api/relationships/ - -To create or update a relationship, you can use the following endpoints: - - POST /api/relationships - PUT /api/relationships - -And use the following payload structure: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -To delete a relationship, you can use this endpoint: - - DELETE /api/relationships/ - -In our example payloads, we use a relationship between trackedEntityInstances. Because of this, the "from" and "to" properties of our payloads include "trackedEntityInstance" objects. If your relationship includes other entities, you can use the following properties: - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### Update strategies { #webapi_tei_update_strategies } - -Two update strategies for all 3 tracker endpoints are supported: -enrollment and event creation. This is useful when you have generated an -identifier on the client side and are not sure if it was created or not -on the server. - - - -Table: Available tracker strategies - -| Paramètre | Description ; | -|---|---| -| CRÉER | Create only, this is the default behavior. | -| CREATE_AND_UPDATE | Try and match the ID, if it exist then update, if not create. | - -To change the parameter, please use the strategy parameter: - - POST /api/33/trackedEntityInstances?strategy=CREATE_AND_UPDATE - -### Tracker bulk deletion { #webapi_tracker_bulk_deletion } - -Bulk deletion of tracker objects work in a similar fashion to adding and -updating tracker objects, the only difference is that the -`importStrategy` is *DELETE*. - -*Example: Bulk deletion of tracked entity instances:* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*Example: Bulk deletion of enrollments:* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*Example: Bulk deletion of events:* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### Identifier reuse and item deletion via POST and PUT methods { #webapi_updating_and_deleting_items } - -Tracker endpoints */trackedEntityInstances*, */enrollments*, */events* -support CRUD operations. The system keeps track of used identifiers. -Therefore, an item which has been created and then deleted (e.g. events, -enrollments) cannot be created or updated again. If attempting to delete -an already deleted item, the system returns a success response as -deletion of an already deleted item implies no change. - -The system does not allow to delete an item via an update (*PUT*) or -create (*POST*) method. Therefore, an attribute *deleted* is ignored in -both *PUT* and *POST* methods, and in *POST* method it is by default set -to *false*. - -### Import parameters { #webapi_import_parameters } - -Le processus d'importation peut être personnalisé à l'aide d'un ensemble de paramètres d'importation : - - - -Tableau : Paramètres d'importation - -| Paramètre | Valeurs (par défaut en premier) | Description ; | -|---|---|---| -| dataElementIdScheme (Schéma d'identification de l'élément de données) | identifiant | nom | code | attribut:ID | Propriété de l'objet d'élément de données à utiliser pour faire correspondre les données. | -| orgUnitIdScheme (Schéma d'identification de l'unité d'organisation) | identifiant | nom | code | attribut:ID | Propriété de l'objet d'unité d'organisation à utiliser pour faire correspondre les données. | -| idScheme (schéma d'identification) | id | name | code| attribute:ID | Property of all objects including data elements, org units and category option combos, to use to map the data values. | -| dryRun (essai) | faux | vrai | Pour sauvegarder les modifications sur le serveur ou pour renvoyer le résumé de l'importation. | -| strategy | CRÉER | METTRE À JOUR | CRÉER _ET_METTRE À JOUR | SUPPRIMER | Sauvegarde des objets de tous les statuts d'importation, nouveaux ou mis à jour, sur le serveur. | -| skipNotifications | vrai | faux | Indicates whether to send notifications for completed events. | -| skipFirst | vrai | faux | Relevant for CSV import only. Indicates whether CSV file contains a header row which should be skipped. | -| importReportMode (mode de rapport d'importation) | FULL, ERRORS, DEBUG | Définit le mode de `rapport d'importation` ; contrôle ce qui est rapporté après l'importation. `ERRORS` n'inclut que les *rapports d'objets* pour les objets qui contiennent des erreurs. `FULL` renvoie un *rapport d'objet* pour tous les objets importés, et `DEBUG` renvoie la même chose plus un nom pour l'objet (si disponible). | - -#### CSV Import / Export { #webapi_events_csv_import_export } - -In addition to XML and JSON for event import/export, in DHIS2.17 we -introduced support for the CSV format. Support for this format builds on -what was described in the last section, so here we will only write about -what the CSV specific parts are. - -To use the CSV format you must either use the `/api/events.csv` -endpoint, or add *content-type: text/csv* for import, and *accept: -text/csv* for export when using the `/api/events` endpoint. - -The order of column in the CSV which are used for both export and import -is as follows: - - - -Table: CSV column - -| Index | Clé | Type | Description ; | -|---|---|---|---| -| 1 | événement | identifiant | Identifier of event | -| 2 | statut | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | programme | identifiant | Identifiant de programme | -| 4 | Étape du programme | identifiant | Identifiant de l'étape de programme | -| 5 | inscription | identifiant | Identifier of enrollment (program instance) | -| 6 | orgUnit (Unité d'organisation) | identifiant | Identifiant de l'unité d'organisation | -| 7 | eventDate (date de l'événement) | date | Date de l'événement | -| 8 | dueDate | date | Due Date | -| 9 | latitude | double | Latitude where event happened | -| 10 | longitude | double | Longitude where event happened | -| 11 | élément de données | identifiant | Identifier of data element | -| 12 | valeur | chaîne | Value / measure of event | -| 13 | storedBy (Stockée par) | chaîne | Event was stored by (defaults to current user) | -| 14 | Fourni ailleurs | booléen | Was this value collected somewhere else | -| 14 | completedDate | date | Completed date of event | -| 14 | completedBy (effectué par) | chaîne | Username of user who completed event | - -*Example of 2 events with 2 different data value - each:* - -```csv -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,1,, -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,2,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,3,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,4,, -``` - -#### Import strategy: SYNC { #webapi_sync_import_strategy } - -The import strategy SYNC should be used only by internal synchronization -task and not for regular import. The SYNC strategy allows all 3 -operations: CREATE, UPDATE, DELETE to be present in the payload at the -same time. - -### Tracker Ownership Management { #webapi_tracker_ownership_management } - -A new concept called Tracker Ownership is introduced from 2.30. There -will now be one owner organisation unit for a tracked entity instance in -the context of a program. Programs that are configured with an access -level of *PROTECTED* or *CLOSED* will adhere to the ownership -privileges. Only those users belonging to the owning org unit for a -tracked entity-program combination will be able to access the data -related to that program for that tracked entity. - -#### Tracker Ownership Override : Break the Glass { #webapi_tracker_ownership_override_api } - -It is possible to temporarily override this ownership privilege for a -program that is configured with an access level of *PROTECTED*. Any user -will be able to temporarily gain access to the program related data, if -the user specifies a reason for accessing the tracked entity-program -data. This act of temporarily gaining access is termed as *breaking the -glass*. Currently, the temporary access is granted for 3 hours. DHIS2 -audits breaking the glass along with the reason specified by the user. -It is not possible to gain temporary access to a program that has been -configured with an access level of *CLOSED*. To break the glass for a -tracked entity program combination, you can issue a POST request as -shown: - - /api/33/tracker/ownership/override?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care - -#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer_api } - -It is possible to transfer the ownership of a tracked entity-program -from one org unit to another. This will be useful in case of patient -referrals or migrations. Only an owner (or users who have broken the -glass) can transfer the ownership. To transfer ownership of a tracked -entity-program to another organisation unit, you can issue a PUT request -as shown: - - /api/33/tracker/ownership/transfer?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&ou=EJNxP3WreNP - - -## Potential Duplicates { #potential-duplicates } - -Potential duplicates are records we work with in the data deduplication feature. Due to the nature of the deduplication feature, this API endpoint is somewhat restricted. - -A potential duplicate represents a pair of records which are suspected to be a duplicate. - -The payload of a potential duplicate looks like this: - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -You can retrieve a list of potential duplicates using the following endpoint: - - GET /api/potentialDuplicates - -| Nom du paramètre | Description ; | Type | Valeurs autorisées | -|---|---|---|---| -| teis | List of tracked entity instances | List of string (separated by comma)| existing tracked entity instance id | -| statut | Potential duplicate status | chaîne | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Status code | Description ; -|---|---| -| 400 | Invalid input status - -You can inspect individual potential duplicate records: - - GET /api/potentialDuplicates/ - -| Status code | Description ; -|---|---| -| 404 | Potential duplicate not found - -To create a new potential duplicate, you can use this endpoint: - - POST /api/potentialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Status code | Description ; -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -To update a potential duplicate status: - - PUT /api/potentialDuplicates/ - -| Nom du paramètre | Description ; | Type | Valeurs autorisées | -|---|---|---|---| -| statut | Potential duplicate status | chaîne | `OPEN`, `INVALID`, `MERGED` | - -| Status code | Description ; -|---|---| -| 400 | You can't update a potential duplicate to MERGED as this is possible only by a merging request -| 400 | You can't update a potential duplicate that is already in a MERGED status - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -To merge a Potential Duplicate, or the two tracked entity instances the Potential Duplicate represents, the following endpoint can be used: - - POST /api/potentialDuplicates//merge - -| Nom du paramètre | Description ; | Type | Valeurs autorisées | -|---|---|---|---| -| mergeStrategy | Strategy to use for merging the potentialDuplicate | enum | AUTO(default) or MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- The same attribute has different values in each tracked entity instance -- Both tracked entity instances are enrolled in the same program -- Tracked entity instances have different types - -If any conflict is encountered, an errormessage is returned to the user. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -When requesting an automatic merge like this, a payload is not required and will be ignored. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Relationship cannot be between the original and the duplicate (This results in an invalid self-referencing relationship) -- Relationship cannot be of the same type and to the same object in both tracked entity instances (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) - -There are two ways to do a manual merge: With and without a payload. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -Otherwise, if a manual merge is requested with a payload, the payload refers to what data should be moved from the duplicate to the original. The payload looks like this: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -The fields are explained in the following table. - - -Table: Program Notification Template payload - -| Champ | Obligatoire | Description ; | Valeurs | -|---|---|---|---| -| nom | Oui | name of Program Notification Template | case-notification-alert | -| notificationTrigger | Oui | When notification should be triggered. Possible values are ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| ENROLLMENT (inscription) | -| subjectTemplate | Non | Subject template string | Case notification V{org_unit_name} | -| messageTemplate | Oui | Message template string | Case notification A{h5FuguPFF2j} | -| notificationRecipient | OUI | Who is going to receive notification. Possible values are USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | Non | Which channel should be used for this notification. It can be either SMS, EMAIL or HTTP | SMS | -| sendRepeatable | Non | Whether notification should be sent multiple times | faux | - -NOTE: WEB_HOOK notificationRecipient is used only to POST http request to an external system. Make sure to choose HTTP delivery channel when using WEB_HOOK. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -The list of Program Notification Templates can be retrieved using GET. - - GET /api/programNotificationTemplates - -For one particular Program Notification Template. - - GET /api/33/programNotificationTemplates/{uid} - -To get filtered list of Program Notification Templates - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Program Notification Template can be deleted using DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -Program message lets you send messages to tracked entity instances, -contact addresses associated with organisation units, phone numbers and -email addresses. You can send messages through the `messages` resource. - - /api/33/messages - -### Sending program messages { #sending-program-messages } - -Program messages can be sent using two delivery channels: - - - SMS (SMS) - - - Email address (EMAIL) - -Program messages can be sent to various recipients: - - - Tracked entity instance: The system will look up attributes of value - type PHONE_NUMBER or EMAIL (depending on the specified delivery - channels) and use the corresponding attribute values. - - - Organisation unit: The system will use the phone number or email - information registered for the organisation unit. - - - List of phone numbers: The system will use the explicitly defined - phone numbers. - - - List of email addresses: The system will use the explicitly defined - email addresses. - -Below is a sample JSON payload for sending messages using POST requests. -Note that message resource accepts a wrapper object named -`programMessages` which can contain any number of program messages. - - POST /api/33/messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -The fields are explained in the following table. - - - -Table: Program message payload - -| Champ | Obligatoire | Description ; | Valeurs | -|---|---|---|---| -| recipients | Oui | Recipients of the program message. At least one recipient must be specified. Any number of recipients / types can be specified for a message. | Can be trackedEntityInstance, organisationUnit, an array of phoneNumbers or an array of emailAddresses. | -| programInstance | Either this or programStageInstance required | The program instance / enrollment. | Enrollment ID. | -| programStageInstance | Either this or programInstance required | The program stage instance / event. | Event ID. | -| deliveryChannels | Oui | Array of delivery channels. | SMS | EMAIL | -| subject | Non | The message subject. Not applicable for SMS delivery channel. | Text. | -| texte | Oui | The message text. | Text. | -| storeCopy | Non | Whether to store a copy of the program message in DHIS2. | false (default) | true | - -A minimalistic example for sending a message over SMS to a tracked -entity instance looks like this: - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### Retrieving and deleting program messages { #retrieving-and-deleting-program-messages } - -The list of messages can be retrieved using GET. - - GET /api/33/messages - -To get the list of sent tracker messages, the below endpoint can be used. ProgramInstance or ProgramStageInstance uid has to be provided. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -To get the list of all scheduled message - - GET /api/33/messages/scheduled - GET /api/33/messages/scheduled?scheduledAt=2020-12-12 - -One particular message can also be retrieved using GET. - - GET /api/33/messages/{uid} - -Message can be deleted using DELETE. - - DELETE /api/33/messages/{uid} - - -### Querying program messages { #querying-program-messages } - -The program message API supports program message queries based on -request parameters. Messages can be filtered based on below mentioned -query parameters. All requests should use the GET HTTP verb for -retrieving information. - - - -Table: Query program messages API - -| Paramètre | URL | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # Adresses électronique { #email } diff --git a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index 531da9bfe..221783e5a 100644 --- a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- Gestion - DHIS core version 2.37 +- Gestion template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md index cd0d7388a..6a12f595f 100644 --- a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- Gestion - DHIS version 2.39 +- Gestion template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index 51c604ec7..3d8a5f43c 100644 --- a/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/fr/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- Gestion - Version Master de DHIS2 Central +- Gestion template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index 0a7806871..e284bd8a7 100644 --- a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/fr/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 - Utilisation +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index 24044d8a8..c66ea52b9 100644 --- a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/fr/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 - Utilisation +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 4a6fd9981..8e7c0c5ea 100644 --- a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS version 2.39 - Utilisation +- DHIS version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 89feffc0c..c8e18f723 100644 --- a/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS version 2.39 - Utilisation +- DHIS version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/.cache_timestamp b/projects/dhis2-single-page-docs/id_ID/.cache_timestamp index 089fbed47..d6f04475e 100644 --- a/projects/dhis2-single-page-docs/id_ID/.cache_timestamp +++ b/projects/dhis2-single-page-docs/id_ID/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:27:38Z \ No newline at end of file +2024-06-04T21:27:34Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index b03a4093d..222d2a7a1 100644 --- a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2023-01-13' tags: -- DHIS core version 2.37 - pengembang +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index 4873033e8..23cf1e2fb 100644 --- a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- DHIS core version 2.38 - pengembang +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index c2d03619e..391bd2930 100644 --- a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - pengembang +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index ebe82d255..3e12265ca 100644 --- a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - pengembang +- DHIS core version 2.40 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 5d3291025..ab1ca4831 100644 --- a/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - pengembang - DHIS core version master @@ -12221,7 +12221,7 @@ Table: Query parameters for event query analytics only | Query parameter | Required | Description | Options | |---|---|---|---| -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return events which have coordinates. | false | true | @@ -13128,7 +13128,7 @@ Table: Query parameters for enrollment query endpoint | filter | No | Dimension identifier including data elements, attributes, periods, organisation units and organisation unit group sets. Parameter can be repeated any number of times. Item filters can be applied to a dimension on the format ::. Filter values are case-insensitive. || | programStatus | No | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | No | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return enrollments which have coordinates. | false | true | @@ -17837,20 +17837,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17953,7 +17954,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | No | Yes | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | Yes | No | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | No | Yes | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -18013,9 +18013,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Attributes { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -18030,18 +18032,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -18056,31 +18060,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Notes { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -18091,10 +18095,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -18136,92 +18140,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the working list. Required. || -| description | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Description | Example | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -18230,9 +18149,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -18265,7 +18184,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -18665,7 +18584,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -19111,7 +19030,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -19241,7 +19160,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | N/A | Undefined error message. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -19251,7 +19170,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -19276,8 +19195,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -19330,7 +19249,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -19386,7 +19305,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -19408,7 +19327,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -19442,7 +19361,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -19494,9 +19413,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -19576,8 +19495,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -19682,7 +19601,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19944,8 +19863,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -20149,8 +20068,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -20445,13 +20364,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -20497,7 +20416,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -20566,13 +20485,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -20584,7 +20503,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -20597,7 +20516,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -20607,7 +20526,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -20637,7 +20556,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -20653,2767 +20572,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Table: Payload -|Tracker Object|Previously|Now| +| Payload values | Description | Example | |---|---|---| -|**Attribute**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Event**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Note**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Relationship**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribute`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes`|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus`|`enrollmentStatus`| -|`query`|Removed - use `filter` instead| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Previously|Now| -|---|---| -|`enrollment`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus`|`status`| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`event`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`lastUpdated`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus`|`enrollmentStatus`| -|`skipEventId`|Removed| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Previously|Now| -|---|---| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity`| - -## Tracker Web API { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### Tracked entity instance management { #webapi_tracked_entity_instance_management } - -Tracked entity instances have full CRUD support in the API. Together -with the API for enrollment most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/trackedEntityInstances - -#### Creating a new tracked entity instance { #webapi_creating_tei } - -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -The field "geometry" accepts a GeoJson object, where the type of the -GeoJson have to match the featureType of the TrackedEntityType -definition. An example GeoJson object looks like this: - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +| name | Name of the working list. Required. || +| description | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Table: Program Stage Query Criteria - /api/trackedEntityInstances +| Criteria values | Description | Example | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +See an example payload below: ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -To push this to the server you can use the cURL command like this: - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -To create multiple instances in one request you can wrap the payload in -an outer array like this and POST to the same resource as above:[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -The system does not allow the creation of a tracked entity instance -(as well as enrollment and event) with a UID that was already used in -the system. That means that UIDs cannot be reused. - -#### Updating a tracked entity instance { #webapi_updating_tei } - -For updating a tracked entity instance, the payload is equal to the -previous section. The difference is that you must use the HTTP *PUT* -method for the request when sending the payload. You will also need to -append the person identifier to the *trackedEntityInstances* resource in -the URL like this, where `` should -be replaced by the identifier of the tracked entity instance: - - /api/trackedEntityInstances/ - -The payload has to contain all, even non-modified, attributes and -relationships. Attributes or relationships that were present before and -are not present in the current payload any more will be removed from the -system. This means that if attributes/relationships are empty in the -current payload, all existing attributes/relationships will be deleted -from the system. From 2.31, it is possible to ignore empty -attributes/relationships in the current payload. A request parameter of -`ignoreEmptyCollection` set to `true` can be used in case you do not -wish to send in any attributes/relationships and also do not want them -to be deleted from the system. - -It is not allowed to update an already deleted tracked entity instance. -Also, it is not allowed to mark a tracked entity instance as deleted via -an update request. The same rules apply to enrollments and events. - -#### Deleting a tracked entity instance { #webapi_deleting_tei } - -In order to delete a tracked entity instance, make a request to the URL -identifying the tracked entity instance with the *DELETE* -method. The URL is equal to the one above used for update. - -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } - -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Complete example of payload including: tracked entity instance, enrollment and event { #webapi_create_enroll_tei_create_event } - -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute":"cejWyOfXge6", - "value":"Male" - } - ], - "enrollments":[ - { - "orgUnit":"DiszpKrYNg8", - "program":"ur1Edk5Oe2n", - "enrollmentDate":"2017-09-15", - "incidentDate":"2017-09-15", - "events":[ - { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues": [ - { - "dataElement":"qrur9Dvnyt5", - "value":"22" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Male" - } - ] - }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues":[ - { - "dataElement":"qrur9Dvnyt5", - "value":"26" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Female" - } - ] - } - ] - } - ] + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Generated tracked entity instance attributes { #webapi_generate_tei_attributes } - -Tracked entity instance attributes that are using automatic generation of -unique values have three endpoints that are used by apps. The endpoints -are all used for generating and reserving values. - -In 2.29 we introduced TextPattern for defining and generating these -patterns. All existing patterns will be converted to a valid TextPattern -when upgrading to 2.29. - -> **Note** -> -> As of 2.29, all these endpoints will require you to include any -> variables reported by the `requiredValues` endpoint listed as -> required. Existing patterns, consisting of only `#`, will be upgraded -> to the new TextPattern syntax `RANDOM()`. The RANDOM -> segment of the TextPattern is not a required variable, so this -> endpoint will work as before for patterns defined before 2.29. - -##### Finding required values { #finding-required-values } - -A TextPattern can contain variables that change based on different -factors. Some of these factors will be unknown to the server, so the -values for these variables have to be supplied when generating and -reserving values. - -This endpoint will return a map of required and optional values, that -the server will inject into the TextPattern when generating new values. -Required variables have to be supplied for the generation, but optional -variables should only be supplied if you know what you are doing. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### Generate value endpoint { #webapi_generate_values } - -Online web apps and other clients that want to generate a value that -will be used right away can use the simple generate endpoint. This -endpoint will generate a value that is guaranteed to be unique at the -time of generation. The value is also guaranteed not to be reserved. As -of 2.29, this endpoint will also reserve the value generated for 3 days. - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } - -The generate and reserve endpoint is used by offline clients that need -to be able to register tracked entities with unique ids. They will -reserve a number of unique ids that this device will then use when -registering new tracked entity instances. The endpoint is called to -retrieve a number of tracked entity instance reserved values. An -optional parameter numberToReserve specifies how many ids to generate -(default is 1). - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -Similar to the /generate endpoint, this endpoint can also specify the -expiration time in the same way. By adding the `?expiration=` -you can override the default 60 days. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### Reserved values { #reserved-values } - -Reserved values are currently not accessible through the api, however, they -are returned by the `generate` and `generateAndReserve` endpoints. The -following table explains the properties of the reserved value object: - -##### - - - -Table: Reserved values - -| Property | Description | -|---|---| -| ownerObject | The metadata type referenced when generating and reserving the value. Currently only TRACKEDENTITYATTRIBUTE is supported. | -| ownerUid | The uid of the metadata object referenced when generating and reserving the value. | -| key | A partially generated value where generated segments are not yet added. | -| value | The fully resolved value reserved. This is the value you send to the server when storing data. | -| created | The timestamp when the reservation was made | -| expiryDate | The timestamp when the reservation will no longer be reserved | - -Expired reservations are removed daily. If a pattern changes, values -that were already reserved will be accepted when storing data, even if -they don't match the new pattern, as long as the reservation has not -expired. - -#### Image attributes { #image-attributes } - -Working with image attributes is a lot like working with file data -values. The value of an attribute with the image value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///image` -endpoint will return the actual image. The optional height and width -parameters can be used to specify the dimensions of the image. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } - -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. - - /api/33/trackedEntityInstances - -##### Request syntax { #webapi_tei_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Description | -|---|---| -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Indicates whether to include soft deleted teis or not. It is false by default. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | The selected organisation units and the immediate children, i.e. the organisation units at the level below. | -| DESCENDANTS | The selected organisation units and all children, i.e. all organisation units in the sub-hierarchy. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| ALL | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -The available assigned user modes are explained in the following table. - - - -Table: Assigned user modes - -| Mode | Description | -|---|---| -| CURRENT | Includes events assigned to the current logged in user. | -| PROVIDED | Includes events assigned to the user provided in the request. | -| NONE | Includes unassigned events only. | -| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendant organisation unit query mode: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a filter: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an *IN* filter: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - &filter=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&page=2&pageSize=3 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Description | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### Tracked entity instance grid query { #webapi_tracked_entity_instance_grid_query } - -To query for tracked entity instances you can interact with the -*/api/trackedEntityInstances/grid* resource. There are two types of -queries: One where a *query* query parameter and optionally *attribute* -parameters are defined, and one where *attribute* and *filter* -parameters are defined. This endpoint uses a more compact "grid" format, -and is an alternative to the query in the previous section. - - /api/33/trackedEntityInstances/query - -##### Request syntax { #webapi_tei_grid_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Description | -|---|---| -| query | Query string. Attribute query parameter can be used to define which attributes to include in the response. If no attributes but a program is defined, the attributes from the program will be used. If no program is defined, all attributes will be used. There are two formats. The first is a plan query string. The second is on the format :. Operators can be EQ | LIKE. EQ implies exact matches on words, LIKE implies partial matches on words. The query will be split on space, where each word will form a logical AND query. | -| attribute | Attributes to be included in the response. Can also be used as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. Filters can be omitted in order to simply include the attribute in the response without any constraints. | -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| eventStatus | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Start date of event associated with the given program and event status. | -| eventEndDate | End date of event associated with the given program and event status. | -| programStage | The programStage for which the event related filters should be applied to. If not provided all stages will be considered. | -| skipMeta | Indicates whether meta data for the response should be included. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| CAPTURE | The data capture organisation units associated with the current user and all children, i.e. all organisation units in the sub-hierarchy. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -Note that you can specify "attribute" with filters or directly using the "filter" params for constraining the -instances to return. - -Certain rules apply to which attributes are returned. - - - If "query" is specified without any attributes or program, then all attributes that - are marked as "Display in List without Program" is included in the response. - - - If program is specified, all the attributes linked to the program will - be included in the response. - - - If tracked entity type is specified, then all tracked entity type attributes - will be included in the response. - -You can specify queries with words separated by space - in that -situation the system will query for each word independently and return -records where each word is contained in any attribute. A query item can -be specified once as an attribute and once as a filter if needed. The -query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - If *eventStatus* is specified then *eventStartDate* and - *eventEndDate* must also be specified. - - - A query cannot be specified together with filters. - - - Attribute items can only be specified once. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -A query on all attributes for a specific value and organisation unit, -using an exact word match: - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -A query on all attributes for a specific value, using a partial word -match: - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -You can query on multiple words separated by the URL character for -space which is %20, will use a logical AND query for each - word: - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -A query where the attributes to include in the response are specified: - - /api/33/trackedEntityInstances/query.json?query=isabel - &attribute=dv3nChNSIxy&attribute=AMpUYgxuCaE&ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendants organisation unit query mode: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &attribute=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a - filter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an IN - filter: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - &attribute=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&program=ur1Edk5Oe2n&programStartDate=2013-01-01 - &programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -To query for instances which have events of a given status within a -given time span: - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Description | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_grid_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - - - csv (application/csv) - - - xls (application/vnd.ms-excel) - -The response in JSON comes is in a tabular format and can look like the -following. The *headers* section describes the content of each column. -The instance, created, last updated, org unit and tracked entity columns -are always present. The following columns correspond to attributes -specified in the query. The *rows* section contains one row per -instance. - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### Tracked entity instance filters { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - /api/33/trackedEntityInstanceFilters - -##### Create and update a tracked entity instance filter definition { #create-and-update-a-tracked-entity-instance-filter-definition } - -For creating and updating a tracked entity instance filter in the -system, you will be working with the *trackedEntityInstanceFilters* -resource. The tracked entity instance filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the filter. Required. || -| description | A description of the filter. || -| sortOrder | The sort order of the filter. Used in Tracker Capture to order the filters in the program dashboard. || -| style | Object containing css style. | ( "color": "blue", "icon": "fa fa-calendar"} | -| program | Object containing the id of the program. Required. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Table: Entity Query Criteria definition - -|||| -|---|---|---| -| attributeValueFilters | A list of attributeValueFilters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| enrollmentStatus | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | When this parameter is true, the filter only returns TEIs that have an enrollment with status followup. || -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayColumnOrder | To specify the output ordering of columns | "displayOrderColumns": ["enrollmentDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus | Any valid EventStatus | "eventStatus": "COMPLETED" | -| programStage | To specify a programStage uid to filter on. TEIs will be filtered based on presence of enrollment in the specified program stage.| "programStage"="a3kGcGDCuk6" | -| trackedEntityType | To specify a trackedEntityType filter TEIs on. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | To specify a list of trackedEntityInstances to use when querying TEIs. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod object date filtering based on enrollment incident date. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod object date filtering based on enrollment created date. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Table: Event filters definition - -|||| -|---|---|---| -| programStage | Which programStage the TEI needs an event in to be returned. | "eaDH9089uMp" | -| eventStatus | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT (events assigned to current user)| PROVIDED (events assigned to users provided in "assignedUsers" list) | NONE (events assigned to no one) | ANY (events assigned to anyone). If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -Table: Period definition - -|||| -|---|---|---| -| periodFrom | Number of days from current day. Can be positive or negative integer. | -15 | -| periodTo | Number of days from current day. Must be bigger than periodFrom. Can be positive or negative integer. | 15 | - -##### Tracked entity instance filters query { #tracked-entity-instance-filters-query } - -To query for tracked entity instance filters in the system, you can -interact with the */api/trackedEntityInstanceFilters* resource. - - - -Table: Tracked entity instance filters query parameters - -| Query parameter | Description | -|---|---| -| program | Program identifier. Restricts filters to the given program. | - -### Enrollment management { #webapi_enrollment_management } - -Enrollments have full CRUD support in the API. Together with the API -for tracked entity instances most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/enrollments - -#### Enrolling a tracked entity instance into a program { #webapi_enrolling_tei } - -For enrolling persons into a program, you will need to first get the -identifier of the person from the *trackedEntityInstances* resource. -Then, you will need to get the program identifier from the *programs* -resource. A template payload can be seen below: - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -This payload should be used in a *POST* request to the enrollments -resource identified by the following URL: - - /api/33/enrollments - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - /api/33/enrollments//cancelled - -For completing an enrollment for a tracked entity instance you can make a -*PUT* request to the following URL: - - /api/33/enrollments//completed - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - /api/33/enrollments/ - -#### Enrollment instance query { #webapi_enrollment_instance_query } - -To query for enrollments you can interact with the */api/enrollments* -resource. - - /api/33/enrollments - -##### Request syntax { #webapi_enrollment_query_request_syntax } - - - -Table: Enrollment query parameters - -| Query parameter | Description | -|---|---| -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| trackedEntityInstance | Tracked entity instance identifier. Should not be used together with trackedEntity. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| includeDeleted | Indicates whether to include soft deleted enrollments or not. It is false by default. | - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request (default). | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - -A query for all enrollments associated with a specific organisation unit -can look like this: - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -To constrain the response to enrollments which are part of a specific -program you can include a program query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the - query: - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - &programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to enrollments of a specific tracked entity -you can include a tracked entity query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -To constrain the response to enrollments of a specific tracked entity -instance you can include a tracked entity instance query parameter, in -this case we have restricted it to available enrollments viewable for -current - user: - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -By default the enrollments are returned in pages of size 50, to change -this you can use the page and pageSize query - parameters: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### Response format { #webapi_enrollment_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### Events { #webapi_events } - -This section is about sending and reading events. - - /api/33/events - -The different status of an event are: - -* **ACTIVE**: If a event has ACTIVE status, it is possible to edit the event details. COMPLETED events can be turned ACTIVE again and vice versa. -* **COMPLETED**: An event change the status to COMPLETED only when a user clicks the complete button. If a event has COMPLETED status, it is not possible to edit the event details. ACTIVE events can be turned COMPLETED again and vice versa. -* **SKIPPED**: Scheduled events that no longer need to happen. In Tracker Capture, there is a button for that. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### Sending events { #webapi_sending_events } - -DHIS2 supports three kinds of events: single events with no registration -(also referred to as anonymous events), single event with registration -and multiple events with registration. Registration implies that the -data is linked to a tracked entity instance which is identified using -some sort of identifier. - -To send events to DHIS2 you must interact with the *events* resource. -The approach to sending events is similar to sending aggregate data -values. You will need a *program* which can be looked up using the -*programs* resource, an *orgUnit* which can be looked up using the -*organisationUnits* resource, and a list of valid data element -identifiers which can be looked up using the *dataElements* resource. -For events with registration, a *tracked entity instance* identifier is -required, read about how to get this in the section about the -*trackedEntityInstances* resource. For sending events to programs with -multiple stages, you will need to also include the *programStage* -identifier, the identifiers for programStages can be found in the -*programStages* resource. - -A simple single event with no registration example payload in XML format -where we send events from the "Inpatient morbidity and mortality" -program for the "Ngelehun CHC" facility in the demo database can be seen -below: - -```xml - - - - - - - - - -``` - -To perform some testing we can save the XML payload as a file -called *event.xml* and send it as a POST request to the events resource -in the API using curl with the following command: - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -The same payload in JSON format looks like this: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -To send this you can save it to a file called *event.json* and use curl -like this: - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -We also support sending multiple events at the same time. A payload in -XML format might look like this: - -```xml - - - - - - - - - - - - - - - - - -``` - -You will receive an import summary with the response which can be -inspected in order to get information about the outcome of the request, -like how many values were imported successfully. The payload in JSON -format looks like this: - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -You can also use GeoJson to store any kind of geometry on your event. An example payload using GeoJson instead of the former latitude and longitude properties can be seen here: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -As part of the import summary you will also get the identifier -*reference* to the event you just sent, together with a *href* element -which points to the server location of this event. The table below -describes the meaning of each element. - - - -Table: Events resource format - -| Parameter | Type | Required | Options (default first) | Description | -|---|---|---|---|---| -| program | string | true || Identifier of the single event with no registration program | -| orgUnit | string | true || Identifier of the organisation unit where the event took place | -| eventDate | date | true || The date of when the event occurred | -| completedDate | date | false || The date of when the event is completed. If not provided, the current date is selected as the event completed date | -| status | enum | false | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Whether the event is complete or not | -| storedBy | string | false | Defaults to current user | Who stored this event (can be username, system-name, etc) | -| coordinate | double | false || Refers to where the event took place geographically (latitude and longitude) | -| dataElement | string | true || Identifier of data element | -| value | string | true || Data value or measure for this event | - -##### OrgUnit matching { #orgunit-matching } - -By default the orgUnit parameter will match on the -ID, you can also select the orgUnit id matching scheme by using the -parameter orgUnitIdScheme=SCHEME, where the options are: *ID*, *UID*, -*UUID*, *CODE*, and *NAME*. There is also the *ATTRIBUTE:* scheme, which -matches on a *unique* metadata attribute value. - -#### Updating events { #webapi_updating_events } - -To update an existing event, the format of the payload is the same, but -the URL you are posting to must add the identifier to the end of the URL -string and the request must be PUT. - -The payload has to contain all, even non-modified, attributes. -Attributes that were present before and are not present in the current -payload any more will be removed by the system. - -It is not allowed to update an already deleted event. The same applies -to tracked entity instance and enrollment. - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### Deleting events { #webapi_deleting_events } - -To delete an existing event, all you need is to send a DELETE request -with an identifier reference to the server you are using. - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### Assigning user to events { #webapi_user_assign_event } - -A user can be assigned to an event. This can be done by including the appropriate property in the payload when updating or creating the event. - - "assignedUser": "" - -The id refers to the if of the user. Only one user can be assigned to an event at a time. - -User assignment must be enabled in the program stage before users can be assigned to events. -#### Getting events { #webapi_getting_events } - -To get an existing event you can issue a GET request including the -identifier like this: - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### Querying and reading events { #webapi_querying_reading_events } - -This section explains how to read out the events that have been stored -in the DHIS2 instance. For more advanced uses of the event data, please -see the section on event analytics. The output format from the -`/api/events` endpoint will match the format that is used to send events -to it (which the analytics event api does not support). Both XML and -JSON are supported, either through adding .json/.xml or by setting the -appropriate *Accept* header. The query is paged by default and the -default page size is 50 events, *field* filtering works as it does for -metadata, add the *fields* parameter and include your wanted properties, -i.e. *?fields=program,status*. - - - -Table: Events resource query parameters - -| Key | Type | Required | Description | -|---|---|---|---| -| program | identifier | true (if not programStage is provided) | Identifier of program | -| programStage | identifier | false | Identifier of program stage | -| programStatus | enum | false | Status of event in program, ca be ACTIVE | COMPLETED | CANCELLED | -| followUp | boolean | false | Whether event is considered for follow up in program, can be true | false or omitted. | -| trackedEntityInstance | identifier | false | Identifier of tracked entity instance | -| orgUnit | identifier | true | Identifier of organisation unit | -| ouMode | enum | false | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| startDate | date | false | Only events newer than this date | -| endDate | date | false | Only events older than this date | -| status | enum | false | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | date | false | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | date | false | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | string | false | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta | boolean | false | Exclude the meta data part of response (improves performance) | -| page | integer | false | Page number | -| pageSize | integer | false | Number of items in each page | -| totalPages | boolean | false | Indicates whether to include the total number of pages in the paging response. | -| skipPaging | boolean | false | Indicates whether to skip paging in the query and return all events. | -| dataElementIdScheme | string | false | Data element ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme | string | false | Category Option Combo ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| orgUnitIdScheme | string | false | Organisation Unit ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programIdScheme | string | false | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programStageIdScheme | string | false | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| idScheme | string | false | Allows to set id scheme for data element, category option combo, orgUnit, program and program stage at once. | -| order | string | false | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| event | comma delimited string | false | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | boolean | false | Skips event identifiers in the response | -| attributeCc (\*\*) | string | false | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | string | false | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | false | true | false | Indicates whether the import should be done asynchronous or synchronous. | -| includeDeleted | boolean | false | When true, soft deleted events will be included in your query result. | -| assignedUserMode | enum | false | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | comma delimited strings | false | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> **Note** -> -> If the query contains neither `attributeCC` nor `attributeCos`, the server returns events for all attribute option combos where the user has read access. - -##### Examples { #examples } - -Query for all events with children of a certain organisation unit: - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -Query for all events with all descendants of a certain organisation -unit, implying all organisation units in the sub-hierarchy: - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -Query for all events with a certain program and organisation unit: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -Query for all events with a certain program and organisation unit, -sorting by due date - ascending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -Query for the 10 events with the newest event date in a certain program -and organisation unit - by paging and ordering by due date descending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &order=eventDate:desc&pageSize=10&page=1 - -Query for all events with a certain program and organisation unit for a -specific tracked entity instance: - - /api/33/events.json?orgUnit=DiszpKrYNg8 - &program=eBAyeGv0exc&trackedEntityInstance=gfVxE3ALA9m - -Query for all events with a certain program and organisation unit older -or equal to - 2014-02-03: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -Query for all events with a certain program stage, organisation unit and -tracked entity instance in the year 2014: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &trackedEntityInstance=gfVxE3ALA9m&startDate=2014-01-01&endDate=2014-12-31 - -Query files associated with event data values. In the specific case of fetching an image file an -additional parameter can be provided to fetch the image with different dimensions. If dimension is -not provided, the system will return the original image. The parameter will be ignored in case of -fetching non-image files e.g pdf. Possible dimension values are *small(254 x 254), -medium(512 x 512), large(1024 x 1024) or original*. Any value other than those mentioned will be -discarded and the original image will be returned. - - /api/33/events/files?eventUid=hcmcWlYkg9u&dataElementUid=C0W4aFuVm4P&dimension=small - -Retrieve events with specified Organisation unit and Program, and use _Attribute:Gq0oWTf2DtN_ as -identifier scheme - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for -orgUnits, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as identifier -scheme for the rest of the metadata with assigned attribute. - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=Code - -#### Event grid query { #event-grid-query } - -In addition to the above event query end point, there is an event grid -query end point where a more compact "grid" format of events are -returned. This is possible by interacting with -/api/events/query.json|xml|xls|csv endpoint. - - /api/33/events/query - -Most of the query parameters mentioned in event querying and reading -section above are valid here. However, since the grid to be returned -comes with specific set of columns that apply to all rows (events), it -is mandatory to specify a program stage. It is not possible to mix -events from different programs or program stages in the return. - -Returning events from a single program stage, also opens up for new -functionality - for example sorting and searching events based on their -data element values. api/events/query has support for this. Below are -some examples - -A query to return an event grid containing only selected data elements -for a program stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &dataElement=qrur9Dvnyt5,fWIAEtYVEGk,K6uUAvq500H&order=lastUpdated:desc - &pageSize=50&page=1&totalPages=true - -A query to return an event grid containing all data elements of a -program - stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &includeAllDataElements=true - -A query to filter events based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50 - -In addition to the filtering, the above example also illustrates one -thing: the fact that there are no data elements mentioned to be returned -in the grid. When this happens, the system defaults back to return only -those data elements marked "Display in report" under program stage -configuration. - -We can also extend the above query to return us a grid sorted (asc|desc) -based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50&order=qrur9Dvnyt5:desc - -#### Event filters { #webapi_event_filters } - -To create, read, update and delete event filters you -can interact with the `/api/eventFilters` resource. - - /api/33/eventFilters - -##### Create and update an event filter definition { #create-and-update-an-event-filter-definition } - -For creating and updating an event filter in the -system, you will be working with the *eventFilters* -resource. *POST* is used to create and *PUT* method is used to update. The event filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Request Payload - -| Request Property | Description | Example | -|---|---|---| -| name | Name of the filter. | "name":"My working list" | -| description | A description of the filter. | "description":"for listing all events assigned to me". | -| program | The uid of the program. | "program" : "a3kGcGDCuk6" | -| programStage | The uid of the program stage. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Object containing parameters for querying, sorting and filtering events. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Table: Event Query Criteria definition - -|||| -|---|---|---| -| followUp | Used to filter events based on enrollment followUp flag. Possible values are true|false. | "followUp": true | -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | To specify the output ordering of columns | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| dataFilters | To specify filters to be applied when listing events | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| status | Any valid EventStatus | "eventStatus": "COMPLETED" | -| events | To specify list of events | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod object date filtering based on completed date. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod object date filtering based on due date. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -The available assigned user selection modes are explained in the -following table. - - - -Table: Assigned user selection modes (event assignment) - -| Mode | Description | -|---|---| -| CURRENT | Assigned to the current logged in user | -| PROVIDED | Assigned to the users provided in the "assignedUser" parameter | -| NONE | Assigned to no users. | -| ANY | Assigned to any users. | - -A sample payload that can be used to create/update an eventFilter is shown below. - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### Retrieving and deleting event filters { #retrieving-and-deleting-event-filters } - -A specific event filter can be retrieved by using the following api - - GET /api/33/eventFilters/{uid} - -All event filters can be retrieved by using the following api. - - GET /api/33/eventFilters?fields=* - -All event filters for a specific program can be retrieved by using the following api - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -An event filter can be deleted by using the following api - - DELETE /api/33/eventFilters/{uid} - -### Relationships { #relationships } -Relationships are links between two entities in tracker. These entities can be tracked entity instances, enrollments and events. - -There are multiple endpoints that allow you to see, create, delete and update relationships. The most common is the /api/trackedEntityInstances endpoint, where you can include relationships in the payload to create, update or deleting them if you omit them - Similar to how you work with enrollments and events in the same endpoint. All the tracker endpoints, /api/trackedEntityInstances, /api/enrollments and /api/events also list their relationships if requested in the field filter. - -The standard endpoint for relationships is, however, /api/relationships. This endpoint provides all the normal CRUD operations for relationships. - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -This request will return a list of any relationship you have access to see that includes the trackedEntityInstance, enrollment or event you specified. Each relationship is represented with the following JSON: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -You can also view specified relationships using the following endpoint: - - GET /api/relationships/ - -To create or update a relationship, you can use the following endpoints: - - POST /api/relationships - PUT /api/relationships - -And use the following payload structure: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -To delete a relationship, you can use this endpoint: - - DELETE /api/relationships/ - -In our example payloads, we use a relationship between trackedEntityInstances. Because of this, the "from" and "to" properties of our payloads include "trackedEntityInstance" objects. If your relationship includes other entities, you can use the following properties: - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### Update strategies { #webapi_tei_update_strategies } - -Two update strategies for all 3 tracker endpoints are supported: -enrollment and event creation. This is useful when you have generated an -identifier on the client side and are not sure if it was created or not -on the server. - - - -Table: Available tracker strategies - -| Parameter | Description | -|---|---| -| CREATE | Create only, this is the default behavior. | -| CREATE_AND_UPDATE | Try and match the ID, if it exist then update, if not create. | - -To change the parameter, please use the strategy parameter: - - POST /api/33/trackedEntityInstances?strategy=CREATE_AND_UPDATE - -### Tracker bulk deletion { #webapi_tracker_bulk_deletion } - -Bulk deletion of tracker objects work in a similar fashion to adding and -updating tracker objects, the only difference is that the -`importStrategy` is *DELETE*. - -*Example: Bulk deletion of tracked entity instances:* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*Example: Bulk deletion of enrollments:* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*Example: Bulk deletion of events:* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### Identifier reuse and item deletion via POST and PUT methods { #webapi_updating_and_deleting_items } - -Tracker endpoints */trackedEntityInstances*, */enrollments*, */events* -support CRUD operations. The system keeps track of used identifiers. -Therefore, an item which has been created and then deleted (e.g. events, -enrollments) cannot be created or updated again. If attempting to delete -an already deleted item, the system returns a success response as -deletion of an already deleted item implies no change. - -The system does not allow to delete an item via an update (*PUT*) or -create (*POST*) method. Therefore, an attribute *deleted* is ignored in -both *PUT* and *POST* methods, and in *POST* method it is by default set -to *false*. - -### Import parameters { #webapi_import_parameters } - -The import process can be customized using a set of import parameters: - - - -Table: Import parameters - -| Parameter | Values (default first) | Description | -|---|---|---| -| dataElementIdScheme | id | name | code | attribute:ID | Property of the data element object to use to map the data values. | -| orgUnitIdScheme | id | name | code | attribute:ID | Property of the org unit object to use to map the data values. | -| idScheme | id | name | code| attribute:ID | Property of all objects including data elements, org units and category option combos, to use to map the data values. | -| dryRun | false | true | Whether to save changes on the server or just return the import summary. | -| strategy | CREATE | UPDATE | CREATE_AND_UPDATE | DELETE | Save objects of all, new or update import status on the server. | -| skipNotifications | true | false | Indicates whether to send notifications for completed events. | -| skipFirst | true | false | Relevant for CSV import only. Indicates whether CSV file contains a header row which should be skipped. | -| importReportMode | FULL, ERRORS, DEBUG | Sets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes *ObjectReports* for object which has errors. `FULL` returns an *ObjectReport* for all objects imported, and `DEBUG` returns the same plus a name for the object (if available). | - -#### CSV Import / Export { #webapi_events_csv_import_export } - -In addition to XML and JSON for event import/export, in DHIS2.17 we -introduced support for the CSV format. Support for this format builds on -what was described in the last section, so here we will only write about -what the CSV specific parts are. - -To use the CSV format you must either use the `/api/events.csv` -endpoint, or add *content-type: text/csv* for import, and *accept: -text/csv* for export when using the `/api/events` endpoint. - -The order of column in the CSV which are used for both export and import -is as follows: - - - -Table: CSV column - -| Index | Key | Type | Description | -|---|---|---|---| -| 1 | event | identifier | Identifier of event | -| 2 | status | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | program | identifier | Identifier of program | -| 4 | programStage | identifier | Identifier of program stage | -| 5 | enrollment | identifier | Identifier of enrollment (program instance) | -| 6 | orgUnit | identifier | Identifier of organisation unit | -| 7 | eventDate | date | Event date | -| 8 | dueDate | date | Due Date | -| 9 | latitude | double | Latitude where event happened | -| 10 | longitude | double | Longitude where event happened | -| 11 | dataElement | identifier | Identifier of data element | -| 12 | value | string | Value / measure of event | -| 13 | storedBy | string | Event was stored by (defaults to current user) | -| 14 | providedElsewhere | boolean | Was this value collected somewhere else | -| 14 | completedDate | date | Completed date of event | -| 14 | completedBy | string | Username of user who completed event | - -*Example of 2 events with 2 different data value - each:* - -```csv -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,1,, -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,2,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,3,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,4,, -``` - -#### Import strategy: SYNC { #webapi_sync_import_strategy } - -The import strategy SYNC should be used only by internal synchronization -task and not for regular import. The SYNC strategy allows all 3 -operations: CREATE, UPDATE, DELETE to be present in the payload at the -same time. - -### Tracker Ownership Management { #webapi_tracker_ownership_management } - -A new concept called Tracker Ownership is introduced from 2.30. There -will now be one owner organisation unit for a tracked entity instance in -the context of a program. Programs that are configured with an access -level of *PROTECTED* or *CLOSED* will adhere to the ownership -privileges. Only those users belonging to the owning org unit for a -tracked entity-program combination will be able to access the data -related to that program for that tracked entity. - -#### Tracker Ownership Override : Break the Glass { #webapi_tracker_ownership_override_api } - -It is possible to temporarily override this ownership privilege for a -program that is configured with an access level of *PROTECTED*. Any user -will be able to temporarily gain access to the program related data, if -the user specifies a reason for accessing the tracked entity-program -data. This act of temporarily gaining access is termed as *breaking the -glass*. Currently, the temporary access is granted for 3 hours. DHIS2 -audits breaking the glass along with the reason specified by the user. -It is not possible to gain temporary access to a program that has been -configured with an access level of *CLOSED*. To break the glass for a -tracked entity program combination, you can issue a POST request as -shown: - - /api/33/tracker/ownership/override?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care - -#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer_api } - -It is possible to transfer the ownership of a tracked entity-program -from one org unit to another. This will be useful in case of patient -referrals or migrations. Only an owner (or users who have broken the -glass) can transfer the ownership. To transfer ownership of a tracked -entity-program to another organisation unit, you can issue a PUT request -as shown: - - /api/33/tracker/ownership/transfer?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&ou=EJNxP3WreNP - - -## Potential Duplicates { #potential-duplicates } - -Potential duplicates are records we work with in the data deduplication feature. Due to the nature of the deduplication feature, this API endpoint is somewhat restricted. - -A potential duplicate represents a pair of records which are suspected to be a duplicate. - -The payload of a potential duplicate looks like this: - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -You can retrieve a list of potential duplicates using the following endpoint: - - GET /api/potentialDuplicates - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| teis | List of tracked entity instances | List of string (separated by comma)| existing tracked entity instance id | -| status | Potential duplicate status | string | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Status code | Description -|---|---| -| 400 | Invalid input status - -You can inspect individual potential duplicate records: - - GET /api/potentialDuplicates/ - -| Status code | Description -|---|---| -| 404 | Potential duplicate not found - -To create a new potential duplicate, you can use this endpoint: - - POST /api/potentialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Status code | Description -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -To update a potential duplicate status: - - PUT /api/potentialDuplicates/ - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| status | Potential duplicate status | string | `OPEN`, `INVALID`, `MERGED` | - -| Status code | Description -|---|---| -| 400 | You can't update a potential duplicate to MERGED as this is possible only by a merging request -| 400 | You can't update a potential duplicate that is already in a MERGED status - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -To merge a Potential Duplicate, or the two tracked entity instances the Potential Duplicate represents, the following endpoint can be used: - - POST /api/potentialDuplicates//merge - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| mergeStrategy | Strategy to use for merging the potentialDuplicate | enum | AUTO(default) or MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- The same attribute has different values in each tracked entity instance -- Both tracked entity instances are enrolled in the same program -- Tracked entity instances have different types - -If any conflict is encountered, an errormessage is returned to the user. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -When requesting an automatic merge like this, a payload is not required and will be ignored. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Relationship cannot be between the original and the duplicate (This results in an invalid self-referencing relationship) -- Relationship cannot be of the same type and to the same object in both tracked entity instances (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) - -There are two ways to do a manual merge: With and without a payload. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -Otherwise, if a manual merge is requested with a payload, the payload refers to what data should be moved from the duplicate to the original. The payload looks like this: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -The fields are explained in the following table. - - -Table: Program Notification Template payload - -| Field | Required | Description | Values | -|---|---|---|---| -| name | Yes | name of Program Notification Template | case-notification-alert | -| notificationTrigger | Yes | When notification should be triggered. Possible values are ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| ENROLLMENT | -| subjectTemplate | No | Subject template string | Case notification V{org_unit_name} | -| messageTemplate | Yes | Message template string | Case notification A{h5FuguPFF2j} | -| notificationRecipient | YES | Who is going to receive notification. Possible values are USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | No | Which channel should be used for this notification. It can be either SMS, EMAIL or HTTP | SMS | -| sendRepeatable | No | Whether notification should be sent multiple times | false | - -NOTE: WEB_HOOK notificationRecipient is used only to POST http request to an external system. Make sure to choose HTTP delivery channel when using WEB_HOOK. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -The list of Program Notification Templates can be retrieved using GET. - - GET /api/programNotificationTemplates - -For one particular Program Notification Template. - - GET /api/33/programNotificationTemplates/{uid} - -To get filtered list of Program Notification Templates - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Program Notification Template can be deleted using DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -Program message lets you send messages to tracked entity instances, -contact addresses associated with organisation units, phone numbers and -email addresses. You can send messages through the `messages` resource. - - /api/33/messages - -### Sending program messages { #sending-program-messages } - -Program messages can be sent using two delivery channels: - - - SMS (SMS) - - - Email address (EMAIL) - -Program messages can be sent to various recipients: - - - Tracked entity instance: The system will look up attributes of value - type PHONE_NUMBER or EMAIL (depending on the specified delivery - channels) and use the corresponding attribute values. - - - Organisation unit: The system will use the phone number or email - information registered for the organisation unit. - - - List of phone numbers: The system will use the explicitly defined - phone numbers. - - - List of email addresses: The system will use the explicitly defined - email addresses. - -Below is a sample JSON payload for sending messages using POST requests. -Note that message resource accepts a wrapper object named -`programMessages` which can contain any number of program messages. - - POST /api/33/messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -The fields are explained in the following table. - - - -Table: Program message payload - -| Field | Required | Description | Values | -|---|---|---|---| -| recipients | Yes | Recipients of the program message. At least one recipient must be specified. Any number of recipients / types can be specified for a message. | Can be trackedEntityInstance, organisationUnit, an array of phoneNumbers or an array of emailAddresses. | -| programInstance | Either this or programStageInstance required | The program instance / enrollment. | Enrollment ID. | -| programStageInstance | Either this or programInstance required | The program stage instance / event. | Event ID. | -| deliveryChannels | Yes | Array of delivery channels. | SMS | EMAIL | -| subject | No | The message subject. Not applicable for SMS delivery channel. | Text. | -| text | Yes | The message text. | Text. | -| storeCopy | No | Whether to store a copy of the program message in DHIS2. | false (default) | true | - -A minimalistic example for sending a message over SMS to a tracked -entity instance looks like this: - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### Retrieving and deleting program messages { #retrieving-and-deleting-program-messages } - -The list of messages can be retrieved using GET. - - GET /api/33/messages - -To get the list of sent tracker messages, the below endpoint can be used. ProgramInstance or ProgramStageInstance uid has to be provided. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -To get the list of all scheduled message - - GET /api/33/messages/scheduled - GET /api/33/messages/scheduled?scheduledAt=2020-12-12 - -One particular message can also be retrieved using GET. - - GET /api/33/messages/{uid} - -Message can be deleted using DELETE. - - DELETE /api/33/messages/{uid} - - -### Querying program messages { #querying-program-messages } - -The program message API supports program message queries based on -request parameters. Messages can be filtered based on below mentioned -query parameters. All requests should use the GET HTTP verb for -retrieving information. - - - -Table: Query program messages API - -| Parameter | URL | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # Email { #email } diff --git a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index 473e2b48a..cd0f951fd 100644 --- a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- mengatur - DHIS core version 2.37 +- mengatur template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md index 0999a92f3..d69c687cb 100644 --- a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- mengatur - DHIS core version 2.39 +- mengatur template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index 2e63b66d6..082e7d836 100644 --- a/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/id_ID/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- mengatur - DHIS core version master +- mengatur template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index 95dac2535..cf6ba05e1 100644 --- a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/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 - gunakan/pakai/masukkan +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index 23092640f..52b896e37 100644 --- a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/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 - gunakan/pakai/masukkan +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 8eda02835..d28bb1c3b 100644 --- a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - gunakan/pakai/masukkan +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 460216fd3..f8ba1df0b 100644 --- a/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/id_ID/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - gunakan/pakai/masukkan +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ko/.cache_timestamp b/projects/dhis2-single-page-docs/ko/.cache_timestamp index e6639a6fd..f1afa4d1c 100644 --- a/projects/dhis2-single-page-docs/ko/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ko/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:27:46Z \ No newline at end of file +2024-06-04T21:27:45Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp b/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp index e6639a6fd..f1afa4d1c 100644 --- a/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:27:46Z \ No newline at end of file +2024-06-04T21:27:45Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index c3c6a6f70..fb3995672 100644 --- a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/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 --- diff --git a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index b594ca4ef..a5c70b112 100644 --- a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/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 --- diff --git a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 7a0e035de..f7931272f 100644 --- a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - 사용 +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 44fdc7b2d..dbe935a13 100644 --- a/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ko_KR/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - 사용 +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/.cache_timestamp b/projects/dhis2-single-page-docs/pt/.cache_timestamp index eaf182b25..3cf2dba52 100644 --- a/projects/dhis2-single-page-docs/pt/.cache_timestamp +++ b/projects/dhis2-single-page-docs/pt/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:27:55Z \ No newline at end of file +2024-06-04T21:27:51Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index a0331142f..69396b969 100644 --- a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/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 --- diff --git a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index 860967b8b..f56ef6b03 100644 --- a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- DHIS core version 2.38 - Desenvolver +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index 19fd9a399..ad7ee2397 100644 --- a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - Desenvolver +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 922c33841..f854e3898 100644 --- a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Desenvolver +- DHIS core version 2.40 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 8b7c9cb8e..3318a798a 100644 --- a/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/pt/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - Desenvolver - DHIS core version master @@ -12220,7 +12220,7 @@ Table: Query parameters for event query analytics only | Query parameter | Requerido | Descrição | Options | |---|---|---|---| -| ouMode | Não | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | Não | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Não | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Não | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | Não | Whether to only return events which have coordinates. | false | true | @@ -13122,7 +13122,7 @@ Table: Query parameters for enrollment query endpoint | filter | Não | Dimension identifier including data elements, attributes, periods, organisation units and organisation unit group sets. Parameter can be repeated any number of times. Item filters can be applied to a dimension on the format ::. Filter values are case-insensitive. || | programStatus | Não | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | Não | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | Não | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | Não | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Não | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Não | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | Não | Whether to only return enrollments which have coordinates. | false | true | @@ -17831,20 +17831,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17947,7 +17948,6 @@ point out any exceptional cases between these two. | “Registro de Casos de Malária” | Only for reading data. The type of program the enrollment which owns the event has. | Não | sim | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | Não | Não | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | Não | Não | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | Não | Não | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | sim | Não | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | Não | sim | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | Não | Não | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -18007,9 +18007,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Atributos { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | Descrição | Requerido | Immutable | Modelo | Exemplo | |---|---|---|---|---|---| @@ -18024,18 +18026,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | Descrição | Requerido | Immutable | Modelo | Exemplo | |---|---|---|---|---|---| @@ -18050,31 +18054,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Notas { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -18085,10 +18089,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -18130,92 +18134,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | Descrição | Exemplo | -|---|---|---| -| nome | Name of the working list. Required. || -| descrição | A description of the working list. || -| “Registro de Casos de Malária” | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Descrição | Exemplo | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -18224,9 +18143,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -18259,7 +18178,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -18659,7 +18578,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -19105,7 +19024,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -19235,7 +19154,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | N/D | Undefined error message. | -### Validação { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -19245,7 +19164,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -19270,8 +19189,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -19324,7 +19243,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -19380,7 +19299,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -19402,7 +19321,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -19436,7 +19355,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -19488,9 +19407,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -19570,8 +19489,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -19676,7 +19595,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19938,8 +19857,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -20143,8 +20062,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -20439,13 +20358,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -20491,7 +20410,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -20560,13 +20479,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -20578,7 +20497,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Substituição de propriedade do rastreador: Quebre o vidro { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -20591,7 +20510,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -20601,7 +20520,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -20631,7 +20550,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -20647,2766 +20566,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Table: Payload -|Tracker Object|Previously|Now| +| Payload values | Descrição | Exemplo | |---|---|---| -|**Attribute**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Event**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Note**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Relationship**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribute`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes`|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus`|`enrollmentStatus`| -|`query`|Removed - use `filter` instead| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Previously|Now| -|---|---| -|`enrollment`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus`|`status`| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`event`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`lastUpdated`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus`|`enrollmentStatus`| -|`skipEventId`|Removed| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Previously|Now| -|---|---| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity`| - -## API Tracker Web { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### Gerenciamento de instância de entidade rastreada { #webapi_tracked_entity_instance_management } - -Tracked entity instances have full CRUD support in the API. Together -with the API for enrollment most operations needed for working with -tracked entity instances and programs are supported. - - / api / 33 / trackedEntityInstances - -#### Criar uma nova instância de entidade rastreada { #webapi_creating_tei } - -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -The field "geometry" accepts a GeoJson object, where the type of the -GeoJson have to match the featureType of the TrackedEntityType -definition. An example GeoJson object looks like this: - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +| nome | Name of the working list. Required. || +| descrição | A description of the working list. || +| “Registro de Casos de Malária” | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Table: Program Stage Query Criteria - / api / trackedEntityInstances +| Criteria values | Descrição | Exemplo | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +See an example payload below: ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -Para enviar isso para o servidor, você pode usar o comando cURL desta forma: - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -To create multiple instances in one request you can wrap the payload in -an outer array like this and POST to the same resource as above:[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -The system does not allow the creation of a tracked entity instance -(as well as enrollment and event) with a UID that was already used in -the system. That means that UIDs cannot be reused. - -#### Atualizar uma instância de entidade rastreada { #webapi_updating_tei } - -For updating a tracked entity instance, the payload is equal to the -previous section. The difference is that you must use the HTTP *PUT* -method for the request when sending the payload. You will also need to -append the person identifier to the *trackedEntityInstances* resource in -the URL like this, where `` should -be replaced by the identifier of the tracked entity instance: - - / api / trackedEntityInstances / - -The payload has to contain all, even non-modified, attributes and -relationships. Attributes or relationships that were present before and -are not present in the current payload any more will be removed from the -system. This means that if attributes/relationships are empty in the -current payload, all existing attributes/relationships will be deleted -from the system. From 2.31, it is possible to ignore empty -attributes/relationships in the current payload. A request parameter of -`ignoreEmptyCollection` set to `true` can be used in case you do not -wish to send in any attributes/relationships and also do not want them -to be deleted from the system. - -It is not allowed to update an already deleted tracked entity instance. -Also, it is not allowed to mark a tracked entity instance as deleted via -an update request. The same rules apply to enrollments and events. - -#### Excluir uma instância de entidade rastreada { #webapi_deleting_tei } - -In order to delete a tracked entity instance, make a request to the URL -identifying the tracked entity instance with the *DELETE* -method. The URL is equal to the one above used for update. - -#### Criar e inscrever instâncias de entidades rastreadas { #webapi_create_enroll_tei } - -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Exemplo completo de carga útil, incluindo: instância de entidade rastreada, inscrição e evento { #webapi_create_enroll_tei_create_event } - -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "cejWyOfXge6", - "value": "Male" - } - ], - "enrollments": [ - { - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollmentDate": "2017-09-15", - "incidentDate": "2017-09-15", - "events": [ - { - "program": "ur1Edk5Oe2n", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2017-10-17", - "status": "COMPLETED", - "storedBy": "admin", - "programStage": "EPEcjy3FWmI", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "ur1Edk5Oe2n", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2017-10-17", - "status": "COMPLETED", - "storedBy": "admin", - "programStage": "EPEcjy3FWmI", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } - ] - } - ] + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ + { + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Atributos de instância de entidade rastreada gerados { #webapi_generate_tei_attributes } - -Tracked entity instance attributes that are using automatic generation of -unique values have three endpoints that are used by apps. The endpoints -are all used for generating and reserving values. - -In 2.29 we introduced TextPattern for defining and generating these -patterns. All existing patterns will be converted to a valid TextPattern -when upgrading to 2.29. - -> **Note** -> -> As of 2.29, all these endpoints will require you to include any -> variables reported by the `requiredValues` endpoint listed as -> required. Existing patterns, consisting of only `#`, will be upgraded -> to the new TextPattern syntax `RANDOM()`. The RANDOM -> segment of the TextPattern is not a required variable, so this -> endpoint will work as before for patterns defined before 2.29. - -##### Encontrando os valores necessários { #finding-required-values } - -A TextPattern can contain variables that change based on different -factors. Some of these factors will be unknown to the server, so the -values for these variables have to be supplied when generating and -reserving values. - -This endpoint will return a map of required and optional values, that -the server will inject into the TextPattern when generating new values. -Required variables have to be supplied for the generation, but optional -variables should only be supplied if you know what you are doing. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### Gerar valor-limite { #webapi_generate_values } - -Online web apps and other clients that want to generate a value that -will be used right away can use the simple generate endpoint. This -endpoint will generate a value that is guaranteed to be unique at the -time of generation. The value is also guaranteed not to be reserved. As -of 2.29, this endpoint will also reserve the value generated for 3 days. - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### Gerar e reservar valor final { #webapi_generate_reserve_values } - -The generate and reserve endpoint is used by offline clients that need -to be able to register tracked entities with unique ids. They will -reserve a number of unique ids that this device will then use when -registering new tracked entity instances. The endpoint is called to -retrieve a number of tracked entity instance reserved values. An -optional parameter numberToReserve specifies how many ids to generate -(default is 1). - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -Similar to the /generate endpoint, this endpoint can also specify the -expiration time in the same way. By adding the `?expiration=` -you can override the default 60 days. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### Valores reservados { #reserved-values } - -Reserved values are currently not accessible through the api, however, they -are returned by the `generate` and `generateAndReserve` endpoints. The -following table explains the properties of the reserved value object: - -##### - - - -Table: Reserved values - -| Property | Descrição | -|---|---| -| ownerObject | The metadata type referenced when generating and reserving the value. Currently only TRACKEDENTITYATTRIBUTE is supported. | -| ownerUid | The uid of the metadata object referenced when generating and reserving the value. | -| key | A partially generated value where generated segments are not yet added. | -| value | The fully resolved value reserved. This is the value you send to the server when storing data. | -| created | The timestamp when the reservation was made | -| expiryDate | The timestamp when the reservation will no longer be reserved | - -Expired reservations are removed daily. If a pattern changes, values -that were already reserved will be accepted when storing data, even if -they don't match the new pattern, as long as the reservation has not -expired. - -#### Atributos de imagem { #image-attributes } - -Working with image attributes is a lot like working with file data -values. The value of an attribute with the image value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///image` -endpoint will return the actual image. The optional height and width -parameters can be used to specify the dimensions of the image. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### Consulta de instância de entidade rastreada { #webapi_tracked_entity_instance_query } - -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. - - / api / 33 / trackedEntityInstances - -##### Sintaxe de solicitação { #webapi_tei_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Descrição | -|---|---| -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected selected organisation units only. See table below for explanations. | -| “Registro de Casos de Malária” | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Indicates whether to include soft deleted teis or not. It is false by default. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Descrição | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | The selected organisation units and the immediate children, i.e. the organisation units at the level below. | -| DESCENDANTS | The selected organisation units and all children, i.e. all organisation units in the sub-hierarchy. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| TODOS | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -The available assigned user modes are explained in the following table. - - - -Table: Assigned user modes - -| Mode | Descrição | -|---|---| -| CURRENT | Includes events assigned to the current logged in user. | -| PROVIDED | Includes events assigned to the user provided in the request. | -| NONE | Includes unassigned events only. | -| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - Os itens do filtro só podem ser especificados uma vez. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendant organisation unit query mode: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - & filter = AMpUYgxuCaE & ou = DiszpKrYNg8; yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a filter: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - & filter = AMpUYgxuCaE: LIKE: Road & ou = DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - api / 33 / trackedEntityInstances.json? ou = DiszpKrYNg8 & program = ur1Edk5Oe2n - & filter = lw1SqmMlnfh: GT: 150: LT: 190 - -To query on an attribute using multiple values in an *IN* filter: - - api / 33 / trackedEntityInstances.json? ou = DiszpKrYNg8 - & filter = dv3nChNSIxy: IN: Scott; Jimmy; Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - api / 33 / trackedEntityInstances.json? filter = zHXD5Ve1Efw: EQ: A & ou = O6uvpzGd5pu - & ouMode = DESCENDANTS & program = ur1Edk5Oe2n - -Para especificar as datas de inscrição no programa como parte da consulta: - - api / 33 / trackedEntityInstances.json? filter = zHXD5Ve1Efw: EQ: A & ou = O6uvpzGd5pu - & program = ur1Edk5Oe2n & programStartDate = 2013-01-01 & programEndDate = 2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - api / 33 / trackedEntityInstances.json? filter = zHXD5Ve1Efw: EQ: A & ou = O6uvpzGd5pu - & ouMode = DESCENDANTS & trackedEntity = cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - api / 33 / trackedEntityInstances.json? filter = zHXD5Ve1Efw: EQ: A & ou = O6uvpzGd5pu - & ouMode = DESCENDANTES & page = 2 & pageSize = 3 - -Você pode usar uma variedade de operadores para a filtragem: - - - -Table: Filter operators - -| Operator | Descrição | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Formato de resposta { #webapi_tei_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (aplicativo/json) - - - jsonp (aplicativo / javascript) - - - xml (aplicativo/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### Consulta de grade de instância de entidade rastreada { #webapi_tracked_entity_instance_grid_query } - -To query for tracked entity instances you can interact with the -*/api/trackedEntityInstances/grid* resource. There are two types of -queries: One where a *query* query parameter and optionally *attribute* -parameters are defined, and one where *attribute* and *filter* -parameters are defined. This endpoint uses a more compact "grid" format, -and is an alternative to the query in the previous section. - - / api / 33 / trackedEntityInstances / query - -##### Sintaxe de solicitação { #webapi_tei_grid_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Descrição | -|---|---| -| query | Query string. Attribute query parameter can be used to define which attributes to include in the response. If no attributes but a program is defined, the attributes from the program will be used. If no program is defined, all attributes will be used. There are two formats. The first is a plan query string. The second is on the format :. Operators can be EQ | LIKE. EQ implies exact matches on words, LIKE implies partial matches on words. The query will be split on space, where each word will form a logical AND query. | -| attribute | Attributes to be included in the response. Can also be used as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. Filters can be omitted in order to simply include the attribute in the response without any constraints. | -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| “Registro de Casos de Malária” | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| eventStatus | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Start date of event associated with the given program and event status. | -| eventEndDate | End date of event associated with the given program and event status. | -| programStage | The programStage for which the event related filters should be applied to. If not provided all stages will be considered. | -| skipMeta | Indicates whether meta data for the response should be included. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Descrição | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| CAPTURE | The data capture organisation units associated with the current user and all children, i.e. all organisation units in the sub-hierarchy. | -| TODOS | All organisation units in the system. Requires `ALL` authority. | - -Note that you can specify "attribute" with filters or directly using the "filter" params for constraining the -instances to return. - -Certas regras se aplicam a quais atributos são retornados. - - - If "query" is specified without any attributes or program, then all attributes that - are marked as "Display in List without Program" is included in the response. - - - If program is specified, all the attributes linked to the program will - be included in the response. - - - If tracked entity type is specified, then all tracked entity type attributes - will be included in the response. - -You can specify queries with words separated by space - in that -situation the system will query for each word independently and return -records where each word is contained in any attribute. A query item can -be specified once as an attribute and once as a filter if needed. The -query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - If *eventStatus* is specified then *eventStartDate* and - *eventEndDate* must also be specified. - - - Uma consulta não pode ser especificada junto com filtros. - - - Os itens de atributo só podem ser especificados uma vez. - - - Os itens do filtro só podem ser especificados uma vez. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -A query on all attributes for a specific value and organisation unit, -using an exact word match: - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -A query on all attributes for a specific value, using a partial word -match: - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -You can query on multiple words separated by the URL character for -space which is %20, will use a logical AND query for each - word: - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -Uma consulta em que os atributos a serem incluídos na resposta são especificados: - - /api/33/trackedEntityInstances/query.json?query=isabel - & attribute = dv3nChNSIxy & attribute = AMpUYgxuCaE & ou = DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendants organisation unit query mode: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - & attribute = AMpUYgxuCaE & ou = DiszpKrYNg8; yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a - filter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - & filter = AMpUYgxuCaE: LIKE: Road & ou = DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - & filter = lw1SqmMlnfh: GT: 150: LT: 190 - -To query on an attribute using multiple values in an IN - filter: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - & attribute = dv3nChNSIxy: IN: Scott; Jimmy; Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - & ou = O6uvpzGd5pu & ouMode = DESCENDANTES & program = ur1Edk5Oe2n - -Para especificar as datas de inscrição no programa como parte da consulta: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - & ou = O6uvpzGd5pu & program = ur1Edk5Oe2n & programStartDate = 2013-01-01 - & programEndDate = 2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - & ou = O6uvpzGd5pu & ouMode = DESCENDANTES & trackedEntity = cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - & ou = O6uvpzGd5pu & ouMode = DESCENDANTES & page = 2 & pageSize = 3 - -To query for instances which have events of a given status within a -given time span: - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -Você pode usar uma variedade de operadores para a filtragem: - - - -Table: Filter operators - -| Operator | Descrição | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Formato de resposta { #webapi_tei_grid_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (aplicativo/json) - - - jsonp (aplicativo / javascript) - - - xml (aplicativo/xml) - - - csv (aplicativo/csv) - - - xls (application / vnd.ms-excel) - -The response in JSON comes is in a tabular format and can look like the -following. The *headers* section describes the content of each column. -The instance, created, last updated, org unit and tracked entity columns -are always present. The following columns correspond to attributes -specified in the query. The *rows* section contains one row per -instance. - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### Filtros de instância de entidade rastreada { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - / api / 33 / trackedEntityInstanceFilters - -##### Criar e atualizar uma definição de filtro de instância de entidade rastreada { #create-and-update-a-tracked-entity-instance-filter-definition } - -For creating and updating a tracked entity instance filter in the -system, you will be working with the *trackedEntityInstanceFilters* -resource. The tracked entity instance filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Payload - -| Payload values | Descrição | Exemplo | -|---|---|---| -| nome | Name of the filter. Required. || -| descrição | A description of the filter. || -| sortOrder | The sort order of the filter. Used in Tracker Capture to order the filters in the program dashboard. || -| style | Object containing css style. | ( "color": "blue", "icon": "fa fa-calendar"} | -| “Registro de Casos de Malária” | Object containing the id of the program. Required. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Table: Entity Query Criteria definition - -|||| -|---|---|---| -| attributeValueFilters | A list of attributeValueFilters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| enrollmentStatus | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | When this parameter is true, the filter only returns TEIs that have an enrollment with status followup. || -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayColumnOrder | To specify the output ordering of columns | "displayOrderColumns": ["enrollmentDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus | Any valid EventStatus | "eventStatus": "COMPLETED" | -| programStage | To specify a programStage uid to filter on. TEIs will be filtered based on presence of enrollment in the specified program stage.| "programStage"="a3kGcGDCuk6" | -| trackedEntityType | To specify a trackedEntityType filter TEIs on. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | To specify a list of trackedEntityInstances to use when querying TEIs. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod object date filtering based on enrollment incident date. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod object date filtering based on enrollment created date. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Table: Event filters definition - -|||| -|---|---|---| -| programStage | Which programStage the TEI needs an event in to be returned. | "eaDH9089uMp" | -| eventStatus | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT (events assigned to current user)| PROVIDED (events assigned to users provided in "assignedUsers" list) | NONE (events assigned to no one) | ANY (events assigned to anyone). If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -Table: Period definition - -|||| -|---|---|---| -| periodFrom | Number of days from current day. Can be positive or negative integer. | -15 | -| periodTo | Number of days from current day. Must be bigger than periodFrom. Can be positive or negative integer. | 15 | - -##### Consulta de filtros de instância de entidade rastreada { #tracked-entity-instance-filters-query } - -To query for tracked entity instance filters in the system, you can -interact with the */api/trackedEntityInstanceFilters* resource. - - - -Table: Tracked entity instance filters query parameters - -| Query parameter | Descrição | -|---|---| -| “Registro de Casos de Malária” | Program identifier. Restricts filters to the given program. | - -### Gestão de matrículas { #webapi_enrollment_management } - -Enrollments have full CRUD support in the API. Together with the API -for tracked entity instances most operations needed for working with -tracked entity instances and programs are supported. - - / api / 33 / matrículas - -#### Inscrever uma instância de entidade rastreada em um programa { #webapi_enrolling_tei } - -For enrolling persons into a program, you will need to first get the -identifier of the person from the *trackedEntityInstances* resource. -Then, you will need to get the program identifier from the *programs* -resource. A template payload can be seen below: - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -This payload should be used in a *POST* request to the enrollments -resource identified by the following URL: - - / api / 33 / matrículas - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - / api / 33 / matrículas / / cancelado - -For completing an enrollment for a tracked entity instance you can make a -*PUT* request to the following URL: - - / api / 33 / matrículas / / concluído - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - / api / 33 / inscrições / - -#### Consulta de instância de inscrição { #webapi_enrollment_instance_query } - -To query for enrollments you can interact with the */api/enrollments* -resource. - - / api / 33 / matrículas - -##### Sintaxe de solicitação { #webapi_enrollment_query_request_syntax } - - - -Table: Enrollment query parameters - -| Query parameter | Descrição | -|---|---| -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| “Registro de Casos de Malária” | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| trackedEntityInstance | Tracked entity instance identifier. Should not be used together with trackedEntity. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| includeDeleted | Indicates whether to include soft deleted enrollments or not. It is false by default. | - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Descrição | -|---|---| -| SELECTED | Organisation units defined in the request (default). | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| TODOS | All organisation units in the system. Requires `ALL` authority. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - -A query for all enrollments associated with a specific organisation unit -can look like this: - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -To constrain the response to enrollments which are part of a specific -program you can include a program query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -Para especificar as datas de inscrição no programa como parte da consulta: - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - & programStartDate = 2013-01-01 & programEndDate = 2013-09-01 - -To constrain the response to enrollments of a specific tracked entity -you can include a tracked entity query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -To constrain the response to enrollments of a specific tracked entity -instance you can include a tracked entity instance query parameter, in -this case we have restricted it to available enrollments viewable for -current - user: - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -By default the enrollments are returned in pages of size 50, to change -this you can use the page and pageSize query - parameters: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### Formato de resposta { #webapi_enrollment_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (aplicativo/json) - - - jsonp (aplicativo / javascript) - - - xml (aplicativo/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### Eventos { #webapi_events } - -Esta seção é sobre como enviar e ler eventos. - - / api / 33 / events - -The different status of an event are: - -* **ACTIVE**: If a event has ACTIVE status, it is possible to edit the event details. COMPLETED events can be turned ACTIVE again and vice versa. -* **COMPLETED**: An event change the status to COMPLETED only when a user clicks the complete button. If a event has COMPLETED status, it is not possible to edit the event details. ACTIVE events can be turned COMPLETED again and vice versa. -* **SKIPPED**: Scheduled events that no longer need to happen. In Tracker Capture, there is a button for that. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### Enviando eventos { #webapi_sending_events } - -DHIS2 supports three kinds of events: single events with no registration -(also referred to as anonymous events), single event with registration -and multiple events with registration. Registration implies that the -data is linked to a tracked entity instance which is identified using -some sort of identifier. - -To send events to DHIS2 you must interact with the *events* resource. -The approach to sending events is similar to sending aggregate data -values. You will need a *program* which can be looked up using the -*programs* resource, an *orgUnit* which can be looked up using the -*organisationUnits* resource, and a list of valid data element -identifiers which can be looked up using the *dataElements* resource. -For events with registration, a *tracked entity instance* identifier is -required, read about how to get this in the section about the -*trackedEntityInstances* resource. For sending events to programs with -multiple stages, you will need to also include the *programStage* -identifier, the identifiers for programStages can be found in the -*programStages* resource. - -A simple single event with no registration example payload in XML format -where we send events from the "Inpatient morbidity and mortality" -program for the "Ngelehun CHC" facility in the demo database can be seen -below: - -`` `xml - - - - - - - - - -`` ` - -To perform some testing we can save the XML payload as a file -called *event.xml* and send it as a POST request to the events resource -in the API using curl with the following command: - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -A mesma carga no formato JSON se parece com isto: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -To send this you can save it to a file called *event.json* and use curl -like this: - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -We also support sending multiple events at the same time. A payload in -XML format might look like this: - -`` `xml - - - - - - - - - - - - - - - - - -`` ` - -You will receive an import summary with the response which can be -inspected in order to get information about the outcome of the request, -like how many values were imported successfully. The payload in JSON -format looks like this: - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -Você também pode usar GeoJson para armazenar qualquer tipo de geometria em seu evento. Um exemplo de carga útil usando GeoJson em vez das propriedades de latitude e longitude anteriores pode ser visto aqui: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -As part of the import summary you will also get the identifier -*reference* to the event you just sent, together with a *href* element -which points to the server location of this event. The table below -describes the meaning of each element. - - - -Table: Events resource format - -| Parameter | Modelo | Requerido | Options (default first) | Descrição | -|---|---|---|---|---| -| “Registro de Casos de Malária” | string | verdade || Identifier of the single event with no registration program | -| orgUnit | string | verdade || Identifier of the organisation unit where the event took place | -| eventDate | date | verdade || The date of when the event occurred | -| completedDate | date | falso || The date of when the event is completed. If not provided, the current date is selected as the event completed date | -| status | enum | falso | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Whether the event is complete or not | -| storedBy | string | falso | Defaults to current user | Who stored this event (can be username, system-name, etc) | -| coordinate | double | falso || Refers to where the event took place geographically (latitude and longitude) | -| dataElement | string | verdade || Identifier of data element | -| value | string | verdade || Data value or measure for this event | - -##### Correspondência de unidades orgânicas { #orgunit-matching } - -By default the orgUnit parameter will match on the -ID, you can also select the orgUnit id matching scheme by using the -parameter orgUnitIdScheme=SCHEME, where the options are: *ID*, *UID*, -*UUID*, *CODE*, and *NAME*. There is also the *ATTRIBUTE:* scheme, which -matches on a *unique* metadata attribute value. - -#### Atualizando eventos { #webapi_updating_events } - -To update an existing event, the format of the payload is the same, but -the URL you are posting to must add the identifier to the end of the URL -string and the request must be PUT. - -The payload has to contain all, even non-modified, attributes. -Attributes that were present before and are not present in the current -payload any more will be removed by the system. - -It is not allowed to update an already deleted event. The same applies -to tracked entity instance and enrollment. - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### Excluindo eventos { #webapi_deleting_events } - -To delete an existing event, all you need is to send a DELETE request -with an identifier reference to the server you are using. - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### Atribuição de usuário a eventos { #webapi_user_assign_event } - -Um usuário pode ser atribuído a um evento. Isso pode ser feito incluindo a propriedade apropriada na carga útil ao atualizar ou criar o evento. - - "assignUser ":" " - -O id se refere ao if do usuário. Apenas um usuário pode ser atribuído a um evento por vez. - -A atribuição de usuário deve ser habilitada no estágio do programa antes que os usuários possam ser atribuídos a eventos. -#### Obtendo eventos { #webapi_getting_events } - -To get an existing event you can issue a GET request including the -identifier like this: - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### Consultando e lendo eventos { #webapi_querying_reading_events } - -This section explains how to read out the events that have been stored -in the DHIS2 instance. For more advanced uses of the event data, please -see the section on event analytics. The output format from the -`/api/events` endpoint will match the format that is used to send events -to it (which the analytics event api does not support). Both XML and -JSON are supported, either through adding .json/.xml or by setting the -appropriate *Accept* header. The query is paged by default and the -default page size is 50 events, *field* filtering works as it does for -metadata, add the *fields* parameter and include your wanted properties, -i.e. *?fields=program,status*. - - - -Table: Events resource query parameters - -| Chave | Modelo | Requerido | Descrição | -|---|---|---|---| -| “Registro de Casos de Malária” | identifier | true (if not programStage is provided) | Identifier of program | -| programStage | identifier | falso | Identifier of program stage | -| programStatus | enum | falso | Status of event in program, ca be ACTIVE | COMPLETED | CANCELLED | -| followUp | boolean | falso | Whether event is considered for follow up in program, can be true | false or omitted. | -| trackedEntityInstance | identifier | falso | Identifier of tracked entity instance | -| orgUnit | identifier | verdade | Identifier of organisation unit | -| ouMode | enum | falso | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| startDate | date | falso | Only events newer than this date | -| endDate | date | falso | Only events older than this date | -| status | enum | falso | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | date | falso | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | date | falso | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | string | falso | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta | boolean | falso | Exclude the meta data part of response (improves performance) | -| page | inteiro | falso | Page number | -| pageSize | inteiro | falso | Number of items in each page | -| totalPages | boolean | falso | Indicates whether to include the total number of pages in the paging response. | -| skipPaging | boolean | falso | Indicates whether to skip paging in the query and return all events. | -| dataElementIdScheme | string | falso | Data element ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme | string | falso | Category Option Combo ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| orgUnitIdScheme | string | falso | Organisation Unit ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programIdScheme | string | falso | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programStageIdScheme | string | falso | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| idScheme | string | falso | Allows to set id scheme for data element, category option combo, orgUnit, program and program stage at once. | -| order | string | falso | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| event | comma delimited string | falso | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | boolean | falso | Skips event identifiers in the response | -| attributeCc (\*\*) | string | falso | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | string | falso | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | false | true | falso | Indicates whether the import should be done asynchronous or synchronous. | -| includeDeleted | boolean | falso | When true, soft deleted events will be included in your query result. | -| assignedUserMode | enum | falso | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | comma delimited strings | falso | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> ** Nota ** -> -> Se a consulta não contém `attributeCC` nem` attributeCos`, o servidor retorna eventos para todos os combos de opções de atributos onde o usuário tem acesso de leitura. - -##### Exemplos { #examples } - -Consulta para todos os eventos com filhos de uma determinada unidade organizacional: - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -Query for all events with all descendants of a certain organisation -unit, implying all organisation units in the sub-hierarchy: - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -Consulta para todos os eventos com um determinado programa e unidade organizacional: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -Query for all events with a certain program and organisation unit, -sorting by due date - ascending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -Query for the 10 events with the newest event date in a certain program -and organisation unit - by paging and ordering by due date descending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - & order = eventDate: desc & pageSize = 10 & page = 1 - -Query for all events with a certain program and organisation unit for a -specific tracked entity instance: - - /api/33/events.json?orgUnit=DiszpKrYNg8 - & program = eBAyeGv0exc & trackedEntityInstance = gfVxE3ALA9m - -Query for all events with a certain program and organisation unit older -or equal to - 2014-02-03: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -Query for all events with a certain program stage, organisation unit and -tracked entity instance in the year 2014: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - & trackedEntityInstance = gfVxE3ALA9m & startDate = 2014-01-01 & endDate = 2014-12-31 - -Query files associated with event data values. In the specific case of fetching an image file an -additional parameter can be provided to fetch the image with different dimensions. If dimension is -not provided, the system will return the original image. The parameter will be ignored in case of -fetching non-image files e.g pdf. Possible dimension values are *small(254 x 254), -medium(512 x 512), large(1024 x 1024) or original*. Any value other than those mentioned will be -discarded and the original image will be returned. - - / api / 33 / events / files? eventUid = hcmcWlYkg9u & dataElementUid = C0W4aFuVm4P & dimension = small - -Retrieve events with specified Organisation unit and Program, and use _Attribute:Gq0oWTf2DtN_ as -identifier scheme - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for -orgUnits, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as identifier -scheme for the rest of the metadata with assigned attribute. - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=Code - -#### Consulta de grade de eventos { #event-grid-query } - -In addition to the above event query end point, there is an event grid -query end point where a more compact "grid" format of events are -returned. This is possible by interacting with -/api/events/query.json|xml|xls|csv endpoint. - - / api / 33 / events / query - -Most of the query parameters mentioned in event querying and reading -section above are valid here. However, since the grid to be returned -comes with specific set of columns that apply to all rows (events), it -is mandatory to specify a program stage. It is not possible to mix -events from different programs or program stages in the return. - -Returning events from a single program stage, also opens up for new -functionality - for example sorting and searching events based on their -data element values. api/events/query has support for this. Below are -some examples - -A query to return an event grid containing only selected data elements -for a program stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - & dataElement = qrur9Dvnyt5, fWIAEtYVEGk, K6uUAvq500H & order = lastUpdated: desc - & pageSize = 50 & page = 1 & totalPages = true - -A query to return an event grid containing all data elements of a -program - stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - & includeAllDataElements = true - -A query to filter events based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - & filter = qrur9Dvnyt5: GT: 20: LT: 50 - -In addition to the filtering, the above example also illustrates one -thing: the fact that there are no data elements mentioned to be returned -in the grid. When this happens, the system defaults back to return only -those data elements marked "Display in report" under program stage -configuration. - -We can also extend the above query to return us a grid sorted (asc|desc) -based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - & filter = qrur9Dvnyt5: GT: 20: LT: 50 & order = qrur9Dvnyt5: desc - -#### Filtros de eventos { #webapi_event_filters } - -To create, read, update and delete event filters you -can interact with the `/api/eventFilters` resource. - - / api / 33 / eventFilters - -##### Crie e atualize uma definição de filtro de evento { #create-and-update-an-event-filter-definition } - -For creating and updating an event filter in the -system, you will be working with the *eventFilters* -resource. *POST* is used to create and *PUT* method is used to update. The event filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Request Payload - -| Request Property | Descrição | Exemplo | -|---|---|---| -| nome | Name of the filter. | "name":"My working list" | -| descrição | A description of the filter. | "description":"for listing all events assigned to me". | -| “Registro de Casos de Malária” | The uid of the program. | "program" : "a3kGcGDCuk6" | -| programStage | The uid of the program stage. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Object containing parameters for querying, sorting and filtering events. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Table: Event Query Criteria definition - -|||| -|---|---|---| -| followUp | Used to filter events based on enrollment followUp flag. Possible values are true|false. | "followUp": true | -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | To specify the output ordering of columns | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| dataFilters | To specify filters to be applied when listing events | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| status | Any valid EventStatus | "eventStatus": "COMPLETED" | -| events | To specify list of events | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod object date filtering based on completed date. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod object date filtering based on due date. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -The available assigned user selection modes are explained in the -following table. - - - -Table: Assigned user selection modes (event assignment) - -| Mode | Descrição | -|---|---| -| CURRENT | Assigned to the current logged in user | -| PROVIDED | Assigned to the users provided in the "assignedUser" parameter | -| NONE | Assigned to no users. | -| ANY | Assigned to any users. | - -Um exemplo de carga útil que pode ser usado para criar / atualizar um eventFilter é mostrado abaixo. - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### Recuperando e excluindo filtros de eventos { #retrieving-and-deleting-event-filters } - -Um filtro de evento específico pode ser recuperado usando a seguinte API - - GET /api/33/eventFilters/{uid} - -Todos os filtros de eventos podem ser recuperados usando a seguinte API. - - GET /api/33/eventFilters?fields=* - -Todos os filtros de eventos para um programa específico podem ser recuperados usando a seguinte API - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -Um filtro de evento pode ser excluído usando a seguinte API - - DELETE / api / 33 / eventFilters / {uid} - -### Relacionamentos { #relationships } -Relacionamentos são links entre duas entidades no rastreador. Essas entidades podem ser instâncias de entidades, inscrições e eventos rastreados. - -Existem vários terminais que permitem ver, criar, excluir e atualizar relacionamentos. O mais comum é o endpoint / api / trackedEntityInstances, onde você pode incluir relacionamentos na carga útil para criá-los, atualizá-los ou excluí-los se omiti-los - Semelhante a como você trabalha com inscrições e eventos no mesmo endpoint. Todos os endpoints do rastreador, / api / trackedEntityInstances, / api / inscrições e / api / events também listam seus relacionamentos, se solicitados no filtro de campo. - -O ponto de extremidade padrão para relacionamentos é, entretanto, / api / relationships. Este terminal fornece todas as operações CRUD normais para relacionamentos. - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -Essa solicitação retornará uma lista de qualquer relacionamento que você tenha acesso para ver que inclua o trackedEntityInstance, inscrição ou evento que você especificou. Cada relacionamento é representado com o seguinte JSON: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -Você também pode visualizar relacionamentos especificados usando o seguinte endpoint: - - GET /api/relationships/ - -Para criar ou atualizar um relacionamento, você pode usar os seguintes endpoints: - - POST / api / relationships - PUT / api / relationships - -E use a seguinte estrutura de carga útil: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -Para excluir um relacionamento, você pode usar este ponto de extremidade: - - DELETE / api / relationships / - -Em nossas cargas úteis de exemplo, usamos um relacionamento entre trackedEntityInstances. Por causa disso, as propriedades "de" e "para" de nossas cargas úteis incluem objetos "trackedEntityInstance". Se o seu relacionamento inclui outras entidades, você pode usar as seguintes propriedades: - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### Estratégias de atualização { #webapi_tei_update_strategies } - -Two update strategies for all 3 tracker endpoints are supported: -enrollment and event creation. This is useful when you have generated an -identifier on the client side and are not sure if it was created or not -on the server. - - - -Table: Available tracker strategies - -| Parameter | Descrição | -|---|---| -| CREATE | Create only, this is the default behavior. | -| CREATE_AND_UPDATE | Try and match the ID, if it exist then update, if not create. | - -Para alterar o parâmetro, use o parâmetro de estratégia: - - POST / api / 33 / trackedEntityInstances? Estratégia = CREATE_AND_UPDATE - -### Exclusão em massa do rastreador { #webapi_tracker_bulk_deletion } - -Bulk deletion of tracker objects work in a similar fashion to adding and -updating tracker objects, the only difference is that the -`importStrategy` is *DELETE*. - -*Example: Bulk deletion of tracked entity instances:* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*Example: Bulk deletion of enrollments:* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*Example: Bulk deletion of events:* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### Reutilização de identificadores e exclusão de itens por meio dos métodos POST e PUT { #webapi_updating_and_deleting_items } - -Tracker endpoints */trackedEntityInstances*, */enrollments*, */events* -support CRUD operations. The system keeps track of used identifiers. -Therefore, an item which has been created and then deleted (e.g. events, -enrollments) cannot be created or updated again. If attempting to delete -an already deleted item, the system returns a success response as -deletion of an already deleted item implies no change. - -The system does not allow to delete an item via an update (*PUT*) or -create (*POST*) method. Therefore, an attribute *deleted* is ignored in -both *PUT* and *POST* methods, and in *POST* method it is by default set -to *false*. - -### Parâmetros de importação { #webapi_import_parameters } - -O processo de importação pode ser personalizado usando um conjunto de parâmetros de importação: - - - -Table: Import parameters - -| Parameter | Values (default first) | Descrição | -|---|---|---| -| dataElementIdScheme | id | name | code | attribute:ID | Property of the data element object to use to map the data values. | -| orgUnitIdScheme | id | name | code | attribute:ID | Property of the org unit object to use to map the data values. | -| idScheme | id | name | code| attribute:ID | Property of all objects including data elements, org units and category option combos, to use to map the data values. | -| dryRun | false | true | Whether to save changes on the server or just return the import summary. | -| strategy | CREATE | UPDATE | CREATE_AND_UPDATE | DELETE | Save objects of all, new or update import status on the server. | -| skipNotifications | true | false | Indicates whether to send notifications for completed events. | -| skipFirst | true | false | Relevant for CSV import only. Indicates whether CSV file contains a header row which should be skipped. | -| importReportMode | FULL, ERRORS, DEBUG | Sets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes *ObjectReports* for object which has errors. `FULL` returns an *ObjectReport* for all objects imported, and `DEBUG` returns the same plus a name for the object (if available). | - -#### Importar / Exportar CSV { #webapi_events_csv_import_export } - -In addition to XML and JSON for event import/export, in DHIS2.17 we -introduced support for the CSV format. Support for this format builds on -what was described in the last section, so here we will only write about -what the CSV specific parts are. - -To use the CSV format you must either use the `/api/events.csv` -endpoint, or add *content-type: text/csv* for import, and *accept: -text/csv* for export when using the `/api/events` endpoint. - -The order of column in the CSV which are used for both export and import -is as follows: - - - -Table: CSV column - -| Index | Chave | Modelo | Descrição | -|---|---|---|---| -| 1 | event | identifier | Identifier of event | -| 2 | status | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | “Registro de Casos de Malária” | identifier | Identifier of program | -| 4 | programStage | identifier | Identifier of program stage | -| 5 | enrollment | identifier | Identifier of enrollment (program instance) | -| 6 | orgUnit | identifier | Identifier of organisation unit | -| 7 | eventDate | date | Event date | -| 8 | dueDate | date | Due Date | -| 9 | latitude | double | Latitude where event happened | -| 10 | longitude | double | Longitude where event happened | -| 11 | dataElement | identifier | Identifier of data element | -| 12 | value | string | Value / measure of event | -| 13 | storedBy | string | Event was stored by (defaults to current user) | -| 14 | providedElsewhere | boolean | Was this value collected somewhere else | -| 14 | completedDate | date | Completed date of event | -| 14 | completedBy | string | Username of user who completed event | - -*Example of 2 events with 2 different data value - each:* - -`` `csv -EJNxP3WreNP, COMPLETED, , , , , 2016-01-01,2016-01-01 ,,, , 1 ,,, -EJNxP3WreNP, COMPLETED, , , , , 2016-01-01,2016-01-01 ,,, , ,,, -qPEdI1xn7k0, COMPLETED, , , , , 2016-01-01,2016-01-01 ,,, , 3 ,, -qPEdI1xn7k0, COMPLETED, , , , , 2016-01-01,2016-01-01 ,,, , 4 ,, -`` ` - -#### Estratégia de importação: SYNC { #webapi_sync_import_strategy } - -The import strategy SYNC should be used only by internal synchronization -task and not for regular import. The SYNC strategy allows all 3 -operations: CREATE, UPDATE, DELETE to be present in the payload at the -same time. - -### Tracker Ownership Management { #webapi_tracker_ownership_management } - -A new concept called Tracker Ownership is introduced from 2.30. There -will now be one owner organisation unit for a tracked entity instance in -the context of a program. Programs that are configured with an access -level of *PROTECTED* or *CLOSED* will adhere to the ownership -privileges. Only those users belonging to the owning org unit for a -tracked entity-program combination will be able to access the data -related to that program for that tracked entity. - -#### Substituição de propriedade do rastreador: Quebre o vidro { #webapi_tracker_ownership_override_api } - -It is possible to temporarily override this ownership privilege for a -program that is configured with an access level of *PROTECTED*. Any user -will be able to temporarily gain access to the program related data, if -the user specifies a reason for accessing the tracked entity-program -data. This act of temporarily gaining access is termed as *breaking the -glass*. Currently, the temporary access is granted for 3 hours. DHIS2 -audits breaking the glass along with the reason specified by the user. -It is not possible to gain temporary access to a program that has been -configured with an access level of *CLOSED*. To break the glass for a -tracked entity program combination, you can issue a POST request as -shown: - - / api / 33 / tracker / propriedade / override? trackedEntityInstance = DiszpKrYNg8 - & program = eBAyeGv0exc & reason = paciente + apareceu + para + emergência + atendimento - -#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer_api } - -It is possible to transfer the ownership of a tracked entity-program -from one org unit to another. This will be useful in case of patient -referrals or migrations. Only an owner (or users who have broken the -glass) can transfer the ownership. To transfer ownership of a tracked -entity-program to another organisation unit, you can issue a PUT request -as shown: - - / api / 33 / tracker / propriedade / transfer? trackedEntityInstance = DiszpKrYNg8 - & program = eBAyeGv0exc & ou = EJNxP3WreNP - - -## Potenciais duplicados { #potential-duplicates } - -As duplicatas potenciais são registros com os quais trabalhamos no recurso de desduplicação de dados. Devido à natureza do recurso de desduplicação, este terminal de API é um tanto restrito. - -A potential duplicate represents a pair of records which are suspected to be a duplicate. - -A carga útil de uma possível duplicata se parece com isto: - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -Você pode recuperar uma lista de possíveis duplicatas usando o seguinte endpoint: - - GET /api/potentialDuplicates - -| Parameter name | Descrição | Modelo | Allowed values | -|---|---|---|---| -| teis | List of tracked entity instances | List of string (separated by comma)| existing tracked entity instance id | -| status | Potential duplicate status | string | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Status code | Descrição -|---|---| -| 400 | Invalid input status - -You can inspect individual potential duplicate records: - - GET /api/potentialDuplicates/ - -| Status code | Descrição -|---|---| -| 404 | Potential duplicate not found - -Para criar uma nova duplicata potencial, você pode usar este endpoint: - - POST / api / potencialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Status code | Descrição -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -To update a potential duplicate status: - - PUT /api/potentialDuplicates/ - -| Parameter name | Descrição | Modelo | Allowed values | -|---|---|---|---| -| status | Potential duplicate status | string | `OPEN`, `INVALID`, `MERGED` | - -| Status code | Descrição -|---|---| -| 400 | You can't update a potential duplicate to MERGED as this is possible only by a merging request -| 400 | You can't update a potential duplicate that is already in a MERGED status - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -To merge a Potential Duplicate, or the two tracked entity instances the Potential Duplicate represents, the following endpoint can be used: - - POST /api/potentialDuplicates//merge - -| Parameter name | Descrição | Modelo | Allowed values | -|---|---|---|---| -| mergeStrategy | Strategy to use for merging the potentialDuplicate | enum | AUTO(default) or MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- The same attribute has different values in each tracked entity instance -- Both tracked entity instances are enrolled in the same program -- Tracked entity instances have different types - -If any conflict is encountered, an errormessage is returned to the user. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -When requesting an automatic merge like this, a payload is not required and will be ignored. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Relationship cannot be between the original and the duplicate (This results in an invalid self-referencing relationship) -- Relationship cannot be of the same type and to the same object in both tracked entity instances (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) - -There are two ways to do a manual merge: With and without a payload. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -Otherwise, if a manual merge is requested with a payload, the payload refers to what data should be moved from the duplicate to the original. The payload looks like this: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -Os campos são explicados na tabela a seguir. - - -Table: Program Notification Template payload - -| Campo | Requerido | Descrição | Values | -|---|---|---|---| -| nome | sim | name of Program Notification Template | case-notification-alert | -| notificationTrigger | sim | When notification should be triggered. Possible values are ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| INSCRIÇÃO | -| subjectTemplate | Não | Subject template string | Case notification V{org_unit_name} | -| messageTemplate | sim | Message template string | Case notification A{h5FuguPFF2j} | -| notificationRecipient | YES | Who is going to receive notification. Possible values are USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | Não | Which channel should be used for this notification. It can be either SMS, EMAIL or HTTP | SMS | -| sendRepeatable | Não | Whether notification should be sent multiple times | falso | - -NOTE: WEB_HOOK notificationRecipient is used only to POST http request to an external system. Make sure to choose HTTP delivery channel when using WEB_HOOK. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -The list of Program Notification Templates can be retrieved using GET. - - GET /api/programNotificationTemplates - -For one particular Program Notification Template. - - GET /api/33/programNotificationTemplates/{uid} - -To get filtered list of Program Notification Templates - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Program Notification Template can be deleted using DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -Program message lets you send messages to tracked entity instances, -contact addresses associated with organisation units, phone numbers and -email addresses. You can send messages through the `messages` resource. - - / api / 33 / messages - -### Enviando mensagens do programa { #sending-program-messages } - -As mensagens do programa podem ser enviadas usando dois canais de entrega: - - - SMS (SMS) - - - Endereço de email (EMAIL) - -As mensagens do programa podem ser enviadas para vários destinatários: - - - Tracked entity instance: The system will look up attributes of value - type PHONE_NUMBER or EMAIL (depending on the specified delivery - channels) and use the corresponding attribute values. - - - Organisation unit: The system will use the phone number or email - information registered for the organisation unit. - - - List of phone numbers: The system will use the explicitly defined - phone numbers. - - - List of email addresses: The system will use the explicitly defined - email addresses. - -Below is a sample JSON payload for sending messages using POST requests. -Note that message resource accepts a wrapper object named -`programMessages` which can contain any number of program messages. - - POST / api / 33 / messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -Os campos são explicados na tabela a seguir. - - - -Table: Program message payload - -| Campo | Requerido | Descrição | Values | -|---|---|---|---| -| recipients | sim | Recipients of the program message. At least one recipient must be specified. Any number of recipients / types can be specified for a message. | Can be trackedEntityInstance, organisationUnit, an array of phoneNumbers or an array of emailAddresses. | -| programInstance | Either this or programStageInstance required | The program instance / enrollment. | Enrollment ID. | -| programStageInstance | Either this or programInstance required | The program stage instance / event. | Event ID. | -| deliveryChannels | sim | Array of delivery channels. | SMS | EMAIL | -| subject | Não | The message subject. Not applicable for SMS delivery channel. | Text. | -| texto | sim | The message text. | Text. | -| storeCopy | Não | Whether to store a copy of the program message in DHIS2. | false (default) | true | - -A minimalistic example for sending a message over SMS to a tracked -entity instance looks like this: - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### Recuperando e excluindo mensagens do programa { #retrieving-and-deleting-program-messages } - -A lista de mensagens pode ser recuperada usando GET. - - GET /api/33/messages - -To get the list of sent tracker messages, the below endpoint can be used. ProgramInstance or ProgramStageInstance uid has to be provided. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -To get the list of all scheduled message - - GET /api/33/messages/scheduled - GET /api/33/messages/scheduled?scheduledAt=2020-12-12 - -Uma mensagem específica também pode ser recuperada usando GET. - - GET /api/33/messages/{uid} - -A mensagem pode ser excluída usando DELETE. - - DELETE / api / 33 / messages / {uid} - - -### Consultando mensagens do programa { #querying-program-messages } - -The program message API supports program message queries based on -request parameters. Messages can be filtered based on below mentioned -query parameters. All requests should use the GET HTTP verb for -retrieving information. - - - -Table: Query program messages API - -| Parameter | URL | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # O email { #email } diff --git a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index 50293e95f..1bbb4d944 100644 --- a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/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: -- Gerir - DHIS core version 2.37 +- Gerir template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md index 5d57d32d1..c4812d1b7 100644 --- a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md +++ b/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 --- diff --git a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index c61b1b77c..219a99f5d 100644 --- a/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/pt/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- Gerir - DHIS core version master +- Gerir template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index 79d2e1e85..a7c001b96 100644 --- a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/pt/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 - Usar +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index 8c3d28a39..ae6ab47c7 100644 --- a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/pt/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 - Usar +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index ac5b057cd..063c5856a 100644 --- a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - Usar +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 981a1ff49..19d6dbefe 100644 --- a/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - Usar +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ru/.cache_timestamp b/projects/dhis2-single-page-docs/ru/.cache_timestamp index 0375ea179..8e64c3765 100644 --- a/projects/dhis2-single-page-docs/ru/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ru/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:28:04Z \ No newline at end of file +2024-06-04T21:28:00Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index ff65d7b30..914f1765b 100644 --- a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ru/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 --- diff --git a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index a4e29f600..40fba1b92 100644 --- a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ru/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 --- diff --git a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 0fb8e769b..718ede252 100644 --- a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - Использовать +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 92171437c..26be1b252 100644 --- a/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - Использовать +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/si/.cache_timestamp b/projects/dhis2-single-page-docs/si/.cache_timestamp index 8663c9e65..d2954d368 100644 --- a/projects/dhis2-single-page-docs/si/.cache_timestamp +++ b/projects/dhis2-single-page-docs/si/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:28:11Z \ No newline at end of file +2024-06-04T21:28:08Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp b/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp index 8663c9e65..d2954d368 100644 --- a/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:28:11Z \ No newline at end of file +2024-06-04T21:28:08Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index 698e99f45..2003e0a94 100644 --- a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2023-01-13' tags: -- DHIS core version 2.37 - بنایا +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index 38aade537..6ae4e3d3f 100644 --- a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- DHIS core version 2.38 - بنایا +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index 4cdf7c2ca..8424e4ac1 100644 --- a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - بنایا +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index e3e605159..153d8995f 100644 --- a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - بنایا +- DHIS core version 2.40 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 8a1becc95..20da20378 100644 --- a/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - بنایا - DHIS core version master @@ -12217,7 +12217,7 @@ Table: Query parameters for event query analytics only | Query parameter | Required | Description | Options | |---|---|---|---| -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return events which have coordinates. | false | true | @@ -13124,7 +13124,7 @@ Table: Query parameters for enrollment query endpoint | filter | No | Dimension identifier including data elements, attributes, periods, organisation units and organisation unit group sets. Parameter can be repeated any number of times. Item filters can be applied to a dimension on the format ::. Filter values are case-insensitive. || | programStatus | No | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | No | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return enrollments which have coordinates. | false | true | @@ -17833,20 +17833,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17949,7 +17950,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | No | Yes | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | Yes | No | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | No | Yes | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -18009,9 +18009,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Attributes { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -18026,18 +18028,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -18052,31 +18056,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Notes { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -18087,10 +18091,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -18132,92 +18136,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the working list. Required. || -| description | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Description | Example | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -18226,9 +18145,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -18261,7 +18180,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -18661,7 +18580,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -19107,7 +19026,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -19237,7 +19156,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | N/A | Undefined error message. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -19247,7 +19166,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -19272,8 +19191,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -19326,7 +19245,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -19382,7 +19301,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -19404,7 +19323,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -19438,7 +19357,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -19490,9 +19409,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -19572,8 +19491,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -19678,7 +19597,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19940,8 +19859,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -20145,8 +20064,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -20441,13 +20360,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -20493,7 +20412,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -20562,13 +20481,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -20580,7 +20499,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -20593,7 +20512,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -20603,7 +20522,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -20633,7 +20552,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -20649,2767 +20568,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Table: Payload -|Tracker Object|Previously|Now| +| Payload values | Description | Example | |---|---|---| -|**Attribute**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Event**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Note**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Relationship**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribute`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes`|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus`|`enrollmentStatus`| -|`query`|Removed - use `filter` instead| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Previously|Now| -|---|---| -|`enrollment`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus`|`status`| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`event`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`lastUpdated`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus`|`enrollmentStatus`| -|`skipEventId`|Removed| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Previously|Now| -|---|---| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity`| - -## Tracker Web API { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### Tracked entity instance management { #webapi_tracked_entity_instance_management } - -Tracked entity instances have full CRUD support in the API. Together -with the API for enrollment most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/trackedEntityInstances - -#### Creating a new tracked entity instance { #webapi_creating_tei } - -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -The field "geometry" accepts a GeoJson object, where the type of the -GeoJson have to match the featureType of the TrackedEntityType -definition. An example GeoJson object looks like this: - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +| name | Name of the working list. Required. || +| description | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Table: Program Stage Query Criteria - /api/trackedEntityInstances +| Criteria values | Description | Example | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +See an example payload below: ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -To push this to the server you can use the cURL command like this: - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -To create multiple instances in one request you can wrap the payload in -an outer array like this and POST to the same resource as above:[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -The system does not allow the creation of a tracked entity instance -(as well as enrollment and event) with a UID that was already used in -the system. That means that UIDs cannot be reused. - -#### Updating a tracked entity instance { #webapi_updating_tei } - -For updating a tracked entity instance, the payload is equal to the -previous section. The difference is that you must use the HTTP *PUT* -method for the request when sending the payload. You will also need to -append the person identifier to the *trackedEntityInstances* resource in -the URL like this, where `` should -be replaced by the identifier of the tracked entity instance: - - /api/trackedEntityInstances/ - -The payload has to contain all, even non-modified, attributes and -relationships. Attributes or relationships that were present before and -are not present in the current payload any more will be removed from the -system. This means that if attributes/relationships are empty in the -current payload, all existing attributes/relationships will be deleted -from the system. From 2.31, it is possible to ignore empty -attributes/relationships in the current payload. A request parameter of -`ignoreEmptyCollection` set to `true` can be used in case you do not -wish to send in any attributes/relationships and also do not want them -to be deleted from the system. - -It is not allowed to update an already deleted tracked entity instance. -Also, it is not allowed to mark a tracked entity instance as deleted via -an update request. The same rules apply to enrollments and events. - -#### Deleting a tracked entity instance { #webapi_deleting_tei } - -In order to delete a tracked entity instance, make a request to the URL -identifying the tracked entity instance with the *DELETE* -method. The URL is equal to the one above used for update. - -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } - -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Complete example of payload including: tracked entity instance, enrollment and event { #webapi_create_enroll_tei_create_event } - -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute":"cejWyOfXge6", - "value":"Male" - } - ], - "enrollments":[ - { - "orgUnit":"DiszpKrYNg8", - "program":"ur1Edk5Oe2n", - "enrollmentDate":"2017-09-15", - "incidentDate":"2017-09-15", - "events":[ - { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues": [ - { - "dataElement":"qrur9Dvnyt5", - "value":"22" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Male" - } - ] - }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues":[ - { - "dataElement":"qrur9Dvnyt5", - "value":"26" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Female" - } - ] - } - ] - } - ] + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Generated tracked entity instance attributes { #webapi_generate_tei_attributes } - -Tracked entity instance attributes that are using automatic generation of -unique values have three endpoints that are used by apps. The endpoints -are all used for generating and reserving values. - -In 2.29 we introduced TextPattern for defining and generating these -patterns. All existing patterns will be converted to a valid TextPattern -when upgrading to 2.29. - -> **Note** -> -> As of 2.29, all these endpoints will require you to include any -> variables reported by the `requiredValues` endpoint listed as -> required. Existing patterns, consisting of only `#`, will be upgraded -> to the new TextPattern syntax `RANDOM()`. The RANDOM -> segment of the TextPattern is not a required variable, so this -> endpoint will work as before for patterns defined before 2.29. - -##### Finding required values { #finding-required-values } - -A TextPattern can contain variables that change based on different -factors. Some of these factors will be unknown to the server, so the -values for these variables have to be supplied when generating and -reserving values. - -This endpoint will return a map of required and optional values, that -the server will inject into the TextPattern when generating new values. -Required variables have to be supplied for the generation, but optional -variables should only be supplied if you know what you are doing. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### Generate value endpoint { #webapi_generate_values } - -Online web apps and other clients that want to generate a value that -will be used right away can use the simple generate endpoint. This -endpoint will generate a value that is guaranteed to be unique at the -time of generation. The value is also guaranteed not to be reserved. As -of 2.29, this endpoint will also reserve the value generated for 3 days. - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } - -The generate and reserve endpoint is used by offline clients that need -to be able to register tracked entities with unique ids. They will -reserve a number of unique ids that this device will then use when -registering new tracked entity instances. The endpoint is called to -retrieve a number of tracked entity instance reserved values. An -optional parameter numberToReserve specifies how many ids to generate -(default is 1). - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -Similar to the /generate endpoint, this endpoint can also specify the -expiration time in the same way. By adding the `?expiration=` -you can override the default 60 days. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### Reserved values { #reserved-values } - -Reserved values are currently not accessible through the api, however, they -are returned by the `generate` and `generateAndReserve` endpoints. The -following table explains the properties of the reserved value object: - -##### - - - -Table: Reserved values - -| Property | Description | -|---|---| -| ownerObject | The metadata type referenced when generating and reserving the value. Currently only TRACKEDENTITYATTRIBUTE is supported. | -| ownerUid | The uid of the metadata object referenced when generating and reserving the value. | -| key | A partially generated value where generated segments are not yet added. | -| value | The fully resolved value reserved. This is the value you send to the server when storing data. | -| created | The timestamp when the reservation was made | -| expiryDate | The timestamp when the reservation will no longer be reserved | - -Expired reservations are removed daily. If a pattern changes, values -that were already reserved will be accepted when storing data, even if -they don't match the new pattern, as long as the reservation has not -expired. - -#### Image attributes { #image-attributes } - -Working with image attributes is a lot like working with file data -values. The value of an attribute with the image value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///image` -endpoint will return the actual image. The optional height and width -parameters can be used to specify the dimensions of the image. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } - -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. - - /api/33/trackedEntityInstances - -##### Request syntax { #webapi_tei_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Description | -|---|---| -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Indicates whether to include soft deleted teis or not. It is false by default. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | The selected organisation units and the immediate children, i.e. the organisation units at the level below. | -| DESCENDANTS | The selected organisation units and all children, i.e. all organisation units in the sub-hierarchy. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| ALL | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -The available assigned user modes are explained in the following table. - - - -Table: Assigned user modes - -| Mode | Description | -|---|---| -| CURRENT | Includes events assigned to the current logged in user. | -| PROVIDED | Includes events assigned to the user provided in the request. | -| NONE | Includes unassigned events only. | -| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendant organisation unit query mode: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a filter: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an *IN* filter: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - &filter=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&page=2&pageSize=3 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Description | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### Tracked entity instance grid query { #webapi_tracked_entity_instance_grid_query } - -To query for tracked entity instances you can interact with the -*/api/trackedEntityInstances/grid* resource. There are two types of -queries: One where a *query* query parameter and optionally *attribute* -parameters are defined, and one where *attribute* and *filter* -parameters are defined. This endpoint uses a more compact "grid" format, -and is an alternative to the query in the previous section. - - /api/33/trackedEntityInstances/query - -##### Request syntax { #webapi_tei_grid_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Description | -|---|---| -| query | Query string. Attribute query parameter can be used to define which attributes to include in the response. If no attributes but a program is defined, the attributes from the program will be used. If no program is defined, all attributes will be used. There are two formats. The first is a plan query string. The second is on the format :. Operators can be EQ | LIKE. EQ implies exact matches on words, LIKE implies partial matches on words. The query will be split on space, where each word will form a logical AND query. | -| attribute | Attributes to be included in the response. Can also be used as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. Filters can be omitted in order to simply include the attribute in the response without any constraints. | -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| eventStatus | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Start date of event associated with the given program and event status. | -| eventEndDate | End date of event associated with the given program and event status. | -| programStage | The programStage for which the event related filters should be applied to. If not provided all stages will be considered. | -| skipMeta | Indicates whether meta data for the response should be included. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| CAPTURE | The data capture organisation units associated with the current user and all children, i.e. all organisation units in the sub-hierarchy. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -Note that you can specify "attribute" with filters or directly using the "filter" params for constraining the -instances to return. - -Certain rules apply to which attributes are returned. - - - If "query" is specified without any attributes or program, then all attributes that - are marked as "Display in List without Program" is included in the response. - - - If program is specified, all the attributes linked to the program will - be included in the response. - - - If tracked entity type is specified, then all tracked entity type attributes - will be included in the response. - -You can specify queries with words separated by space - in that -situation the system will query for each word independently and return -records where each word is contained in any attribute. A query item can -be specified once as an attribute and once as a filter if needed. The -query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - If *eventStatus* is specified then *eventStartDate* and - *eventEndDate* must also be specified. - - - A query cannot be specified together with filters. - - - Attribute items can only be specified once. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -A query on all attributes for a specific value and organisation unit, -using an exact word match: - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -A query on all attributes for a specific value, using a partial word -match: - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -You can query on multiple words separated by the URL character for -space which is %20, will use a logical AND query for each - word: - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -A query where the attributes to include in the response are specified: - - /api/33/trackedEntityInstances/query.json?query=isabel - &attribute=dv3nChNSIxy&attribute=AMpUYgxuCaE&ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendants organisation unit query mode: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &attribute=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a - filter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an IN - filter: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - &attribute=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&program=ur1Edk5Oe2n&programStartDate=2013-01-01 - &programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -To query for instances which have events of a given status within a -given time span: - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Description | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_grid_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - - - csv (application/csv) - - - xls (application/vnd.ms-excel) - -The response in JSON comes is in a tabular format and can look like the -following. The *headers* section describes the content of each column. -The instance, created, last updated, org unit and tracked entity columns -are always present. The following columns correspond to attributes -specified in the query. The *rows* section contains one row per -instance. - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### Tracked entity instance filters { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - /api/33/trackedEntityInstanceFilters - -##### Create and update a tracked entity instance filter definition { #create-and-update-a-tracked-entity-instance-filter-definition } - -For creating and updating a tracked entity instance filter in the -system, you will be working with the *trackedEntityInstanceFilters* -resource. The tracked entity instance filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the filter. Required. || -| description | A description of the filter. || -| sortOrder | The sort order of the filter. Used in Tracker Capture to order the filters in the program dashboard. || -| style | Object containing css style. | ( "color": "blue", "icon": "fa fa-calendar"} | -| program | Object containing the id of the program. Required. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Table: Entity Query Criteria definition - -|||| -|---|---|---| -| attributeValueFilters | A list of attributeValueFilters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| enrollmentStatus | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | When this parameter is true, the filter only returns TEIs that have an enrollment with status followup. || -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayColumnOrder | To specify the output ordering of columns | "displayOrderColumns": ["enrollmentDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus | Any valid EventStatus | "eventStatus": "COMPLETED" | -| programStage | To specify a programStage uid to filter on. TEIs will be filtered based on presence of enrollment in the specified program stage.| "programStage"="a3kGcGDCuk6" | -| trackedEntityType | To specify a trackedEntityType filter TEIs on. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | To specify a list of trackedEntityInstances to use when querying TEIs. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod object date filtering based on enrollment incident date. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod object date filtering based on enrollment created date. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Table: Event filters definition - -|||| -|---|---|---| -| programStage | Which programStage the TEI needs an event in to be returned. | "eaDH9089uMp" | -| eventStatus | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT (events assigned to current user)| PROVIDED (events assigned to users provided in "assignedUsers" list) | NONE (events assigned to no one) | ANY (events assigned to anyone). If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -Table: Period definition - -|||| -|---|---|---| -| periodFrom | Number of days from current day. Can be positive or negative integer. | -15 | -| periodTo | Number of days from current day. Must be bigger than periodFrom. Can be positive or negative integer. | 15 | - -##### Tracked entity instance filters query { #tracked-entity-instance-filters-query } - -To query for tracked entity instance filters in the system, you can -interact with the */api/trackedEntityInstanceFilters* resource. - - - -Table: Tracked entity instance filters query parameters - -| Query parameter | Description | -|---|---| -| program | Program identifier. Restricts filters to the given program. | - -### Enrollment management { #webapi_enrollment_management } - -Enrollments have full CRUD support in the API. Together with the API -for tracked entity instances most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/enrollments - -#### Enrolling a tracked entity instance into a program { #webapi_enrolling_tei } - -For enrolling persons into a program, you will need to first get the -identifier of the person from the *trackedEntityInstances* resource. -Then, you will need to get the program identifier from the *programs* -resource. A template payload can be seen below: - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -This payload should be used in a *POST* request to the enrollments -resource identified by the following URL: - - /api/33/enrollments - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - /api/33/enrollments//cancelled - -For completing an enrollment for a tracked entity instance you can make a -*PUT* request to the following URL: - - /api/33/enrollments//completed - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - /api/33/enrollments/ - -#### Enrollment instance query { #webapi_enrollment_instance_query } - -To query for enrollments you can interact with the */api/enrollments* -resource. - - /api/33/enrollments - -##### Request syntax { #webapi_enrollment_query_request_syntax } - - - -Table: Enrollment query parameters - -| Query parameter | Description | -|---|---| -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| trackedEntityInstance | Tracked entity instance identifier. Should not be used together with trackedEntity. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| includeDeleted | Indicates whether to include soft deleted enrollments or not. It is false by default. | - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request (default). | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - -A query for all enrollments associated with a specific organisation unit -can look like this: - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -To constrain the response to enrollments which are part of a specific -program you can include a program query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the - query: - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - &programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to enrollments of a specific tracked entity -you can include a tracked entity query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -To constrain the response to enrollments of a specific tracked entity -instance you can include a tracked entity instance query parameter, in -this case we have restricted it to available enrollments viewable for -current - user: - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -By default the enrollments are returned in pages of size 50, to change -this you can use the page and pageSize query - parameters: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### Response format { #webapi_enrollment_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### Events { #webapi_events } - -This section is about sending and reading events. - - /api/33/events - -The different status of an event are: - -* **ACTIVE**: If a event has ACTIVE status, it is possible to edit the event details. COMPLETED events can be turned ACTIVE again and vice versa. -* **COMPLETED**: An event change the status to COMPLETED only when a user clicks the complete button. If a event has COMPLETED status, it is not possible to edit the event details. ACTIVE events can be turned COMPLETED again and vice versa. -* **SKIPPED**: Scheduled events that no longer need to happen. In Tracker Capture, there is a button for that. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### Sending events { #webapi_sending_events } - -DHIS2 supports three kinds of events: single events with no registration -(also referred to as anonymous events), single event with registration -and multiple events with registration. Registration implies that the -data is linked to a tracked entity instance which is identified using -some sort of identifier. - -To send events to DHIS2 you must interact with the *events* resource. -The approach to sending events is similar to sending aggregate data -values. You will need a *program* which can be looked up using the -*programs* resource, an *orgUnit* which can be looked up using the -*organisationUnits* resource, and a list of valid data element -identifiers which can be looked up using the *dataElements* resource. -For events with registration, a *tracked entity instance* identifier is -required, read about how to get this in the section about the -*trackedEntityInstances* resource. For sending events to programs with -multiple stages, you will need to also include the *programStage* -identifier, the identifiers for programStages can be found in the -*programStages* resource. - -A simple single event with no registration example payload in XML format -where we send events from the "Inpatient morbidity and mortality" -program for the "Ngelehun CHC" facility in the demo database can be seen -below: - -```xml - - - - - - - - - -``` - -To perform some testing we can save the XML payload as a file -called *event.xml* and send it as a POST request to the events resource -in the API using curl with the following command: - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -The same payload in JSON format looks like this: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -To send this you can save it to a file called *event.json* and use curl -like this: - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -We also support sending multiple events at the same time. A payload in -XML format might look like this: - -```xml - - - - - - - - - - - - - - - - - -``` - -You will receive an import summary with the response which can be -inspected in order to get information about the outcome of the request, -like how many values were imported successfully. The payload in JSON -format looks like this: - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -You can also use GeoJson to store any kind of geometry on your event. An example payload using GeoJson instead of the former latitude and longitude properties can be seen here: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -As part of the import summary you will also get the identifier -*reference* to the event you just sent, together with a *href* element -which points to the server location of this event. The table below -describes the meaning of each element. - - - -Table: Events resource format - -| Parameter | Type | Required | Options (default first) | Description | -|---|---|---|---|---| -| program | string | true || Identifier of the single event with no registration program | -| orgUnit | string | true || Identifier of the organisation unit where the event took place | -| eventDate | date | true || The date of when the event occurred | -| completedDate | date | false || The date of when the event is completed. If not provided, the current date is selected as the event completed date | -| status | enum | false | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Whether the event is complete or not | -| storedBy | string | false | Defaults to current user | Who stored this event (can be username, system-name, etc) | -| coordinate | double | false || Refers to where the event took place geographically (latitude and longitude) | -| dataElement | string | true || Identifier of data element | -| value | string | true || Data value or measure for this event | - -##### OrgUnit matching { #orgunit-matching } - -By default the orgUnit parameter will match on the -ID, you can also select the orgUnit id matching scheme by using the -parameter orgUnitIdScheme=SCHEME, where the options are: *ID*, *UID*, -*UUID*, *CODE*, and *NAME*. There is also the *ATTRIBUTE:* scheme, which -matches on a *unique* metadata attribute value. - -#### Updating events { #webapi_updating_events } - -To update an existing event, the format of the payload is the same, but -the URL you are posting to must add the identifier to the end of the URL -string and the request must be PUT. - -The payload has to contain all, even non-modified, attributes. -Attributes that were present before and are not present in the current -payload any more will be removed by the system. - -It is not allowed to update an already deleted event. The same applies -to tracked entity instance and enrollment. - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### Deleting events { #webapi_deleting_events } - -To delete an existing event, all you need is to send a DELETE request -with an identifier reference to the server you are using. - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### Assigning user to events { #webapi_user_assign_event } - -A user can be assigned to an event. This can be done by including the appropriate property in the payload when updating or creating the event. - - "assignedUser": "" - -The id refers to the if of the user. Only one user can be assigned to an event at a time. - -User assignment must be enabled in the program stage before users can be assigned to events. -#### Getting events { #webapi_getting_events } - -To get an existing event you can issue a GET request including the -identifier like this: - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### Querying and reading events { #webapi_querying_reading_events } - -This section explains how to read out the events that have been stored -in the DHIS2 instance. For more advanced uses of the event data, please -see the section on event analytics. The output format from the -`/api/events` endpoint will match the format that is used to send events -to it (which the analytics event api does not support). Both XML and -JSON are supported, either through adding .json/.xml or by setting the -appropriate *Accept* header. The query is paged by default and the -default page size is 50 events, *field* filtering works as it does for -metadata, add the *fields* parameter and include your wanted properties, -i.e. *?fields=program,status*. - - - -Table: Events resource query parameters - -| Key | Type | Required | Description | -|---|---|---|---| -| program | identifier | true (if not programStage is provided) | Identifier of program | -| programStage | identifier | false | Identifier of program stage | -| programStatus | enum | false | Status of event in program, ca be ACTIVE | COMPLETED | CANCELLED | -| followUp | boolean | false | Whether event is considered for follow up in program, can be true | false or omitted. | -| trackedEntityInstance | identifier | false | Identifier of tracked entity instance | -| orgUnit | identifier | true | Identifier of organisation unit | -| ouMode | enum | false | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| startDate | date | false | Only events newer than this date | -| endDate | date | false | Only events older than this date | -| status | enum | false | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | date | false | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | date | false | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | string | false | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta | boolean | false | Exclude the meta data part of response (improves performance) | -| page | integer | false | Page number | -| pageSize | integer | false | Number of items in each page | -| totalPages | boolean | false | Indicates whether to include the total number of pages in the paging response. | -| skipPaging | boolean | false | Indicates whether to skip paging in the query and return all events. | -| dataElementIdScheme | string | false | Data element ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme | string | false | Category Option Combo ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| orgUnitIdScheme | string | false | Organisation Unit ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programIdScheme | string | false | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programStageIdScheme | string | false | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| idScheme | string | false | Allows to set id scheme for data element, category option combo, orgUnit, program and program stage at once. | -| order | string | false | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| event | comma delimited string | false | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | boolean | false | Skips event identifiers in the response | -| attributeCc (\*\*) | string | false | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | string | false | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | false | true | false | Indicates whether the import should be done asynchronous or synchronous. | -| includeDeleted | boolean | false | When true, soft deleted events will be included in your query result. | -| assignedUserMode | enum | false | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | comma delimited strings | false | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> **Note** -> -> If the query contains neither `attributeCC` nor `attributeCos`, the server returns events for all attribute option combos where the user has read access. - -##### Examples { #examples } - -Query for all events with children of a certain organisation unit: - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -Query for all events with all descendants of a certain organisation -unit, implying all organisation units in the sub-hierarchy: - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -Query for all events with a certain program and organisation unit: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -Query for all events with a certain program and organisation unit, -sorting by due date - ascending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -Query for the 10 events with the newest event date in a certain program -and organisation unit - by paging and ordering by due date descending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &order=eventDate:desc&pageSize=10&page=1 - -Query for all events with a certain program and organisation unit for a -specific tracked entity instance: - - /api/33/events.json?orgUnit=DiszpKrYNg8 - &program=eBAyeGv0exc&trackedEntityInstance=gfVxE3ALA9m - -Query for all events with a certain program and organisation unit older -or equal to - 2014-02-03: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -Query for all events with a certain program stage, organisation unit and -tracked entity instance in the year 2014: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &trackedEntityInstance=gfVxE3ALA9m&startDate=2014-01-01&endDate=2014-12-31 - -Query files associated with event data values. In the specific case of fetching an image file an -additional parameter can be provided to fetch the image with different dimensions. If dimension is -not provided, the system will return the original image. The parameter will be ignored in case of -fetching non-image files e.g pdf. Possible dimension values are *small(254 x 254), -medium(512 x 512), large(1024 x 1024) or original*. Any value other than those mentioned will be -discarded and the original image will be returned. - - /api/33/events/files?eventUid=hcmcWlYkg9u&dataElementUid=C0W4aFuVm4P&dimension=small - -Retrieve events with specified Organisation unit and Program, and use _Attribute:Gq0oWTf2DtN_ as -identifier scheme - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for -orgUnits, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as identifier -scheme for the rest of the metadata with assigned attribute. - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=Code - -#### Event grid query { #event-grid-query } - -In addition to the above event query end point, there is an event grid -query end point where a more compact "grid" format of events are -returned. This is possible by interacting with -/api/events/query.json|xml|xls|csv endpoint. - - /api/33/events/query - -Most of the query parameters mentioned in event querying and reading -section above are valid here. However, since the grid to be returned -comes with specific set of columns that apply to all rows (events), it -is mandatory to specify a program stage. It is not possible to mix -events from different programs or program stages in the return. - -Returning events from a single program stage, also opens up for new -functionality - for example sorting and searching events based on their -data element values. api/events/query has support for this. Below are -some examples - -A query to return an event grid containing only selected data elements -for a program stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &dataElement=qrur9Dvnyt5,fWIAEtYVEGk,K6uUAvq500H&order=lastUpdated:desc - &pageSize=50&page=1&totalPages=true - -A query to return an event grid containing all data elements of a -program - stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &includeAllDataElements=true - -A query to filter events based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50 - -In addition to the filtering, the above example also illustrates one -thing: the fact that there are no data elements mentioned to be returned -in the grid. When this happens, the system defaults back to return only -those data elements marked "Display in report" under program stage -configuration. - -We can also extend the above query to return us a grid sorted (asc|desc) -based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50&order=qrur9Dvnyt5:desc - -#### Event filters { #webapi_event_filters } - -To create, read, update and delete event filters you -can interact with the `/api/eventFilters` resource. - - /api/33/eventFilters - -##### Create and update an event filter definition { #create-and-update-an-event-filter-definition } - -For creating and updating an event filter in the -system, you will be working with the *eventFilters* -resource. *POST* is used to create and *PUT* method is used to update. The event filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Request Payload - -| Request Property | Description | Example | -|---|---|---| -| name | Name of the filter. | "name":"My working list" | -| description | A description of the filter. | "description":"for listing all events assigned to me". | -| program | The uid of the program. | "program" : "a3kGcGDCuk6" | -| programStage | The uid of the program stage. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Object containing parameters for querying, sorting and filtering events. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Table: Event Query Criteria definition - -|||| -|---|---|---| -| followUp | Used to filter events based on enrollment followUp flag. Possible values are true|false. | "followUp": true | -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | To specify the output ordering of columns | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| dataFilters | To specify filters to be applied when listing events | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| status | Any valid EventStatus | "eventStatus": "COMPLETED" | -| events | To specify list of events | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod object date filtering based on completed date. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod object date filtering based on due date. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -The available assigned user selection modes are explained in the -following table. - - - -Table: Assigned user selection modes (event assignment) - -| Mode | Description | -|---|---| -| CURRENT | Assigned to the current logged in user | -| PROVIDED | Assigned to the users provided in the "assignedUser" parameter | -| NONE | Assigned to no users. | -| ANY | Assigned to any users. | - -A sample payload that can be used to create/update an eventFilter is shown below. - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### Retrieving and deleting event filters { #retrieving-and-deleting-event-filters } - -A specific event filter can be retrieved by using the following api - - GET /api/33/eventFilters/{uid} - -All event filters can be retrieved by using the following api. - - GET /api/33/eventFilters?fields=* - -All event filters for a specific program can be retrieved by using the following api - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -An event filter can be deleted by using the following api - - DELETE /api/33/eventFilters/{uid} - -### Relationships { #relationships } -Relationships are links between two entities in tracker. These entities can be tracked entity instances, enrollments and events. - -There are multiple endpoints that allow you to see, create, delete and update relationships. The most common is the /api/trackedEntityInstances endpoint, where you can include relationships in the payload to create, update or deleting them if you omit them - Similar to how you work with enrollments and events in the same endpoint. All the tracker endpoints, /api/trackedEntityInstances, /api/enrollments and /api/events also list their relationships if requested in the field filter. - -The standard endpoint for relationships is, however, /api/relationships. This endpoint provides all the normal CRUD operations for relationships. - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -This request will return a list of any relationship you have access to see that includes the trackedEntityInstance, enrollment or event you specified. Each relationship is represented with the following JSON: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -You can also view specified relationships using the following endpoint: - - GET /api/relationships/ - -To create or update a relationship, you can use the following endpoints: - - POST /api/relationships - PUT /api/relationships - -And use the following payload structure: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -To delete a relationship, you can use this endpoint: - - DELETE /api/relationships/ - -In our example payloads, we use a relationship between trackedEntityInstances. Because of this, the "from" and "to" properties of our payloads include "trackedEntityInstance" objects. If your relationship includes other entities, you can use the following properties: - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### Update strategies { #webapi_tei_update_strategies } - -Two update strategies for all 3 tracker endpoints are supported: -enrollment and event creation. This is useful when you have generated an -identifier on the client side and are not sure if it was created or not -on the server. - - - -Table: Available tracker strategies - -| Parameter | Description | -|---|---| -| CREATE | Create only, this is the default behavior. | -| CREATE_AND_UPDATE | Try and match the ID, if it exist then update, if not create. | - -To change the parameter, please use the strategy parameter: - - POST /api/33/trackedEntityInstances?strategy=CREATE_AND_UPDATE - -### Tracker bulk deletion { #webapi_tracker_bulk_deletion } - -Bulk deletion of tracker objects work in a similar fashion to adding and -updating tracker objects, the only difference is that the -`importStrategy` is *DELETE*. - -*Example: Bulk deletion of tracked entity instances:* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*Example: Bulk deletion of enrollments:* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*Example: Bulk deletion of events:* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### Identifier reuse and item deletion via POST and PUT methods { #webapi_updating_and_deleting_items } - -Tracker endpoints */trackedEntityInstances*, */enrollments*, */events* -support CRUD operations. The system keeps track of used identifiers. -Therefore, an item which has been created and then deleted (e.g. events, -enrollments) cannot be created or updated again. If attempting to delete -an already deleted item, the system returns a success response as -deletion of an already deleted item implies no change. - -The system does not allow to delete an item via an update (*PUT*) or -create (*POST*) method. Therefore, an attribute *deleted* is ignored in -both *PUT* and *POST* methods, and in *POST* method it is by default set -to *false*. - -### Import parameters { #webapi_import_parameters } - -The import process can be customized using a set of import parameters: - - - -Table: Import parameters - -| Parameter | Values (default first) | Description | -|---|---|---| -| dataElementIdScheme | id | name | code | attribute:ID | Property of the data element object to use to map the data values. | -| orgUnitIdScheme | id | name | code | attribute:ID | Property of the org unit object to use to map the data values. | -| idScheme | id | name | code| attribute:ID | Property of all objects including data elements, org units and category option combos, to use to map the data values. | -| dryRun | false | true | Whether to save changes on the server or just return the import summary. | -| strategy | CREATE | UPDATE | CREATE_AND_UPDATE | DELETE | Save objects of all, new or update import status on the server. | -| skipNotifications | true | false | Indicates whether to send notifications for completed events. | -| skipFirst | true | false | Relevant for CSV import only. Indicates whether CSV file contains a header row which should be skipped. | -| importReportMode | FULL, ERRORS, DEBUG | Sets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes *ObjectReports* for object which has errors. `FULL` returns an *ObjectReport* for all objects imported, and `DEBUG` returns the same plus a name for the object (if available). | - -#### CSV Import / Export { #webapi_events_csv_import_export } - -In addition to XML and JSON for event import/export, in DHIS2.17 we -introduced support for the CSV format. Support for this format builds on -what was described in the last section, so here we will only write about -what the CSV specific parts are. - -To use the CSV format you must either use the `/api/events.csv` -endpoint, or add *content-type: text/csv* for import, and *accept: -text/csv* for export when using the `/api/events` endpoint. - -The order of column in the CSV which are used for both export and import -is as follows: - - - -Table: CSV column - -| Index | Key | Type | Description | -|---|---|---|---| -| 1 | event | identifier | Identifier of event | -| 2 | status | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | program | identifier | Identifier of program | -| 4 | programStage | identifier | Identifier of program stage | -| 5 | enrollment | identifier | Identifier of enrollment (program instance) | -| 6 | orgUnit | identifier | Identifier of organisation unit | -| 7 | eventDate | date | Event date | -| 8 | dueDate | date | Due Date | -| 9 | latitude | double | Latitude where event happened | -| 10 | longitude | double | Longitude where event happened | -| 11 | dataElement | identifier | Identifier of data element | -| 12 | value | string | Value / measure of event | -| 13 | storedBy | string | Event was stored by (defaults to current user) | -| 14 | providedElsewhere | boolean | Was this value collected somewhere else | -| 14 | completedDate | date | Completed date of event | -| 14 | completedBy | string | Username of user who completed event | - -*Example of 2 events with 2 different data value - each:* - -```csv -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,1,, -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,2,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,3,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,4,, -``` - -#### Import strategy: SYNC { #webapi_sync_import_strategy } - -The import strategy SYNC should be used only by internal synchronization -task and not for regular import. The SYNC strategy allows all 3 -operations: CREATE, UPDATE, DELETE to be present in the payload at the -same time. - -### Tracker Ownership Management { #webapi_tracker_ownership_management } - -A new concept called Tracker Ownership is introduced from 2.30. There -will now be one owner organisation unit for a tracked entity instance in -the context of a program. Programs that are configured with an access -level of *PROTECTED* or *CLOSED* will adhere to the ownership -privileges. Only those users belonging to the owning org unit for a -tracked entity-program combination will be able to access the data -related to that program for that tracked entity. - -#### Tracker Ownership Override : Break the Glass { #webapi_tracker_ownership_override_api } - -It is possible to temporarily override this ownership privilege for a -program that is configured with an access level of *PROTECTED*. Any user -will be able to temporarily gain access to the program related data, if -the user specifies a reason for accessing the tracked entity-program -data. This act of temporarily gaining access is termed as *breaking the -glass*. Currently, the temporary access is granted for 3 hours. DHIS2 -audits breaking the glass along with the reason specified by the user. -It is not possible to gain temporary access to a program that has been -configured with an access level of *CLOSED*. To break the glass for a -tracked entity program combination, you can issue a POST request as -shown: - - /api/33/tracker/ownership/override?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care - -#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer_api } - -It is possible to transfer the ownership of a tracked entity-program -from one org unit to another. This will be useful in case of patient -referrals or migrations. Only an owner (or users who have broken the -glass) can transfer the ownership. To transfer ownership of a tracked -entity-program to another organisation unit, you can issue a PUT request -as shown: - - /api/33/tracker/ownership/transfer?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&ou=EJNxP3WreNP - - -## Potential Duplicates { #potential-duplicates } - -Potential duplicates are records we work with in the data deduplication feature. Due to the nature of the deduplication feature, this API endpoint is somewhat restricted. - -A potential duplicate represents a pair of records which are suspected to be a duplicate. - -The payload of a potential duplicate looks like this: - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -You can retrieve a list of potential duplicates using the following endpoint: - - GET /api/potentialDuplicates - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| teis | List of tracked entity instances | List of string (separated by comma)| existing tracked entity instance id | -| status | Potential duplicate status | string | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Status code | Description -|---|---| -| 400 | Invalid input status - -You can inspect individual potential duplicate records: - - GET /api/potentialDuplicates/ - -| Status code | Description -|---|---| -| 404 | Potential duplicate not found - -To create a new potential duplicate, you can use this endpoint: - - POST /api/potentialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Status code | Description -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -To update a potential duplicate status: - - PUT /api/potentialDuplicates/ - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| status | Potential duplicate status | string | `OPEN`, `INVALID`, `MERGED` | - -| Status code | Description -|---|---| -| 400 | You can't update a potential duplicate to MERGED as this is possible only by a merging request -| 400 | You can't update a potential duplicate that is already in a MERGED status - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -To merge a Potential Duplicate, or the two tracked entity instances the Potential Duplicate represents, the following endpoint can be used: - - POST /api/potentialDuplicates//merge - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| mergeStrategy | Strategy to use for merging the potentialDuplicate | enum | AUTO(default) or MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- The same attribute has different values in each tracked entity instance -- Both tracked entity instances are enrolled in the same program -- Tracked entity instances have different types - -If any conflict is encountered, an errormessage is returned to the user. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -When requesting an automatic merge like this, a payload is not required and will be ignored. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Relationship cannot be between the original and the duplicate (This results in an invalid self-referencing relationship) -- Relationship cannot be of the same type and to the same object in both tracked entity instances (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) - -There are two ways to do a manual merge: With and without a payload. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -Otherwise, if a manual merge is requested with a payload, the payload refers to what data should be moved from the duplicate to the original. The payload looks like this: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -The fields are explained in the following table. - - -Table: Program Notification Template payload - -| Field | Required | Description | Values | -|---|---|---|---| -| name | Yes | name of Program Notification Template | case-notification-alert | -| notificationTrigger | Yes | When notification should be triggered. Possible values are ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| ENROLLMENT | -| subjectTemplate | No | Subject template string | Case notification V{org_unit_name} | -| messageTemplate | Yes | Message template string | Case notification A{h5FuguPFF2j} | -| notificationRecipient | YES | Who is going to receive notification. Possible values are USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | No | Which channel should be used for this notification. It can be either SMS, EMAIL or HTTP | SMS | -| sendRepeatable | No | Whether notification should be sent multiple times | false | - -NOTE: WEB_HOOK notificationRecipient is used only to POST http request to an external system. Make sure to choose HTTP delivery channel when using WEB_HOOK. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -The list of Program Notification Templates can be retrieved using GET. - - GET /api/programNotificationTemplates - -For one particular Program Notification Template. - - GET /api/33/programNotificationTemplates/{uid} - -To get filtered list of Program Notification Templates - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Program Notification Template can be deleted using DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -Program message lets you send messages to tracked entity instances, -contact addresses associated with organisation units, phone numbers and -email addresses. You can send messages through the `messages` resource. - - /api/33/messages - -### Sending program messages { #sending-program-messages } - -Program messages can be sent using two delivery channels: - - - SMS (SMS) - - - Email address (EMAIL) - -Program messages can be sent to various recipients: - - - Tracked entity instance: The system will look up attributes of value - type PHONE_NUMBER or EMAIL (depending on the specified delivery - channels) and use the corresponding attribute values. - - - Organisation unit: The system will use the phone number or email - information registered for the organisation unit. - - - List of phone numbers: The system will use the explicitly defined - phone numbers. - - - List of email addresses: The system will use the explicitly defined - email addresses. - -Below is a sample JSON payload for sending messages using POST requests. -Note that message resource accepts a wrapper object named -`programMessages` which can contain any number of program messages. - - POST /api/33/messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -The fields are explained in the following table. - - - -Table: Program message payload - -| Field | Required | Description | Values | -|---|---|---|---| -| recipients | Yes | Recipients of the program message. At least one recipient must be specified. Any number of recipients / types can be specified for a message. | Can be trackedEntityInstance, organisationUnit, an array of phoneNumbers or an array of emailAddresses. | -| programInstance | Either this or programStageInstance required | The program instance / enrollment. | Enrollment ID. | -| programStageInstance | Either this or programInstance required | The program stage instance / event. | Event ID. | -| deliveryChannels | Yes | Array of delivery channels. | SMS | EMAIL | -| subject | No | The message subject. Not applicable for SMS delivery channel. | Text. | -| text | Yes | The message text. | Text. | -| storeCopy | No | Whether to store a copy of the program message in DHIS2. | false (default) | true | - -A minimalistic example for sending a message over SMS to a tracked -entity instance looks like this: - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### Retrieving and deleting program messages { #retrieving-and-deleting-program-messages } - -The list of messages can be retrieved using GET. - - GET /api/33/messages - -To get the list of sent tracker messages, the below endpoint can be used. ProgramInstance or ProgramStageInstance uid has to be provided. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -To get the list of all scheduled message - - GET /api/33/messages/scheduled - GET /api/33/messages/scheduled?scheduledAt=2020-12-12 - -One particular message can also be retrieved using GET. - - GET /api/33/messages/{uid} - -Message can be deleted using DELETE. - - DELETE /api/33/messages/{uid} - - -### Querying program messages { #querying-program-messages } - -The program message API supports program message queries based on -request parameters. Messages can be filtered based on below mentioned -query parameters. All requests should use the GET HTTP verb for -retrieving information. - - - -Table: Query program messages API - -| Parameter | URL | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # Email { #email } diff --git a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md index 7c0b8dfe3..cd13617cf 100644 --- a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-237__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2023-03-22' tags: -- انتظام - DHIS core version 2.37 +- انتظام template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md index c8627b2fa..e4a6174d1 100644 --- a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-239__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-02-16' tags: -- انتظام - DHIS core version 2.39 +- انتظام template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index 80853c82e..54d383903 100644 --- a/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/ur_PK/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- انتظام - DHIS core version master +- انتظام template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index fdd7e4a9d..ca88fed9d 100644 --- a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/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 --- diff --git a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index bc0ac4d6e..5fc7231e7 100644 --- a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/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 --- diff --git a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index a5cf7c4ea..c076f3443 100644 --- a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - استعمال کریں +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index ed676e78c..442e3b083 100644 --- a/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ur_PK/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - استعمال کریں +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/.cache_timestamp b/projects/dhis2-single-page-docs/zh/.cache_timestamp index 54f753bdc..ae920c5c0 100644 --- a/projects/dhis2-single-page-docs/zh/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:28:20Z \ No newline at end of file +2024-06-04T21:28:19Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index 54aac5887..0497a9867 100644 --- a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2023-01-13' tags: -- DHIS core version 2.37 - Develop +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index 5ba6b696a..c6e973471 100644 --- a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index fc2047e39..bd9d4df3b 100644 --- a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index cf15abc96..716d331ed 100644 --- a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 9ed487a80..e095adae4 100644 --- a/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - Develop - DHIS核心 主版 @@ -12216,7 +12216,7 @@ Table: Query parameters for event query analytics only | 查询参数 | 需要 | 描述 | 选项 | |---|---|---|---| -| ouMode | 不 | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | 不 | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | 不 | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | 不 | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | 不 | Whether to only return events which have coordinates. | false | true | @@ -13111,7 +13111,7 @@ Table: Query parameters for enrollment query endpoint | filter | 不 | 维度标识符包括数据元素、属性、期间、组织单位和组织单位组集。参数可以重复任意次数。项目过滤器可以应用于维度，格式为::。过滤器值不区分大小写。 || | programStatus | 不 | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | 不 | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | 不 | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | 不 | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | 不 | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | 不 | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | 不 | Whether to only return enrollments which have coordinates. | false | true | @@ -17822,20 +17822,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17938,7 +17939,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | 不 | 是的 | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | 不 | 不 | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | 不 | 不 | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | 不 | 不 | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | 是的 | 不 | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | 不 | 是的 | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | 不 | 不 | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -17998,9 +17998,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### 属性 { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | 描述 | 需要 | Immutable | 类型 | 例 | |---|---|---|---|---|---| @@ -18015,18 +18017,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | 描述 | 需要 | Immutable | 类型 | 例 | |---|---|---|---|---|---| @@ -18041,31 +18045,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### 笔记 { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -18076,10 +18080,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -18121,92 +18125,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | 描述 | 例 | -|---|---|---| -| 名称 | Name of the working list. Required. || -| 描述 | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | 描述 | 例 | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| 跟进 | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -18215,9 +18134,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -18250,7 +18169,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -18650,7 +18569,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -19096,7 +19015,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -19226,7 +19145,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | 不适用 | Undefined error message. | -### 验证方式 { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -19236,7 +19155,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -19261,8 +19180,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -19315,7 +19234,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -19371,7 +19290,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -19393,7 +19312,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -19427,7 +19346,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -19479,9 +19398,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -19561,8 +19480,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -19668,7 +19587,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19930,8 +19849,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -20136,8 +20055,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -20432,13 +20351,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -20484,7 +20403,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -20553,13 +20472,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -20571,7 +20490,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### 跟踪器所有权优先：打破常规 { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -20584,7 +20503,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### 跟踪器所有权转移 { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -20594,7 +20513,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -20624,7 +20543,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -20640,2766 +20559,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Table: Payload -|Tracker Object|Previously|Now| +| Payload values | 描述 | 例 | |---|---|---| -|**Attribute**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Event**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Note**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Relationship**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribute`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes`|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus`|`enrollmentStatus`| -|`query`|Removed - use `filter` instead| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Previously|Now| -|---|---| -|`enrollment`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus`|`status`| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`event`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`lastUpdated`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus`|`enrollmentStatus`| -|`skipEventId`|Removed| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Previously|Now| -|---|---| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity`| - -## 跟踪器Web API { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### 跟踪实体实例管理 { #webapi_tracked_entity_instance_management } - -跟踪的实体实例在API中具有完整的CRUD支持。一起 -使用API进行注册，需要使用以下大部分操作 -支持跟踪的实体实例和程序。 - - / api / 33 / trackedEntityInstances - -#### 创建一个新的跟踪实体实例 { #webapi_creating_tei } - -要在系统中创建新人员，您将使用 -* trackedEntityInstances *资源。模板有效负载如下所示： - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -字段“ geometry”接受一个GeoJson对象，其中 -GeoJson必须匹配TrackedEntityType的featureType -定义。一个示例GeoJson对象如下所示： - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -“坐标”字段在2.29中引入，并接受一个坐标 -或多边形作为值。 +| 名称 | Name of the working list. Required. || +| 描述 | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Table: Program Stage Query Criteria - / api / trackedEntityInstances +| Criteria values | 描述 | 例 | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| 跟进 | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -例如，让我们创建一个人员跟踪实体的新实例，然后 -指定其名字和姓氏属性： +See an example payload below: ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -要将其推送到服务器，您可以使用cURL命令，如下所示： - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -要在一个请求中创建多个实例，您可以将有效负载包装在 -像这样的外部数组并 POST 到与上面相同的资源：[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -系统不允许创建跟踪实体实例 -（以及注册和事件）具有已在 -系统。这意味着不能重复使用 UID。 - -#### 更新跟踪的实体实例 { #webapi_updating_tei } - -为了更新被跟踪的实体实例，有效载荷等于 -上一节。不同之处在于您必须使用 HTTP *PUT* -发送有效负载时请求的方法。您还需要 -将人员标识符附加到 *trackedEntityInstances* 资源中 -像这样的 URL，其中 `` 应该 -被跟踪实体实例的标识符替换： - - / api / trackedEntityInstances / - -有效载荷必须包含所有，甚至未修改的属性和 -关系。之前和之前存在的属性或关系 -不再存在于当前有效载荷中，将从中删除 -系统。这意味着如果属性/关系在 -当前有效负载，所有现有的属性/关系都将被删除 -从系统。从 2.31 开始，可以忽略空 -当前有效负载中的属性/关系。一个请求参数 -`ignoreEmptyCollection` 设置为 `true` 可以在你不这样做的情况下使用 -希望发送任何属性/关系，也不想要它们 -要从系统中删除。 - -不允许更新已删除的跟踪实体实例。 -此外，不允许通过以下方式将跟踪的实体实例标记为已删除 -更新请求。相同的规则适用于注册和活动。 - -#### 删除跟踪的实体实例 { #webapi_deleting_tei } - -为了删除跟踪的实体实例，向 URL 发出请求 -使用 *DELETE* 标识被跟踪的实体实例 -方法。 URL 等于上面用于更新的 URL。 - -#### 创建并注册跟踪的实体实例 { #webapi_create_enroll_tei } - -也可以创建（和更新）一个被跟踪的实体 -实例，同时注册一个程序。 - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -您可以像通常在创建或 -更新一个新的跟踪实体实例。 - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### 有效负载的完整示例包括：跟踪的实体实例，注册和事件 { #webapi_create_enroll_tei_create_event } - -也可以创建（和更新）一个被跟踪的实体实例，在 -同时注册一个程序并创建一个事件。 - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute":"cejWyOfXge6", - "value":"Male" - } - ], - "enrollments":[ - { - "orgUnit":"DiszpKrYNg8", - "program":"ur1Edk5Oe2n", - "enrollmentDate":"2017-09-15", - "incidentDate":"2017-09-15", - "events":[ - { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues": [ - { - "dataElement":"qrur9Dvnyt5", - "value":"22" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Male" - } - ] - }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues":[ - { - "dataElement":"qrur9Dvnyt5", - "value":"26" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Female" - } - ] - } - ] - } - ] + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -您可以像通常在创建或 -更新一个新的跟踪实体实例。 - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### 生成的跟踪实体实例属性 { #webapi_generate_tei_attributes } - -使用自动生成的跟踪实体实例属性 -唯一值具有应用程序使用的三个端点。端点 -都用于生成和保留值。 - -在 2.29 中，我们引入了 TextPattern 来定义和生成这些 -模式。所有现有模式都将转换为有效的 TextPattern -升级到 2.29 时。 - -> **注意** -> -> 自 2.29 起，所有这些端点都将要求您包括任何 -> `requiredValues` 端点报告的变量被列为 -> 需要。现有模式，仅由`#` 组成，将被升级 -> 到新的 TextPattern 语法`RANDOM()`。随机 -> TextPattern 的段不是必需的变量，所以这个 -> 对于 2.29 之前定义的模式，端点将像以前一样工作。 - -##### 寻找所需的值 { #finding-required-values } - -TextPattern 可以包含根据不同的变量而变化的变量 -因素。其中一些因素对服务器来说是未知的，因此 -这些变量的值必须在生成和 -保留值。 - -此端点将返回必需值和可选值的映射，即 -服务器将在生成新值时注入 TextPattern。 -必须为生成提供必需的变量，但可选 -仅当您知道自己在做什么时才应提供变量。 - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### 产生价值终点 { #webapi_generate_values } - -在线 Web 应用程序和其他希望产生价值的客户 -将立即使用可以使用简单的生成端点。这 -端点将生成一个值，该值保证在 -世代时间。该值也保证不被保留。作为 -2.29，此端点还将保留生成的值 3 天。 - -如果您的 TextPattern 包含必需的值，您可以将它们作为 -参数如下例： - -过期时间也可以在生成时被覆盖，通过 -将 `?expiration= ` 添加到请求中。 - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### 产生并保留价值终点 { #webapi_generate_reserve_values } - -生成和保留端点由需要的离线客户端使用 -能够注册具有唯一 ID 的跟踪实体。他们会 -保留一些唯一的 ID，此设备将在以下情况下使用 -注册新的跟踪实体实例。端点被称为 -检索多个跟踪的实体实例保留值。一个 -可选参数 numberToReserve 指定要生成多少个 id -（默认值为 1）。 - -如果您的 TextPattern 包含必需的值，您可以将它们作为 -参数如下例： - -与 /generate 端点类似，该端点也可以指定 -过期时间同理。通过添加`?expiration=` -您可以覆盖默认的 60 天。 - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### 保留值 { #reserved-values } - -目前无法通过 api 访问保留值，但是，它们 -由`generate` 和`generateAndReserve` 端点返回。这 -下表解释了保留值对象的属性： - -##### - - - -Table: Reserved values - -| Property | 描述 | -|---|---| -| ownerObject | The metadata type referenced when generating and reserving the value. Currently only TRACKEDENTITYATTRIBUTE is supported. | -| ownerUid | The uid of the metadata object referenced when generating and reserving the value. | -| key | A partially generated value where generated segments are not yet added. | -| 价值 | The fully resolved value reserved. This is the value you send to the server when storing data. | -| created | The timestamp when the reservation was made | -| expiryDate | The timestamp when the reservation will no longer be reserved | - -过期的预订每天都会被删除。如果模式发生变化，则值 -存储数据时将接受已经保留的数据，即使 -它们与新模式不匹配，只要预订没有 -已到期。 - -#### 图片属性 { #image-attributes } - -处理图像属性很像处理文件数据 -值。具有图像值类型的属性的值是 -关联的文件资源。一个 GET 请求 -`/api/trackedEntityInstances/ / /image` -端点将返回实际图像。可选的高度和宽度 -参数可用于指定图像的尺寸。 - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### 跟踪实体实例查询 { #webapi_tracked_entity_instance_query } - -要查询跟踪的实体实例，您可以与 -`/api/trackedEntityInstances` 资源。 - - / api / 33 / trackedEntityInstances - -##### 请求语法 { #webapi_tei_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| 查询参数 | 描述 | -|---|---| -| filter | 用作查询过滤器的属性。参数可以重复任意次。过滤器可以应用于格式为 ::[::].维度过滤器值不区分大小写，可以与运算符一起重复任意次数。运算符可以是 EQ | GT |通用电气| LT |乐| NE |喜欢 |在。 | -| 欧 | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| 跟进 | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Indicates whether to include soft deleted teis or not. It is false by default. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -可用的组织单元选择模式在 -下表。 - - - -Table: Organisation unit selection modes - -| Mode | 描述 | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | The selected organisation units and the immediate children, i.e. the organisation units at the level below. | -| DESCENDANTS | The selected organisation units and all children, i.e. all organisation units in the sub-hierarchy. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| 全部 | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -The available assigned user modes are explained in the following table. - - - -Table: Assigned user modes - -| Mode | 描述 | -|---|---| -| CURRENT | Includes events assigned to the current logged in user. | -| PROVIDED | Includes events assigned to the user provided in the request. | -| NONE | Includes unassigned events only. | -| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | - -查询不区分大小写。以下规则适用于查询 -参数。 - - - 必须使用 *ou* 指定至少一个组织单位 - 参数（一个或多个）或 *ouMode=ALL* 必须指定。 - - - 只能使用 *program* 和 *trackedEntity* 参数之一 - 指定（零或一）。 - - - 如果指定了 *programStatus* 那么 *program* 也必须是 - 指定的。 - - - 如果指定了 *followUp*，则还必须指定 *program*。 - - - 如果指定了 *programStartDate* 或 *programEndDate*，则 - *程序* 也必须指定。 - - - 过滤器项目只能指定一次。 - -查询与特定组织单位关联的所有实例 -看起来像这样： - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -使用一个带有过滤器的属性和一个属性来查询实例 -没有过滤器的属性，一个组织单位使用 -后代组织单位查询方式： - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - ＆filter = AMpUYgxuCaE＆ou = DiszpKrYNg8; yMCshbaVExv - -对响应中包含一个属性的实例的查询 -并且一个属性被用作 - 筛选： - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - ＆filter = AMpUYgxuCaE：LIKE：Road＆ou = DiszpKrYNg8 - -为过滤器指定了多个操作数和过滤器的查询 -物品： - - api / 33 / trackedEntityInstances.json？ou = DiszpKrYNg8＆program = ur1Edk5Oe2n - ＆filter = lw1SqmMlnfh：GT：150：LT：190 - -要在 *IN* 过滤器中使用多个值查询属性： - - api / 33 / trackedEntityInstances.json？ou = DiszpKrYNg8 - ＆filter = dv3nChNSIxy：IN：Scott; Jimmy; Santiago - -限制对属于特定事件一部分的实例的响应 -program 你可以包含一个 program 查询参数： - - api / 33 / trackedEntityInstances.json？filter = zHXD5Ve1Efw：EQ：A＆ou = O6uvpzGd5pu - ＆ouMode = DESCENDANTS＆program = ur1Edk5Oe2n - -要将程序注册日期指定为查询的一部分，请执行以下操作： - - api / 33 / trackedEntityInstances.json？filter = zHXD5Ve1Efw：EQ：A＆ou = O6uvpzGd5pu - ＆program = ur1Edk5Oe2n＆programStartDate = 2013-01-01＆programEndDate = 2013-09-01 - -要限制对特定跟踪实体实例的响应，您 -可以包含跟踪实体查询参数： - - api / 33 / trackedEntityInstances.json？filter = zHXD5Ve1Efw：EQ：A＆ou = O6uvpzGd5pu - ＆ouMode = DESCENDANTS＆trackedEntity = cyl5vuJ5ETQ - -默认情况下，实例以大小为 50 的页面返回，以更改 -您可以使用 page 和 pageSize 查询参数： - - api / 33 / trackedEntityInstances.json？filter = zHXD5Ve1Efw：EQ：A＆ou = O6uvpzGd5pu - ＆ouMode = DESCENDANTS＆page = 2＆pageSize = 3 - -您可以使用一系列运算符进行过滤： - - - -Table: Filter operators - -| Operator | 描述 | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### 回应格式 { #webapi_tei_query_response_format } - -此资源支持 JSON、JSONP、XLS 和 CSV 资源 -表示。 - - - json（应用程序/ json） - - - jsonp（应用程序/ javascript） - - - xml（应用程序/ xml） - -JSON/XML 中的响应采用对象格式，看起来像 -下列的。请注意，支持字段过滤，所以如果你想 -一个完整的视图，您可能希望将 `fields=*` 添加到查询中： - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### 跟踪实体实例网格查询 { #webapi_tracked_entity_instance_grid_query } - -要查询跟踪的实体实例，您可以与 -*/api/trackedEntityInstances/grid* 资源。有两种类型 -查询：其中一个 *query* 查询参数和可选的 *attribute* -参数已定义，其中 *attribute* 和 *filter* -定义了参数。此端点使用更紧凑的“网格”格式， -并且是上一节中查询的替代方法。 - - / api / 33 / trackedEntityInstances / query - -##### 请求语法 { #webapi_tei_grid_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| 查询参数 | 描述 | -|---|---| -| query | Query string. Attribute query parameter can be used to define which attributes to include in the response. If no attributes but a program is defined, the attributes from the program will be used. If no program is defined, all attributes will be used. There are two formats. The first is a plan query string. The second is on the format :. Operators can be EQ | LIKE. EQ implies exact matches on words, LIKE implies partial matches on words. The query will be split on space, where each word will form a logical AND query. | -| attribute | 要包含在响应中的属性。也可以用作查询的过滤器。参数可以重复任意次。过滤器可以应用于格式为 ::[::].维度过滤器值不区分大小写，可以与运算符一起重复任意次数。运算符可以是 EQ | GT |通用电气| LT |乐| NE |喜欢 |在。可以省略过滤器，以便在没有任何约束的情况下简单地在响应中包含属性。 | -| filter | 用作查询过滤器的属性。参数可以重复任意次。过滤器可以应用于格式为 ::[::].维度过滤器值不区分大小写，可以与运算符一起重复任意次数。运算符可以是 EQ | GT |通用电气| LT |乐| NE |喜欢 |在。 | -| 欧 | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| 跟进 | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| eventStatus | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Start date of event associated with the given program and event status. | -| eventEndDate | End date of event associated with the given program and event status. | -| programStage | The programStage for which the event related filters should be applied to. If not provided all stages will be considered. | -| skipMeta | Indicates whether meta data for the response should be included. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -可用的组织单元选择模式在 -下表。 - - - -Table: Organisation unit selection modes - -| Mode | 描述 | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| CAPTURE | The data capture organisation units associated with the current user and all children, i.e. all organisation units in the sub-hierarchy. | -| 全部 | All organisation units in the system. Requires `ALL` authority. | - -请注意，您可以使用过滤器指定“属性”或直接使用“过滤器”参数来限制 -实例返回。 - -某些规则适用于返回的属性。 - - - 如果在没有任何属性或程序的情况下指定“查询”，则所有属性 - 标记为“在没有程序的列表中显示”包含在响应中。 - - - 如果指定了程序，则链接到该程序的所有属性都将 - 包含在响应中。 - - - 如果指定了被跟踪实体类型，则所有被跟踪实体类型属性 - 将包含在响应中。 - -您可以使用由空格分隔的单词来指定查询 - 即 -情况系统会独立查询每个单词并返回 -每个词都包含在任何属性中的记录。一个查询项可以 -一次指定为属性，一次指定为过滤器（如果需要）。这 -查询不区分大小写。以下规则适用于查询 -参数。 - - - 必须使用 *ou* 指定至少一个组织单位 - 参数（一个或多个）或 *ouMode=ALL* 必须指定。 - - - 只能使用 *program* 和 *trackedEntity* 参数之一 - 指定（零或一）。 - - - 如果指定了 *programStatus* 那么 *program* 也必须是 - 指定的。 - - - 如果指定了 *followUp*，则还必须指定 *program*。 - - - 如果指定了 *programStartDate* 或 *programEndDate*，则 - *程序* 也必须指定。 - - - 如果指定了 *eventStatus*，则 *eventStartDate* 和 - *eventEndDate* 也必须指定。 - - - 不能与过滤器一起指定查询。 - - - 属性项目只能指定一次。 - - - 过滤器项目只能指定一次。 - -查询与特定组织单位关联的所有实例 -看起来像这样： - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -查询特定值和组织单位的所有属性， -使用精确的单词匹配： - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -使用部分词查询特定值的所有属性 -比赛： - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -您可以查询由 URL 字符分隔的多个单词 -空间为 %20，将对每个空间使用逻辑 AND 查询 - 单词： - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -指定要包含在响应中的属性的查询： - - /api/33/trackedEntityInstances/query.json?query=isabel - ＆attribute = dv3nChNSIxy＆attribute = AMpUYgxuCaE＆ou = DiszpKrYNg8 - -使用一个带有过滤器的属性和一个属性来查询实例 -没有过滤器的属性，一个组织单位使用 -后代组织单位查询方式： - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - ＆attribute = AMpUYgxuCaE＆ou = DiszpKrYNg8; yMCshbaVExv - -对响应中包含一个属性的实例的查询 -并且一个属性被用作 - 筛选： - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - ＆filter = AMpUYgxuCaE：LIKE：Road＆ou = DiszpKrYNg8 - -为过滤器指定了多个操作数和过滤器的查询 -物品： - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - ＆filter = lw1SqmMlnfh：GT：150：LT：190 - -使用 IN 中的多个值查询属性 - 筛选： - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - ＆attribute = dv3nChNSIxy：IN：Scott; Jimmy; Santiago - -限制对属于特定事件一部分的实例的响应 -program 你可以包含一个 program 查询参数： - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - ＆ou = O6uvpzGd5pu＆ouMode = DESCENDANTS＆program = ur1Edk5Oe2n - -要将程序注册日期指定为查询的一部分，请执行以下操作： - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - ＆ou = O6uvpzGd5pu＆program = ur1Edk5Oe2n＆programStartDate = 2013-01-01 - ＆programEndDate = 2013-09-01 - -要限制对特定跟踪实体实例的响应，您 -可以包含跟踪实体查询参数： - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - ＆ou = O6uvpzGd5pu＆ouMode = DESCENDANTS＆trackedEntity = cyl5vuJ5ETQ - -默认情况下，实例以大小为 50 的页面返回，以更改 -您可以使用 page 和 pageSize 查询参数： - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - ＆ou = O6uvpzGd5pu＆ouMode = DESCENDANTS＆page = 2＆pageSize = 3 - -查询具有给定状态的事件的实例 -给定的时间跨度： - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -您可以使用一系列运算符进行过滤： - - - -Table: Filter operators - -| Operator | 描述 | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### 回应格式 { #webapi_tei_grid_query_response_format } - -此资源支持 JSON、JSONP、XLS 和 CSV 资源 -表示。 - - - json（应用程序/ json） - - - jsonp（应用程序/ javascript） - - - xml（应用程序/ xml） - - - csv（应用程序/ csv） - - - xls（application / vnd.ms-excel） - -JSON 中的响应采用表格格式，看起来像 -下列的。 *headers* 部分描述了每列的内容。 -实例、创建、上次更新、组织单位和跟踪实体列 -总是存在。以下列对应属性 -在查询中指定。 *rows* 部分包含一行 -实例。 - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### 跟踪实体实例过滤器 { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - / api / 33 / trackedEntityInstanceFilters - -##### 创建和更新跟踪的实体实例过滤器定义 { #create-and-update-a-tracked-entity-instance-filter-definition } - -用于创建和更新跟踪实体实例过滤器 -系统，您将使用 *trackedEntityInstanceFilters* -资源。跟踪实体实例过滤器定义用于 -Tracker Capture 应用程序显示相关的预定义“工作列表” -跟踪器用户界面。 - - - -Table: Payload - -| Payload values | 描述 | 例 | -|---|---|---| -| 名称 | Name of the filter. Required. || -| 描述 | A description of the filter. || -| sortOrder | The sort order of the filter. Used in Tracker Capture to order the filters in the program dashboard. || -| style | Object containing css style. | ( "color": "blue", "icon": "fa fa-calendar"} | -| program | Object containing the id of the program. Required. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Table: Entity Query Criteria definition - -|||| -|---|---|---| -| attributeValueFilters | A list of attributeValueFilters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| enrollmentStatus | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | When this parameter is true, the filter only returns TEIs that have an enrollment with status followup. || -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayColumnOrder | To specify the output ordering of columns | "displayOrderColumns": ["enrollmentDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus | Any valid EventStatus | "eventStatus": "COMPLETED" | -| programStage | To specify a programStage uid to filter on. TEIs will be filtered based on presence of enrollment in the specified program stage.| "programStage"="a3kGcGDCuk6" | -| trackedEntityType | To specify a trackedEntityType filter TEIs on. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | To specify a list of trackedEntityInstances to use when querying TEIs. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod object date filtering based on enrollment incident date. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod object date filtering based on enrollment created date. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Table: Event filters definition - -|||| -|---|---|---| -| programStage | Which programStage the TEI needs an event in to be returned. | "eaDH9089uMp" | -| eventStatus | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT (events assigned to current user)| PROVIDED (events assigned to users provided in "assignedUsers" list) | NONE (events assigned to no one) | ANY (events assigned to anyone). If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| 开始日期 | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| 结束日期 | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -Table: Period definition - -|||| -|---|---|---| -| periodFrom | Number of days from current day. Can be positive or negative integer. | -15 | -| periodTo | Number of days from current day. Must be bigger than periodFrom. Can be positive or negative integer. | 15 | - -##### 跟踪实体实例过滤器查询 { #tracked-entity-instance-filters-query } - -要在系统中查询被跟踪实体实例过滤器，您可以 -与 */api/trackedEntityInstanceFilters* 资源交互。 - - - -Table: Tracked entity instance filters query parameters - -| 查询参数 | 描述 | -|---|---| -| program | Program identifier. Restricts filters to the given program. | - -### 招生管理 { #webapi_enrollment_management } - -注册在 API 中具有完整的 CRUD 支持。与 API 一起 -对于跟踪的实体实例，使用所需的大多数操作 -支持被跟踪的实体实例和程序。 - - / api / 33 /注册 - -#### 将跟踪的实体实例注册到程序中 { #webapi_enrolling_tei } - -要让人员加入计划，您首先需要获得 -*trackedEntityInstances* 资源中人员的标识符。 -然后，您需要从 *programs* 中获取程序标识符 -资源。模板有效负载如下所示： - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -此有效负载应在对注册的 *POST* 请求中使用 -由以下 URL 标识的资源： - - / api / 33 /注册 - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - / api / 33 / enrollments / /取消 - -要完成被跟踪实体实例的注册，您可以创建一个 -*PUT* 请求到以下 URL： - - / api / 33 / enrollments / /已完成 - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - / api / 33 / enrollments / - -#### 注册实例查询 { #webapi_enrollment_instance_query } - -要查询注册，您可以与 */api/enrollments* 交互 -资源。 - - / api / 33 /注册 - -##### 请求语法 { #webapi_enrollment_query_request_syntax } - - - -Table: Enrollment query parameters - -| 查询参数 | 描述 | -|---|---| -| 欧 | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| 跟进 | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| trackedEntityInstance | Tracked entity instance identifier. Should not be used together with trackedEntity. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| includeDeleted | Indicates whether to include soft deleted enrollments or not. It is false by default. | - -可用的组织单元选择模式在 -下表。 - - - -Table: Organisation unit selection modes - -| Mode | 描述 | -|---|---| -| SELECTED | Organisation units defined in the request (default). | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| 全部 | All organisation units in the system. Requires `ALL` authority. | - -查询不区分大小写。以下规则适用于查询 -参数。 - - - 必须使用 *ou* 指定至少一个组织单位 - 参数（一个或多个）或 *ouMode=ALL* 必须指定。 - - - 只能使用 *program* 和 *trackedEntity* 参数之一 - 指定（零或一）。 - - - 如果指定了 *programStatus* 那么 *program* 也必须是 - 指定的。 - - - 如果指定了 *followUp*，则还必须指定 *program*。 - - - 如果指定了 *programStartDate* 或 *programEndDate*，则 - *程序* 也必须指定。 - -查询与特定组织单位关联的所有注册 -看起来像这样： - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -限制对作为特定活动一部分的注册的响应 -程序，您可以包含程序查询 - 范围： - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -要将程序注册日期指定为查询的一部分，请执行以下操作： - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - ＆programStartDate = 2013-01-01＆programEndDate = 2013-09-01 - -限制对特定被跟踪实体的注册的响应 -您可以包含跟踪实体查询 - 范围： - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -限制对特定被跟踪实体的注册的响应 -例如，您可以包含一个跟踪实体实例查询参数，在 -在这种情况下，我们已将其限制为可查看的可用注册 -当前的 - 用户： - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -默认情况下，注册以 50 页大小的页面返回，以更改 -这您可以使用 page 和 pageSize 查询 - 参数： - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### 回应格式 { #webapi_enrollment_query_response_format } - -此资源支持 JSON、JSONP、XLS 和 CSV 资源 -表示。 - - - json（应用程序/ json） - - - jsonp（应用程序/ javascript） - - - xml（应用程序/ xml） - -JSON/XML 中的响应采用对象格式，看起来像 -下列的。请注意，支持字段过滤，所以如果你想 -一个完整的视图，您可能希望将 `fields=*` 添加到查询中： - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### 大事记 { #webapi_events } - -本节关于发送和读取事件。 - - / api / 33 / events - -The different status of an event are: - -* **ACTIVE**: If a event has ACTIVE status, it is possible to edit the event details. COMPLETED events can be turned ACTIVE again and vice versa. -* **COMPLETED**: An event change the status to COMPLETED only when a user clicks the complete button. If a event has COMPLETED status, it is not possible to edit the event details. ACTIVE events can be turned COMPLETED again and vice versa. -* **SKIPPED**: Scheduled events that no longer need to happen. In Tracker Capture, there is a button for that. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### 发送事件 { #webapi_sending_events } - -DHIS2 支持三种事件： 没有注册的单一事件 -（也称为匿名事件），注册的单一事件 -和多个注册的事件。注册意味着 -数据链接到使用标识的跟踪实体实例 -某种标识符。 - -要将事件发送到 DHIS2，您必须与 *events* 资源进行交互。 -发送事件的方法类似于发送聚合数据 -值。您将需要一个*程序*，可以使用 -*programs* 资源，一个 *orgUnit*，可以使用 -*organisationUnits* 资源，以及有效数据元素的列表 -可以使用 *dataElements* 资源查找的标识符。 -对于注册的事件，*跟踪实体实例*标识符是 -需要，请在有关 -*trackedEntityInstances* 资源。用于向程序发送事件 -多个阶段，您还需要包括 *programStage* -标识符，programStages 的标识符可以在 -*programStages* 资源。 - -XML 格式的没有注册示例有效负载的简单单个事件 -我们从“住院发病率和死亡率”发送事件的地方 -可以看到演示数据库中“Ngelehun CHC”设施的程序 -以下： - -```xml - - - - - - - - - -``` - -为了执行一些测试，我们可以将 XML 负载保存为文件 -调用*event.xml* 并将其作为 POST 请求发送到事件资源 -在 API 中使用 curl 和以下命令： - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -JSON格式的相同负载如下所示： - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -要发送它，您可以将其保存到一个名为 *event.json* 的文件中并使用 curl -像这样： - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -我们还支持同时发送多个事件。一个有效载荷 -XML 格式可能如下所示： - -```xml - - - - - - - - - - - - - - - - - -``` - -您将收到一份包含回复的导入摘要，该回复可以是 -检查以获取有关请求结果的信息， -比如成功导入了多少值。 JSON 格式的负载 -格式如下： - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -您还可以使用GeoJson在事件上存储任何类型的几何图形。在此处可以看到使用GeoJson代替以前的经度和纬度属性的有效负载示例： - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -作为导入摘要的一部分，您还将获得标识符 -*引用*您刚刚发送的事件，以及一个 *href* 元素 -指向此事件的服务器位置。下表 -描述每个元素的含义。 - - - -Table: Events resource format - -| Parameter | 类型 | 需要 | 选项（默认为默认） | 描述 | -|---|---|---|---|---| -| program | string | 真正 || Identifier of the single event with no registration program | -| orgUnit | string | 真正 || Identifier of the organisation unit where the event took place | -| eventDate | date | 真正 || The date of when the event occurred | -| completedDate | date | 假 || The date of when the event is completed. If not provided, the current date is selected as the event completed date | -| status | enum | 假 | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Whether the event is complete or not | -| storedBy | string | 假 | Defaults to current user | Who stored this event (can be username, system-name, etc) | -| coordinate | double | 假 || Refers to where the event took place geographically (latitude and longitude) | -| dataElement | string | 真正 || Identifier of data element | -| 价值 | string | 真正 || Data value or measure for this event | - -##### OrgUnit匹配 { #orgunit-matching } - -默认情况下，orgUnit 参数将匹配 -ID，您还可以使用 orgUnit id 匹配方案选择 -参数 orgUnitIdScheme=SCHEME，其中选项为：*ID*、*UID*、 -*UUID*、*CODE* 和 *NAME*。还有 *ATTRIBUTE:* 方案，它 -匹配*唯一*元数据属性值。 - -#### 更新事件 { #webapi_updating_events } - -要更新现有事件，有效负载的格式是相同的，但是 -您要发布到的 URL 必须将标识符添加到 URL 的末尾 -字符串并且请求必须是 PUT。 - -有效载荷必须包含所有属性，即使是未修改的属性。 -以前存在但现在不存在的属性 -系统将删除任何更多的有效载荷。 - -不允许更新已删除的事件。同样适用 -跟踪实体实例和注册。 - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### 删除活动 { #webapi_deleting_events } - -要删除现有事件，您只需要发送 DELETE 请求 -带有对您正在使用的服务器的标识符引用。 - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### 为用户分配事件 { #webapi_user_assign_event } - -可以将用户分配给事件。这可以通过在更新或创建事件时在有效负载中包含适当的属性来完成。 - - “ assignedUser”：“ ” - -id是指用户的if。一次只能为一个事件分配一个用户。 - -必须先在程序阶段启用用户分配，然后才能将用户分配给事件。 -#### 获取事件 { #webapi_getting_events } - -要获取现有事件，您可以发出 GET 请求，包括 -像这样的标识符： - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### 查询和阅读事件 { #webapi_querying_reading_events } - -本节说明如何读出已存储的事件 -在 DHIS2 实例中。有关事件数据的更高级用途，请 -请参阅事件分析部分。从输出格式 -`/api/events` 端点将匹配用于发送事件的格式 -到它（分析事件 api 不支持）。 XML 和 -支持 JSON，可以通过添加 .json/.xml 或通过设置 -适当的*接受*标题。查询默认分页， -默认页面大小为 50 个事件，*field* 过滤的工作原理与 -元数据，添加 *fields* 参数并包含您想要的属性， -即 *?fields=program,status*。 - - - -Table: Events resource query parameters - -| 键 | 类型 | 需要 | 描述 | -|---|---|---|---| -| program | identifier | true (if not programStage is provided) | Identifier of program | -| programStage | identifier | 假 | Identifier of program stage | -| programStatus | enum | 假 | Status of event in program, ca be ACTIVE | COMPLETED | CANCELLED | -| 跟进 | boolean | 假 | Whether event is considered for follow up in program, can be true | false or omitted. | -| trackedEntityInstance | identifier | 假 | Identifier of tracked entity instance | -| orgUnit | identifier | 真正 | Identifier of organisation unit | -| ouMode | enum | 假 | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| 开始日期 | date | 假 | Only events newer than this date | -| 结束日期 | date | 假 | Only events older than this date | -| status | enum | 假 | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | date | 假 | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | date | 假 | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | string | 假 | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta | boolean | 假 | Exclude the meta data part of response (improves performance) | -| page | 整数 | 假 | Page number | -| pageSize | 整数 | 假 | Number of items in each page | -| totalPages | boolean | 假 | Indicates whether to include the total number of pages in the paging response. | -| skipPaging | boolean | 假 | Indicates whether to skip paging in the query and return all events. | -| 数据元素标识方案 | string | 假 | Data element ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme | string | 假 | Category Option Combo ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| orgUnitIdScheme | string | 假 | Organisation Unit ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| 程序标识方案 | string | 假 | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| 程序阶段标识方案 | string | 假 | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| 方案 | string | 假 | Allows to set id scheme for data element, category option combo, orgUnit, program and program stage at once. | -| order | string | 假 | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| event | comma delimited string | 假 | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | boolean | 假 | Skips event identifiers in the response | -| attributeCc (\*\*) | string | 假 | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | string | 假 | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | false | true | 假 | Indicates whether the import should be done asynchronous or synchronous. | -| includeDeleted | boolean | 假 | When true, soft deleted events will be included in your query result. | -| assignedUserMode | enum | 假 | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | comma delimited strings | 假 | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> **注意** -> ->如果查询既不包含`attributeCC`也不包含`attributeCos`，则服务器将为用户具有读取访问权限的所有属性选项组合返回事件。 - -##### 例子 { #examples } - -查询具有特定组织单位的子级的所有事件： - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -查询某个组织的所有后代的所有事件 -单位，暗示子层次结构中的所有组织单位： - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -使用特定程序和组织单位查询所有事件： - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -查询具有一定节目和组织单位的所有事件， -按截止日期排序 - 上升： - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -查询某节目中活动日期最新的10个活动 -和组织单位 - 按到期日降序分页和排序： - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - ＆order = eventDate：desc＆pageSize = 10＆page = 1 - -查询具有特定节目和组织单位的所有事件 -特定的跟踪实体实例： - - /api/33/events.json?orgUnit=DiszpKrYNg8 - ＆program = eBAyeGv0exc＆trackedEntityInstance = gfVxE3ALA9m - -查询某个程序和组织单位较旧的所有事件 -或等于 - 2014-02-03： - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -查询具有一定节目阶段、组织单位和 -2014年被跟踪实体实例： - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - ＆trackedEntityInstance = gfVxE3ALA9m＆startDate = 2014-01-01＆endDate = 2014-12-31 - -与事件数据值关联的查询文件。在获取图像文件的特定情况下 -可以提供附加参数来获取不同尺寸的图像。如果维度是 -未提供，系统将返回原图。在以下情况下将忽略该参数 -获取非图像文件，例如 pdf。可能的尺寸值为 *small(254 x 254)， -中 (512 x 512)、大 (1024 x 1024) 或原始*。除了提到的那些值之外的任何值都将是 -丢弃并返回原始图像。 - - / api / 33 / events / files？eventUid = hcmcWlYkg9u＆dataElementUid = C0W4aFuVm4P＆dimension = small - -检索具有指定组织单位和程序的事件，并使用 _Attribute:Gq0oWTf2DtN_ 作为 -标识符方案 - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -检索具有指定组织单位和程序的事件，并使用 UID 作为标识符方案 -orgUnits，代码作为程序阶段的标识符方案，以及 _Attribute:Gq0oWTf2DtN_ 作为标识符 -具有指定属性的其余元数据的方案。 - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=属性：Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=代码 - -#### 事件网格查询 { #event-grid-query } - -除了上面的事件查询端点，还有一个事件网格 -查询终点，其中更紧凑的“网格”事件格式 -回。这可以通过与 -/api/events/query.json|xml|xls|csv 端点。 - - / api / 33 / events / query - -事件查询和读取中提到的大部分查询参数 -上面的部分在此处有效。但是，由于要返回的网格 -带有适用于所有行（事件）的特定列集，它 -必须指定程序阶段。混合是不可能的 -来自不同程序或程序阶段的事件返回。 - -从单个程序阶段返回事件，也为新的事件打开 -功能 - 例如根据事件对事件进行排序和搜索 -数据元素值。 api/events/query 对此有支持。以下是 -一些例子 - -返回仅包含选定数据元素的事件网格的查询 -对于一个程序阶段 - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - ＆dataElement = qrur9Dvnyt5，fWIAEtYVEGk，K6uUAvq500H＆order = lastUpdated：desc - ＆pageSize = 50＆page = 1＆totalPages = true - -返回包含所有数据元素的事件网格的查询 -程序 - 阶段 - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - ＆includeAllDataElements = true - -基于数据元素过滤事件的查询 - 价值 - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - ＆filter = qrur9Dvnyt5：GT：20：LT：50 - -除了过滤，上面的例子还说明了一个 -事情：没有提到要返回的数据元素的事实 -在网格中。发生这种情况时，系统默认返回只返回 -在程序阶段标记为“在报告中显示”的那些数据元素 -配置。 - -我们还可以扩展上面的查询以返回一个排序的网格（asc|desc） -基于数据元素 - 价值 - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - ＆filter = qrur9Dvnyt5：GT：20：LT：50＆order = qrur9Dvnyt5：desc - -#### 事件过滤器 { #webapi_event_filters } - -要创建、读取、更新和删除事件过滤器，您 -可以与`/api/eventFilters` 资源交互。 - - / api / 33 / eventFilters - -##### 创建和更新事件过滤器定义 { #create-and-update-an-event-filter-definition } - -用于创建和更新事件过滤器 -系统，您将使用 *eventFilters* -资源。 *POST* 用于创建，*PUT* 方法用于更新。事件过滤器定义用于 -Tracker Capture 应用程序显示相关的预定义“工作列表” -跟踪器用户界面。 - - - -Table: Request Payload - -| Request Property | 描述 | 例 | -|---|---|---| -| 名称 | Name of the filter. | "name":"My working list" | -| 描述 | A description of the filter. | "description":"for listing all events assigned to me". | -| program | The uid of the program. | "program" : "a3kGcGDCuk6" | -| programStage | The uid of the program stage. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Object containing parameters for querying, sorting and filtering events. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Table: Event Query Criteria definition - -|||| -|---|---|---| -| 跟进 | Used to filter events based on enrollment followUp flag. Possible values are true|false. | "followUp": true | -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | To specify the output ordering of columns | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| dataFilters | To specify filters to be applied when listing events | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| status | Any valid EventStatus | "eventStatus": "COMPLETED" | -| events | To specify list of events | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod object date filtering based on completed date. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod object date filtering based on due date. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| 开始日期 | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| 结束日期 | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -可用的分配用户选择模式在 -下表。 - - - -Table: Assigned user selection modes (event assignment) - -| Mode | 描述 | -|---|---| -| CURRENT | Assigned to the current logged in user | -| PROVIDED | Assigned to the users provided in the "assignedUser" parameter | -| NONE | Assigned to no users. | -| ANY | Assigned to any users. | - -下面显示了可用于创建/更新eventFilter的示例有效负载。 - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### 检索和删除事件过滤器 { #retrieving-and-deleting-event-filters } - -可以使用以下api检索特定的事件过滤器 - - GET /api/33/eventFilters/{uid} - -可以使用以下api检索所有事件过滤器。 - - GET /api/33/eventFilters?fields=* - -可以使用以下api检索特定程序的所有事件过滤器 - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -可以使用以下API删除事件过滤器 - - 删除/ api / 33 / eventFilters / {uid} - -### 人际关系 { #relationships } -关系是跟踪器中两个实体之间的链接。这些实体可以跟踪实体实例，注册和事件。 - -有多个端点，可让您查看，创建，删除和更新关系。最常见的是/ api / trackedEntityInstances端点，您可以在其中将关系包括在有效负载中以创建，更新或删除它们（如果忽略它们）-类似于在同一端点中处理注册和事件的方式。如果在字段过滤器中请求，所有跟踪器端点，/ api / trackedEntityInstances，/ api / enrollments和/ api / events也会列出它们的关系。 - -但是，关系的标准端点是/ api / relationships。该端点为关系提供所有正常的CRUD操作。 - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -该请求将返回您有权访问的任何关系的列表，其中包括您指定的trackedEntityInstance，注册或事件。每个关系都使用以下JSON表示： - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -您还可以使用以下端点查看指定的关系： - - GET /api/relationships/ - -要创建或更新关系，可以使用以下端点： - - POST / api / relationships - PUT / api /关系 - -并使用以下有效负载结构： - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -要删除关系，可以使用以下端点： - - 删除/ api / relationships / - -在示例有效负载中，我们使用trackedEntityInstances之间的关系。因此，有效负载的“从”和“到”属性包括“ trackedEntityInstance”对象。如果您的关系包括其他实体，则可以使用以下属性： - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### 更新策略 { #webapi_tei_update_strategies } - -支持所有 3 个跟踪器端点的两种更新策略： -注册和事件创建。当您生成一个 -客户端的标识符，不确定它是否被创建 -在服务器上。 - - - -Table: Available tracker strategies - -| Parameter | 描述 | -|---|---| -| CREATE | Create only, this is the default behavior. | -| CREATE_AND_UPDATE | Try and match the ID, if it exist then update, if not create. | - -要更改参数，请使用策略参数： - - POST / api / 33 / trackedEntityInstances？strategy = CREATE_AND_UPDATE - -### 跟踪器批量删除 { #webapi_tracker_bulk_deletion } - -批量删除跟踪器对象的工作方式与添加和删除跟踪器对象的方式类似 -更新跟踪器对象，唯一的不同是 -`importStrategy`是*DELETE*。 - -*示例：批量删除跟踪实体实例：* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*示例：批量删除注册：* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*示例：批量删除事件：* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### 通过POST和PUT方法重复使用标识符和删除项目 { #webapi_updating_and_deleting_items } - -跟踪器端点 */trackedEntityInstances*、*/enrollments*、*/events* -支持 CRUD 操作。系统跟踪使用的标识符。 -因此，已创建然后删除的项目（例如事件、 -注册）不能再次创建或更新。如果试图删除 -已删除的项目，系统返回成功响应为 -删除已删除的项目意味着没有更改。 - -系统不允许通过更新（* PUT *）删除项目或 -创建（* POST *）方法。因此，* PUT *和* POST *方法中的* deleted *属性将被忽略，并且在* POST *方法中默认设置 -为* false *。 - -### 导入参数 { #webapi_import_parameters } - -可以使用一组导入参数来自定义导入过程： - - - -Table: Import parameters - -| Parameter | Values (default first) | 描述 | -|---|---|---| -| 数据元素标识方案 | id | name | code | attribute:ID | Property of the data element object to use to map the data values. | -| orgUnitIdScheme | id | name | code | attribute:ID | Property of the org unit object to use to map the data values. | -| 方案 | id | name | code| attribute:ID | Property of all objects including data elements, org units and category option combos, to use to map the data values. | -| dryRun | false | true | Whether to save changes on the server or just return the import summary. | -| strategy | CREATE | UPDATE | CREATE_AND_UPDATE | DELETE | Save objects of all, new or update import status on the server. | -| skipNotifications | true | false | Indicates whether to send notifications for completed events. | -| skipFirst | true | false | Relevant for CSV import only. Indicates whether CSV file contains a header row which should be skipped. | -| importReportMode | FULL, ERRORS, DEBUG | Sets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes *ObjectReports* for object which has errors. `FULL` returns an *ObjectReport* for all objects imported, and `DEBUG` returns the same plus a name for the object (if available). | - -#### CSV导入/导出 { #webapi_events_csv_import_export } - -除了用于事件导入/导出的 XML 和 JSON 之外，在 DHIS2.17 中我们 -引入了对 CSV 格式的支持。对这种格式的支持建立在 -上一节已经描述过，所以这里我们只写 -CSV 特定部分是什么。 - -要使用 CSV 格式，您必须使用 `/api/events.csv` -端点，或添加 *content-type: text/csv* 以进行导入，并 *accept: -text/csv* 用于在使用 `/api/events` 端点时导出。 - -CSV 中用于导出和导入的列的顺序 -如下： - - - -Table: CSV column - -| Index | 键 | 类型 | 描述 | -|---|---|---|---| -| 1 | event | identifier | Identifier of event | -| 2 | status | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | program | identifier | Identifier of program | -| 4 | programStage | identifier | Identifier of program stage | -| 5 | enrollment | identifier | Identifier of enrollment (program instance) | -| 6 | orgUnit | identifier | Identifier of organisation unit | -| 7 | eventDate | date | Event date | -| 8 | dueDate | date | Due Date | -| 9 | latitude | double | Latitude where event happened | -| 10 | longitude | double | Longitude where event happened | -| 11 | dataElement | identifier | Identifier of data element | -| 12 | 价值 | string | Value / measure of event | -| 13 | storedBy | string | Event was stored by (defaults to current user) | -| 14 | providedElsewhere | boolean | Was this value collected somewhere else | -| 14 | completedDate | date | Completed date of event | -| 14 | completedBy | string | Username of user who completed event | - -*具有 2 个不同数据值的 2 个事件的示例 - 每个：* - -```csv -EJNxP3WreNP，COMPLETED，，，，，2016-01-01,2016-01-01 ,,, ，1 ,, -EJNxP3WreNP，COMPLETED，，，，，2016-01-01,2016-01-01 ,,, ，2 ,, -qPEdI1xn7k0，COMPLETED，，，，，2016-01-01,2016-01-01 ,,, ，3 ,, -qPEdI1xn7k0，COMPLETED，，，，，2016-01-01,2016-01-01 ,,, ，4 ,, -``` - -#### 导入策略：SYNC { #webapi_sync_import_strategy } - -导入策略 SYNC 应仅用于内部同步 -任务而不是常规导入。 SYNC 策略允许所有 3 -操作：CREATE、UPDATE、DELETE 出现在有效载荷中 -同时。 - -### 跟踪器所有权管理 { #webapi_tracker_ownership_management } - -从 2.30 开始引入了一个名为 Tracker Ownership 的新概念。那里 -现在将成为跟踪实体实例的一个所有者组织单位 -程序的上下文。配置了访问权限的程序 -*PROTECTED* 或 *CLOSED* 的级别将遵守所有权 -特权。仅属于所属组织单位的用户 -被跟踪的实体-程序组合将能够访问数据 -与该被跟踪实体的该计划相关。 - -#### 跟踪器所有权优先：打破常规 { #webapi_tracker_ownership_override_api } - -可以临时覆盖此所有权特权 -访问级别配置为 *PROTECTED* 的程序。任何用户 -将能够临时访问程序相关数据，如果 -用户指定访问被跟踪实体程序的原因 -数据。这种暂时获得访问权限的行为被称为*破坏 -玻璃*。目前，临时访问权限为 3 小时。 DHIS2 -审计打破玻璃以及用户指定的原因。 -无法临时访问已被删除的程序 -配置访问级别为 *CLOSED*。打破玻璃 -被跟踪的实体程序组合，您可以发出 POST 请求作为 -显示： - - / api / 33 / tracker / ownership / override？trackedEntityInstance = DiszpKrYNg8 - ＆program = eBAyeGv0exc＆reason =耐心+显示+急诊+急诊 - -#### 跟踪器所有权转移 { #webapi_tracker_ownership_transfer_api } - -可以转移被跟踪实体程序的所有权 -从一个组织单位到另一个组织单位。这将有助于患者 -转介或迁移。只有所有者（或破坏了 -glass）可以转让所有权。转移被跟踪的所有权 -entity-program 到另一个组织单位，你可以发出 PUT 请求 -如图所示： - - / api / 33 / tracker /所有权/转让？trackedEntityInstance = DiszpKrYNg8 - ＆program = eBAyeGv0exc＆ou = EJNxP3WreNP - - -## 潜在重复 { #potential-duplicates } - -潜在的重复项是我们在重复数据删除功能中使用的记录。由于重复数据删除功能的性质，此API端点受到一定程度的限制。 - -A potential duplicate represents a pair of records which are suspected to be a duplicate. - -潜在重复项的有效负载如下所示： - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -您可以使用以下端点检索可能重复的列表： - - GET /api/potentialDuplicates - -| Parameter name | 描述 | 类型 | Allowed values | -|---|---|---|---| -| teis | List of tracked entity instances | List of string (separated by comma)| existing tracked entity instance id | -| status | Potential duplicate status | string | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Status code | 描述 -|---|---| -| 400 | Invalid input status - -You can inspect individual potential duplicate records: - - GET /api/potentialDuplicates/ - -| Status code | 描述 -|---|---| -| 404 | Potential duplicate not found - -要创建新的潜在重复项，可以使用以下端点： - - POST / api / potentialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Status code | 描述 -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -To update a potential duplicate status: - - PUT /api/potentialDuplicates/ - -| Parameter name | 描述 | 类型 | Allowed values | -|---|---|---|---| -| status | Potential duplicate status | string | `OPEN`, `INVALID`, `MERGED` | - -| Status code | 描述 -|---|---| -| 400 | You can't update a potential duplicate to MERGED as this is possible only by a merging request -| 400 | You can't update a potential duplicate that is already in a MERGED status - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -To merge a Potential Duplicate, or the two tracked entity instances the Potential Duplicate represents, the following endpoint can be used: - - POST /api/potentialDuplicates//merge - -| Parameter name | 描述 | 类型 | Allowed values | -|---|---|---|---| -| mergeStrategy | Strategy to use for merging the potentialDuplicate | enum | AUTO(default) or MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- The same attribute has different values in each tracked entity instance -- Both tracked entity instances are enrolled in the same program -- Tracked entity instances have different types - -If any conflict is encountered, an errormessage is returned to the user. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -When requesting an automatic merge like this, a payload is not required and will be ignored. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Relationship cannot be between the original and the duplicate (This results in an invalid self-referencing relationship) -- Relationship cannot be of the same type and to the same object in both tracked entity instances (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) - -There are two ways to do a manual merge: With and without a payload. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -Otherwise, if a manual merge is requested with a payload, the payload refers to what data should be moved from the duplicate to the original. The payload looks like this: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -下表中说明了这些字段。 - - -Table: Program Notification Template payload - -| 领域 | 需要 | 描述 | Values | -|---|---|---|---| -| 名称 | 是的 | name of Program Notification Template | case-notification-alert | -| notificationTrigger | 是的 | When notification should be triggered. Possible values are ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| 注册 | -| subjectTemplate | 不 | Subject template string | Case notification V{org_unit_name} | -| messageTemplate | 是的 | Message template string | Case notification A{h5FuguPFF2j} | -| notificationRecipient | YES | Who is going to receive notification. Possible values are USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | 不 | Which channel should be used for this notification. It can be either SMS, EMAIL or HTTP | SMS | -| sendRepeatable | 不 | Whether notification should be sent multiple times | 假 | - -NOTE: WEB_HOOK notificationRecipient is used only to POST http request to an external system. Make sure to choose HTTP delivery channel when using WEB_HOOK. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -The list of Program Notification Templates can be retrieved using GET. - - GET /api/programNotificationTemplates - -For one particular Program Notification Template. - - GET /api/33/programNotificationTemplates/{uid} - -To get filtered list of Program Notification Templates - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Program Notification Template can be deleted using DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -程序消息可让您向跟踪的实体实例发送消息， -与组织单位关联的联系地址、电话号码和 -电子邮件地址。您可以通过 `messages` 资源发送消息。 - - / api / 33 /消息 - -### 发送程序信息 { #sending-program-messages } - -程序消息可以使用两个传递渠道发送： - - - 短信（SMS） - - - 电子邮件地址（EMAIL） - -程序消息可以发送给各种收件人： - - - 跟踪实体实例：系统将查找值的属性 - 输入 PHONE_NUMBER 或 EMAIL（取决于指定的递送 - 通道）并使用相应的属性值。 - - - 组织单位：系统将使用电话号码或邮箱 - 为组织单位注册的信息。 - - - 电话号码列表：系统将使用明确定义的 - 电话号码。 - - - 电子邮件地址列表：系统将使用明确定义的 - 电子邮件地址。 - -下面是使用 POST 请求发送消息的示例 JSON 负载。 -请注意，消息资源接受一个名为 -`programMessages` 可以包含任意数量的程序消息。 - - 开机自检/ api / 33 / messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -下表中说明了这些字段。 - - - -Table: Program message payload - -| 领域 | 需要 | 描述 | Values | -|---|---|---|---| -| recipients | 是的 | Recipients of the program message. At least one recipient must be specified. Any number of recipients / types can be specified for a message. | Can be trackedEntityInstance, organisationUnit, an array of phoneNumbers or an array of emailAddresses. | -| programInstance | Either this or programStageInstance required | The program instance / enrollment. | Enrollment ID. | -| programStageInstance | Either this or programInstance required | The program stage instance / event. | Event ID. | -| deliveryChannels | 是的 | Array of delivery channels. | SMS | EMAIL | -| subject | 不 | The message subject. Not applicable for SMS delivery channel. | Text. | -| 文本 | 是的 | The message text. | Text. | -| storeCopy | 不 | Whether to store a copy of the program message in DHIS2. | false (default) | true | - -通过 SMS 向被跟踪对象发送消息的简约示例 -实体实例如下所示： - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### 检索和删除程序消息 { #retrieving-and-deleting-program-messages } - -可以使用GET检索消息列表。 - - GET /api/33/messages - -To get the list of sent tracker messages, the below endpoint can be used. ProgramInstance or ProgramStageInstance uid has to be provided. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -To get the list of all scheduled message - - GET / api / 33 / messages / scheduled - GET / api / 33 / messages / scheduled？scheduledAt = 2020-12-12 - -也可以使用GET检索一条特定的消息。 - - GET /api/33/messages/{uid} - -可以使用DELETE删除消息。 - - 删除/ api / 33 / messages / {uid} - - -### 查询程序信息 { #querying-program-messages } - -程序消息API支持基于 -请求参数。可以根据下面提到的过滤消息 -查询参数。所有请求都应使用 GET HTTP 动词 -检索信息。 - - - -Table: Query program messages API - -| Parameter | 网址 | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # 电子邮件 { #email } diff --git a/projects/dhis2-single-page-docs/zh/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md b/projects/dhis2-single-page-docs/zh/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md index ceff82dd9..8d57633f5 100644 --- a/projects/dhis2-single-page-docs/zh/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md +++ b/projects/dhis2-single-page-docs/zh/MANAGE__DHIS-CORE-VERSION-MASTER__system-administration-guide-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- Manage - DHIS核心 主版 +- Manage template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md index b71750a54..c96616441 100644 --- a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/zh/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 --- diff --git a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md index 67ffa67da..5c4a9bd88 100644 --- a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-237__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/zh/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 --- diff --git a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index e3b69cdab..2b5cc5650 100644 --- a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - 使用 +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 04f456b1a..3e7406f0b 100644 --- a/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-29' tags: -- DHIS core version 2.39 - 使用 +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp b/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp index 711602a9e..4b8ecf280 100644 --- a/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:28:28Z \ No newline at end of file +2024-06-04T21:28:35Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md index 4a8629e57..6dafd19e3 100644 --- a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-237__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2023-01-13' tags: -- DHIS core version 2.37 - Develop +- DHIS core version 2.37 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md index 446371fd3..36ca24258 100644 --- a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-238__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-21' tags: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md index 9f4cf5990..d4f6c7e8c 100644 --- a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-239__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md index 19487c519..a6f21b82e 100644 --- a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-240__developer-manual-md @@ -1,8 +1,8 @@ --- revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 template: single.html --- diff --git a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md index 1d6d84576..513fa4d92 100644 --- a/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md +++ b/projects/dhis2-single-page-docs/zh_CN/DEVELOP__DHIS-CORE-VERSION-MASTER__developer-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: - Develop - DHIS core version master @@ -12221,7 +12221,7 @@ Table: Query parameters for event query analytics only | Query parameter | Required | Description | Options | |---|---|---|---| -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return events which have coordinates. | false | true | @@ -13128,7 +13128,7 @@ Table: Query parameters for enrollment query endpoint | filter | No | Dimension identifier including data elements, attributes, periods, organisation units and organisation unit group sets. Parameter can be repeated any number of times. Item filters can be applied to a dimension on the format ::. Filter values are case-insensitive. || | programStatus | No | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | No | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return enrollments which have coordinates. | false | true | @@ -17837,20 +17837,21 @@ The appearance of the login dialog can also be modified by defining css variable > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -17953,7 +17954,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | No | Yes | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | Yes | No | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | No | Yes | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -18013,9 +18013,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Attributes { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -18030,18 +18032,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -18056,31 +18060,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Notes { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -18091,10 +18095,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -18136,92 +18140,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the working list. Required. || -| description | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Description | Example | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -18230,9 +18149,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -18265,7 +18184,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -18665,7 +18584,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -19111,7 +19030,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -19241,7 +19160,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | N/A | Undefined error message. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -19251,7 +19170,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -19276,8 +19195,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -19330,7 +19249,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -19386,7 +19305,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -19408,7 +19327,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -19442,7 +19361,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -19494,9 +19413,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -19576,8 +19495,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -19682,7 +19601,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -19944,8 +19863,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -20149,8 +20068,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -20445,13 +20364,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -20497,7 +20416,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -20566,13 +20485,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -20584,7 +20503,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -20597,7 +20516,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -20607,7 +20526,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -20637,7 +20556,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -20653,2767 +20572,122 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } -# Tracker (deprecated APIs) { #webapi_deprecated_tracker } - -> **Caution** -> -> Tracker has been re-implemented in DHIS2 2.36. The new endpoints are documented at -> [Tracker](#webapi_tracker). -> -> Endpoints -> -> * `GET/POST/PUT/DELETE /api/trackedEntityInstance` -> * `GET/POST/PUT/DELETE /api/enrollments` -> * `GET/POST/PUT/DELETE /api/events` -> * `GET/POST/PUT/DELETE /api/relationships` -> -> have been removed in version **42**! -> -> We also removed the ability to sync Tracker data via [metadata sync](#metadata_sync). -> -> * If you plan to use the tracker endpoints use the new endpoints described in -> [Tracker](#webapi_tracker) -> * If you are still using the deprecated tracker endpoints in production, please migrate over to the -> new endpoints. [Migrating to new tracker endpoints](#webapi_tracker_migration) should help you -> get started. Reach out on the [community of practice](https://community.dhis2.org) if you need -> further assistance. - -## Migrating to new tracker endpoints { #webapi_tracker_migration } +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. -The following sections highlight the important differences between the deprecated endpoints. +### Program stage working lists { #program-stage-working-lists } -* `GET/POST/PUT/DELETE /api/trackedEntityInstance` -* `GET/POST/PUT/DELETE /api/enrollments` -* `GET/POST/PUT/DELETE /api/events` -* `GET/POST/PUT/DELETE /api/relationships` +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. -and the newly introduced endpoints + /api/programStageWorkingLists -* `POST /api/tracker` -* `GET /api/tracker/trackedEntities` -* `GET /api/tracker/enrollments` -* `GET /api/tracker/events` -* `GET /api/tracker/relationships` +#### Payload { #payload } -### Property names { #webapi_tracker_migration_names } +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: -API property names have changed so they are consistent across all the endpoints. The following table -lists the old and new property names. +Table: Payload -|Tracker Object|Previously|Now| +| Payload values | Description | Example | |---|---|---| -|**Attribute**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| -|**Event**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`
`assignedUser`*|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`
`createdBy`
`updatedBy`
`assignedUser`*| -|**Note**|`storedDate`
`lastUpdatedBy`|`storedAt`
`createdBy`| -|**ProgramOwner**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| -|**RelationshipItem**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| -|**Relationship**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**TrackedEntity**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| - -> **Note** -> -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): -> ```json -> { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } -> } -> ``` - -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } - -Fields or query parameters accepting multiple values like UIDs are now consistently separated by -comma instead of semicolon. This is to ensure UIDs are consistently separated by comma across all -DHIS2 endpoints. - -The following fields are affected - -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship -`from`/`to`) - -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } - -The previous tracker import endpoints - -* `POST/PUT/DELETE /api/trackedEntityInstance` -* `POST/PUT/DELETE /api/enrollments` -* `POST/PUT/DELETE /api/events` -* `POST/PUT/DELETE /api/relationships` - -are replaced by the new endpoint - -* `POST /api/tracker` - -[Tracker -Import](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) -describes how to use this new endpoint. - -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } - -In addition to the changed names shown in [Property names](#webapi_tracker_migration_names) some -request parameters have been changed as well. - -The following tables list the differences in old and new request parameters for `GET` endpoints. - -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribute`|Removed - use `filter` instead| -|`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes`|Removed| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| -|`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`programStatus`|`enrollmentStatus`| -|`query`|Removed - use `filter` instead| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntities`
Values are now separated by comma instead of semicolon.| - -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } - -|Previously|Now| -|---|---| -|`enrollment`|`enrollments`
Values are now separated by comma instead of semicolon.| -|`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| -|`ouMode`|`orgUnitMode`| -|`ou`|`orgUnits`
Values are now separated by comma instead of semicolon.| -|`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`programStatus`|`status`| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } - -|Previously|Now| -|---|---| -|`assignedUser`|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| -|`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`event`|`events`
Values are now separated by comma instead of semicolon.| -|`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`lastUpdated`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| -|`ouMode`|`orgUnitMode`| -|`programStatus`|`enrollmentStatus`| -|`skipEventId`|Removed| -|`skipMeta`|Removed| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity`| - -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } - -|Previously|Now| -|---|---| -|`skipPaging`|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity`| - -## Tracker Web API { #webapi_tracker_api } - -Tracker Web API consists of 3 endpoints that have full CRUD (create, -read, update, delete) support. The 3 endpoints are -`/api/trackedEntityInstances`, `/api/enrollments` and -`/api/events` and they are responsible for tracked entity instance, -enrollment and event items. - -### Tracked entity instance management { #webapi_tracked_entity_instance_management } - -Tracked entity instances have full CRUD support in the API. Together -with the API for enrollment most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/trackedEntityInstances - -#### Creating a new tracked entity instance { #webapi_creating_tei } - -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "geometry": "", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }] -} -``` - -The field "geometry" accepts a GeoJson object, where the type of the -GeoJson have to match the featureType of the TrackedEntityType -definition. An example GeoJson object looks like this: - -```json -{ - "type": "Point", - "coordinates": [1, 1] -} -``` - -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +| name | Name of the working list. Required. || +| description | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. -For getting the IDs for `relationship` and `attributes` you can have a look -at the respective resources `relationshipTypes`, `trackedEntityAttributes`. -To create a tracked entity instance you must use the HTTP *POST* method. -You can post the payload the following URL: +Table: Program Stage Query Criteria - /api/trackedEntityInstances +| Criteria values | Description | Example | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +See an example payload below: ```json { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] -} -``` - -To push this to the server you can use the cURL command like this: - -```bash -curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST - -H "Content-Type: application/json" -u admin:district -``` - -To create multiple instances in one request you can wrap the payload in -an outer array like this and POST to the same resource as above:[]() - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Smith" - } - ] + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" }, - { - "trackedEntity": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Jennifer" - }, - { - "attribute": "zDhUuAYrxNC", - "value": "Johnson" - } - ] - } - ] -} -``` - -The system does not allow the creation of a tracked entity instance -(as well as enrollment and event) with a UID that was already used in -the system. That means that UIDs cannot be reused. - -#### Updating a tracked entity instance { #webapi_updating_tei } - -For updating a tracked entity instance, the payload is equal to the -previous section. The difference is that you must use the HTTP *PUT* -method for the request when sending the payload. You will also need to -append the person identifier to the *trackedEntityInstances* resource in -the URL like this, where `` should -be replaced by the identifier of the tracked entity instance: - - /api/trackedEntityInstances/ - -The payload has to contain all, even non-modified, attributes and -relationships. Attributes or relationships that were present before and -are not present in the current payload any more will be removed from the -system. This means that if attributes/relationships are empty in the -current payload, all existing attributes/relationships will be deleted -from the system. From 2.31, it is possible to ignore empty -attributes/relationships in the current payload. A request parameter of -`ignoreEmptyCollection` set to `true` can be used in case you do not -wish to send in any attributes/relationships and also do not want them -to be deleted from the system. - -It is not allowed to update an already deleted tracked entity instance. -Also, it is not allowed to mark a tracked entity instance as deleted via -an update request. The same rules apply to enrollments and events. - -#### Deleting a tracked entity instance { #webapi_deleting_tei } - -In order to delete a tracked entity instance, make a request to the URL -identifying the tracked entity instance with the *DELETE* -method. The URL is equal to the one above used for update. - -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } - -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. - -```json -{ - "trackedEntity": "tracked-entity-id", - "orgUnit": "org-unit-id", - "attributes": [{ - "attribute": "attribute-id", - "value": "attribute-value" - }], - "enrollments": [{ - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }, { - "orgUnit": "org-unit-id", - "program": "program-id", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" - }] -} -``` - -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Complete example of payload including: tracked entity instance, enrollment and event { #webapi_create_enroll_tei_create_event } - -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. - -```json -{ - "trackedEntityType": "nEenWmSyUEp", - "orgUnit": "DiszpKrYNg8", - "attributes": [ - { - "attribute": "w75KJ2mc4zz", - "value": "Joe" + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute": "zDhUuAYrxNC", - "value": "Rufus" + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" }, - { - "attribute":"cejWyOfXge6", - "value":"Male" - } - ], - "enrollments":[ - { - "orgUnit":"DiszpKrYNg8", - "program":"ur1Edk5Oe2n", - "enrollmentDate":"2017-09-15", - "incidentDate":"2017-09-15", - "events":[ - { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues": [ - { - "dataElement":"qrur9Dvnyt5", - "value":"22" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Male" - } - ] - }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ { - "program":"ur1Edk5Oe2n", - "orgUnit":"DiszpKrYNg8", - "eventDate":"2017-10-17", - "status":"COMPLETED", - "storedBy":"admin", - "programStage":"EPEcjy3FWmI", - "coordinate": { - "latitude":"59.8", - "longitude":"10.9" - }, - "dataValues":[ - { - "dataElement":"qrur9Dvnyt5", - "value":"26" - }, - { - "dataElement":"oZg33kd9taw", - "value":"Female" - } - ] - } - ] - } - ] + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. - -```bash -curl -X POST -d @tei.json -H "Content-Type: application/json" - -u user:pass "http://server/api/33/trackedEntityInstances" -``` - -#### Generated tracked entity instance attributes { #webapi_generate_tei_attributes } - -Tracked entity instance attributes that are using automatic generation of -unique values have three endpoints that are used by apps. The endpoints -are all used for generating and reserving values. - -In 2.29 we introduced TextPattern for defining and generating these -patterns. All existing patterns will be converted to a valid TextPattern -when upgrading to 2.29. - -> **Note** -> -> As of 2.29, all these endpoints will require you to include any -> variables reported by the `requiredValues` endpoint listed as -> required. Existing patterns, consisting of only `#`, will be upgraded -> to the new TextPattern syntax `RANDOM()`. The RANDOM -> segment of the TextPattern is not a required variable, so this -> endpoint will work as before for patterns defined before 2.29. - -##### Finding required values { #finding-required-values } - -A TextPattern can contain variables that change based on different -factors. Some of these factors will be unknown to the server, so the -values for these variables have to be supplied when generating and -reserving values. - -This endpoint will return a map of required and optional values, that -the server will inject into the TextPattern when generating new values. -Required variables have to be supplied for the generation, but optional -variables should only be supplied if you know what you are doing. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues - -```json -{ - "REQUIRED": [ - "ORG_UNIT_CODE" - ], - "OPTIONAL": [ - "RANDOM" - ] -} -``` - -##### Generate value endpoint { #webapi_generate_values } - -Online web apps and other clients that want to generate a value that -will be used right away can use the simple generate endpoint. This -endpoint will generate a value that is guaranteed to be unique at the -time of generation. The value is also guaranteed not to be reserved. As -of 2.29, this endpoint will also reserve the value generated for 3 days. - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO - -```json -{ - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "C-OSL", - "created": "2018-03-02T12:01:36.680", - "expiryDate": "2018-03-05T12:01:36.678" -} -``` - -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } - -The generate and reserve endpoint is used by offline clients that need -to be able to register tracked entities with unique ids. They will -reserve a number of unique ids that this device will then use when -registering new tracked entity instances. The endpoint is called to -retrieve a number of tracked entity instance reserved values. An -optional parameter numberToReserve specifies how many ids to generate -(default is 1). - -If your TextPattern includes required values, you can pass them as -parameters like the example below: - -Similar to the /generate endpoint, this endpoint can also specify the -expiration time in the same way. By adding the `?expiration=` -you can override the default 60 days. - - GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO - -```json -[ - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "B-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "Q-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - }, - { - "ownerObject": "TRACKEDENTITYATTRIBUTE", - "ownerUid": "Gs1ICEQTPlG", - "key": "RANDOM(X)-OSL", - "value": "S-OSL", - "created": "2018-03-02T13:22:35.175", - "expiryDate": "2018-05-01T13:22:35.174" - } -] -``` - -##### Reserved values { #reserved-values } - -Reserved values are currently not accessible through the api, however, they -are returned by the `generate` and `generateAndReserve` endpoints. The -following table explains the properties of the reserved value object: - -##### - - - -Table: Reserved values - -| Property | Description | -|---|---| -| ownerObject | The metadata type referenced when generating and reserving the value. Currently only TRACKEDENTITYATTRIBUTE is supported. | -| ownerUid | The uid of the metadata object referenced when generating and reserving the value. | -| key | A partially generated value where generated segments are not yet added. | -| value | The fully resolved value reserved. This is the value you send to the server when storing data. | -| created | The timestamp when the reservation was made | -| expiryDate | The timestamp when the reservation will no longer be reserved | - -Expired reservations are removed daily. If a pattern changes, values -that were already reserved will be accepted when storing data, even if -they don't match the new pattern, as long as the reservation has not -expired. - -#### Image attributes { #image-attributes } - -Working with image attributes is a lot like working with file data -values. The value of an attribute with the image value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///image` -endpoint will return the actual image. The optional height and width -parameters can be used to specify the dimensions of the image. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" - > image.jpg -``` - -The API also supports a *dimension* parameter. It can take three possible values (please note capital letters): `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) or `ORIGINAL`. Image type attributes will be stored in pre-generated sizes -and will be furnished upon request based on the value of the `dimension` parameter. - -```bash -curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" -``` - -#### File attributes { #file-attributes } - -Working with file attributes is a lot like working with image data -values. The value of an attribute with the file value type is the id of -the associated file resource. A GET request to the -`/api/trackedEntityInstances///file` -endpoint will return the actual file content. - -```bash -curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file -``` - -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } - -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. - - /api/33/trackedEntityInstances - -##### Request syntax { #webapi_tei_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Description | -|---|---| -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| lastUpdatedStartDate | Filter for teis which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | Filter for teis which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. See table below "Assigned user modes" for explanations. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| includeDeleted | Indicates whether to include soft deleted teis or not. It is false by default. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | The selected organisation units and the immediate children, i.e. the organisation units at the level below. | -| DESCENDANTS | The selected organisation units and all children, i.e. all organisation units in the sub-hierarchy. | -| ACCESSIBLE | technically, returns everything in the user's tracker search organisation units. In practice, if a user lacks search organisation units, the system defaults to the data capture scope. As the capture scope is mandatory, we ensure that a user always has at least one universe. | -| CAPTURE | The data capture organisation units associated with the current user and all descendants, encompassing all organisation units in the sub-hierarchy. | -| ALL | The term "ALL" logically refers to the entire organisation unit available in the system for super users. However, for non-superusers, "ALL" is equivalent to "ACCESSIBLE" organisation units. | - -The available assigned user modes are explained in the following table. - - - -Table: Assigned user modes - -| Mode | Description | -|---|---| -| CURRENT | Includes events assigned to the current logged in user. | -| PROVIDED | Includes events assigned to the user provided in the request. | -| NONE | Includes unassigned events only. | -| ANY | Includes all assigned events, doesn't matter who are they assigned to as long as they assigned to someone. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendant organisation unit query mode: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a filter: - - /api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an *IN* filter: - - api/33/trackedEntityInstances.json?ou=DiszpKrYNg8 - &filter=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - api/33/trackedEntityInstances.json?filter=zHXD5Ve1Efw:EQ:A&ou=O6uvpzGd5pu - &ouMode=DESCENDANTS&page=2&pageSize=3 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Description | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "trackedEntityInstances": [ - { - "lastUpdated": "2014-03-28 12:27:52.399", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-26 15:40:19.997", - "orgUnit": "ueuQlqb8ccl", - "trackedEntityInstance": "tphfdyIiVL6", - "relationships": [], - "attributes": [ - { - "displayName": "Address", - "attribute": "AMpUYgxuCaE", - "type": "string", - "value": "2033 Akasia St" - }, - { - "displayName": "TB number", - "attribute": "ruQQnf6rswq", - "type": "string", - "value": "1Z 989 408 56 9356 521 9" - }, - { - "displayName": "Weight in kg", - "attribute": "OvY4VVhSDeJ", - "type": "number", - "value": "68.1" - }, - { - "displayName": "Email", - "attribute": "NDXw0cluzSw", - "type": "string", - "value": "LiyaEfrem@armyspy.com" - }, - { - "displayName": "Gender", - "attribute": "cejWyOfXge6", - "type": "optionSet", - "value": "Female" - }, - { - "displayName": "Phone number", - "attribute": "P2cwLGskgxn", - "type": "phoneNumber", - "value": "085 813 9447" - }, - { - "displayName": "First name", - "attribute": "dv3nChNSIxy", - "type": "string", - "value": "Liya" - }, - { - "displayName": "Last name", - "attribute": "hwlRTFIFSUq", - "type": "string", - "value": "Efrem" - }, - { - "code": "Height in cm", - "displayName": "Height in cm", - "attribute": "lw1SqmMlnfh", - "type": "number", - "value": "164" - }, - { - "code": "City", - "displayName": "City", - "attribute": "VUvgVao8Y5z", - "type": "string", - "value": "Kranskop" - }, - { - "code": "State", - "displayName": "State", - "attribute": "GUOBQt5K2WI", - "type": "number", - "value": "KwaZulu-Natal" - }, - { - "code": "Zip code", - "displayName": "Zip code", - "attribute": "n9nUvfpTsxQ", - "type": "number", - "value": "3282" - }, - { - "code": "National identifier", - "displayName": "National identifier", - "attribute": "AuPLng5hLbE", - "type": "string", - "value": "465700042" - }, - { - "code": "Blood type", - "displayName": "Blood type", - "attribute": "H9IlTX2X6SL", - "type": "string", - "value": "B-" - }, - { - "code": "Latitude", - "displayName": "Latitude", - "attribute": "Qo571yj6Zcn", - "type": "string", - "value": "-30.659626" - }, - { - "code": "Longitude", - "displayName": "Longitude", - "attribute": "RG7uGl4w5Jq", - "type": "string", - "value": "26.916172" - } - ] - } - ] -} -``` - -#### Tracked entity instance grid query { #webapi_tracked_entity_instance_grid_query } - -To query for tracked entity instances you can interact with the -*/api/trackedEntityInstances/grid* resource. There are two types of -queries: One where a *query* query parameter and optionally *attribute* -parameters are defined, and one where *attribute* and *filter* -parameters are defined. This endpoint uses a more compact "grid" format, -and is an alternative to the query in the previous section. - - /api/33/trackedEntityInstances/query - -##### Request syntax { #webapi_tei_grid_query_request_syntax } - - - -Table: Tracked entity instances query parameters - -| Query parameter | Description | -|---|---| -| query | Query string. Attribute query parameter can be used to define which attributes to include in the response. If no attributes but a program is defined, the attributes from the program will be used. If no program is defined, all attributes will be used. There are two formats. The first is a plan query string. The second is on the format :. Operators can be EQ | LIKE. EQ implies exact matches on words, LIKE implies partial matches on words. The query will be split on space, where each word will form a logical AND query. | -| attribute | Attributes to be included in the response. Can also be used as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. Filters can be omitted in order to simply include the attribute in the response without any constraints. | -| filter | Attributes to use as a filter for the query. Param can be repeated any number of times. Filters can be applied to a dimension on the format ::[::]. Filter values are case-insensitive and can be repeated together with operator any number of times. Operators can be EQ | GT | GE | LT | LE | NE | LIKE | IN. | -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| eventStatus | Status of any event associated with the given program and the tracked entity instance. Can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED. | -| eventStartDate | Start date of event associated with the given program and event status. | -| eventEndDate | End date of event associated with the given program and event status. | -| programStage | The programStage for which the event related filters should be applied to. If not provided all stages will be considered. | -| skipMeta | Indicates whether meta data for the response should be included. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| assignedUserMode | Restricts result to tei with events assigned based on the assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | Filter the result down to a limited set of teis with events that are assigned to the given user IDs by using *assignedUser=id1;id2*.This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | -| trackedEntityInstance | Filter the result down to a limited set of teis using explicit uids of the tracked entity instances by using *trackedEntityInstance=id1;id2*. This parameter will at the very least create the outer boundary of the results, forming the list of all teis using the uids provided. If other parameters/filters from this table are used, they will further limit the results from the explicit outer boundary. | -| potentialDuplicate | Filter the result based on the fact that a TEI is a Potential Duplicate. true: return TEIs flagged as Potential Duplicates. false: return TEIs NOT flagged as Potential Duplicates. If omitted, we don't check whether a TEI is a Potential Duplicate or not.| - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request. | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| CAPTURE | The data capture organisation units associated with the current user and all children, i.e. all organisation units in the sub-hierarchy. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -Note that you can specify "attribute" with filters or directly using the "filter" params for constraining the -instances to return. - -Certain rules apply to which attributes are returned. - - - If "query" is specified without any attributes or program, then all attributes that - are marked as "Display in List without Program" is included in the response. - - - If program is specified, all the attributes linked to the program will - be included in the response. - - - If tracked entity type is specified, then all tracked entity type attributes - will be included in the response. - -You can specify queries with words separated by space - in that -situation the system will query for each word independently and return -records where each word is contained in any attribute. A query item can -be specified once as an attribute and once as a filter if needed. The -query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - - - If *eventStatus* is specified then *eventStartDate* and - *eventEndDate* must also be specified. - - - A query cannot be specified together with filters. - - - Attribute items can only be specified once. - - - Filter items can only be specified once. - -A query for all instances associated with a specific organisation unit -can look like this: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - -A query on all attributes for a specific value and organisation unit, -using an exact word match: - - /api/33/trackedEntityInstances/query.json?query=scott&ou=DiszpKrYNg8 - -A query on all attributes for a specific value, using a partial word -match: - - /api/33/trackedEntityInstances/query.json?query=LIKE:scott&ou=DiszpKrYNg8 - -You can query on multiple words separated by the URL character for -space which is %20, will use a logical AND query for each - word: - - /api/33/trackedEntityInstances/query.json?query=isabel%20may&ou=DiszpKrYNg8 - -A query where the attributes to include in the response are specified: - - /api/33/trackedEntityInstances/query.json?query=isabel - &attribute=dv3nChNSIxy&attribute=AMpUYgxuCaE&ou=DiszpKrYNg8 - -To query for instances using one attribute with a filter and one -attribute without a filter, with one organisation unit using the -descendants organisation unit query mode: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &attribute=AMpUYgxuCaE&ou=DiszpKrYNg8;yMCshbaVExv - -A query for instances where one attribute is included in the response -and one attribute is used as a - filter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &filter=AMpUYgxuCaE:LIKE:Road&ou=DiszpKrYNg8 - -A query where multiple operand and filters are specified for a filter -item: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8&program=ur1Edk5Oe2n - &filter=lw1SqmMlnfh:GT:150:LT:190 - -To query on an attribute using multiple values in an IN - filter: - - /api/33/trackedEntityInstances/query.json?ou=DiszpKrYNg8 - &attribute=dv3nChNSIxy:IN:Scott;Jimmy;Santiago - -To constrain the response to instances which are part of a specific -program you can include a program query parameter: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the query: - - /api/33/trackedEntityInstances/query.json?filter=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&program=ur1Edk5Oe2n&programStartDate=2013-01-01 - &programEndDate=2013-09-01 - -To constrain the response to instances of a specific tracked entity you -can include a tracked entity query parameter: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -By default the instances are returned in pages of size 50, to change -this you can use the page and pageSize query parameters: - - /api/33/trackedEntityInstances/query.json?attribute=zHXD5Ve1Efw:EQ:A - &ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -To query for instances which have events of a given status within a -given time span: - - /api/33/trackedEntityInstances/query.json?ou=O6uvpzGd5pu - &program=ur1Edk5Oe2n&eventStatus=COMPLETED - &eventStartDate=2014-01-01&eventEndDate=2014-09-01 - -You can use a range of operators for the filtering: - - - -Table: Filter operators - -| Operator | Description | -|---|---| -| EQ | Equal to | -| GT | Greater than | -| GE | Greater than or equal to | -| LT | Less than | -| LE | Less than or equal to | -| NE | Not equal to | -| LIKE | Free text match (Contains) | -| SW | Starts with | -| EW | Ends with | -| IN | Equal to one of multiple values separated by ";" | - -##### Response format { #webapi_tei_grid_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - - - csv (application/csv) - - - xls (application/vnd.ms-excel) - -The response in JSON comes is in a tabular format and can look like the -following. The *headers* section describes the content of each column. -The instance, created, last updated, org unit and tracked entity columns -are always present. The following columns correspond to attributes -specified in the query. The *rows* section contains one row per -instance. - -```json -{ - "headers": [{ - "name": "instance", - "column": "Instance", - "type": "java.lang.String" - }, { - "name": "created", - "column": "Created", - "type": "java.lang.String" - }, { - "name": "lastupdated", - "column": "Last updated", - "type": "java.lang.String" - }, { - "name": "ou", - "column": "Org unit", - "type": "java.lang.String" - }, { - "name": "te", - "column": "Tracked entity", - "type": "java.lang.String" - }, { - "name": "zHXD5Ve1Efw", - "column": "Date of birth type", - "type": "java.lang.String" - }, { - "name": "AMpUYgxuCaE", - "column": "Address", - "type": "java.lang.String" - }], - "metaData": { - "names": { - "cyl5vuJ5ETQ": "Person" - } - }, - "width": 7, - "height": 7, - "rows": [ - ["yNCtJ6vhRJu", "2013-09-08 21:40:28.0", "2014-01-09 19:39:32.19", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "21 Kenyatta Road"], - ["fSofnQR6lAU", "2013-09-08 21:40:28.0", "2014-01-09 19:40:19.62", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Upper Road"], - ["X5wZwS5lgm2", "2013-09-08 21:40:28.0", "2014-01-09 19:40:31.11", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "56 Main Road"], - ["pCbogmlIXga", "2013-09-08 21:40:28.0", "2014-01-09 19:40:45.02", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "12 Lower Main Road"], - ["WnUXrY4XBMM", "2013-09-08 21:40:28.0", "2014-01-09 19:41:06.97", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "13 Main Road"], - ["xLNXbDs9uDF", "2013-09-08 21:40:28.0", "2014-01-09 19:42:25.66", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "14 Mombasa Road"], - ["foc5zag6gbE", "2013-09-08 21:40:28.0", "2014-01-09 19:42:36.93", "DiszpKrYNg8", "cyl5vuJ5ETQ", "A", "15 Upper Hill"] - ] -} -``` - -#### Tracked entity instance filters { #webapi_tei_filters } - -To create, read, update and delete tracked entity instance filters you -can interact with the */api/trackedEntityInstanceFilters* resource. Tracked entity instance filters are shareable and follows the same pattern of sharing as any other metadata object. When using the */api/sharing* the type parameter will be *trackedEntityInstanceFilter*. - - /api/33/trackedEntityInstanceFilters - -##### Create and update a tracked entity instance filter definition { #create-and-update-a-tracked-entity-instance-filter-definition } - -For creating and updating a tracked entity instance filter in the -system, you will be working with the *trackedEntityInstanceFilters* -resource. The tracked entity instance filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the filter. Required. || -| description | A description of the filter. || -| sortOrder | The sort order of the filter. Used in Tracker Capture to order the filters in the program dashboard. || -| style | Object containing css style. | ( "color": "blue", "icon": "fa fa-calendar"} | -| program | Object containing the id of the program. Required. | { "id" : "uy2gU8kTjF"} | -| entityQueryCriteria | An object representing various possible filtering values. See *Entity Query Criteria* definition table below. -| eventFilters | A list of eventFilters. See *Event filters* definition table below. | [{"programStage": "eaDH9089uMp", "eventStatus": "OVERDUE", "eventCreatedPeriod": {"periodFrom": -15, "periodTo": 15}}] | - -Table: Entity Query Criteria definition - -|||| -|---|---|---| -| attributeValueFilters | A list of attributeValueFilters. This is used to specify filters for attribute values when listing tracked entity instances | "attributeValueFilters"=[{ "attribute": "abcAttributeUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "sw": "abc", "ew": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| enrollmentStatus | The TEIs enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED || -| followup | When this parameter is true, the filter only returns TEIs that have an enrollment with status followup. || -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayColumnOrder | To specify the output ordering of columns | "displayOrderColumns": ["enrollmentDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "orderDimension:direction". Note: Supported orderDimensions are trackedEntity, created, createdAt, createdAtClient, updatedAt, updatedAtClient, enrolledAt, inactive and the tracked entity attributes | "order"="a3kGcGDCuk6:desc" | -| eventStatus | Any valid EventStatus | "eventStatus": "COMPLETED" | -| programStage | To specify a programStage uid to filter on. TEIs will be filtered based on presence of enrollment in the specified program stage.| "programStage"="a3kGcGDCuk6" | -| trackedEntityType | To specify a trackedEntityType filter TEIs on. | "trackedEntityType"="a3kGcGDCuk6" | -| trackedEntityInstances | To specify a list of trackedEntityInstances to use when querying TEIs. | "trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"] | -| enrollmentIncidentDate | DateFilterPeriod object date filtering based on enrollment incident date. | "enrollmentIncidentDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| enrollmentCreatedDate | DateFilterPeriod object date filtering based on enrollment created date. | "enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - -Table: Event filters definition - -|||| -|---|---|---| -| programStage | Which programStage the TEI needs an event in to be returned. | "eaDH9089uMp" | -| eventStatus | The events status. Can be none(any event status) or ACTIVE|COMPLETED|SCHEDULE|OVERDUE | ACTIVE | -| eventCreatedPeriod | Period object containing a period in which the event must be created. See *Period* definition below. | { "periodFrom": -15, "periodTo": 15} | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT (events assigned to current user)| PROVIDED (events assigned to users provided in "assignedUsers" list) | NONE (events assigned to no one) | ANY (events assigned to anyone). If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -Table: Period definition - -|||| -|---|---|---| -| periodFrom | Number of days from current day. Can be positive or negative integer. | -15 | -| periodTo | Number of days from current day. Must be bigger than periodFrom. Can be positive or negative integer. | 15 | - -##### Tracked entity instance filters query { #tracked-entity-instance-filters-query } - -To query for tracked entity instance filters in the system, you can -interact with the */api/trackedEntityInstanceFilters* resource. - - - -Table: Tracked entity instance filters query parameters - -| Query parameter | Description | -|---|---| -| program | Program identifier. Restricts filters to the given program. | - -### Enrollment management { #webapi_enrollment_management } - -Enrollments have full CRUD support in the API. Together with the API -for tracked entity instances most operations needed for working with -tracked entity instances and programs are supported. - - /api/33/enrollments - -#### Enrolling a tracked entity instance into a program { #webapi_enrolling_tei } - -For enrolling persons into a program, you will need to first get the -identifier of the person from the *trackedEntityInstances* resource. -Then, you will need to get the program identifier from the *programs* -resource. A template payload can be seen below: - -```json -{ - "trackedEntityInstance": "ZRyCnJ1qUXS", - "orgUnit": "ImspTQPwCqd", - "program": "S8uo8AlvYMz", - "enrollmentDate": "2013-09-17", - "incidentDate": "2013-09-17" -} -``` - -This payload should be used in a *POST* request to the enrollments -resource identified by the following URL: - - /api/33/enrollments - -The different status of an enrollment are: - -* **ACTIVE**: It is used meanwhile when the tracked entity participates on the program. -* **COMPLETED**: It is used when the tracked entity finished its participation on the program. -* **CANCELLED**: "Deactivated" in the web UI. It is used when the tracked entity cancelled its participation on the program. - -For cancelling or completing an enrollment, you can make a *PUT* -request to the `enrollments` resource, including the identifier and the -action you want to perform. For cancelling an enrollment for a tracked -entity instance: - - /api/33/enrollments//cancelled - -For completing an enrollment for a tracked entity instance you can make a -*PUT* request to the following URL: - - /api/33/enrollments//completed - -For deleting an enrollment, you can make a *DELETE* request to the -following URL: - - /api/33/enrollments/ - -#### Enrollment instance query { #webapi_enrollment_instance_query } - -To query for enrollments you can interact with the */api/enrollments* -resource. - - /api/33/enrollments - -##### Request syntax { #webapi_enrollment_query_request_syntax } - - - -Table: Enrollment query parameters - -| Query parameter | Description | -|---|---| -| ou | Organisation unit identifiers, separated by ";". | -| ouMode | The mode of selecting organisation units, can be SELECTED | CHILDREN | DESCENDANTS | ACCESSIBLE | CAPTURE | ALL. Default is SELECTED, which refers to the selected organisation units only. See table below for explanations. | -| program | Program identifier. Restricts instances to being enrolled in the given program. | -| programStatus | Status of the instance for the given program. Can be ACTIVE | COMPLETED | CANCELLED. | -| followUp | Follow up status of the instance for the given program. Can be true | false or omitted. | -| programStartDate | Start date of enrollment in the given program for the tracked entity instance. | -| programEndDate | End date of enrollment in the given program for the tracked entity instance. | -| lastUpdatedDuration | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). | -| trackedEntity | Tracked entity identifier. Restricts instances to the given tracked instance type. | -| trackedEntityInstance | Tracked entity instance identifier. Should not be used together with trackedEntity. | -| page | The page number. Default page is 1. | -| pageSize | The page size. Default size is 50 rows per page. | -| totalPages | Indicates whether to include the total number of pages in the paging response (implies higher response time). | -| skipPaging | Indicates whether paging should be ignored and all rows should be returned. | -| includeDeleted | Indicates whether to include soft deleted enrollments or not. It is false by default. | - -The available organisation unit selection modes are explained in the -following table. - - - -Table: Organisation unit selection modes - -| Mode | Description | -|---|---| -| SELECTED | Organisation units defined in the request (default). | -| CHILDREN | Immediate children, i.e. only the first level below, of the organisation units defined in the request. | -| DESCENDANTS | All children, i.e. at only levels below, e.g. including children of children, of the organisation units defined in the request. | -| ACCESSIBLE | All descendants of the data view organisation units associated with the current user. Will fall back to data capture organisation units associated with the current user if the former is not defined. | -| ALL | All organisation units in the system. Requires `ALL` authority. | - -The query is case insensitive. The following rules apply to the query -parameters. - - - At least one organisation unit must be specified using the *ou* - parameter (one or many), or *ouMode=ALL* must be specified. - - - Only one of the *program* and *trackedEntity* parameters can be - specified (zero or one). - - - If *programStatus* is specified then *program* must also be - specified. - - - If *followUp* is specified then *program* must also be specified. - - - If *programStartDate* or *programEndDate* is specified then - *program* must also be specified. - -A query for all enrollments associated with a specific organisation unit -can look like this: - - /api/33/enrollments.json?ou=DiszpKrYNg8 - -To constrain the response to enrollments which are part of a specific -program you can include a program query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&program=ur1Edk5Oe2n - -To specify program enrollment dates as part of the - query: - - /api/33/enrollments.json?&ou=O6uvpzGd5pu&program=ur1Edk5Oe2n - &programStartDate=2013-01-01&programEndDate=2013-09-01 - -To constrain the response to enrollments of a specific tracked entity -you can include a tracked entity query - parameter: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&trackedEntity=cyl5vuJ5ETQ - -To constrain the response to enrollments of a specific tracked entity -instance you can include a tracked entity instance query parameter, in -this case we have restricted it to available enrollments viewable for -current - user: - - /api/33/enrollments.json?ouMode=ACCESSIBLE&trackedEntityInstance=tphfdyIiVL6 - -By default the enrollments are returned in pages of size 50, to change -this you can use the page and pageSize query - parameters: - - /api/33/enrollments.json?ou=O6uvpzGd5pu&ouMode=DESCENDANTS&page=2&pageSize=3 - -##### Response format { #webapi_enrollment_query_response_format } - -This resource supports JSON, JSONP, XLS and CSV resource -representations. - - - json (application/json) - - - jsonp (application/javascript) - - - xml (application/xml) - -The response in JSON/XML is in object format and can look like the -following. Please note that field filtering is supported, so if you want -a full view, you might want to add `fields=*` to the query: - -```json -{ - "enrollments": [ - { - "lastUpdated": "2014-03-28T05:27:48.512+0000", - "trackedEntity": "cyl5vuJ5ETQ", - "created": "2014-03-28T05:27:48.500+0000", - "orgUnit": "DiszpKrYNg8", - "program": "ur1Edk5Oe2n", - "enrollment": "HLFOK0XThjr", - "trackedEntityInstance": "qv0j4JBXQX0", - "followup": false, - "enrollmentDate": "2013-05-23T05:27:48.490+0000", - "incidentDate": "2013-05-10T05:27:48.490+0000", - "status": "ACTIVE" - } - ] -} -``` - -### Events { #webapi_events } - -This section is about sending and reading events. - - /api/33/events - -The different status of an event are: - -* **ACTIVE**: If a event has ACTIVE status, it is possible to edit the event details. COMPLETED events can be turned ACTIVE again and vice versa. -* **COMPLETED**: An event change the status to COMPLETED only when a user clicks the complete button. If a event has COMPLETED status, it is not possible to edit the event details. ACTIVE events can be turned COMPLETED again and vice versa. -* **SKIPPED**: Scheduled events that no longer need to happen. In Tracker Capture, there is a button for that. -* **SCHEDULE**: If an event has no event date (but it has an due date) then the event status is saved as SCHEDULE. -* **OVERDUE**: If the due date of a scheduled event (no event date) has expired, it can be interpreted as OVERDUE. -* **VISITED**: (Removed since 2.38. VISITED migrate to ACTIVE). In Tracker Capture its possible to reach VISITED by adding a new event with an event date, and then leave before adding any data to the event - but it is not known to the tracker product team that anyone uses the status for anything. The VISITED status is not visible in the UI, and in all means treated in the same way as an ACTIVE event. - - -#### Sending events { #webapi_sending_events } - -DHIS2 supports three kinds of events: single events with no registration -(also referred to as anonymous events), single event with registration -and multiple events with registration. Registration implies that the -data is linked to a tracked entity instance which is identified using -some sort of identifier. - -To send events to DHIS2 you must interact with the *events* resource. -The approach to sending events is similar to sending aggregate data -values. You will need a *program* which can be looked up using the -*programs* resource, an *orgUnit* which can be looked up using the -*organisationUnits* resource, and a list of valid data element -identifiers which can be looked up using the *dataElements* resource. -For events with registration, a *tracked entity instance* identifier is -required, read about how to get this in the section about the -*trackedEntityInstances* resource. For sending events to programs with -multiple stages, you will need to also include the *programStage* -identifier, the identifiers for programStages can be found in the -*programStages* resource. - -A simple single event with no registration example payload in XML format -where we send events from the "Inpatient morbidity and mortality" -program for the "Ngelehun CHC" facility in the demo database can be seen -below: - -```xml - - - - - - - - - -``` - -To perform some testing we can save the XML payload as a file -called *event.xml* and send it as a POST request to the events resource -in the API using curl with the following command: - -```bash -curl -d @event.xml "https://play.dhis2.org/demo/api/33/events" - -H "Content-Type:application/xml" -u admin:district -``` - -The same payload in JSON format looks like this: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "completedDate": "2013-05-18", - "storedBy": "admin", - "coordinate": { - "latitude": 59.8, - "longitude": 10.9 - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -To send this you can save it to a file called *event.json* and use curl -like this: - -```bash -curl -d @event.json "localhost/api/33/events" -H "Content-Type:application/json" - -u admin:district -``` - -We also support sending multiple events at the same time. A payload in -XML format might look like this: - -```xml - - - - - - - - - - - - - - - - - -``` - -You will receive an import summary with the response which can be -inspected in order to get information about the outcome of the request, -like how many values were imported successfully. The payload in JSON -format looks like this: - -```json -{ - "events": [ - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - } - ] - }, - { - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "coordinate": { - "latitude": "59.8", - "longitude": "10.9" - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "26" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Female" - } - ] - } ] -} -``` - -You can also use GeoJson to store any kind of geometry on your event. An example payload using GeoJson instead of the former latitude and longitude properties can be seen here: - -```json -{ - "program": "eBAyeGv0exc", - "orgUnit": "DiszpKrYNg8", - "eventDate": "2013-05-17", - "status": "COMPLETED", - "storedBy": "admin", - "geometry": { - "type": "POINT", - "coordinates": [59.8, 10.9] - }, - "dataValues": [ - { - "dataElement": "qrur9Dvnyt5", - "value": "22" - }, - { - "dataElement": "oZg33kd9taw", - "value": "Male" - }, - { - "dataElement": "msodh3rEMJa", - "value": "2013-05-18" - } - ] -} -``` - -As part of the import summary you will also get the identifier -*reference* to the event you just sent, together with a *href* element -which points to the server location of this event. The table below -describes the meaning of each element. - - - -Table: Events resource format - -| Parameter | Type | Required | Options (default first) | Description | -|---|---|---|---|---| -| program | string | true || Identifier of the single event with no registration program | -| orgUnit | string | true || Identifier of the organisation unit where the event took place | -| eventDate | date | true || The date of when the event occurred | -| completedDate | date | false || The date of when the event is completed. If not provided, the current date is selected as the event completed date | -| status | enum | false | ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | Whether the event is complete or not | -| storedBy | string | false | Defaults to current user | Who stored this event (can be username, system-name, etc) | -| coordinate | double | false || Refers to where the event took place geographically (latitude and longitude) | -| dataElement | string | true || Identifier of data element | -| value | string | true || Data value or measure for this event | - -##### OrgUnit matching { #orgunit-matching } - -By default the orgUnit parameter will match on the -ID, you can also select the orgUnit id matching scheme by using the -parameter orgUnitIdScheme=SCHEME, where the options are: *ID*, *UID*, -*UUID*, *CODE*, and *NAME*. There is also the *ATTRIBUTE:* scheme, which -matches on a *unique* metadata attribute value. - -#### Updating events { #webapi_updating_events } - -To update an existing event, the format of the payload is the same, but -the URL you are posting to must add the identifier to the end of the URL -string and the request must be PUT. - -The payload has to contain all, even non-modified, attributes. -Attributes that were present before and are not present in the current -payload any more will be removed by the system. - -It is not allowed to update an already deleted event. The same applies -to tracked entity instance and enrollment. - -```bash -curl -X PUT -d @updated_event.xml "localhost/api/33/events/ID" - -H "Content-Type: application/xml" -u admin:district -``` - -```bash -curl -X PUT -d @updated_event.json "localhost/api/33/events/ID" - -H "Content-Type: application/json" -u admin:district -``` - -#### Deleting events { #webapi_deleting_events } - -To delete an existing event, all you need is to send a DELETE request -with an identifier reference to the server you are using. - -```bash -curl -X DELETE "localhost/api/33/events/ID" -u admin:district -``` - -#### Assigning user to events { #webapi_user_assign_event } - -A user can be assigned to an event. This can be done by including the appropriate property in the payload when updating or creating the event. - - "assignedUser": "" - -The id refers to the if of the user. Only one user can be assigned to an event at a time. - -User assignment must be enabled in the program stage before users can be assigned to events. -#### Getting events { #webapi_getting_events } - -To get an existing event you can issue a GET request including the -identifier like this: - -```bash -curl "http://localhost/api/33/events/ID" -H "Content-Type: application/xml" -u admin:district -``` - -#### Querying and reading events { #webapi_querying_reading_events } - -This section explains how to read out the events that have been stored -in the DHIS2 instance. For more advanced uses of the event data, please -see the section on event analytics. The output format from the -`/api/events` endpoint will match the format that is used to send events -to it (which the analytics event api does not support). Both XML and -JSON are supported, either through adding .json/.xml or by setting the -appropriate *Accept* header. The query is paged by default and the -default page size is 50 events, *field* filtering works as it does for -metadata, add the *fields* parameter and include your wanted properties, -i.e. *?fields=program,status*. - - - -Table: Events resource query parameters - -| Key | Type | Required | Description | -|---|---|---|---| -| program | identifier | true (if not programStage is provided) | Identifier of program | -| programStage | identifier | false | Identifier of program stage | -| programStatus | enum | false | Status of event in program, ca be ACTIVE | COMPLETED | CANCELLED | -| followUp | boolean | false | Whether event is considered for follow up in program, can be true | false or omitted. | -| trackedEntityInstance | identifier | false | Identifier of tracked entity instance | -| orgUnit | identifier | true | Identifier of organisation unit | -| ouMode | enum | false | Org unit selection mode, can be SELECTED | CHILDREN | DESCENDANTS | -| startDate | date | false | Only events newer than this date | -| endDate | date | false | Only events older than this date | -| status | enum | false | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| lastUpdatedStartDate | date | false | Filter for events which were updated after this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedEndDate | date | false | Filter for events which were updated up until this date. Cannot be used together with *lastUpdatedDuration*. | -| lastUpdatedDuration | string | false | Include only items which are updated within the given duration. The format is , where the supported time units are “d” (days), “h” (hours), “m” (minutes) and “s” (seconds). Cannot be used together with *lastUpdatedStartDate* and/or *lastUpdatedEndDate*. | -| skipMeta | boolean | false | Exclude the meta data part of response (improves performance) | -| page | integer | false | Page number | -| pageSize | integer | false | Number of items in each page | -| totalPages | boolean | false | Indicates whether to include the total number of pages in the paging response. | -| skipPaging | boolean | false | Indicates whether to skip paging in the query and return all events. | -| dataElementIdScheme | string | false | Data element ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| categoryOptionComboIdScheme | string | false | Category Option Combo ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| orgUnitIdScheme | string | false | Organisation Unit ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programIdScheme | string | false | Program ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| programStageIdScheme | string | false | Program Stage ID scheme to use for export, valid options are UID, CODE and ATTRIBUTE:{ID} | -| idScheme | string | false | Allows to set id scheme for data element, category option combo, orgUnit, program and program stage at once. | -| order | string | false | The order of which to retrieve the events from the API. Usage: order=:asc/desc - Ascending order is default.
Properties: event | program | programStage | enrollment | enrollmentStatus | orgUnit | orgUnitName | trackedEntityInstance | eventDate | followup | status | dueDate | storedBy | created | lastUpdated | completedBy | completedDate
order=orgUnitName:DESC order=lastUpdated:ASC | -| event | comma delimited string | false | Filter the result down to a limited set of IDs by using *event=id1;id2*. | -| skipEventId | boolean | false | Skips event identifiers in the response | -| attributeCc (\*\*) | string | false | Attribute category combo identifier (must be combined with *attributeCos*) | -| attributeCos (\*\*) | string | false | Attribute category option identifiers, separated with ; (must be combined with *attributeCc*) | -| async | false | true | false | Indicates whether the import should be done asynchronous or synchronous. | -| includeDeleted | boolean | false | When true, soft deleted events will be included in your query result. | -| assignedUserMode | enum | false | Assigned user selection mode, can be CURRENT | PROVIDED | NONE | ANY. | -| assignedUser | comma delimited strings | false | Filter the result down to a limited set of events that are assigned to the given user IDs by using *assignedUser=id1;id2*. This parameter will be considered only if assignedUserMode is either PROVIDED or null. The API will error out, if for example, assignedUserMode=CURRENT and assignedUser=someId | - -> **Note** -> -> If the query contains neither `attributeCC` nor `attributeCos`, the server returns events for all attribute option combos where the user has read access. - -##### Examples { #examples } - -Query for all events with children of a certain organisation unit: - - /api/29/events.json?orgUnit=YuQRtpLP10I&ouMode=CHILDREN - -Query for all events with all descendants of a certain organisation -unit, implying all organisation units in the sub-hierarchy: - - /api/33/events.json?orgUnit=O6uvpzGd5pu&ouMode=DESCENDANTS - -Query for all events with a certain program and organisation unit: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - -Query for all events with a certain program and organisation unit, -sorting by due date - ascending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&order=dueDate - -Query for the 10 events with the newest event date in a certain program -and organisation unit - by paging and ordering by due date descending: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &order=eventDate:desc&pageSize=10&page=1 - -Query for all events with a certain program and organisation unit for a -specific tracked entity instance: - - /api/33/events.json?orgUnit=DiszpKrYNg8 - &program=eBAyeGv0exc&trackedEntityInstance=gfVxE3ALA9m - -Query for all events with a certain program and organisation unit older -or equal to - 2014-02-03: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc&endDate=2014-02-03 - -Query for all events with a certain program stage, organisation unit and -tracked entity instance in the year 2014: - - /api/33/events.json?orgUnit=DiszpKrYNg8&program=eBAyeGv0exc - &trackedEntityInstance=gfVxE3ALA9m&startDate=2014-01-01&endDate=2014-12-31 - -Query files associated with event data values. In the specific case of fetching an image file an -additional parameter can be provided to fetch the image with different dimensions. If dimension is -not provided, the system will return the original image. The parameter will be ignored in case of -fetching non-image files e.g pdf. Possible dimension values are *small(254 x 254), -medium(512 x 512), large(1024 x 1024) or original*. Any value other than those mentioned will be -discarded and the original image will be returned. - - /api/33/events/files?eventUid=hcmcWlYkg9u&dataElementUid=C0W4aFuVm4P&dimension=small - -Retrieve events with specified Organisation unit and Program, and use _Attribute:Gq0oWTf2DtN_ as -identifier scheme - - /api/events?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - -Retrieve events with specified Organisation unit and Program, and use UID as identifier scheme for -orgUnits, Code as identifier scheme for Program stages, and _Attribute:Gq0oWTf2DtN_ as identifier -scheme for the rest of the metadata with assigned attribute. - - api/events.json?orgUnit=DiszpKrYNg8&program=lxAQ7Zs9VYR&idScheme=Attribute:Gq0oWTf2DtN - &orgUnitIdScheme=UID&programStageIdScheme=Code - -#### Event grid query { #event-grid-query } - -In addition to the above event query end point, there is an event grid -query end point where a more compact "grid" format of events are -returned. This is possible by interacting with -/api/events/query.json|xml|xls|csv endpoint. - - /api/33/events/query - -Most of the query parameters mentioned in event querying and reading -section above are valid here. However, since the grid to be returned -comes with specific set of columns that apply to all rows (events), it -is mandatory to specify a program stage. It is not possible to mix -events from different programs or program stages in the return. - -Returning events from a single program stage, also opens up for new -functionality - for example sorting and searching events based on their -data element values. api/events/query has support for this. Below are -some examples - -A query to return an event grid containing only selected data elements -for a program stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &dataElement=qrur9Dvnyt5,fWIAEtYVEGk,K6uUAvq500H&order=lastUpdated:desc - &pageSize=50&page=1&totalPages=true - -A query to return an event grid containing all data elements of a -program - stage - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &includeAllDataElements=true - -A query to filter events based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50 - -In addition to the filtering, the above example also illustrates one -thing: the fact that there are no data elements mentioned to be returned -in the grid. When this happens, the system defaults back to return only -those data elements marked "Display in report" under program stage -configuration. - -We can also extend the above query to return us a grid sorted (asc|desc) -based on data element - value - - /api/33/events/query.json?orgUnit=DiszpKrYNg8&programStage=Zj7UnCAulEk - &filter=qrur9Dvnyt5:GT:20:LT:50&order=qrur9Dvnyt5:desc - -#### Event filters { #webapi_event_filters } - -To create, read, update and delete event filters you -can interact with the `/api/eventFilters` resource. - - /api/33/eventFilters - -##### Create and update an event filter definition { #create-and-update-an-event-filter-definition } - -For creating and updating an event filter in the -system, you will be working with the *eventFilters* -resource. *POST* is used to create and *PUT* method is used to update. The event filter definitions are used in the -Tracker Capture app to display relevant predefined "Working lists" in -the tracker user interface. - - - -Table: Request Payload - -| Request Property | Description | Example | -|---|---|---| -| name | Name of the filter. | "name":"My working list" | -| description | A description of the filter. | "description":"for listing all events assigned to me". | -| program | The uid of the program. | "program" : "a3kGcGDCuk6" | -| programStage | The uid of the program stage. | "programStage" : "a3kGcGDCuk6" | -| eventQueryCriteria | Object containing parameters for querying, sorting and filtering events. | "eventQueryCriteria": { "organisationUnit":"a3kGcGDCuk6", "status": "COMPLETED", "createdDate": { "from": "2014-05-01", "to": "2019-03-20" }, "dataElements": ["a3kGcGDCuk6:EQ:1", "a3kGcGDCuk6"], "filters": ["a3kGcGDCuk6:EQ:1"], "programStatus": "ACTIVE", "ouMode": "SELECTED", "assignedUserMode": "PROVIDED", "assignedUsers" : ["a3kGcGDCuk7", "a3kGcGDCuk8"], "followUp": false, "trackedEntityInstance": "a3kGcGDCuk6", "events": ["a3kGcGDCuk7", "a3kGcGDCuk8"], "fields": "eventDate,dueDate", "order": "dueDate:asc,createdDate:desc" } | - - - -Table: Event Query Criteria definition - -|||| -|---|---|---| -| followUp | Used to filter events based on enrollment followUp flag. Possible values are true|false. | "followUp": true | -| organisationUnit | To specify the uid of the organisation unit | "organisationUnit": "a3kGcGDCuk7" | -| ouMode | To specify the OU selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL | "ouMode": "SELECTED" | -| assignedUserMode | To specify the assigned user selection mode for events. Possible values are CURRENT| PROVIDED| NONE | ANY. See table below to understand what each value indicates. If PROVIDED (or null), non-empty assignedUsers in the payload will be considered. | "assignedUserMode": "PROVIDED" | -| assignedUsers | To specify a list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers": ["a3kGcGDCuk7", "a3kGcGDCuk8"] | -| displayOrderColumns | To specify the output ordering of columns | "displayOrderColumns": ["eventDate", "dueDate", "program"] | -| order | To specify ordering/sorting of fields and its directions in comma separated values. A single item in order is of the form "dataItem:direction". | "order"="a3kGcGDCuk6:desc,eventDate:asc" | -| dataFilters | To specify filters to be applied when listing events | "dataFilters"=[{ "dataItem": "abcDataElementUid", "le": "20", "ge": "10", "lt": "20", "gt": "10", "in": ["India", "Norway"], "like": "abc", "dateFilter": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } }] | -| status | Any valid EventStatus | "eventStatus": "COMPLETED" | -| events | To specify list of events | "events"=["a3kGcGDCuk6"] | -| completedDate | DateFilterPeriod object date filtering based on completed date. | "completedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "startBuffer": -5, "endBuffer": 5, "period": "LAST_WEEK", "type": "RELATIVE" } | -| eventDate | DateFilterPeriod object date filtering based on event date. | "eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" } | -| dueDate | DateFilterPeriod object date filtering based on due date. | "dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" } | -| lastUpdatedDate | DateFilterPeriod object date filtering based on last updated date. | "lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" } | - - - -Table: DateFilterPeriod object definition - -|||| -|---|---|---| -| type | Specify whether the date period type is ABSOLUTE | RELATIVE | "type" : "RELATIVE" | -| period | Specify if a relative system defined period is to be used. Applicable only when "type" is RELATIVE. (see [Relative Periods](#webapi_date_relative_period_values) for supported relative periods) | "period" : "THIS_WEEK" | -| startDate | Absolute start date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| endDate | Absolute end date. Applicable only when "type" is ABSOLUTE | "startDate":"2014-05-01" | -| startBuffer | Relative custom start date. Applicable only when "type" is RELATIVE | "startBuffer":-10 | -| endBuffer | Relative custom end date. Applicable only when "type" is RELATIVE | "startDate":+10 | - -The available assigned user selection modes are explained in the -following table. - - - -Table: Assigned user selection modes (event assignment) - -| Mode | Description | -|---|---| -| CURRENT | Assigned to the current logged in user | -| PROVIDED | Assigned to the users provided in the "assignedUser" parameter | -| NONE | Assigned to no users. | -| ANY | Assigned to any users. | - -A sample payload that can be used to create/update an eventFilter is shown below. - -```json -{ - "program": "ur1Edk5Oe2n", - "description": "Simple Filter for TB events", - "name": "TB events", - "eventQueryCriteria": { - "organisationUnit":"DiszpKrYNg8", - "eventStatus": "COMPLETED", - "eventDate": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "startBuffer": -5, - "endBuffer": 5, - "period": "LAST_WEEK", - "type": "RELATIVE" - }, - "dataFilters": [{ - "dataItem": "abcDataElementUid", - "le": "20", - "ge": "10", - "lt": "20", - "gt": "10", - "in": ["India", "Norway"], - "like": "abc" - }, - { - "dataItem": "dateDataElementUid", - "dateFilter": { - "startDate": "2014-05-01", - "endDate": "2019-03-20", - "type": "ABSOLUTE" - } - }, - { - "dataItem": "anotherDateDataElementUid", - "dateFilter": { - "startBuffer": -5, - "endBuffer": 5, - "type": "RELATIVE" - } - }, - { - "dataItem": "yetAnotherDateDataElementUid", - "dateFilter": { - "period": "LAST_WEEK", - "type": "RELATIVE" - } - }], - "programStatus": "ACTIVE" - } -} -``` - - -##### Retrieving and deleting event filters { #retrieving-and-deleting-event-filters } - -A specific event filter can be retrieved by using the following api - - GET /api/33/eventFilters/{uid} - -All event filters can be retrieved by using the following api. - - GET /api/33/eventFilters?fields=* - -All event filters for a specific program can be retrieved by using the following api - - GET /api/33/eventFilters?filter=program:eq:IpHINAT79UW - -An event filter can be deleted by using the following api - - DELETE /api/33/eventFilters/{uid} - -### Relationships { #relationships } -Relationships are links between two entities in tracker. These entities can be tracked entity instances, enrollments and events. - -There are multiple endpoints that allow you to see, create, delete and update relationships. The most common is the /api/trackedEntityInstances endpoint, where you can include relationships in the payload to create, update or deleting them if you omit them - Similar to how you work with enrollments and events in the same endpoint. All the tracker endpoints, /api/trackedEntityInstances, /api/enrollments and /api/events also list their relationships if requested in the field filter. - -The standard endpoint for relationships is, however, /api/relationships. This endpoint provides all the normal CRUD operations for relationships. - -You can view a list of relationships by trackedEntityInstance, enrollment or event: - - - GET /api/relationships?[tei={teiUID}|enrollment={enrollmentUID}|event={eventUID}] - - -This request will return a list of any relationship you have access to see that includes the trackedEntityInstance, enrollment or event you specified. Each relationship is represented with the following JSON: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "relationshipName": "Mother-Child", - "relationship": "t0HIBrc65Rm", - "bidirectional": false, - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - }, - "created": "2019-04-26T09:30:56.267", - "lastUpdated": "2019-04-26T09:30:56.267" -} -``` - -You can also view specified relationships using the following endpoint: - - GET /api/relationships/ - -To create or update a relationship, you can use the following endpoints: - - POST /api/relationships - PUT /api/relationships - -And use the following payload structure: - -```json -{ - "relationshipType": "dDrh5UyCyvQ", - "from": { - "trackedEntityInstance": { - "trackedEntityInstance": "vOxUH373fy5" - } - }, - "to": { - "trackedEntityInstance": { - "trackedEntityInstance": "pybd813kIWx" - } - } -} -``` - -To delete a relationship, you can use this endpoint: - - DELETE /api/relationships/ - -In our example payloads, we use a relationship between trackedEntityInstances. Because of this, the "from" and "to" properties of our payloads include "trackedEntityInstance" objects. If your relationship includes other entities, you can use the following properties: - -```json -{ - "enrollment": { - "enrollment": "" - } -} -``` - -```json -{ - "event": { - "event": "" - } -} -``` - -Relationship can be soft deleted. In that case, you can use the `includeDeleted` request parameter to see the relationship. - - - GET /api/relationships?tei=pybd813kIWx?includeDeleted=true - - -### Update strategies { #webapi_tei_update_strategies } - -Two update strategies for all 3 tracker endpoints are supported: -enrollment and event creation. This is useful when you have generated an -identifier on the client side and are not sure if it was created or not -on the server. - - - -Table: Available tracker strategies - -| Parameter | Description | -|---|---| -| CREATE | Create only, this is the default behavior. | -| CREATE_AND_UPDATE | Try and match the ID, if it exist then update, if not create. | - -To change the parameter, please use the strategy parameter: - - POST /api/33/trackedEntityInstances?strategy=CREATE_AND_UPDATE - -### Tracker bulk deletion { #webapi_tracker_bulk_deletion } - -Bulk deletion of tracker objects work in a similar fashion to adding and -updating tracker objects, the only difference is that the -`importStrategy` is *DELETE*. - -*Example: Bulk deletion of tracked entity instances:* - -```json -{ - "trackedEntityInstances": [ - { - "trackedEntityInstance": "ID1" - }, { - "trackedEntityInstance": "ID2" - }, { - "trackedEntityInstance": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/trackedEntityInstances?strategy=DELETE" -``` - -*Example: Bulk deletion of enrollments:* - -```json -{ - "enrollments": [ - { - "enrollment": "ID1" - }, { - "enrollment": "ID2" - }, { - "enrollment": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/enrollments?strategy=DELETE" -``` - -*Example: Bulk deletion of events:* - -```json -{ - "events": [ - { - "event": "ID1" - }, { - "event": "ID2" - }, { - "event": "ID3" - } - ] -} -``` - -```bash -curl -X POST -d @data.json -H "Content-Type: application/json" - "http://server/api/33/events?strategy=DELETE" -``` - -### Identifier reuse and item deletion via POST and PUT methods { #webapi_updating_and_deleting_items } - -Tracker endpoints */trackedEntityInstances*, */enrollments*, */events* -support CRUD operations. The system keeps track of used identifiers. -Therefore, an item which has been created and then deleted (e.g. events, -enrollments) cannot be created or updated again. If attempting to delete -an already deleted item, the system returns a success response as -deletion of an already deleted item implies no change. - -The system does not allow to delete an item via an update (*PUT*) or -create (*POST*) method. Therefore, an attribute *deleted* is ignored in -both *PUT* and *POST* methods, and in *POST* method it is by default set -to *false*. - -### Import parameters { #webapi_import_parameters } - -The import process can be customized using a set of import parameters: - - - -Table: Import parameters - -| Parameter | Values (default first) | Description | -|---|---|---| -| dataElementIdScheme | id | name | code | attribute:ID | Property of the data element object to use to map the data values. | -| orgUnitIdScheme | id | name | code | attribute:ID | Property of the org unit object to use to map the data values. | -| idScheme | id | name | code| attribute:ID | Property of all objects including data elements, org units and category option combos, to use to map the data values. | -| dryRun | false | true | Whether to save changes on the server or just return the import summary. | -| strategy | CREATE | UPDATE | CREATE_AND_UPDATE | DELETE | Save objects of all, new or update import status on the server. | -| skipNotifications | true | false | Indicates whether to send notifications for completed events. | -| skipFirst | true | false | Relevant for CSV import only. Indicates whether CSV file contains a header row which should be skipped. | -| importReportMode | FULL, ERRORS, DEBUG | Sets the `ImportReport` mode, controls how much is reported back after the import is done. `ERRORS` only includes *ObjectReports* for object which has errors. `FULL` returns an *ObjectReport* for all objects imported, and `DEBUG` returns the same plus a name for the object (if available). | - -#### CSV Import / Export { #webapi_events_csv_import_export } - -In addition to XML and JSON for event import/export, in DHIS2.17 we -introduced support for the CSV format. Support for this format builds on -what was described in the last section, so here we will only write about -what the CSV specific parts are. - -To use the CSV format you must either use the `/api/events.csv` -endpoint, or add *content-type: text/csv* for import, and *accept: -text/csv* for export when using the `/api/events` endpoint. - -The order of column in the CSV which are used for both export and import -is as follows: - - - -Table: CSV column - -| Index | Key | Type | Description | -|---|---|---|---| -| 1 | event | identifier | Identifier of event | -| 2 | status | enum | Status of event, can be ACTIVE | COMPLETED | VISITED | SCHEDULE | OVERDUE | SKIPPED | -| 3 | program | identifier | Identifier of program | -| 4 | programStage | identifier | Identifier of program stage | -| 5 | enrollment | identifier | Identifier of enrollment (program instance) | -| 6 | orgUnit | identifier | Identifier of organisation unit | -| 7 | eventDate | date | Event date | -| 8 | dueDate | date | Due Date | -| 9 | latitude | double | Latitude where event happened | -| 10 | longitude | double | Longitude where event happened | -| 11 | dataElement | identifier | Identifier of data element | -| 12 | value | string | Value / measure of event | -| 13 | storedBy | string | Event was stored by (defaults to current user) | -| 14 | providedElsewhere | boolean | Was this value collected somewhere else | -| 14 | completedDate | date | Completed date of event | -| 14 | completedBy | string | Username of user who completed event | - -*Example of 2 events with 2 different data value - each:* - -```csv -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,1,, -EJNxP3WreNP,COMPLETED,,,,,2016-01-01,2016-01-01,,,,2,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,3,, -qPEdI1xn7k0,COMPLETED,,,,,2016-01-01,2016-01-01,,,,4,, -``` - -#### Import strategy: SYNC { #webapi_sync_import_strategy } - -The import strategy SYNC should be used only by internal synchronization -task and not for regular import. The SYNC strategy allows all 3 -operations: CREATE, UPDATE, DELETE to be present in the payload at the -same time. - -### Tracker Ownership Management { #webapi_tracker_ownership_management } - -A new concept called Tracker Ownership is introduced from 2.30. There -will now be one owner organisation unit for a tracked entity instance in -the context of a program. Programs that are configured with an access -level of *PROTECTED* or *CLOSED* will adhere to the ownership -privileges. Only those users belonging to the owning org unit for a -tracked entity-program combination will be able to access the data -related to that program for that tracked entity. - -#### Tracker Ownership Override : Break the Glass { #webapi_tracker_ownership_override_api } - -It is possible to temporarily override this ownership privilege for a -program that is configured with an access level of *PROTECTED*. Any user -will be able to temporarily gain access to the program related data, if -the user specifies a reason for accessing the tracked entity-program -data. This act of temporarily gaining access is termed as *breaking the -glass*. Currently, the temporary access is granted for 3 hours. DHIS2 -audits breaking the glass along with the reason specified by the user. -It is not possible to gain temporary access to a program that has been -configured with an access level of *CLOSED*. To break the glass for a -tracked entity program combination, you can issue a POST request as -shown: - - /api/33/tracker/ownership/override?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care - -#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer_api } - -It is possible to transfer the ownership of a tracked entity-program -from one org unit to another. This will be useful in case of patient -referrals or migrations. Only an owner (or users who have broken the -glass) can transfer the ownership. To transfer ownership of a tracked -entity-program to another organisation unit, you can issue a PUT request -as shown: - - /api/33/tracker/ownership/transfer?trackedEntityInstance=DiszpKrYNg8 - &program=eBAyeGv0exc&ou=EJNxP3WreNP - - -## Potential Duplicates { #potential-duplicates } - -Potential duplicates are records we work with in the data deduplication feature. Due to the nature of the deduplication feature, this API endpoint is somewhat restricted. - -A potential duplicate represents a pair of records which are suspected to be a duplicate. - -The payload of a potential duplicate looks like this: - -```json -{ - "original": "", - "duplicate": "", - "status": "OPEN|INVALID|MERGED" -} -``` - -You can retrieve a list of potential duplicates using the following endpoint: - - GET /api/potentialDuplicates - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| teis | List of tracked entity instances | List of string (separated by comma)| existing tracked entity instance id | -| status | Potential duplicate status | string | `OPEN `, `INVALID`, `MERGED`, `ALL` | - -| Status code | Description -|---|---| -| 400 | Invalid input status - -You can inspect individual potential duplicate records: - - GET /api/potentialDuplicates/ - -| Status code | Description -|---|---| -| 404 | Potential duplicate not found - -To create a new potential duplicate, you can use this endpoint: - - POST /api/potentialDuplicates - -The payload you provide must include IDs of Original and Duplicate TEIs. - -```json -{ - "original": "", - "duplicate": "" -} -``` - -| Status code | Description -|---|---| -| 400 | Input original or duplicate is null or has invalid id -| 403 | User do not have access to read origianl or duplicate TEIs -| 404 | TEI not found -| 409 | Pair of original and duplicate TEIs already existing - -To update a potential duplicate status: - - PUT /api/potentialDuplicates/ - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| status | Potential duplicate status | string | `OPEN`, `INVALID`, `MERGED` | - -| Status code | Description -|---|---| -| 400 | You can't update a potential duplicate to MERGED as this is possible only by a merging request -| 400 | You can't update a potential duplicate that is already in a MERGED status - -## Merging Tracked Entity Instances { #merging-tracked-entity-instances } -Tracked entity instances can now be merged together if they are viable. To initiate a merge, the first step is to define two tracked entity instances as a Potential Duplicate. The merge endpoint -will move data from the duplicate tracked entity instance to the original tracked entity instance, and delete the remaining data of the duplicate. - -To merge a Potential Duplicate, or the two tracked entity instances the Potential Duplicate represents, the following endpoint can be used: - - POST /api/potentialDuplicates//merge - -| Parameter name | Description | Type | Allowed values | -|---|---|---|---| -| mergeStrategy | Strategy to use for merging the potentialDuplicate | enum | AUTO(default) or MANUAL | - -The endpoint accepts a single parameter, "mergeStrategy", which decides which strategy to use when merging. For the AUTO strategy, the server will attempt to merge the two tracked entities -automatically, without any input from the user. This strategy only allows merging tracked entities without conflicting data (See examples below). The other strategy, MANUAL, requires the -user to send in a payload describing how the merge should be done. For examples and rules for each strategy, see their respective sections below. - -### Merge Strategy AUTO { #merge-strategy-auto } -The automatic merge will evaluate the mergability of the two tracked entity instances, and merge them if they are deemed mergable. The mergability is based on whether the two tracked entity instances -has any conflicts or not. Conflicts refers to data which cannot be merged together automatically. Examples of possible conflicts are: -- The same attribute has different values in each tracked entity instance -- Both tracked entity instances are enrolled in the same program -- Tracked entity instances have different types - -If any conflict is encountered, an errormessage is returned to the user. - -When no conflicts are found, all data in the duplicate that is not already in the original will be moved over to the original. This includes attribute values, enrollments (Including events) and relationships. -After the merge completes, the duplicate is deleted and the potentialDuplicate is marked as MERGED. - -When requesting an automatic merge like this, a payload is not required and will be ignored. - -### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when the merge has resolvable conflicts, or when not all the data is required to be moved over during a merge. For example, if an attribute has different values in both tracked -entity instances, the user can specify whether to keep the original value, or move over the duplicate's value. Since the manual merge is the user explicitly requesting to move data, there are some different -checks being done here: -- Relationship cannot be between the original and the duplicate (This results in an invalid self-referencing relationship) -- Relationship cannot be of the same type and to the same object in both tracked entity instances (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) - -There are two ways to do a manual merge: With and without a payload. - -When a manual merge is requested without a payload, we are telling the API to merge the two tracked entity instances without moving any data. In other words, we are just removing the duplicate and marking the -potentialDuplicate MERGED. This might be valid in a lot of cases where the tracked entity instance was just created, but not enrolled for example. - -Otherwise, if a manual merge is requested with a payload, the payload refers to what data should be moved from the duplicate to the original. The payload looks like this: -```json -{ - "trackedEntityAttributes": ["B58KFJ45L9D"], - "enrollments": ["F61SJ2DhINO"], - "relationships": ["ETkkZVSNSVw"] -} -``` - -This payload contains three lists, one for each of the types of data that can be moved. `trackedEntityAttributes` is a list of uids for tracked entity attributes, `enrollments` is a list of uids for enrollments and `relationships` -a list of uids for relationships. The uids in this payload have to refer to data that actually exists on the duplicate. There is no way to add new data or change data using the merge endpoint - Only moving data. - - -### Additional information about merging { #additional-information-about-merging } -Currently it is not possible to merge tracked entity instances that are enrolled in the same program, due to the added complexity. A workaround is to manually remove the enrollments from one of the tracked entity -instances before starting the merge. - -All merging is based on data already persisted in the database, which means the current merging service is not validating that data again. This means if data was already invalid, it will not be reported during the merge. -The only validation done in the service relates to relationships, as mentioned in the previous section. - - - -## Program Notification Template { #program-notification-template } - -Program Notification Template lets you create message templates which can be sent as a result of different type of events. -Message and Subject templates will be translated into actual values and can be sent to the configured destination. Each program notification template will be -transformed to either MessageConversation object or ProgramMessage object based on external or internal notificationRecipient. These intermediate objects will -only contain translated message and subject text. -There are multiple configuraiton parameters in Program Notification Template which are critical for correct working of notifications. -All those are explained in the table below. - - POST /api/programNotificationTemplates - -```json -{ - "name": "Case notification", - "notificationTrigger": "ENROLLMENT", - "subjectTemplate": "Case notification V{org_unit_name}", - "displaySubjectTemplate": "Case notification V{org_unit_name}", - "notifyUsersInHierarchyOnly": false, - "sendRepeatable": false, - "notificationRecipient": "ORGANISATION_UNIT_CONTACT", - "notifyParentOrganisationUnitOnly": false, - "displayMessageTemplate": "Case notification A{h5FuguPFF2j}", - "messageTemplate": "Case notification A{h5FuguPFF2j}", - "deliveryChannels": [ - "EMAIL" - ] -} -``` - -The fields are explained in the following table. - - -Table: Program Notification Template payload - -| Field | Required | Description | Values | -|---|---|---|---| -| name | Yes | name of Program Notification Template | case-notification-alert | -| notificationTrigger | Yes | When notification should be triggered. Possible values are ENROLLMENT, COMPLETION, PROGRAM_RULE, SCHEDULED_DAYS_DUE_DATE| ENROLLMENT | -| subjectTemplate | No | Subject template string | Case notification V{org_unit_name} | -| messageTemplate | Yes | Message template string | Case notification A{h5FuguPFF2j} | -| notificationRecipient | YES | Who is going to receive notification. Possible values are USER_GROUP, ORGANISATION_UNIT_CONTACT, TRACKED_ENTITY_INSTANCE, USERS_AT_ORGANISATION_UNIT, DATA_ELEMENT, PROGRAM_ATTRIBUTE, WEB_HOOK | USER_GROUP | -| deliveryChannels | No | Which channel should be used for this notification. It can be either SMS, EMAIL or HTTP | SMS | -| sendRepeatable | No | Whether notification should be sent multiple times | false | - -NOTE: WEB_HOOK notificationRecipient is used only to POST http request to an external system. Make sure to choose HTTP delivery channel when using WEB_HOOK. - -### Retrieving and deleting Program Notification Template { #retrieving-and-deleting-program-notification-template } - -The list of Program Notification Templates can be retrieved using GET. - - GET /api/programNotificationTemplates - -For one particular Program Notification Template. - - GET /api/33/programNotificationTemplates/{uid} - -To get filtered list of Program Notification Templates - - GET /api/programNotificationTemplates/filter?program= - GET /api/programNotificationTemplates/filter?programStage= - -Program Notification Template can be deleted using DELETE. - - DELETE /api/33/programNotificationTemplates/{uid} - - -## Program Messages { #program-messages } - -Program message lets you send messages to tracked entity instances, -contact addresses associated with organisation units, phone numbers and -email addresses. You can send messages through the `messages` resource. - - /api/33/messages - -### Sending program messages { #sending-program-messages } - -Program messages can be sent using two delivery channels: - - - SMS (SMS) - - - Email address (EMAIL) - -Program messages can be sent to various recipients: - - - Tracked entity instance: The system will look up attributes of value - type PHONE_NUMBER or EMAIL (depending on the specified delivery - channels) and use the corresponding attribute values. - - - Organisation unit: The system will use the phone number or email - information registered for the organisation unit. - - - List of phone numbers: The system will use the explicitly defined - phone numbers. - - - List of email addresses: The system will use the explicitly defined - email addresses. - -Below is a sample JSON payload for sending messages using POST requests. -Note that message resource accepts a wrapper object named -`programMessages` which can contain any number of program messages. - - POST /api/33/messages - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "UN810PwyVYO" - }, - "organisationUnit": { - "id": "Rp268JB6Ne4" - }, - "phoneNumbers": [ - "55512345", - "55545678" - ], - "emailAddresses": [ - "johndoe@mail.com", - "markdoe@mail.com" - ] - }, - "programInstance": { - "id": "f3rg8gFag8j" - }, - "programStageInstance": { - "id": "pSllsjpfLH2" - }, - "deliveryChannels": [ - "SMS", "EMAIL" - ], - "notificationTemplate": "Zp268JB6Ne5", - "subject": "Outbreak alert", - "text": "An outbreak has been detected", - "storeCopy": false - }] -} -``` - -The fields are explained in the following table. - - - -Table: Program message payload - -| Field | Required | Description | Values | -|---|---|---|---| -| recipients | Yes | Recipients of the program message. At least one recipient must be specified. Any number of recipients / types can be specified for a message. | Can be trackedEntityInstance, organisationUnit, an array of phoneNumbers or an array of emailAddresses. | -| programInstance | Either this or programStageInstance required | The program instance / enrollment. | Enrollment ID. | -| programStageInstance | Either this or programInstance required | The program stage instance / event. | Event ID. | -| deliveryChannels | Yes | Array of delivery channels. | SMS | EMAIL | -| subject | No | The message subject. Not applicable for SMS delivery channel. | Text. | -| text | Yes | The message text. | Text. | -| storeCopy | No | Whether to store a copy of the program message in DHIS2. | false (default) | true | - -A minimalistic example for sending a message over SMS to a tracked -entity instance looks like this: - -```bash -curl -d @message.json "https://play.dhis2.org/demo/api/33/messages" - -H "Content-Type:application/json" -u admin:district -``` - -```json -{ - "programMessages": [{ - "recipients": { - "trackedEntityInstance": { - "id": "PQfMcpmXeFE" - } - }, - "programInstance": { - "id": "JMgRZyeLWOo" - }, - "deliveryChannels": [ - "SMS" - ], - "text": "Please make a visit on Thursday" - }] -} -``` - -### Retrieving and deleting program messages { #retrieving-and-deleting-program-messages } - -The list of messages can be retrieved using GET. - - GET /api/33/messages - -To get the list of sent tracker messages, the below endpoint can be used. ProgramInstance or ProgramStageInstance uid has to be provided. - - GET /api/33/messages/scheduled/sent?programInstance={uid} - GET /api/33/messages/scheduled/sent?programStageInstance={uid} - -To get the list of all scheduled message - - GET /api/33/messages/scheduled - GET /api/33/messages/scheduled?scheduledAt=2020-12-12 - -One particular message can also be retrieved using GET. - - GET /api/33/messages/{uid} - -Message can be deleted using DELETE. - - DELETE /api/33/messages/{uid} - - -### Querying program messages { #querying-program-messages } - -The program message API supports program message queries based on -request parameters. Messages can be filtered based on below mentioned -query parameters. All requests should use the GET HTTP verb for -retrieving information. - - - -Table: Query program messages API - -| Parameter | URL | -|---|---| -| programInstance | /api/33/messages?programInstance=6yWDMa0LP7 | -| programStageInstance | /api/33/messages?programStageInstance=SllsjpfLH2 | -| trackedEntityInstance | /api/33/messages?trackedEntityInstance=xdfejpfLH2 | -| organisationUnit | /api/33/messages?ou=Sllsjdhoe3 | -| processedDate | /api/33/messages?processedDate=2016-02-01 | - - # Email { #email } diff --git a/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp b/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp index a2217fd66..f6d499ae3 100644 --- a/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:28:34Z \ No newline at end of file +2024-06-04T21:28:44Z \ No newline at end of file diff --git a/projects/docs-full-site/ar/.cache_timestamp b/projects/docs-full-site/ar/.cache_timestamp index 182b56fb4..6580d1863 100644 --- a/projects/docs-full-site/ar/.cache_timestamp +++ b/projects/docs-full-site/ar/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:20:28Z \ No newline at end of file +2024-06-04T21:20:09Z \ No newline at end of file diff --git a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index dc159f688..7959382eb 100644 --- a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/analytics.md" -revision_date: '2024-05-02' +revision_date: '2024-05-31' tags: -- Develop - DHIS core version master +- Develop --- # Analytics { #analytics } @@ -816,7 +816,7 @@ Table: Query parameters for event query analytics only | Query parameter | Required | Description | خيارات | |---|---|---|---| -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return events which have coordinates. | false | true | @@ -1723,7 +1723,7 @@ Table: Query parameters for enrollment query endpoint | filter | No | Dimension identifier including data elements, attributes, periods, organisation units and organisation unit group sets. Parameter can be repeated any number of times. Item filters can be applied to a dimension on the format ::. Filter values are case-insensitive. || | programStatus | No | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | No | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return enrollments which have coordinates. | false | true | diff --git a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index 30ab01c65..d2d3368f7 100644 --- a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- Develop - DHIS core version master +- Develop --- # Metadata { #metadata } diff --git a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index fbd4b2e7f..8bcd1b598 100644 --- a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- Develop - DHIS core version master +- Develop --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index 3c80ebcfa..a1313163a 100644 --- a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- Develop - DHIS core version master +- Develop --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md index a03ae7175..658a067c5 100644 --- a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md +++ b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: -- Develop - DHIS core version master +- Develop --- # Tracker { #webapi_tracker } @@ -18,20 +18,21 @@ tags: > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -134,7 +135,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | No | Yes | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | Yes | No | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | No | Yes | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -194,9 +194,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Attributes { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -211,18 +213,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | Description | Required | Immutable | Type | Example | |---|---|---|---|---|---| @@ -237,31 +241,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Notes { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -272,10 +276,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -317,92 +321,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | Description | Example | -|---|---|---| -| name | Name of the working list. Required. || -| description | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Description | Example | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -411,9 +330,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -446,7 +365,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -846,7 +765,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -1292,7 +1211,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -1422,7 +1341,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | لا ينطبق | Undefined error message. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -1432,7 +1351,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -1457,8 +1376,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -1511,7 +1430,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -1567,7 +1486,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -1589,7 +1508,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -1623,7 +1542,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -1675,9 +1594,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -1757,8 +1676,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -1863,7 +1782,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -2125,8 +2044,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -2330,8 +2249,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -2626,13 +2545,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -2678,7 +2597,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -2747,13 +2666,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -2765,7 +2684,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -2778,7 +2697,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -2788,7 +2707,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -2818,7 +2737,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -2834,3 +2753,119 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } + +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. + +### Program stage working lists { #program-stage-working-lists } + +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. + + /api/programStageWorkingLists + +#### Payload { #payload } + +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: + +Table: Payload + +| Payload values | Description | Example | +|---|---|---| +| name | Name of the working list. Required. || +| description | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. + +Table: Program Stage Query Criteria + +| Criteria values | Description | Example | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | + +See an example payload below: + +```json +{ + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" + }, + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" + }, + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ + { + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } +} +``` + diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 18e9be8c7..b30dea3ad 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Use - DHIS core version 2.41 +- Use --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index fb26437d4..3f73fd44b 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index c6fbcb597..d37dc6d10 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Use - DHIS core version 2.41 +- Use --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 575fc9118..16581ae92 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index e16665726..123c65776 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index 464d94ae2..ce5aec70b 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Use - DHIS core version 2.41 +- Use --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 1ea06ef7c..5ebe76acf 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index b8978480b..0099bce1c 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 48dbfdee8..a177e99d1 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index e11d40608..a825e338b 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index 0629e8d72..c7b9f3c93 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index 73d042d6f..328c184a0 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Use - DHIS core version 2.41 +- Use --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index 05c94b954..88a1f8cde 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Use - DHIS core version 2.41 +- Use --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index d47be21a8..9aa84c2f5 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Use - DHIS core version 2.41 +- Use --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index b2eb9d44f..b90e7379a 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Use - DHIS core version 2.41 +- Use --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index 4c2f576d9..76e65454f 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index b2b2c8194..fd2ae3160 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Use - DHIS core version 2.41 +- Use --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index a50bca106..0c443529d 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Use - DHIS core version 2.41 +- Use --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 887eb37ea..d17b4ccbd 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index 00427b830..bc983707c 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 2b1ad576b..5a352fa9c 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 6786075b2..6b6cbf924 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 5c9487cd1..d98847f90 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # System settings { #settings } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 70be1dc65..a7c3d7878 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 703da69e4..844ae2f13 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Use - DHIS core version 2.41 +- Use --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index 6835e62da..7f9b1dda0 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 70b99bd7b..8463a1d1f 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index 53887d9c9..c8925636c 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index b807f74d8..ecc8ff255 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 10ae5b554..d90a2b30f 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index e556625f2..91eb4e939 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 02b6d19b1..a4c4dbbc1 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Use - DHIS core version 2.41 +- Use --- > **Caution** diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index e31e9d22e..82fdba5bf 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index ce81b04fc..9a6c4c557 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Use - DHIS core version 2.41 +- Use --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 26f498935..97cdc7f4a 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Use - DHIS core version 2.41 +- Use --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 61b57676a..513ac2010 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 16ad233c8..6af3da161 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index cc2d52960..86b6948b0 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index d59391e70..3d6dc22c3 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Use - DHIS core version 2.41 +- Use --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index dda5e012a..56f2bc46e 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Use - DHIS core version 2.41 +- Use --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 28645fff6..d7a5bf33b 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index add7a9713..afaa2df3f 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Messaging { #messages } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index c81cd73b5..55ba690b6 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index adcd05b72..fd2f99f81 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index de2a48b10..3a7546346 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version master +- Use --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index ff7fa25c8..752bed3a1 100644 --- a/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version master +- Use --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/cs/.cache_timestamp b/projects/docs-full-site/cs/.cache_timestamp index 5c6a34f83..61ed9345e 100644 --- a/projects/docs-full-site/cs/.cache_timestamp +++ b/projects/docs-full-site/cs/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:20:40Z \ No newline at end of file +2024-06-04T21:20:24Z \ No newline at end of file diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index ed63b9c8c..00f68b860 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/analytics.md" -revision_date: '2024-05-02' +revision_date: '2024-05-31' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Analytika { #analytics } @@ -775,7 +775,7 @@ Tabulka: Parametry dotazu pouze pro analýzu dotazů událostí | Parametr dotazu | Požadované | Popis | Možnosti | |---|---|---|---| -| ouMode | Ne | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | Ne | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Ne | Dimenze, které mají být seřazeny vzestupně, mohou odkazovat na datum události, název a kód organizační jednotky a jakékoli identifikátory položek. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Ne | Dimenze, které mají být seřazeny sestupně, mohou odkazovat na datum události, název a kód organizační jednotky a jakékoli identifikátory položek. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | Ne | Zda se mají vrátit pouze události, které mají souřadnice. | false | true | @@ -1667,7 +1667,7 @@ Tabulka: Parametry dotazu pro koncový bod dotazu registrace | filtr | Ne | Identifikátor dimenze zahrnující datové prvky, atributy, období, organizační jednotky a sady skupin organizačních jednotek. Parametr lze opakovat libovolněkrát. Filtry položek lze použít na dimenzi ve formátu : : . Hodnoty filtru nerozlišují malá a velká písmena. || | programStatus | Ne | Zadejte stav zápisu zápisů, které chcete zahrnout. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | řetězec | Ne | Identifikátor data, např.: "2016-01-01". Přepíše počáteční datum relativního období | -| ouMode | Ne | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | Ne | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Ne | Dimenze, které mají být seřazeny vzestupně, mohou odkazovat na datum registrace, datum incidentu, název a kód organizační jednotky. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Ne | Dimenze, které mají být seřazeny sestupně, mohou odkazovat na datum registrace, datum incidentu, název a kód organizační jednotky. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | Ne | Zda se mají vrátit pouze zápisy, které mají souřadnice. | false | true | diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index 136cff871..e3409e7ea 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Aplikace { #apps } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index 5548823b6..ec193551c 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" revision_date: '2023-06-23' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index 3dc794d5c..17e1b67b0 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Schválení dat { #data-approval } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index b79a6fe62..93114bac2 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index 7a663ae79..6d3f7abbe 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Výměna dat { #data-exchange } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index b3884ff42..e730acec1 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Data { #data } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index 6cd4cfc5f..705e79c9d 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Data store { #data-store } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index 9e852fe14..71c24c896 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Ověření dat { #data-validation } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index d31c07b59..cb7951add 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 99ccd4e55..119f71957 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # I18n { #i18n } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index 494974f2c..a3ce83224 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Přehled { #webapi } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index ac98e0dc2..602523d97 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Údržba { #maintenance } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md index 1baa747e5..6bb6e2e6a 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Zprávy { #messaging } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index 5e9ea1524..c11d31472 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index 6e0adf3cc..cbf282ee2 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Metadata { #metadata } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md index 878838123..02223986d 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Profil organizační jednotky { #org_unit_profile } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index 9c293b3b2..7b4ed83c6 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index 78a1ef198..f006c65ef 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/route.md" revision_date: '2024-05-15' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Route { #route } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index adf476d70..b9110ae0f 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Plánování { #webapi_scheduling } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index 1b6d4969a..3277fe778 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Nastavení a konfigurace { #settings-and-configuration } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index 1a7595ca2..b45b7c47c 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Sdílení { #sharing } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index 780be007e..2fcc9bb94 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # SMS { #sms } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index 031d42527..a4fce5a7d 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Synchronizace { #webapi_synchronization } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md index 0e8c262ad..6a7ea9d47 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Tracker { #webapi_tracker } @@ -18,20 +18,21 @@ tags: > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Objekty Trasovače { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -134,7 +135,6 @@ point out any exceptional cases between these two. | program | Pouze pro čtení dat. Typ programu, který má registrace, která událost vlastní. | Ne | Ano | String:Uid | ABCDEF12345 | | trackedEntity | Pouze pro čtení dat. Trasovaná entita, která událost vlastní. ***Neplatí pro `PROGRAM AKCE`*** | Ne | Ne | String:Uid | ABCDEF12345 | | status | Stav události. AKTIVNÍ, pokud není součástí dodávky. | Ne | Ne | Výčet | AKTIVNÍ, DOKONČENÉ, NAVŠTÍVENÉ, PLÁNOVANÉ, PO TERMÍNU, PŘESKOČENO | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | Ne | Ne | Výčet | AKTIVNÍ, DOKONČENO, ZRUŠENO | | orgUnit | Organizační jednotka, kde uživatel zaregistroval událost. | Ano | Ne | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | Ne | Ano | Date:ISO 8601 | RRRR-MM-DDThh:mm:ss | | createdAtClient | Časové razítko, kdy uživatel vytvořil událost na klientovi | Ne | Ne | Date:ISO 8601 | RRRR-MM-DDThh:mm:ss | @@ -194,9 +194,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Atributy { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Vlastnictví | Popis | Požadované | Neměnný | Typ | Příklad | |---|---|---|---|---|---| @@ -211,18 +213,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -Zatímco `Attributes` popisuje `trasovanou entitu` nebo `zápis`, `datové hodnoty` popisují `událost`. Hlavní rozdíl spočívá v tom, že `atributy` mohou mít pro danou `trasovanou entitu` pouze jednu hodnotu. Naproti tomu `datové hodnoty` mohou mít mnoho různých hodnot pro různé `události` - i když všechny `události` patří ke stejnému `zápisu` nebo `trasované entitě`. +While attributes describe a tracked entity, data values describe an event. | Vlastnictví | Popis | Požadované | Neměnný | Typ | Příklad | |---|---|---|---|---|---| @@ -237,31 +241,31 @@ Zatímco `Attributes` popisuje `trasovanou entitu` nebo `zápis`, `datové hodno > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Poznámky { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -272,10 +276,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -317,92 +321,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Tabulka: Datový obsah - -| Hodnoty datového obsahu | Popis | Příklad | -|---|---|---| -| název | Name of the working list. Required. || -| popis | A description of the working list. || -| program | Objekt obsahující id programu. Požadované. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Popis | Příklad | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| řazení | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Import trackeru (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -411,9 +330,9 @@ to import i.e. create, update and delete * **Zápisy** * **Události** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -446,7 +365,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -846,7 +765,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Souhrn importu { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -1292,7 +1211,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Kódy chyb { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -1422,7 +1341,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | Nedostupné | Nedefinovaná chybová zpráva. | -### Ověření { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -1432,7 +1351,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -1457,8 +1376,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -1511,7 +1430,7 @@ Some examples of configurable validations: Tyto konfigurace dále změní způsob provádění ověřování během importu. -### Pravidla programu { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -1567,7 +1486,7 @@ information about side effects can be found in the following section. > > Programová pravidla lze během importu přeskočit pomocí parametru `skipProgramRules`. -### Vedlejší účinky { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -1589,7 +1508,7 @@ V současné době jsou podporovány následující vedlejší účinky: > > Určité konfigurace mohou řídit provádění vedlejších účinků. Během importu lze nastavit příznak `skipSideEffects`, aby se vedlejší efekty zcela vynechaly. Tento parametr může být užitečný, pokud například importujete něco, na co nechcete spouštět upozornění. -### Přiřadit uživatele k událostem { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -1623,7 +1542,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -1675,9 +1594,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -1757,8 +1676,8 @@ Koncový bod vrátí seznam trasovaných entit, které odpovídají parametrům |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -1862,7 +1781,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -2124,8 +2043,8 @@ Vrátí seznam událostí na základě filtrů. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| |`program`|`String`|`uid`| Identifikátor programu| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -2329,8 +2248,8 @@ Vrátí seznam událostí na základě poskytnutých filtrů. |`followUp`|`boolean`| `true`|`false` | Zda je událost zvažována pro pokračování v programu. Výchozí hodnota je `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifikátor organizační jednotky| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Způsob výběru organizačních jednotek může být. Výchozí hodnota je `SELECTED`, což se týká pouze vybraných organizačních jednotek.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Stav události| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filtrujte události, které nastaly po tomto datu.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filtrujte události, které nastaly do tohoto data.| @@ -2625,13 +2544,13 @@ Následující pravidla platí pro parametry dotazu. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Sdílení metadat { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -2677,7 +2596,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -2746,13 +2665,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -2764,7 +2683,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Přepsání vlastnictví trasovače: Rozbijte sklo { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -2777,7 +2696,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Převod vlastnictví trasovače { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -2787,7 +2706,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Úroveň přístupu { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -2817,7 +2736,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -2833,3 +2752,119 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } + +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. + +### Program stage working lists { #program-stage-working-lists } + +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. + + /api/programStageWorkingLists + +#### Payload { #payload } + +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: + +Tabulka: Datový obsah + +| Hodnoty datového obsahu | Popis | Příklad | +|---|---|---| +| název | Name of the working list. Required. || +| popis | A description of the working list. || +| program | Objekt obsahující id programu. Požadované. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. + +Table: Program Stage Query Criteria + +| Criteria values | Popis | Příklad | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| řazení | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | + +See an example payload below: + +```json +{ + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" + }, + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" + }, + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ + { + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } +} +``` + diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index 01b2576d0..0a018a6d6 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/users.md" revision_date: '2024-03-08' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Uživatelé { #users } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index 34298efa6..7ec239c40 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Vizualizace { #visualizations } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md index 52b53a6c1..2519230fd 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- DHIS základní verze 2.39 - Správa +- DHIS základní verze 2.39 --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md index d4d7841b4..e04896b65 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/installation.md" revision_date: '2024-02-16' tags: -- DHIS základní verze 2.39 - Správa +- DHIS základní verze 2.39 --- # Instalace { #installation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md index 6ba4e4c6d..ce86aec00 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- DHIS základní verze 2.39 - Správa +- DHIS základní verze 2.39 --- # Aktualizace { #upgrading-dhis2 } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md index a86c66ca2..84757b412 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- DHIS základní verze 2.39 - Správa +- DHIS základní verze 2.39 --- # Používání komunikačních bran pro hlášení SMS { #sms_report_sending } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md index bd2a0c051..ef10424df 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- DHIS základní verze 2.40 - Správa +- DHIS základní verze 2.40 --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md index f98e45363..554f1ccba 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- DHIS základní verze 2.40 - Správa +- DHIS základní verze 2.40 --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md index 418ea2c78..a732fdfbe 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- DHIS základní verze 2.40 - Správa +- DHIS základní verze 2.40 --- # Instalace { #installation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md index c7cc5129c..90ae79bdc 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- DHIS základní verze 2.40 - Správa +- DHIS základní verze 2.40 --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md index b8fe37752..a6cecec22 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- DHIS základní verze 2.40 - Správa +- DHIS základní verze 2.40 --- # Aktualizace { #upgrading-dhis2 } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md index 35387a9bf..32298ca09 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- DHIS základní verze 2.40 - Správa +- DHIS základní verze 2.40 --- # Používání komunikačních bran pro hlášení SMS { #sms_report_sending } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index 7325e2160..652e97e1d 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/audit.md" revision_date: '2024-05-21' tags: -- Hlavní verze jádra DHIS - Správa +- Hlavní verze jádra DHIS --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index 782119f99..c267c5bd8 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- Hlavní verze jádra DHIS - Správa +- Hlavní verze jádra DHIS --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index 9ad7cd6af..b15ab0c82 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- Hlavní verze jádra DHIS - Správa +- Hlavní verze jádra DHIS --- # Instalace { #installation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index 0ac3bbabb..ea00e1e21 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/monitoring.md" revision_date: '2023-09-25' tags: -- Hlavní verze jádra DHIS - Správa +- Hlavní verze jádra DHIS --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index baffc0516..e989ab67d 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Hlavní verze jádra DHIS - Správa +- Hlavní verze jádra DHIS --- # Aktualizace { #upgrading-dhis2 } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index 6eeba277b..f1fb76312 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Hlavní verze jádra DHIS - Správa +- Hlavní verze jádra DHIS --- # Používání komunikačních bran pro hlášení SMS { #sms_report_sending } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index d3a17e0d2..c06e227cf 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-browsing.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.0 +- Použití --- ## Procházení Trasovače Akcí { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index ec348de42..7c76835da 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-introduction.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.0 +- Použití --- # Propojený ovládací panel Trasovač Akcí a Demo server { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index b88fae515..56417bc20 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-maintenance.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.0 +- Použití --- # Údržba aplikace Trasovač Akcí { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index b25bb75dd..10b410739 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-planning.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.0 +- Použití --- # Plánování akcí v Trasovači Akcí { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index 1af944d9e..982fab17d 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-tracking.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.0 +- Použití --- # Trasování akcí v Trasovači Akcí { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index 605b181a7..1ff9c533b 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-installation.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Instalace aplikace BNA { #installing-the-bna-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index 12ed893e0..ae19a7ad8 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-maintenance.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Údržba aplikace BNA { #bna-app-maintenance } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index 6fd72fe6d..bf72f851d 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-analysis-and-interpretation.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Analýza a interpretace BNA { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index b6f2b1745..97d5104c4 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-architecture.md" revision_date: '2022-03-10' tags: -- Použití - App version 1.2.2 +- Použití --- # Architektura aplikace BNA { #bna-app-architecture } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index 1058c5675..cabd0cd85 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bottleneck-analysis-dashboard-and-demo-server.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Ovládací panel analýzy úzkých míst BNA a Demo server { #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index dd23cef70..a818c7e6d 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/navigating-the-bna-app.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Konfigurace intervencí aplikace BNA { #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index cb74cf7ef..8c91568b2 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/visualization-operations.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Vizualizační operace { #visualization-operations } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index 282b9097f..74550cefb 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/adopting-the-use-of-the-bna-app.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Přijetí používání aplikace BNA { #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index 3d247353a..614f43d5f 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/capacity-building.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Budování kapacit { #capacity-building } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index a689d5dfd..fed1cdd83 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/end-user-training.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Školení koncových uživatelů { #end-user-training } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index c3ebe62cb..64c2e0c77 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/guide-to-bna-app-implementation.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Průvodce implementací aplikace BNA { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index 06f547d4b..99dd056d6 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/integration-concepts-for-the-bna-app.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Koncepty integrace pro aplikaci BNA. { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index 89e39af40..2a60e5a85 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/opportunities-and-challenges.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Příležitosti a výzvy { #opportunities-and-challenges } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index 074db1aa0..d73244e0b 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/planning-and-organising.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Plánování a organizace { #planning-and-organising } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md index cf89cdfc3..7023e8fac 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/setting-up-a-new-bna-app.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Nastavení nové aplikace BNA { #setting-up-a-new-bna-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md index 5f0b3a607..13bc0bd1e 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-support-and-scale-up.md" revision_date: '2022-03-22' tags: -- Použití - App version 1.2.2 +- Použití --- # Podpora a rozšiřování aplikací BNA { #bna-app-support-and-scale-up } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md index 39a917d81..ff9ca569c 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/scale-up-and-sustainability.md" revision_date: '2021-09-09' tags: -- Použití - App version 1.2.2 +- Použití --- # Škálování a udržitelnost { #scale-up-and-sustainability } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md index 3cd433398..aba4ee369 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/grant-access-to-user.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- ## 2.4 Grant Access to users { #24-grant-access-to-users } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md index 104d25c52..5d6a6b919 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/interventions-and-indicators-configuration.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- ## 2.2 Interventions and Indicators Configuration { #22-interventions-and-indicators-configuration } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md index 2381f5025..f085d47ab 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/maps-configuration.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- ### 2.2.3 Map configuration { #223-map-configuration } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md index 8de6b1117..12ff31f1b 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-app-installation.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- # Chapter 2. Bottleneck Analysis App Administrators’ guide { #chapter-2-bottleneck-analysis-app-administrators-guide } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md index f70bb3086..a21267df0 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/common/about-this-guide-bna1.4.0.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- # O této příručce { #about_this_guide_ } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md index 3e91df2ea..a0fbfb7ad 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/introduction-to-bna.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- # Chapter 1. Bottleneck Analysis App { #chapter-1-bottleneck-analysis-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md index 25fac8452..4e69b4ae0 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-analysis-and-interpretation.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- ## 3.2 BNA Analysis and Interpretation { #32-bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md index 6652ed136..7ec54d8e1 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-layout.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- # Chapter 3. Bottleneck Analysis App User guide { #chapter-3-bottleneck-analysis-app-user-guide } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md index 21c5cb370..686e59e75 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/data-analystics.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- ## 2.6 Standard data analytics { #26-standard-data-analytics } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md index 484bcfb91..037bc269f 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/map-view.md" revision_date: '2022-12-20' tags: -- Použití - App version 1.4.0 +- Použití --- Zobrazení mapy diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md index cb1dc177e..85a264995 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/metadata-package-development/blob/master/metadata/AEFI/immunisation_analysis_app_user_manual.md" revision_date: '2021-03-18' tags: -- Použití - App version 1.0.3 +- Použití --- # Uživatelská příručka k aplikaci pro analýzu imunizace DHIS2 { #user-manual-for-the-dhis2-immunisation-analysis-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md index 836fc1224..18896bcea 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/about-this-guide.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # About this guide { #about-this-guide } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md index e5c22c3b3..3666f2aba 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-and-translating-scorecard.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Accessing and translating the Scorecard { #accessing-and-translating-the-scorecard } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md index d92c58ab1..51cb190e7 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-scorecard-app.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Login DHIS2 system { #login-dhis2-system } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md index 77485a627..29aa352cd 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/creating-scorecard.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- ## Creating the Scorecard { #creating-the-scorecard } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md index 2869c25a6..9da64f611 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/introduction-to-scorecard.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Introduction to the Scorecard App { #introduction-to-the-scorecard-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md index fe88fb351..b5f559243 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/saving-configurations.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- ## Saving configuration and load the scorecard { #saving-configuration-and-load-the-scorecard } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md index d16145581..e95d4f49c 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/scorecard-app-architecture.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Scorecard App architecture { #scorecard-app-architecture } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md index 30d8fe956..843c68b21 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/support-and-maintanace-options.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Scorecard App Built-in Support and Maintenance Options { #scorecard-app-built-in-support-and-maintenance-options } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md index 3d063e474..a7f26994c 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/viewing-scorecard.md" revision_date: '2021-10-04' tags: -- Použití - App version 2.5.0 +- Použití --- # Viewing the Scorecard App Analysis outputs { #viewing-the-scorecard-app-analysis-outputs } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md index 5e1f8d881..7ce9e8536 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-maintenance.md" revision_date: '2024-02-27' tags: -- Použití - App version 2.0 +- Použití --- If a Standalone action tracker application is taking too long to load, and you’re not on a slow network, make sure you have cleared your browser cache. diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md index d22d196f0..078f5a7bc 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-architecture-and-installation.md" revision_date: '2024-02-22' tags: -- Použití - App version 2.0 +- Použití --- The Standalone Action Tracker Application is built on an architecture that eases user interactions by having a design concept that promotes the user to follow their intuition complemented with high performance that considers the lowest internet connection scenarios with descriptive notification messages if the user misses a step along the way. diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md index 11dd74159..1731bdbcf 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-browsing.md" revision_date: '2024-02-23' tags: -- Použití - App version 2.0 +- Použití --- The Standalone Action Tracker App can be found in the Apps menu. if the application has not yet been installed in your DHIS2 instance or the installation has issues, refer to the installation instructions (Section 3.5) of this documentation for further guidance, or contact the DHIS2 administrator for your instance. diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md index 7d80c9e4f..938b9caa1 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-introduction.md" revision_date: '2024-02-22' tags: -- Použití - App version 2.0 +- Použití --- # Introduction to the Standalone Action Tracker App { #introduction-to-the-standalone-action-tracker-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md index ea03ce2ac..6d3c21a75 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md +++ b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-configuration.md" revision_date: '2024-02-27' tags: -- Použití - App version 2.0 +- Použití --- The Standalone Action Tracker App includes a module for administrators to configure key metadata for the normal user. The administration configurable options include:- diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 154d90e52..ea119db75 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Použití - DHIS core version 2.38 +- Použití --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 1e6284b55..b67979c74 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # DHIS2 Často kladené otázky { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md index 5bffab587..c7e27d112 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 57a39d4ad..9294c6ef5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 3b7368a0b..c3981e4dc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Poznámky k vydání a upgradu { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md index 1089654d0..31792ce18 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md index 30911115f..7df7ad151 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md index f78e40711..36bce72bb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Hlášení o události { #event_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md index 105de9c8a..d3fc5c5dd 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Vizualizér událostí { #event_visualizer_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md index e2b3e041e..44cd3c7d1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md index ec7d52d92..a9bb8dea7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-maps-app.md" revision_date: '2022-03-23' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md index fa7dcc8df..c39e379f8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Funkce hlášení v aplikaci pro přehledy { #using_the_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md index 2dcfdecfd..e2b99d59a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md index 4fdac4057..ee8f9b2a7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md index 838e653c3..ada780f02 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Zadávání dat { #data_entry_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md index 4b0813231..84f95e063 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 829ba9312..d9a36cc42 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Použití - DHIS core version 2.38 +- Použití --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md index b7e0c6c4b..6490d99c5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-the-gis-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nakonfigurujte aplikaci Mapy { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md index bdf038ae7..4a3b3ef77 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata.md" revision_date: '2022-10-02' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md index c4006dd7c..357227467 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Konfigurace programů v aplikaci Údržba { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md index 3a8318e3e..1c22749b6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md index 9011a5d96..7686b95cb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/system-settings.md" revision_date: '2022-04-27' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md index b56310061..0ab9fe85c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index a614019f2..c93c45995 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-03-10' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Spravujte uživatele, uživatelské role a skupiny uživatelů { #manage_user_role_group } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md index 51e5ff351..19c75aab7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/importexport-app.md" revision_date: '2022-02-23' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md index 47a1ef0c9..72ecfe81f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md index ec9af8cea..4d9d1b57d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md index 2fd038a87..9be310723 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md index 388b35354..ff63fd278 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Správce datového úložiště { #datastore_manager_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md index 036a604d9..9d7cfdbe3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Použití - DHIS core version 2.38 +- Použití --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md index 60a00c323..57f989558 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md index 6e7d5a822..2ecd315f8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index a46a77be9..0512550cc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 3363e92ef..3234b785d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 6b4d54ccf..cab40e951 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index a7e9f0b9a..e87220bb9 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index b2ee5160b..220a7e8ba 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Použití - DHIS core version 2.38 +- Použití --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 0cca32a67..7a63a7684 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 61ba9a03c..57bee9f08 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Vztahový model { #relationship_model } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 43973577f..81f58feee 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index e4f6541f6..e4ac69e05 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index d84044fe8..1033b6881 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Nastavte předvolby uživatelského účtu { #user_account_preferences } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 9459244ed..9b2e64894 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 4d14caabc..761f490d0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # DHIS2 Často kladené otázky { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md index 3f7e0a3e3..f02cba5a6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md index ae68e65b2..184234e5d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md index efecd4ae5..874b8f494 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index d29d309ae..e4c80853e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index 80a9e679a..e4df62b8a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Hlášení o události { #event_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index bbb6bb7d8..86817b23b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Vizualizér událostí { #event_visualizer_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index 85f0eac67..138891f69 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index fca4f5107..43a2bcfd5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-maps-app.md" revision_date: '2022-09-13' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index a0770e718..03c0c5d40 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Funkce hlášení v aplikaci pro přehledy { #using_the_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md index de953cb13..e1f9a4687 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md index 42749fe9a..b8f273134 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md index ec2ed23e3..eeaafcd81 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md index a4961cb33..8f4efd094 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Zadávání dat { #data_entry_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md index b1f867cb5..3658b1c03 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index e396c0bda..4ab37e7ba 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md index 72348ee52..d683bf1fd 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index 999f5ce64..6abb2aca3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index 9d7253057..74f3f0e70 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Konfigurace programů v aplikaci Údržba { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md index b66b263f3..99662a899 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md index 5d802bb18..7cab6e326 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/system-settings.md" revision_date: '2022-09-13' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index efaead558..0393d6709 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index be469c5f3..1964102d8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Spravujte uživatele, uživatelské role a skupiny uživatelů { #manage_user_role_group } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md index 1e6c4ef98..f7eda30be 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-exchange.md" revision_date: '2023-02-16' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Výměna dat { #data_exchange } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index f88a62d89..c33442d91 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md index 693f51fd0..015b40b65 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md index ae9e47552..8faadb0a0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md index 140de9238..dc788ce9e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 2fe1257b4..ebb9aafe8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Správce datového úložiště { #datastore_manager_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index e55a5069d..acaf400d4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index 60ef71256..7540172dc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md index 0c16d34f5..702daf2c7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index c3a262aab..e7f38e7f0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 38b54caf0..e56b41ba1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 569ad76c6..72a0adb27 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index b8fceb080..b9ba4601b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 376279a12..8e89fb704 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 3b2f71281..bdf6831cc 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 5bf6c8993..e9ddedb57 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 77d479911..abd8c12bd 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 8a46f2a01..98997496f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index f63b977db..8fe1620c5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # DHIS2 Často kladené otázky { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md index 868760dba..8f7b97d62 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 5c112a3c8..e013f8a7c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index e9fcb5af1..6d035520d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Poznámky k vydání a upgradu { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md index ac5e05d77..743eb486e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md index b99e81cc6..54c04dc6f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md index b259e8023..55bd2e70d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Hlášení o události { #event_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md index e0e6bce4a..aee3d97d6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Vizualizér událostí { #event_visualizer_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md index 08ad78fcd..185693954 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md index ead7b536c..1f5989c6e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md index 6095602c0..140c48fe1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Funkce hlášení v aplikaci pro přehledy { #using_the_reports_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md index 5214d499d..61e17c54d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md index fe4da5ddb..ab6e54b78 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md index 4f1c7800d..b5a32ccc0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md index df0a5e1fe..71427e758 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Zadávání dat { #data_entry_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md index 3b550d085..66e8171a6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 5ae1de328..c6e5e9039 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md index 02e41d42b..167e89175 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md index 9ca945ce5..75993639e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata.md" revision_date: '2023-07-20' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md index b1dd1e7e6..956b12c9b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Konfigurace programů v aplikaci Údržba { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md index 04254ef9b..4504167ac 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md index e1b0d919d..06705b1e2 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/system-settings.md" revision_date: '2024-01-25' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md index da23afae3..995da5e76 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index babeab16a..4dd8bb44c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Spravujte uživatele, uživatelské role a skupiny uživatelů { #manage_user_role_group } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md index e7cd0ac9c..f2bc4c78f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Výměna dat { #data_exchange } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md index da53f95f9..624d942ba 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md index b9d73ab68..679ec2846 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md index c42415e1c..9f3409801 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md index d3f13dd4f..cf8f22d00 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-administration.md" revision_date: '2023-06-21' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md index 4602e8590..ed8c8c783 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Správce datového úložiště { #datastore_manager_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md index 13b9a9a17..de7ac6029 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md index bc61b8593..ed7f23268 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md index b2ddb2225..6bf94887e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 29b93e652..57e9bdde7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 981f48b17..f5522b749 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 092f41485..59eba32dd 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 697a8b761..deb89f892 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 1f79379a8..14325d8a3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/es_419/.cache_timestamp b/projects/docs-full-site/es_419/.cache_timestamp index 4b81a3548..c27f4ab7d 100644 --- a/projects/docs-full-site/es_419/.cache_timestamp +++ b/projects/docs-full-site/es_419/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:21:28Z \ No newline at end of file +2024-06-04T21:21:41Z \ No newline at end of file diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index 6b6993086..ef533c22c 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/analytics.md" -revision_date: '2024-05-02' +revision_date: '2024-05-31' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Analytics { #analytics } @@ -816,7 +816,7 @@ Table: Query parameters for event query analytics only | Query parameter | Requerido | Descripción | Options | |---|---|---|---| -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference event date, org unit name and code and any item identifiers. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return events which have coordinates. | falso | verdadero | @@ -1723,7 +1723,7 @@ Table: Query parameters for enrollment query endpoint | filter | No | Dimension identifier including data elements, attributes, periods, organisation units and organisation unit group sets. Parameter can be repeated any number of times. Item filters can be applied to a dimension on the format ::. Filter values are case-insensitive. || | programStatus | No | Specify enrollment status of enrollments to include. | ACTIVE | COMPLETED | CANCELLED | | relativePeriodDate | string | No | Date identifier e.g: "2016-01-01". Overrides the start date of the relative period | -| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ouMode | No | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | No | Dimensions to be sorted ascending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | No | Dimensions to be sorted descending, can reference enrollment date, incident date, org unit name and code. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly | No | Whether to only return enrollments which have coordinates. | falso | verdadero | diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index 0556d26d6..872b017f5 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Apps { #apps } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index 2d259014e..a024be7bd 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" revision_date: '2023-06-23' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index 1c3454a4d..cb1401dbf 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data approval { #data-approval } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index 418983e57..2c480e5c1 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index fc8e9ccbb..56a681110 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index a5c8b1d69..250ea5920 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data { #data } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index eb5f58cfc..facec65e8 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data store { #data-store } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index be3fd40f0..16447acce 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data validation { #data-validation } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md index dc6f6fd74..1c11721f8 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Email { #email } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index b96a07254..b152b51cb 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 004a2e862..8829f31ce 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # I18n { #i18n } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index d0d2b81a9..89e82a32c 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Overview { #webapi } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index ee7634fb3..1ddb3c50f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Maintenance { #maintenance } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md index 601f7fba3..ecb25ce45 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Messaging { #messaging } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index 2dd9ca447..bf0afe532 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index a280c3ebe..e2814b350 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Metadata { #metadata } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md index 19e27f307..8ee1fce9f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Perfil de la unidad organizativa { #org_unit_profile } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index b932d3892..e4c1c3fd4 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index 634a4dc83..5c2453845 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/route.md" revision_date: '2024-05-15' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Route { #route } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index 28d95434f..3620a9a0a 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Scheduling { #webapi_scheduling } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index 55ca6217e..72c58b5b7 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index 2c646e945..8171225ae 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Sharing { #sharing } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index 527445670..ce988a04b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # SMS { #sms } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index 10e60e9a2..b2fe303b9 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Sincronización { #webapi_synchronization } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md index f1bf49c49..76333668e 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Tracker { #webapi_tracker } @@ -18,20 +18,21 @@ tags: > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Tracker Objects { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -134,7 +135,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | No | Sí | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | No | No | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | No | No | Enum | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | Sí | No | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | No | Sí | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | No | No | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -194,9 +194,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Attributes { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | Descripción | Requerido | Immutable | Tipo | Example | |---|---|---|---|---|---| @@ -211,18 +213,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | Descripción | Requerido | Immutable | Tipo | Example | |---|---|---|---|---|---| @@ -237,31 +241,31 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Notes { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -272,10 +276,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -317,92 +321,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | Descripción | Example | -|---|---|---| -| name | Name of the working list. Required. || -| Descripción | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | Descripción | Example | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -411,9 +330,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -446,7 +365,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -846,7 +765,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -1292,7 +1211,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -1422,7 +1341,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | N/A | Undefined error message. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -1432,7 +1351,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -1457,8 +1376,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -1511,7 +1430,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -1567,7 +1486,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -1589,7 +1508,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -1623,7 +1542,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -1675,9 +1594,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -1757,8 +1676,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -1863,7 +1782,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -2125,8 +2044,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -2330,8 +2249,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -2626,13 +2545,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -2678,7 +2597,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -2747,13 +2666,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -2765,7 +2684,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Tracker Ownership Override: Break the Glass { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -2778,7 +2697,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Tracker Ownership Transfer { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -2788,7 +2707,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -2818,7 +2737,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -2834,3 +2753,119 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } + +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. + +### Program stage working lists { #program-stage-working-lists } + +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. + + /api/programStageWorkingLists + +#### Payload { #payload } + +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: + +Table: Payload + +| Payload values | Descripción | Example | +|---|---|---| +| name | Name of the working list. Required. || +| Descripción | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. + +Table: Program Stage Query Criteria + +| Criteria values | Descripción | Example | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| followUp | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | + +See an example payload below: + +```json +{ + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" + }, + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" + }, + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ + { + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } +} +``` + diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index af584cce8..892dc2444 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/users.md" revision_date: '2024-03-08' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Users { #users } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index 87e159084..d685b2e94 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Visualizations { #visualizations } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md index a74617786..f802c8a9b 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.39 - Gestionar +- DHIS core version 2.39 --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md index e3424b616..bcc6c1d57 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/installation.md" revision_date: '2024-02-16' tags: -- DHIS core version 2.39 - Gestionar +- DHIS core version 2.39 --- # Instalación { #installation } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md index 0e82eb189..d0a24dbd8 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.39 - Gestionar +- DHIS core version 2.39 --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md index e3a4178f5..5f18d07c1 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- DHIS core version 2.39 - Gestionar +- DHIS core version 2.39 --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md index 09fd00713..b6c978390 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.39 - Gestionar +- DHIS core version 2.39 --- # Using Gateways for SMS reporting { #sms_report_sending } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md index a2b3120b5..f10bf8073 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.40 - Gestionar +- DHIS core version 2.40 --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md index 918a5e128..f3a02e02b 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- DHIS core version 2.40 - Gestionar +- DHIS core version 2.40 --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md index a044e6968..d8a602814 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- DHIS core version 2.40 - Gestionar +- DHIS core version 2.40 --- # Instalación { #installation } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md index 285a52232..3c08c5d7e 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Gestionar +- DHIS core version 2.40 --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md index 9b69a8937..4b46a40e7 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- DHIS core version 2.40 - Gestionar +- DHIS core version 2.40 --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md index 3689506dc..bf5bb113e 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.40 - Gestionar +- DHIS core version 2.40 --- # Using Gateways for SMS reporting { #sms_report_sending } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index b67387985..fd1b0cc2a 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/audit.md" revision_date: '2024-05-21' tags: -- DHIS core version master - Gestionar +- DHIS core version master --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index d21b0bddd..7856db8f7 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- DHIS core version master - Gestionar +- DHIS core version master --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index 642e0409b..2e2f0e808 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- DHIS core version master - Gestionar +- DHIS core version master --- # Instalación { #installation } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index 68a962358..ef19e985b 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/monitoring.md" revision_date: '2023-09-25' tags: -- DHIS core version master - Gestionar +- DHIS core version master --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index bc28984a9..0636518b0 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- DHIS core version master - Gestionar +- DHIS core version master --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index 0bea08d7e..d0f802b8b 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- DHIS core version master - Gestionar +- DHIS core version master --- # Using Gateways for SMS reporting { #sms_report_sending } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index aaf649701..288c855a1 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-browsing.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.0 +- Uso --- ## Browsing the Action Tracker { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index 6a3dbccea..5767e2832 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-introduction.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.0 +- Uso --- # Linked Action Tracker Dashboard and Demo server { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index c11158276..d7a6943c6 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-maintenance.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.0 +- Uso --- # Action Tracker App Maintenance { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index c1fee687b..f46963db9 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-planning.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.0 +- Uso --- # Action Planning in Action Tracker { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index ac22d0475..65e8037d8 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-tracking.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.0 +- Uso --- # Action Tracking in Action Tracker { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index c72f194f9..852880fce 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-installation.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Installing the BNA App { #installing-the-bna-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index 5b13ef6cf..5457f42d9 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-maintenance.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # BNA App Maintenance { #bna-app-maintenance } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index fd7dedb82..2a13dfb80 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-analysis-and-interpretation.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # BNA Analysis and Interpretation { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index 411526af1..5b20e5946 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-architecture.md" revision_date: '2022-03-10' tags: -- Uso - App version 1.2.2 +- Uso --- # BNA App architecture { #bna-app-architecture } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index 055b78570..91c8ce9d8 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bottleneck-analysis-dashboard-and-demo-server.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Bottleneck Analysis Dashboard and Demo server { #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index fe71c7e00..88987fbff 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/navigating-the-bna-app.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # BNA App interventions configurations { #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index b1bb1034b..66a5c5737 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/visualization-operations.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Visualization operations { #visualization-operations } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index db10fe15b..098a7b477 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/adopting-the-use-of-the-bna-app.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Adopting the use of the BNA App { #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index 22c721837..2c738a2f4 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/capacity-building.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Capacity building { #capacity-building } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index 2e66e349f..b8a0ee6e5 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/end-user-training.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # End User training { #end-user-training } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index b428ae6c6..5c6585670 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/guide-to-bna-app-implementation.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Guide to BNA App Implementation { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index 60d417db1..691cc5541 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/integration-concepts-for-the-bna-app.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Integration Concepts for the BNA App. { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index ea862ee6d..ce4325cdc 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/opportunities-and-challenges.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Opportunities and Challenges { #opportunities-and-challenges } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index 091259885..37336fed9 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/planning-and-organising.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Planning and organising { #planning-and-organising } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md index 39a45f0eb..e011cd0e7 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/setting-up-a-new-bna-app.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Setting-up a new BNA App { #setting-up-a-new-bna-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md index eb9d45c29..0f35818b3 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-support-and-scale-up.md" revision_date: '2022-03-22' tags: -- Uso - App version 1.2.2 +- Uso --- # BNA App Support and Scale-up { #bna-app-support-and-scale-up } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md index b15469d7f..64d7269ae 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/scale-up-and-sustainability.md" revision_date: '2021-09-09' tags: -- Uso - App version 1.2.2 +- Uso --- # Scale-up and sustainability { #scale-up-and-sustainability } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md index 00cf512ee..78a7c8fdd 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/grant-access-to-user.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- ## 2.4 Grant Access to users { #24-grant-access-to-users } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md index 5d31b3112..3409b8009 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/interventions-and-indicators-configuration.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- ## 2.2 Interventions and Indicators Configuration { #22-interventions-and-indicators-configuration } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md index 4e7cc579c..82a8c8004 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/maps-configuration.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- ### 2.2.3 Map configuration { #223-map-configuration } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md index 9f00face9..6e980cffe 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-app-installation.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- # Chapter 2. Bottleneck Analysis App Administrators’ guide { #chapter-2-bottleneck-analysis-app-administrators-guide } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md index afe7c8a61..24b35d9e5 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/common/about-this-guide-bna1.4.0.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- # About this guide { #about_this_guide_ } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md index bf1053d28..2c68204de 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/introduction-to-bna.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- # Chapter 1. Bottleneck Analysis App { #chapter-1-bottleneck-analysis-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md index d9e725aa4..c2f8f88f4 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-analysis-and-interpretation.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- ## 3.2 BNA Analysis and Interpretation { #32-bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md index 889bfdeaf..d76d0d20f 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-layout.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- # Chapter 3. Bottleneck Analysis App User guide { #chapter-3-bottleneck-analysis-app-user-guide } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md index f2200bf5a..23694eb4f 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/data-analystics.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- ## 2.6 Standard data analytics { #26-standard-data-analytics } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md index 91c9d53ec..2214ac7e9 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/map-view.md" revision_date: '2022-12-20' tags: -- Uso - App version 1.4.0 +- Uso --- Map View diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md index ddff25c2e..d39096e1b 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/metadata-package-development/blob/master/metadata/AEFI/immunisation_analysis_app_user_manual.md" revision_date: '2021-03-18' tags: -- Uso - App version 1.0.3 +- Uso --- # User Manual for the DHIS2 Immunisation Analysis App { #user-manual-for-the-dhis2-immunisation-analysis-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md index d60aad59d..6fac71aa2 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/about-this-guide.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- # About this guide { #about-this-guide } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md index b28f8fb93..ceede9b6f 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-and-translating-scorecard.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- # Accessing and translating the Scorecard { #accessing-and-translating-the-scorecard } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md index 15e9a3090..f28cf77d0 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-scorecard-app.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- # Login DHIS2 system { #login-dhis2-system } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md index 50c730891..70ce843c7 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/creating-scorecard.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- ## Creating the Scorecard { #creating-the-scorecard } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md index b44ea7a05..a7e26cceb 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/introduction-to-scorecard.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- # Introduction to the Scorecard App { #introduction-to-the-scorecard-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md index c9825f555..3ccdd0f87 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/saving-configurations.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- ## Saving configuration and load the scorecard { #saving-configuration-and-load-the-scorecard } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md index b587915aa..787d7c9bb 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/scorecard-app-architecture.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- # Scorecard App architecture { #scorecard-app-architecture } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md index 465f13718..8fb667687 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/support-and-maintanace-options.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- # Scorecard App Built-in Support and Maintenance Options { #scorecard-app-built-in-support-and-maintenance-options } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md index 85e98f539..52f82ff5e 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/viewing-scorecard.md" revision_date: '2021-10-04' tags: -- Uso - App version 2.5.0 +- Uso --- # Viewing the Scorecard App Analysis outputs { #viewing-the-scorecard-app-analysis-outputs } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md index 0a2ca0503..7b96979f0 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-maintenance.md" revision_date: '2024-02-27' tags: -- Uso - App version 2.0 +- Uso --- If a Standalone action tracker application is taking too long to load, and you’re not on a slow network, make sure you have cleared your browser cache. diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md index 7822d17ca..ce27647a2 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-architecture-and-installation.md" revision_date: '2024-02-22' tags: -- Uso - App version 2.0 +- Uso --- The Standalone Action Tracker Application is built on an architecture that eases user interactions by having a design concept that promotes the user to follow their intuition complemented with high performance that considers the lowest internet connection scenarios with descriptive notification messages if the user misses a step along the way. diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md index ef1660e0a..73936e2dc 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-browsing.md" revision_date: '2024-02-23' tags: -- Uso - App version 2.0 +- Uso --- The Standalone Action Tracker App can be found in the Apps menu. if the application has not yet been installed in your DHIS2 instance or the installation has issues, refer to the installation instructions (Section 3.5) of this documentation for further guidance, or contact the DHIS2 administrator for your instance. diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md index e56be051e..75ae5beb8 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-introduction.md" revision_date: '2024-02-22' tags: -- Uso - App version 2.0 +- Uso --- # Introduction to the Standalone Action Tracker App { #introduction-to-the-standalone-action-tracker-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md index 53ebf689c..32f82757a 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md +++ b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-configuration.md" revision_date: '2024-02-27' tags: -- Uso - App version 2.0 +- Uso --- The Standalone Action Tracker App includes a module for administrators to configure key metadata for the normal user. The administration configurable options include:- diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 9afc613b5..6ced70666 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Uso - DHIS core version 2.38 +- Uso --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index eec68cd61..62cae8285 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md index 6c27daf9b..26145aa17 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Uso - DHIS core version 2.38 +- Uso --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 4a0e6103d..35b40e90e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index bc5c3f576..24042b405 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Notas de lanzamiento y actualización { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md index b4b741ba9..8d11bf0c5 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md index dcfc0961d..b190f60ee 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md index 61c1ea197..fb96571d9 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md index 898b8e362..1e3b63dd1 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md index aacf43c47..7eddec723 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md index ae5cbb61c..f8b3ca575 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-maps-app.md" revision_date: '2022-03-23' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md index c09ac2af4..8bac80a85 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md index 8dba5e29b..a69bbffd1 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Aprobación de datos { #data_approval_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md index 2f4340761..25088a645 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md index 08ea3b7ab..b6607181e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md index c8f0ffe98..4432b76e4 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 24a1a30eb..8c89a40eb 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Uso - DHIS core version 2.38 +- Uso --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md index c66151d72..4ec58617c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-the-gis-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Configure the Maps app { #gis_creating } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md index 70c3478bb..391bc0b21 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata.md" revision_date: '2022-10-02' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md index 069574be7..d3ad8d197 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md index 1131794fe..0d7c07f17 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md index 55b769905..90041f0cd 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/system-settings.md" revision_date: '2022-04-27' tags: -- Uso - DHIS core version 2.38 +- Uso --- # System settings { #settings } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md index 89ab29082..04153747a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 7568a836f..75b366922 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-03-10' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md index 4f37bf8ab..57a2c1628 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/importexport-app.md" revision_date: '2022-02-23' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md index 94648e9b4..aec8f18b1 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md index 35bada960..ead0bb0df 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md index ccd516166..8e3f499ff 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md index 9e04adaba..690df8282 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md index e6b7e9b33..07e988f93 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Uso - DHIS core version 2.38 +- Uso --- > **Caution** diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md index 8180fc576..2fba51d07 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Mobile { #mobile } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md index fc81b268c..2889f3d60 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index ef297e84d..63824b85a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Visualizar las estadísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index faec491ad..984a994cc 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 4734ae608..0e404f4ad 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Uso de la aplicación Captura de Eventos { #event_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 7d1996b39..ec1c98e4c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 9919b8e5e..8532af1eb 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Uso - DHIS core version 2.38 +- Uso --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 35c12ca7f..4dfb083b8 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 6c1a92248..423089428 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 43a6d6f87..c840a8b9b 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Messaging { #messages } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 7ba4dd6d4..bf7f84c73 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index c57f47cf9..d7aa72e92 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Establecer las preferencias de la cuenta de usuario { #user_account_preferences } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 4f6906d33..aeb8ae2e5 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Uso - DHIS core version 2.39 +- Uso --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 00cf91fd1..f5a8084b3 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md index 90c554777..b74a3ee2c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Uso - DHIS core version 2.39 +- Uso --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 01be7516d..36761585a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index e2dd38149..9af234327 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Notas de lanzamiento y actualización { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md index 2389668d3..5a4072213 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index 4257f6641..960e960fb 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index dc2476afc..1dea90d9b 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index 18930369e..f17eebed5 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index 0b3775509..2fafe3cee 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index 8d68c2d8c..1ed03668c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-maps-app.md" revision_date: '2022-09-13' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index a9205a3d1..1411bf648 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md index dbe6f0087..fec9d245f 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Aprobación de datos { #data_approval_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md index fa514d246..3c4bbc8d7 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md index b1de80733..f86da7402 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md index db0225a07..1b7564f4c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md index 6aab85d50..57a6f43d8 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 62e3cd698..fc5d98c77 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Uso - DHIS core version 2.39 +- Uso --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md index 1968f9ad7..8bb31e4a8 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index b60883238..c7ff2f11e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index c34cf10ae..78c093ac1 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md index b663c1b8e..673806fbe 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md index c8677c7da..4fcd25911 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/system-settings.md" revision_date: '2022-09-13' tags: -- Uso - DHIS core version 2.39 +- Uso --- # System settings { #settings } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index bc04f4137..caea91152 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 3273e80a5..81f0a40ec 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md index 571a38550..8ac707a69 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-exchange.md" revision_date: '2023-02-16' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index 65ca3a149..3c406e05b 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md index ec2cb1ead..2fb7ae403 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md index 5f209a2f0..100166f5c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md index 670cc95ce..1259461f6 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 97e9d4096..c4a5443b4 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index 646fee37a..75490e93d 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Uso - DHIS core version 2.39 +- Uso --- > **Caution** diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index a565480dd..a5559f929 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Mobile { #mobile } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md index 9ba920ca7..8f9f24661 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index aed636049..82fdbc36d 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Visualizar las estadísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 9aeed97ba..8abd1df64 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 7580ba2e1..bd2c1e195 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Uso de la aplicación Captura de Eventos { #event_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index f33ae351b..61300be81 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 372814e17..65994686d 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Uso - DHIS core version 2.39 +- Uso --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index d8a341a15..6018a0dda 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index cbc6778d3..cfda20522 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 6443a3e92..336cde3a4 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Messaging { #messages } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 10ad10636..f492b2b4c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 95cec546f..341b00c61 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Establecer las preferencias de la cuenta de usuario { #user_account_preferences } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 397ec5405..f759376fa 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Uso - DHIS core version 2.40 +- Uso --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 4097077fc..e84ecabde 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md index 0a29cc425..055db0d9e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Uso - DHIS core version 2.40 +- Uso --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 8d0d64bfc..a01aff231 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index ff9e38973..439088501 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Notas de lanzamiento y actualización { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md index 3837ea654..6f82f6e01 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md index e181aba8b..92b87a894 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Uso de la aplicación Visualizador de Datos { #data_visualizer } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md index a2cd37b1d..91c87607d 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md index ca18bac57..db1f9a87a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md index 324123898..37c1cb3c6 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md index 6115be30e..c1ec59ee6 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md index b4d06ad33..fe56ef12d 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md index b8201e7d8..733f49597 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Aprobación de datos { #data_approval_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md index eb867704a..1396203cd 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md index db1d32c75..2d8dbaacd 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md index 59271d844..528b99a61 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md index acb43c7d5..a2af31fc3 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 370d14cea..7bbeb4685 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Uso - DHIS core version 2.40 +- Uso --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md index 0f752ef56..d0c37ed6c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md index ec9909e22..afa752dfa 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata.md" revision_date: '2023-07-20' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md index bbd06d9d4..90f90a837 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md index af3d8f7e4..8406d0f51 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md index ea1d300cc..5fb7b1179 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/system-settings.md" revision_date: '2024-01-25' tags: -- Uso - DHIS core version 2.40 +- Uso --- # System settings { #settings } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md index 402e66360..98e16583a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 952ddcccb..06c2651ac 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md index a93dd279e..da95b8f0e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md index d3ae3995f..1dff37739 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md index 89fdda1bf..bdad1986e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md index 1f5ed6fea..986e8b645 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md index 18193a6ab..bc093431f 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-administration.md" revision_date: '2023-06-21' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md index 62bbf65f5..2a240fef2 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md index 00c5aa820..8147ee7f0 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Uso - DHIS core version 2.40 +- Uso --- > **Caution** diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md index 497b28315..7c12744ea 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Mobile { #mobile } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md index 28e3a73ae..a91de0b98 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 2735777f1..b089de6d8 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Visualizar las estadísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index e11a6403e..31f73bb98 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 69b55654c..1a8d6d359 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Uso de la aplicación Captura de Eventos { #event_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 8c691efb9..f8791c750 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 541f3567b..d1d9f05d7 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Uso - DHIS core version 2.40 +- Uso --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 2b45c91c7..43bb39870 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 038d75ca7..9a6b0dcca 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 74073600f..cfc683378 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Messaging { #messages } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 5fd444f0a..d9544c05b 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 324737400..6a3cab9c7 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Establecer las preferencias de la cuenta de usuario { #user_account_preferences } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 8c5dd7350..56e3c53ee 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index e7efd9aa3..2f3694290 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 2970d1e1c..7369ccdab 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Uso - DHIS core version 2.41 +- Uso --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 3491b8ec9..ae8f47b17 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 7310ce31f..a85eee05e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Notas de lanzamiento y actualización { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index bd2d2790b..5d2b458a0 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 51e6953d1..cf082fa63 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Uso de la aplicación Visualizador de Datos { #data_visualizer } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index a2edda154..1df9f97ef 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index ca237e3b1..45875d7ba 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index fee706118..920e2788b 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index e91c3f338..8a9c878e0 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index 25dbbb028..e53cbb91c 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index 4c3f7dfe6..ca4901ca6 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Aprobación de datos { #data_approval_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index 81178bf20..5be65cca4 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index 122b38790..331d98326 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index 1f3fcedd9..7bc72b640 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index 4befe5aaa..3e6333873 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index eb7c49480..2e4868c78 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Uso - DHIS core version 2.41 +- Uso --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 75226cec1..c54c0b02f 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index 8bf9ce853..58c75336d 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 302f7a3b1..c041857bd 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 6d4f87bcb..3806a8723 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 340605656..3949b88ee 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # System settings { #settings } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index fd8e0d46e..12ef00097 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 8f53d624e..f345c63fa 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index 3bbad0af0..5332618d9 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 77d537c01..04c69ea17 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index ee9ac7962..2efed8de2 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index d314589a2..a5e03f2fe 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 32674b59d..8b060e012 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index 144b7d4a7..1a0507f01 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 2e0d02c52..91d4da6ce 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Uso - DHIS core version 2.41 +- Uso --- > **Caution** diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 67cfa7274..083ab66c6 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Mobile { #mobile } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index 687362636..ebe000793 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 1302cd646..d822203f9 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Visualizar las estadísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 5ea8b76eb..1913a6208 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index eb144eb19..8960bcc7e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Uso de la aplicación Captura de Eventos { #event_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 1edd7ca7f..05712238f 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index b92e33a68..b4a862c5f 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Uso - DHIS core version 2.41 +- Uso --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 9b362f4c1..d0c0b6cf3 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index a8522ac8e..f8af4aba9 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 352139322..e81e84f3b 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Messaging { #messages } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index f07779baa..53b719551 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index e69d54a39..f60f8e5e5 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Establecer las preferencias de la cuenta de usuario { #user_account_preferences } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 683ba81bc..76b0bede5 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Uso - DHIS core version master +- Uso --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index bd36bcea7..a246eab1a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md index ce105d84d..57990f87a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Uso - DHIS core version master +- Uso --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index f377f3348..f76a5164b 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 1e361a269..fe53a99bb 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Notas de lanzamiento y actualización { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md index d892c70f9..825370daf 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Uso - DHIS core version master +- Uso --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index ea3f5cf8b..ad6e8a96e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Uso - DHIS core version master +- Uso --- # Uso de la aplicación Visualizador de Datos { #data_visualizer } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index 3b43b0ece..a12028bc7 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index 63c8fed63..9cfe6fad4 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version master +- Uso --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index b3f9991af..235fb3952 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Uso - DHIS core version master +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index 372d2e2a3..66f8122af 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Uso - DHIS core version master +- Uso --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md index 1218b8c45..816085740 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Uso - DHIS core version master +- Uso --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md index e2a180a2a..615deb462 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Uso - DHIS core version master +- Uso --- # Aprobación de datos { #data_approval_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md index 25b58ce58..d00ffb847 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version master +- Uso --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md index ee1f00e78..d316d7a2f 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Uso - DHIS core version master +- Uso --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index b43983673..9ee2ba589 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index 69c7aad0a..a91ba1563 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Uso - DHIS core version master +- Uso --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 0d26a5f23..d045dbdb0 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Uso - DHIS core version master +- Uso --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index 5a5cecad9..0d03efed0 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Uso - DHIS core version master +- Uso --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index 92f910a0b..e21e40127 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version master +- Uso --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index fbc80169a..b3063e6fd 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version master +- Uso --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md index 3c6eae5f7..c393ce12a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index 52c7f69af..141a04ceb 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version master +- Uso --- # System settings { #settings } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index 91b609f3a..81c58e348 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version master +- Uso --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 9a7c838a7..c8055e761 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Uso - DHIS core version master +- Uso --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index 1a187edd2..06917ec5d 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Uso - DHIS core version master +- Uso --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index 4b1286f76..ea9bff0f2 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Uso - DHIS core version master +- Uso --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index 1e65895df..53edfa97e 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata-synchronizing.md" revision_date: '2024-05-28' tags: -- Uso - DHIS core version master +- Uso --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md index cb880f37e..bddb1b7a8 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index c8ccc81dc..392f14bfa 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Uso - DHIS core version master +- Uso --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md index f422b75ef..90b2f1403 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md index d5ad9744d..60468c930 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Uso - DHIS core version master +- Uso --- > **Caution** diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md index a064e84d5..c4e4cdc3f 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Mobile { #mobile } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 0a76de8fc..29312651d 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Uso - DHIS core version master +- Uso --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 16a7472cf..7341f3714 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Uso - DHIS core version master +- Uso --- # Visualizar las estadísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 909135f62..46e2b2ee3 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Uso - DHIS core version master +- Uso --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 016065f44..71765a234 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Uso de la aplicación Captura de Eventos { #event_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index bcb5720f0..8220941cc 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Uso - DHIS core version master +- Uso --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index fcdc3ac7a..fb3c0f8b0 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Uso - DHIS core version master +- Uso --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index bc808aa20..49a1b8051 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Uso - DHIS core version master +- Uso --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index e1bccefe7..d720b624a 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 9eae726d3..615363429 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Uso - DHIS core version master +- Uso --- # Messaging { #messages } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 0d7a0e5d4..736605ca9 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Uso - DHIS core version master +- Uso --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 2d41060b5..73776ec3b 100644 --- a/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Uso - DHIS core version master +- Uso --- # Establecer las preferencias de la cuenta de usuario { #user_account_preferences } diff --git a/projects/docs-full-site/fr/.cache_timestamp b/projects/docs-full-site/fr/.cache_timestamp index bb1199e23..a43a16d97 100644 --- a/projects/docs-full-site/fr/.cache_timestamp +++ b/projects/docs-full-site/fr/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:22:47Z \ No newline at end of file +2024-06-04T21:22:56Z \ No newline at end of file diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-232__web-api-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-232__web-api-md index 08759d882..ca47cf17c 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-232__web-api-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-232__web-api-md @@ -4747,7 +4747,7 @@ programRuleVariable model. \-coming- -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } @@ -6370,7 +6370,7 @@ Get all audits for data approval workflow RwNpkAM7Hw7: /api/27/audits/dataApproval?wf=RwNpkAM7Hw7 -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } @@ -6390,17 +6390,17 @@ a message to the *Mobile* user. We will then pretend to be the mobile user and read our new message. Following this we will manage the admin user inbox by marking and removing messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : This is the subject @@ -6412,8 +6412,8 @@ the following XML format for sending to multiple users: -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : This is the subject @@ -6425,8 +6425,8 @@ use: -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : This is the subject @@ -6499,16 +6499,16 @@ that we receive a *Location*HTTP header which value informs us of the URL of the newly created message conversation resource - this can be used by a consumer to perform further action. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : curl "https://play.dhis2.org/demo/api/26/messageConversations" -H "Accept:application/xml" -u mobile:district -X GET -v -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : @@ -6531,9 +6531,9 @@ are now able to construct a URL for sending our reply: "https://play.dhis2.org/demo/api/26/messageConversations/ZjHHSjyyeJ2" -H "Content-Type:text/plain" -u mobile:district -X POST -v -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? @@ -6541,7 +6541,7 @@ The filter searches for matches in subject, messages' text and messages' senders for message conversations. The default query operator is token due to better text search, but you can supply your own operator. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } @@ -6569,14 +6569,14 @@ with id *xE7jOejl9FI* from the conversation with id *jMe43trzrdi*: curl https://play.dhis2.org/demo/api/26/messageConversations/jMe43 -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. { "removed" : ["xE7jOejl9FI"] } -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. { "message" : "No user with uid: dMV6G0tPAEa" } @@ -6599,17 +6599,17 @@ behalf of another user by giving an optional user id curl "https://play.dhis2.org/demo/api/26/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. Marking messages read or unread follows similar semantics as batch removals, and also supports batch operations. To mark messages as read @@ -6619,13 +6619,13 @@ unread we issue an identical request to the *messageConversations/unread* resource. As is the case for removals, an optional *user* request parameter can be given. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : curl "https://play.dhis2.org/dev/api/messageConversations/read" -d '["ZrKML5WiyFm","Gc03smoTm6q"]' -X POST -H "Content-Type: application/json" -u admin:district -v -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : { "markedRead" : [ "ZrKML5WiyFm", "Gc03smoTm6q" ] } @@ -6635,8 +6635,8 @@ message conversation. The resource is located https://play.dhis2.org/demo/api/30/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ``` { @@ -6662,22 +6662,22 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. curl -F file=@attachment.png -u admin:district https://play.dhis2.org/demo/api/messageConversations/attachments -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. { "created":"2018-07-20T16:54:18.210", @@ -6701,8 +6701,8 @@ attachment with the message. "id":"fTpI4GOmujz" } -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ``` { @@ -6734,8 +6734,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. curl -d "Yes the Mortality data set has been reported" "https://play.dhis2.org/demo/api/26/messageConversations/ZjHHSjyyeJ2?attachments=fTpI4GOmujz,h2ZsOxMFMfq" @@ -6751,7 +6751,7 @@ Where \ is the *messageConversation* ID, \ is the ID of the *message* that contains the attachment, and \ is the ID of the specific *messageAttachment*. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } @@ -6764,15 +6764,15 @@ a status and a priority to a ticket. To do this, use these POST https://play.dhis2.org/demo/api/26/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. @@ -6806,9 +6806,9 @@ group.
A list of valid status and priority values
-You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: curl -d "This is an internal message" "https://play.dhis2.org/demo/api/26/messageConversations/ZjHHSjyyeJ2?internal=true" @@ -19267,7 +19267,7 @@ An example curl command looks like this: -d "https://dhis2.org/metadata-repo/221/trainingland-org-units/metadata.json" -H "Content-Type:text/plain" -u admin:district -v -## Icons { #webapi_icons } +## Icônes { #webapi_icons } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-233__web-api-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-233__web-api-md index 04eacf28a..5a856abb3 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-233__web-api-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-233__web-api-md @@ -4932,7 +4932,7 @@ programRuleVariable model. - TODO Coming - -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } @@ -6623,42 +6623,42 @@ Get all audits for data approval workflow RwNpkAM7Hw7: /api/33/audits/dataApproval?wf=RwNpkAM7Hw7 -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6667,13 +6667,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6682,13 +6682,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6707,25 +6707,25 @@ whether she has reported data for January 2014: ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -6757,23 +6757,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -6798,9 +6798,9 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? @@ -6808,7 +6808,7 @@ The filter searches for matches in subject, text, and senders for message conversations. The default query operator is *token*, however other operators can be defined in the query. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } @@ -6818,26 +6818,26 @@ have a look at managing a user's message inbox by removing and marking conversations through the Web-API. We will do so by performing some maintenance in the inbox of the "DHIS Administrator" user. -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -6845,8 +6845,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -6854,38 +6854,38 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. Marking messages read or unread follows similar semantics as batch removals, and also supports batch operations. To mark messages as read @@ -6895,7 +6895,7 @@ unread we issue an identical request to the `messageConversations/unread` resource. As is the case for removals, an optional *user* request parameter can be given. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -6903,7 +6903,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -6911,12 +6911,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -6942,25 +6942,25 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -6986,8 +6986,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -7018,8 +7018,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -7027,38 +7027,36 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. @@ -7092,9 +7090,9 @@ group.
A list of valid status and priority values
-You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" @@ -20097,7 +20095,7 @@ curl "localhost:8080/api/synchronization/metadataPull" -X POST -H "Content-Type:text/plain" -u admin:district ``` -## Icons { #webapi_icons } +## Icônes { #webapi_icons } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-234__web-api-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-234__web-api-md index 21930c060..4354f0522 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-234__web-api-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-234__web-api-md @@ -6120,8 +6120,8 @@ The resource we need to interact with when sending and reading messages is the _ ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6134,8 +6134,8 @@ For sending to all users contained in one or more user groups, we can use: ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6148,8 +6148,8 @@ For sending to all users connected to one or more organisation units, we can use ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6162,8 +6162,8 @@ Since we want to send a message to our friend the mobile user we need to look up ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? @@ -6177,7 +6177,7 @@ curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -6218,7 +6218,7 @@ curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml /status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-235__web-api-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-235__web-api-md index d10a0f9c8..695218582 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-235__web-api-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-235__web-api-md @@ -2922,7 +2922,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | --- | --- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | @@ -6177,8 +6177,8 @@ The resource we need to interact with when sending and reading messages is the _ ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6191,8 +6191,8 @@ For sending to all users contained in one or more user groups, we can use: ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6205,8 +6205,8 @@ For sending to all users connected to one or more organisation units, we can use ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -6219,8 +6219,8 @@ Since we want to send a message to our friend the mobile user we need to look up ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? @@ -6234,7 +6234,7 @@ curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -6275,7 +6275,7 @@ curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml /status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__messaging-md index a5f8be439..ea8bd4395 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__messaging-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__messaging-md @@ -22,8 +22,8 @@ The resource we need to interact with when sending and reading messages is the _ ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -36,8 +36,8 @@ For sending to all users contained in one or more user groups, we can use: ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -50,8 +50,8 @@ For sending to all users connected to one or more organisation units, we can use ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -64,8 +64,8 @@ Since we want to send a message to our friend the mobile user we need to look up ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? @@ -79,7 +79,7 @@ curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -120,7 +120,7 @@ curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml /status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__metadata-md index c33902603..c52cf0145 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__metadata-md @@ -3486,7 +3486,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | --- | --- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__new-tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__new-tracker-md index ba887edb0..ce3fd9dce 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__new-tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__new-tracker-md @@ -346,7 +346,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma de l'identifiant d'option de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NAME`, `ATTRIBUTE`, `AUTO` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être ignoré, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `IGNORER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__messaging-md index bc3dd0093..05119e2d6 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__messaging-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__messaging-md @@ -8,38 +8,38 @@ tags: # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -48,13 +48,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -63,13 +63,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -78,35 +78,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -138,23 +138,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -179,44 +179,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -224,8 +224,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -233,48 +233,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -282,7 +282,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -290,12 +290,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -321,23 +321,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -363,8 +363,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -395,8 +395,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -404,51 +404,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || - -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || + +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-md index 9d2dfeebd..0f1fb5055 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__metadata-md @@ -827,19 +827,18 @@ Tableau : Paramètres d'importation | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | | ~~mergeMode~~ (mode de fusion) | ~~REPLACE, MERGE~~ (remplacer, fusionner) | ~~Définit le mode de fusion. Lors des mises à jour nous avons deux façons de fusionner l'ancien objet avec le nouveau. Le mode `MERGE` ne remplacera l'ancienne propriété que si la nouvelle n'est pas nulle. Pour le mode `REPLACE`, toutes les propriétés sont remplacées qu'elles soient nulles ou non.~~ (*) | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | > (*) Currently the `mergeMode=MERGE` option of the import service has limitations and doesn't support all objects. It doesn't work with some object types such as Embedded objects, or objects which are saved as JSONB format in database ( sharing, attributeValues, etc...). Fixing those issues are complicated and would just cause new issues. Therefore, this `mergedMode=MERGE` is deprecated and currently is not recommended to use. The update mode should always be mergedMode=REPLACE. We have developed a new [JSON Patch API](#webapi_partial_updates) which can be used as an alternative approach. This feature is introduced in 2.37 release. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -876,10 +875,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -952,7 +948,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons @@ -1090,7 +1086,7 @@ Table: Style properties | Propriété | Description | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -1413,7 +1409,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -1472,7 +1468,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -1805,7 +1801,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -2333,7 +2329,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__new-tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__new-tracker-md index 5f1fe4766..d189932ba 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__new-tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__new-tracker-md @@ -346,7 +346,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma de l'identifiant d'option de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NAME`, `ATTRIBUTE`, `AUTO` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être ignoré, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `IGNORER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__visualizations-md index f20a25ac2..875c3d08b 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__visualizations-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__visualizations-md @@ -320,27 +320,27 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | | reportingParams | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | @@ -1622,7 +1622,7 @@ Table: Pivot table configuration | Type d'agrégation | chaîne | Non | "SUM" |"AVERAGE" | "AVERAGE_SUM_ORG_UNIT"|"LAST"|"LAST_AVERAGE_ORG_UNIT"| "COUNT" | "STDDEV" | "VARIANCE" | "MIN" | "MAX" | Override the data element's default aggregation type | | displayDensity (afficher la densité) | chaîne | Non | "NORMAL" | "COMFORTABLE" | "COMPACT" | The amount of space inside table cells | | fontSize (taille de la police) | chaîne | Non | "NORMAL" | "LARGE" | "SMALL" | Table font size | -| digitGroupSeparator | chaîne | Non | "SPACE" | "COMMA" | "NONE" | How values are formatted: 1 000 | 1,000 | 1000 | +| digitGroupSeparator (Séparateur de groupes de chiffres) | chaîne | Non | "SPACE" | "COMMA" | "NONE" | How values are formatted: 1 000 | 1,000 | 1000 | | legendSet (ensemble de légende) | object | Non || Color the values in the table according to the legend set | | userOrgUnit (unité d'organisation d'utilisateur) | string / array | Non || Organisation unit identifiers, overrides organisation units associated with curretn user, single or array | | relativePeriodDate (Date de la période relative) | chaîne | Non || Identifiant de date, par exemple : "2016-01-01". Il remplace la date de début de la période relative | @@ -1770,16 +1770,16 @@ Table: Chart configuration | showValues | booléen | Non | faux | vrai | Whether to display data values on the chart | | hideEmptyRows (cacher les lignes vides) | booléen | Non | faux | vrai | Whether to hide empty categories | | completedOnly | booléen | Non | faux | vrai | Whether to only show completed events | -| regressionType | chaîne | Non | "NONE" | "LINEAR" | Show trend lines | -| targetLineValue | nombre | Non || Display a target line with this value | +| regressionType (type de régression) | chaîne | Non | "NONE" | "LINEAR" | Show trend lines | +| targetLineValue (valeur de la ligne cible) | nombre | Non || Display a target line with this value | | targetLineTitle | chaîne | Non || Display a title on the target line (does not apply without a target line value) | -| baseLineValue | nombre | Non || Display a base line with this value | +| baseLineValue (Valeur de la ligne de base) | nombre | Non || Display a base line with this value | | baseLineTitle | chaîne | Non || Display a title on the base line (does not apply without a base line value) | | rangeAxisTitle | nombre | Non || Title to be displayed along the range axis | -| rangeAxisMaxValue | nombre | Non || Max value for the range axis to display | -| rangeAxisMinValue | nombre | Non || Min value for the range axis to display | -| rangeAxisSteps | nombre | Non || Number of steps for the range axis to display | -| rangeAxisDecimals | nombre | Non || Bumber of decimals for the range axis to display | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | nombre | Non || Max value for the range axis to display | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | nombre | Non || Min value for the range axis to display | +| rangeAxisSteps (Étapes de l'axe de la plage) | nombre | Non || Number of steps for the range axis to display | +| rangeAxisDecimals (Décimales de l'axe de la plage) | nombre | Non || Bumber of decimals for the range axis to display | | domainAxisTitle | nombre | Non || Title to be displayed along the domain axis | | Type d'agrégation | chaîne | Non | "SUM" |"AVERAGE" | "AVERAGE_SUM_ORG_UNIT"|"LAST"|"LAST_AVERAGE_ORG_UNIT"| "COUNT" | "STDDEV" | "VARIANCE" | "MIN" | "MAX" | Override the data element's default aggregation type | | hideLegend | booléen | Non | faux | vrai | Whether to hide the series legend | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md index bae078d36..d88dce408 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md @@ -8,38 +8,38 @@ tags: # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -48,13 +48,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -63,13 +63,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -78,35 +78,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -138,23 +138,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -179,44 +179,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -224,8 +224,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -233,48 +233,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -282,7 +282,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -290,12 +290,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -321,23 +321,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -363,8 +363,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -395,8 +395,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -404,51 +404,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || - -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || + +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md index 747e3c744..290f67d2e 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md @@ -822,19 +822,18 @@ Tableau : Paramètres d'importation | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | | ~~mergeMode~~ (mode de fusion) | ~~REPLACE, MERGE~~ (remplacer, fusionner) | ~~Définit le mode de fusion. Lors des mises à jour nous avons deux façons de fusionner l'ancien objet avec le nouveau. Le mode `MERGE` ne remplacera l'ancienne propriété que si la nouvelle n'est pas nulle. Pour le mode `REPLACE`, toutes les propriétés sont remplacées qu'elles soient nulles ou non.~~ (*) | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | > (*) Currently the `mergeMode=MERGE` option of the import service has limitations and doesn't support all objects. It doesn't work with some object types such as Embedded objects, or objects which are saved as JSONB format in database ( sharing, attributeValues, etc...). Fixing those issues are complicated and would just cause new issues. Therefore, this `mergedMode=MERGE` is deprecated and currently is not recommended to use. The update mode should always be mergedMode=REPLACE. We have developed a new [JSON Patch API](#webapi_partial_updates) which can be used as an alternative approach. This feature is introduced in 2.37 release. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -871,10 +870,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -947,7 +943,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons @@ -1086,7 +1082,7 @@ Table: Style properties | Propriété | Description | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -1409,7 +1405,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -1468,7 +1464,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -1807,7 +1803,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -2335,7 +2331,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md index ff4ee15f2..e73851283 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md @@ -378,7 +378,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md index a38135000..cf71efb19 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md @@ -331,27 +331,27 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | | reportingParams | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | @@ -883,25 +883,25 @@ Tableau : Attributs de la visualisation d'événements | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md index 2a4a28211..d1438af36 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md @@ -8,38 +8,38 @@ tags: # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -48,13 +48,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -63,13 +63,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -78,35 +78,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -138,23 +138,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -179,44 +179,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -224,8 +224,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -233,48 +233,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -282,7 +282,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -290,12 +290,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -321,23 +321,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -363,8 +363,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -395,8 +395,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -404,51 +404,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || - -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || + +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md index 761bba144..70719279f 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md @@ -933,19 +933,18 @@ Tableau : Paramètres d'importation | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | | ~~mergeMode~~ (mode de fusion) | ~~REPLACE, MERGE~~ (remplacer, fusionner) | ~~Définit le mode de fusion. Lors des mises à jour nous avons deux façons de fusionner l'ancien objet avec le nouveau. Le mode `MERGE` ne remplacera l'ancienne propriété que si la nouvelle n'est pas nulle. Pour le mode `REPLACE`, toutes les propriétés sont remplacées qu'elles soient nulles ou non.~~ (*) | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | > (*) Currently the `mergeMode=MERGE` option of the import service has limitations and doesn't support all objects. It doesn't work with some object types such as Embedded objects, or objects which are saved as JSONB format in database ( sharing, attributeValues, etc...). Fixing those issues are complicated and would just cause new issues. Therefore, this `mergedMode=MERGE` is deprecated and currently is not recommended to use. The update mode should always be mergedMode=REPLACE. We have developed a new [JSON Patch API](#webapi_partial_updates) which can be used as an alternative approach. This feature is introduced in 2.37 release. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -982,10 +981,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1040,40 +1036,33 @@ ignored: ## GeoJSON import { #geojson-import } -The GeoJSON import is used to attach geometry data to organisation units. +L'importation GeoJSON est utilisée pour relier les données géométriques aux unités d'organisation. -For a bulk import a GeoJSON file with a feature collection is expected. -Each feature in the collection requires a reference to the organisation unit it -should be linked to. +Pour une importation en masse, il faut un fichier GeoJSON avec une collection d'éléments. +Chaque élément de la collection a besoin d'une référence à l'unité d'organisation à laquelle il doit être relié. -By default, the geometry from the file is stored as the `geometry` property of -an organisation unit. To store additional geometries attributes of type -`GEOJSON` can be created. When attributes are use all geometries from a file -are stored for the same attribute which is provided with an additional -parameter `attributeId`. +Par défaut, la géométrie du fichier est stockée en tant que propriété `geometry` d'une unité d'organisation. Pour stocker des géométries supplémentaires, des attributs de type `GEOJSON` peuvent être créés. Lorsque des attributs sont utilisés, toutes les géométries d'un fichier sont stockées pour le même attribut qui est fourni avec un paramètre supplémentaire `attributeId`. -### GeoJSON Bulk Data Import { #webapi_geojson_bulk_import } +### Importation de données en masse avec GeoJSON { #webapi_geojson_bulk_import } -Table: Import Parameters +Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| -| `geoJsonId` | `booléen` | `vrai` | When `true` the `id` property of the GeoJSON features is expected to hold the organisation unit identifier | -| `geoJsonProperty` | `Chaîne` | _undefined_ | If `geoJsonId` is `false` this parameter names the property in the GeoJSON feature's `properties` that holds the organisation unit identifier | -| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | The property of the organisation unit that is referred to by the identifiers used in the GeoJSON file | -| `attributeId` | `Chaîne` | _undefined_ | When set the geometry is stored as value of the attribute referenced by ID | -| `dryRun` | `booléen` | `faux` | When `true` the import is processed without actually updating the organisation units | -| `async` | `booléen` | `faux` | When `true` the import is processed asnychronously | +| `geoJsonId` | `booléen` | `vrai` | Si le paramètre est défini sur `true`, la propriété `id` des éléments GeoJSON est censée contenir l'identifiant de l'unité d'organisation. | +| `geoJsonProperty` | `Chaîne` | _undefined_ | Si `geoJsonId` est défini sur `false`, ce paramètre nomme la propriété dans les `properties` de l'élément GeoJSON qui contient l'identifiant de l'unité d'organisation. | +| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | La propriété de l'unité d'organisation à laquelle se réfèrent les identifiants utilisés dans le fichier GeoJSON. | +| `attributeId` | `Chaîne` | _undefined_ | Lorsqu'elle est définie, la géométrie est stockée en tant que valeur de l'attribut référencé par l'ID. | +| `dryRun` | `booléen` | `faux` | Si le paramètre est défini sur `true`, l'importation est traitée sans que les unités d'organisation ne soient mis à jour. | +| `async` | `booléen` | `faux` | Lorsque le paramètre est défini sur `true`, l'importation est traitée de manière asynchrone. | Uasge: POST /api/organisationUnits/geometry -The post body is the GeoJSON file. Content type should be `application/json` or -`application/geo+json`. The file may be `.zip` or `.gzip` compressed. +Le corps du message est le fichier GeoJSON. Le type de contenu doit être `application/json` ou `application/geo+json`. Le fichier peut être compressé en `.zip` ou `.gzip`. -For example, a default file where `id` is used to refer to an organisation unit -id has this structure: +Par exemple, un fichier par défaut dans lequel `id` est utilisé pour faire référence à l'identifiant d'une unité d'organisation a la structure suivante : ```json { @@ -1089,8 +1078,7 @@ id has this structure: } ``` -A file where a feature property is used to refer to the organisation unit code -would have this structure: +Un fichier dans lequel une propriété d'élément est utilisée pour faire référence au code de l'unité d'organisation devrait avoir la structure suivante : ```json { @@ -1105,62 +1093,55 @@ would have this structure: ] } ``` -A `geometry` may also be `null` to effectively clear or delete the geometry -for specific organisation units. There is a special bulk deletion API that is -described in the next section. +Une `geometry` peut également être `null` pour effacer ou supprimer efficacement la géométrie pour des unités d'organisation spécifiques. Il existe une API spéciale de suppression en masse ; elle est décrite dans la section suivante. -When run synchronously an import report is returned directly. -The HTTP status code is always `OK`, the `status` in the message payload -indicates if all rows were imported successfully. -The import counts statistics contained in the report give further information: +Lorsqu'elle est exécutée de manière synchrone, un rapport d'importation est renvoyé directement. +Le code de statut HTTP est toujours `OK`, le `status` dans le message indique si toutes les lignes ont été importées avec succès. +Les statistiques sur le nombre de lignes importées, contenues dans le rapport donnent des informations supplémentaires : -* `imported`: number of organisation units that were successfully updated with a geometry that did not have one before for the updated property -* `updated`: number of organisation units that were successfully updated with a geometry that did have value for the updated property already -* `ignored`: number of organisation units that failed to update -* `deleted`: number of organisation units that where successfully update with a _empty_ geometry +* `imported` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui n'en avait pas pour la propriété mise à jour. +* `updated` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui avait déjà une valeur pour la propriété mise à jour. +* `ignored` : nombre d'unités d'organisation qui n'ont pas été mises à jour +* `deleted` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie _vide_. -When the import is run asynchronous the request returns immediately with status -`OK` and job configuration response that contains a relative reference to -the task endpoint that allows to track the status of the asynchronous import. -For example: +Lorsque l'importation est exécutée de manière asynchrone, la requête renvoie immédiatement le statut `OK` de même que la réponse de configuration de la tâche qui contient une référence relative au point d'extrémité de la tâche qui permet de suivre le statut de l'importation asynchrone. Voici un exemple : /api/system/tasks/GEOJSON_IMPORT/{job-id} -The summary that is returned directly for synchronous execution is available at +Le récapitulatif renvoyé directement pour une exécution synchrone est disponible à l'adresse suivante : /api/system/taskSummaries/GEOJSON_IMPORT/{job-id} -once the import is finished. +dès que l'importation est terminée. -### GeoJSON Bulk Data Deletion { #webapi_geojson_bulk_deletion } -To clear or unset the `geometry` data for all organisation units use: +### Suppression de données en masse avec GeoJSON { #webapi_geojson_bulk_deletion } +Pour effacer ou désactiver les données `geometry` pour toutes les unités d'organisation, utilisez : DELETE /api/organisationUnits/geometry -To clear or unset the geometry data for a specific `GEOJSON` attribute for -all organisation units use: +Pour effacer ou désactiver les données géométriques d'un attribut `GEOJSON` spécifique pour toutes les unités d'organisation : DELETE /api/organisationUnits/geometry?attributeId={attr-id} -Clearing is always synchronous and returns a similar report as the bulk import. -It does not support any other parameters. No `dry-run` can be performed. -Bulk clearing requires the `F_PERFORM_MAINTENANCE` authority. +Le nettoyage se fait toujours de façon synchrone et renvoie un rapport similaire à celui de l'importation en masse. +Il ne prend en charge aucun autre paramètre. Aucun `essai` ne peut être effectué. +Pour effectuer un nettoyage en masse, l'utilisateur doit disposer de l'autorité `F_PERFORM_MAINTENANCE`. -### GeoJSON Single Data Import { #webapi_geojson_single_import } -The single import allows to update the geometry of a single organisation unit. +### Importation de données à titre individuel avec GeoJSON { #webapi_geojson_single_import } +L'importation unique permet de mettre à jour la géométrie d'une seule unité d'organisation. POST /api/organisationUnits/{id}/geometry -The post body only contains the GeoJSON `geometry` value, for example: +Le corps du message ne contient que la valeur GeoJSON `geometry`, par exemple : ```json { "type": "Polygon", "coordinates": [...] } ``` -Single import only supports `attributeId` and `dryRun` parameters. +L'importation unique ne prend en charge que les paramètres `attributeId` et `dryRun`. -### GeoJSON Single Data Deletion { #webapi_geojson_single_deletion } +### Suppression de données uniques avec GeoJSON { #webapi_geojson_single_deletion } To clear the `geometry` GeoJSON data of an individual organisation unit use: DELETE /api/organisationUnits/{id}/geometry @@ -1195,7 +1176,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons @@ -1334,7 +1315,7 @@ Table: Style properties | Propriété | Description | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -1657,7 +1638,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -1716,7 +1697,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2055,7 +2036,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -2588,7 +2569,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__new-tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__new-tracker-md index fbb494be9..f84edc443 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__new-tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__new-tracker-md @@ -378,7 +378,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md index b31ea5e39..fc5489a98 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md @@ -334,27 +334,27 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | | reportingParams | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | @@ -884,25 +884,25 @@ Tableau : Attributs de la visualisation d'événements | périodes relatives | Un objet représentant les périodes relatives utilisées dans la requête analytique. | | légende | An object representing the definitions for the legend and legend set, display style (FILL or TEXT) and display strategy (FIXED or BY_DATA_ITEM). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md index 542622229..c0c0c8046 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md @@ -8,38 +8,38 @@ tags: # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -48,13 +48,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -63,13 +63,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -78,35 +78,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -138,23 +138,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -179,44 +179,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -224,8 +224,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -233,48 +233,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -282,7 +282,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -290,12 +290,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -321,23 +321,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -363,8 +363,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -395,8 +395,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -404,51 +404,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || - -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || + +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md index 0c3168bfd..ce36eaeda 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md @@ -929,19 +929,18 @@ Tableau : Paramètres d'importation | importStrategy (stratégie d'importation) | CREATE_AND_UPDATE, CREATE, UPDATE, DELETE (créer et mettre à jour, créer, mettre à jour, supprimer) | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | | ~~mergeMode~~ (mode de fusion) | ~~REPLACE, MERGE~~ (remplacer, fusionner) | ~~Définit le mode de fusion. Lors des mises à jour nous avons deux façons de fusionner l'ancien objet avec le nouveau. Le mode `MERGE` ne remplacera l'ancienne propriété que si la nouvelle n'est pas nulle. Pour le mode `REPLACE`, toutes les propriétés sont remplacées qu'elles soient nulles ou non.~~ (*) | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | > (*) Currently the `mergeMode=MERGE` option of the import service has limitations and doesn't support all objects. It doesn't work with some object types such as Embedded objects, or objects which are saved as JSONB format in database ( sharing, attributeValues, etc...). Fixing those issues are complicated and would just cause new issues. Therefore, this `mergedMode=MERGE` is deprecated and currently is not recommended to use. The update mode should always be mergedMode=REPLACE. We have developed a new [JSON Patch API](#webapi_partial_updates) which can be used as an alternative approach. This feature is introduced in 2.37 release. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -978,10 +977,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1036,40 +1032,33 @@ ignored: ## GeoJSON import { #geojson-import } -The GeoJSON import is used to attach geometry data to organisation units. +L'importation GeoJSON est utilisée pour relier les données géométriques aux unités d'organisation. -For a bulk import a GeoJSON file with a feature collection is expected. -Each feature in the collection requires a reference to the organisation unit it -should be linked to. +Pour une importation en masse, il faut un fichier GeoJSON avec une collection d'éléments. +Chaque élément de la collection a besoin d'une référence à l'unité d'organisation à laquelle il doit être relié. -By default, the geometry from the file is stored as the `geometry` property of -an organisation unit. To store additional geometries attributes of type -`GEOJSON` can be created. When attributes are use all geometries from a file -are stored for the same attribute which is provided with an additional -parameter `attributeId`. +Par défaut, la géométrie du fichier est stockée en tant que propriété `geometry` d'une unité d'organisation. Pour stocker des géométries supplémentaires, des attributs de type `GEOJSON` peuvent être créés. Lorsque des attributs sont utilisés, toutes les géométries d'un fichier sont stockées pour le même attribut qui est fourni avec un paramètre supplémentaire `attributeId`. -### GeoJSON Bulk Data Import { #webapi_geojson_bulk_import } +### Importation de données en masse avec GeoJSON { #webapi_geojson_bulk_import } -Table: Import Parameters +Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| -| `geoJsonId` | `booléen` | `vrai` | When `true` the `id` property of the GeoJSON features is expected to hold the organisation unit identifier | -| `geoJsonProperty` | `Chaîne` | _undefined_ | If `geoJsonId` is `false` this parameter names the property in the GeoJSON feature's `properties` that holds the organisation unit identifier | -| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | The property of the organisation unit that is referred to by the identifiers used in the GeoJSON file | -| `attributeId` | `Chaîne` | _undefined_ | When set the geometry is stored as value of the attribute referenced by ID | -| `dryRun` | `booléen` | `faux` | When `true` the import is processed without actually updating the organisation units | -| `async` | `booléen` | `faux` | When `true` the import is processed asnychronously | +| `geoJsonId` | `booléen` | `vrai` | Si le paramètre est défini sur `true`, la propriété `id` des éléments GeoJSON est censée contenir l'identifiant de l'unité d'organisation. | +| `geoJsonProperty` | `Chaîne` | _undefined_ | Si `geoJsonId` est défini sur `false`, ce paramètre nomme la propriété dans les `properties` de l'élément GeoJSON qui contient l'identifiant de l'unité d'organisation. | +| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | La propriété de l'unité d'organisation à laquelle se réfèrent les identifiants utilisés dans le fichier GeoJSON. | +| `attributeId` | `Chaîne` | _undefined_ | Lorsqu'elle est définie, la géométrie est stockée en tant que valeur de l'attribut référencé par l'ID. | +| `dryRun` | `booléen` | `faux` | Si le paramètre est défini sur `true`, l'importation est traitée sans que les unités d'organisation ne soient mis à jour. | +| `async` | `booléen` | `faux` | Lorsque le paramètre est défini sur `true`, l'importation est traitée de manière asynchrone. | Uasge: POST /api/organisationUnits/geometry -The post body is the GeoJSON file. Content type should be `application/json` or -`application/geo+json`. The file may be `.zip` or `.gzip` compressed. +Le corps du message est le fichier GeoJSON. Le type de contenu doit être `application/json` ou `application/geo+json`. Le fichier peut être compressé en `.zip` ou `.gzip`. -For example, a default file where `id` is used to refer to an organisation unit -id has this structure: +Par exemple, un fichier par défaut dans lequel `id` est utilisé pour faire référence à l'identifiant d'une unité d'organisation a la structure suivante : ```json { @@ -1085,8 +1074,7 @@ id has this structure: } ``` -A file where a feature property is used to refer to the organisation unit code -would have this structure: +Un fichier dans lequel une propriété d'élément est utilisée pour faire référence au code de l'unité d'organisation devrait avoir la structure suivante : ```json { @@ -1101,65 +1089,58 @@ would have this structure: ] } ``` -The `coordinates` in a `geometry` may be pairs or triplets. -If a third dimension is present it is stripped during the import. +Les `coordonnées` d'une `géométrie` peuvent être des paires ou des triplets. +Si une troisième dimension est présente, elle est supprimée lors de l'importation. -A `geometry` may also be `null` to effectively clear or delete the geometry -for specific organisation units. There is a special bulk deletion API that is -described in the next section. +Une `geometry` peut également être `null` pour effacer ou supprimer efficacement la géométrie pour des unités d'organisation spécifiques. Il existe une API spéciale de suppression en masse ; elle est décrite dans la section suivante. -When run synchronously an import report is returned directly. -The HTTP status code is always `OK`, the `status` in the message payload -indicates if all rows were imported successfully. -The import counts statistics contained in the report give further information: +Lorsqu'elle est exécutée de manière synchrone, un rapport d'importation est renvoyé directement. +Le code de statut HTTP est toujours `OK`, le `status` dans le message indique si toutes les lignes ont été importées avec succès. +Les statistiques sur le nombre de lignes importées, contenues dans le rapport donnent des informations supplémentaires : -* `imported`: number of organisation units that were successfully updated with a geometry that did not have one before for the updated property -* `updated`: number of organisation units that were successfully updated with a geometry that did have value for the updated property already -* `ignored`: number of organisation units that failed to update -* `deleted`: number of organisation units that where successfully update with a _empty_ geometry +* `imported` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui n'en avait pas pour la propriété mise à jour. +* `updated` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui avait déjà une valeur pour la propriété mise à jour. +* `ignored` : nombre d'unités d'organisation qui n'ont pas été mises à jour +* `deleted` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie _vide_. -When the import is run asynchronous the request returns immediately with status -`OK` and job configuration response that contains a relative reference to -the task endpoint that allows to track the status of the asynchronous import. -For example: +Lorsque l'importation est exécutée de manière asynchrone, la requête renvoie immédiatement le statut `OK` de même que la réponse de configuration de la tâche qui contient une référence relative au point d'extrémité de la tâche qui permet de suivre le statut de l'importation asynchrone. Voici un exemple : /api/system/tasks/GEOJSON_IMPORT/{job-id} -The summary that is returned directly for synchronous execution is available at +Le récapitulatif renvoyé directement pour une exécution synchrone est disponible à l'adresse suivante : /api/system/taskSummaries/GEOJSON_IMPORT/{job-id} -once the import is finished. +dès que l'importation est terminée. -### GeoJSON Bulk Data Deletion { #webapi_geojson_bulk_deletion } -To clear or unset the `geometry` data for all organisation units use: +### Suppression de données en masse avec GeoJSON { #webapi_geojson_bulk_deletion } +Pour effacer ou désactiver les données `geometry` pour toutes les unités d'organisation, utilisez : DELETE /api/organisationUnits/geometry -To clear or unset the geometry data for a specific `GEOJSON` attribute for -all organisation units use: +Pour effacer ou désactiver les données géométriques d'un attribut `GEOJSON` spécifique pour toutes les unités d'organisation : DELETE /api/organisationUnits/geometry?attributeId={attr-id} -Clearing is always synchronous and returns a similar report as the bulk import. -It does not support any other parameters. No `dry-run` can be performed. -Bulk clearing requires the `F_PERFORM_MAINTENANCE` authority. +Le nettoyage se fait toujours de façon synchrone et renvoie un rapport similaire à celui de l'importation en masse. +Il ne prend en charge aucun autre paramètre. Aucun `essai` ne peut être effectué. +Pour effectuer un nettoyage en masse, l'utilisateur doit disposer de l'autorité `F_PERFORM_MAINTENANCE`. -### GeoJSON Single Data Import { #webapi_geojson_single_import } -The single import allows to update the geometry of a single organisation unit. +### Importation de données à titre individuel avec GeoJSON { #webapi_geojson_single_import } +L'importation unique permet de mettre à jour la géométrie d'une seule unité d'organisation. POST /api/organisationUnits/{id}/geometry -The post body only contains the GeoJSON `geometry` value, for example: +Le corps du message ne contient que la valeur GeoJSON `geometry`, par exemple : ```json { "type": "Polygon", "coordinates": [...] } ``` -Single import only supports `attributeId` and `dryRun` parameters. +L'importation unique ne prend en charge que les paramètres `attributeId` et `dryRun`. -### GeoJSON Single Data Deletion { #webapi_geojson_single_deletion } +### Suppression de données uniques avec GeoJSON { #webapi_geojson_single_deletion } To clear the `geometry` GeoJSON data of an individual organisation unit use: DELETE /api/organisationUnits/{id}/geometry @@ -1194,7 +1175,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. These icons can be accessed through the icons @@ -1333,7 +1314,7 @@ Table: Style properties | Propriété | Description | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -1656,7 +1637,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -1715,7 +1696,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2054,7 +2035,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -2616,7 +2597,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index d88a2508d..5b3ee7b07 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -393,7 +393,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md index 2520d80f3..8745e12a2 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__visualizations-md @@ -334,27 +334,27 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | | reportingParams | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | @@ -884,25 +884,25 @@ Tableau : Attributs de la visualisation d'événements | périodes relatives | Un objet représentant les périodes relatives utilisées dans la requête analytique. | | légende | An object representing the definitions for the legend and legend set, display style (FILL or TEXT) and display strategy (FIXED or BY_DATA_ITEM). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md index 94a82be36..404090470 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md @@ -86,7 +86,7 @@ Pour que le résultat soit ordonné selon une propriété spécifique : /api/indicators.json?order=shortName:desc -To order the result based on created datetime property first (descending order) and then by name property (ascending order): +Pour que le résultat soit d'abord ordonné selon la propriété créée "date et heure" (ordre décroissant), puis selon la propriété "nom" (ordre croissant) : /api/indicators.json?order=created:desc,name:asc @@ -943,19 +943,18 @@ Tableau : Paramètres d'importation | preheatMode (mode préchauffage) | REFERENCE, ALL, NONE (référence, tous, aucun) | Définit le mode de préchauffage ; il est utilisé pour signaler si le préchauffage doit être fait pour `TOUS` (comme c'était le cas auparavant avec *preheatCache=true*) ou faire un scan plus intelligent des objets pour voir ce qu'il faut préchauffer (actuellement le paramètre par défaut). Il n'est pas recommandé de le définir sur `AUCUN`. | | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | NONE, CURRENT, SELECTED (aucun, actuel, sélectionné) | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur (userOverrideMode) est défini sur "SELECTED", utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | -> **NOTE** When updating objects, all property values will be overwritten even if the new values are `null`. Please use [JSON Patch API](#webapi_partial_updates) in case you want do partial update to an object. +> **REMARQUE** Lors de la mise à jour des objets, toutes les valeurs des propriétés seront écrasées même si les nouvelles valeurs sont `null`. Veuillez utiliser [JSON Patch API](#webapi_partial_updates) si vous voulez effectuer une mise à jour partielle d'un objet. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -992,10 +991,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1049,40 +1045,33 @@ ignored: ## GeoJSON import { #geojson-import } -The GeoJSON import is used to attach geometry data to organisation units. +L'importation GeoJSON est utilisée pour relier les données géométriques aux unités d'organisation. -For a bulk import a GeoJSON file with a feature collection is expected. -Each feature in the collection requires a reference to the organisation unit it -should be linked to. +Pour une importation en masse, il faut un fichier GeoJSON avec une collection d'éléments. +Chaque élément de la collection a besoin d'une référence à l'unité d'organisation à laquelle il doit être relié. -By default, the geometry from the file is stored as the `geometry` property of -an organisation unit. To store additional geometries attributes of type -`GEOJSON` can be created. When attributes are use all geometries from a file -are stored for the same attribute which is provided with an additional -parameter `attributeId`. +Par défaut, la géométrie du fichier est stockée en tant que propriété `geometry` d'une unité d'organisation. Pour stocker des géométries supplémentaires, des attributs de type `GEOJSON` peuvent être créés. Lorsque des attributs sont utilisés, toutes les géométries d'un fichier sont stockées pour le même attribut qui est fourni avec un paramètre supplémentaire `attributeId`. -### GeoJSON Bulk Data Import { #webapi_geojson_bulk_import } +### Importation de données en masse avec GeoJSON { #webapi_geojson_bulk_import } -Table: Import Parameters +Tableau : Paramètres d'importation | Nom ; | Type | Par défaut | Description ; | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| -| `geoJsonId` | `booléen` | `vrai` | When `true` the `id` property of the GeoJSON features is expected to hold the organisation unit identifier | -| `geoJsonProperty` | `Chaîne` | _undefined_ | If `geoJsonId` is `false` this parameter names the property in the GeoJSON feature's `properties` that holds the organisation unit identifier | -| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | The property of the organisation unit that is referred to by the identifiers used in the GeoJSON file | -| `attributeId` | `Chaîne` | _undefined_ | When set the geometry is stored as value of the attribute referenced by ID | -| `dryRun` | `booléen` | `faux` | When `true` the import is processed without actually updating the organisation units | -| `async` | `booléen` | `faux` | When `true` the import is processed asnychronously | +| `geoJsonId` | `boolean` | `true` | Si le paramètre est défini sur `true`, la propriété `id` des éléments GeoJSON est censée contenir l'identifiant de l'unité d'organisation. | +| `geoJsonProperty` | `String` | _undefined_ | Si `geoJsonId` est défini sur `false`, ce paramètre nomme la propriété dans les `properties` de l'élément GeoJSON qui contient l'identifiant de l'unité d'organisation. | +| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | La propriété de l'unité d'organisation à laquelle se réfèrent les identifiants utilisés dans le fichier GeoJSON. | +| `attributeId` | `String` | _undefined_ | Lorsqu'elle est définie, la géométrie est stockée en tant que valeur de l'attribut référencé par l'ID. | +| `dryRun` | `booléen` | `faux` | Si le paramètre est défini sur `true`, l'importation est traitée sans que les unités d'organisation ne soient mis à jour. | +| `async` | `booléen` | `faux` | Lorsque le paramètre est défini sur `true`, l'importation est traitée de manière asynchrone. | Uasge: POST /api/organisationUnits/geometry -The post body is the GeoJSON file. Content type should be `application/json` or -`application/geo+json`. The file may be `.zip` or `.gzip` compressed. +Le corps du message est le fichier GeoJSON. Le type de contenu doit être `application/json` ou `application/geo+json`. Le fichier peut être compressé en `.zip` ou `.gzip`. -For example, a default file where `id` is used to refer to an organisation unit -id has this structure: +Par exemple, un fichier par défaut dans lequel `id` est utilisé pour faire référence à l'identifiant d'une unité d'organisation a la structure suivante : ```json { @@ -1098,8 +1087,7 @@ id has this structure: } ``` -A file where a feature property is used to refer to the organisation unit code -would have this structure: +Un fichier dans lequel une propriété d'élément est utilisée pour faire référence au code de l'unité d'organisation devrait avoir la structure suivante : ```json { @@ -1114,65 +1102,58 @@ would have this structure: ] } ``` -The `coordinates` in a `geometry` may be pairs or triplets. -If a third dimension is present it is stripped during the import. +Les `coordonnées` d'une `géométrie` peuvent être des paires ou des triplets. +Si une troisième dimension est présente, elle est supprimée lors de l'importation. -A `geometry` may also be `null` to effectively clear or delete the geometry -for specific organisation units. There is a special bulk deletion API that is -described in the next section. +Une `geometry` peut également être `null` pour effacer ou supprimer efficacement la géométrie pour des unités d'organisation spécifiques. Il existe une API spéciale de suppression en masse ; elle est décrite dans la section suivante. -When run synchronously an import report is returned directly. -The HTTP status code is always `OK`, the `status` in the message payload -indicates if all rows were imported successfully. -The import counts statistics contained in the report give further information: +Lorsqu'elle est exécutée de manière synchrone, un rapport d'importation est renvoyé directement. +Le code de statut HTTP est toujours `OK`, le `status` dans le message indique si toutes les lignes ont été importées avec succès. +Les statistiques sur le nombre de lignes importées, contenues dans le rapport donnent des informations supplémentaires : -* `imported`: number of organisation units that were successfully updated with a geometry that did not have one before for the updated property -* `updated`: number of organisation units that were successfully updated with a geometry that did have value for the updated property already -* `ignored`: number of organisation units that failed to update -* `deleted`: number of organisation units that where successfully update with a _empty_ geometry +* `imported` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui n'avait aucune valeur pour la propriété mise à jour. +* `updated` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui avait déjà une valeur pour la propriété mise à jour. +* `ignored` : nombre d'unités d'organisation qui n'ont pas été mises à jour +* `deleted` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie _vide_. -When the import is run asynchronous the request returns immediately with status -`OK` and job configuration response that contains a relative reference to -the task endpoint that allows to track the status of the asynchronous import. -For example: +Lorsque l'importation est exécutée de manière asynchrone, la requête renvoie immédiatement le statut `OK` de même que la réponse de configuration de la tâche qui contient une référence relative au point d'extrémité de la tâche qui permet de suivre le statut de l'importation asynchrone. Voici un exemple : /api/system/tasks/GEOJSON_IMPORT/{job-id} -The summary that is returned directly for synchronous execution is available at +Le récapitulatif renvoyé directement pour une exécution synchrone est disponible à l'adresse suivante /api/system/taskSummaries/GEOJSON_IMPORT/{job-id} -once the import is finished. +dès que l'importation est terminée. -### GeoJSON Bulk Data Deletion { #webapi_geojson_bulk_deletion } -To clear or unset the `geometry` data for all organisation units use: +### Suppression de données en masse avec GeoJSON { #webapi_geojson_bulk_deletion } +Pour effacer ou désactiver les données `geometry` pour toutes les unités d'organisation, utilisez : DELETE /api/organisationUnits/geometry -To clear or unset the geometry data for a specific `GEOJSON` attribute for -all organisation units use: +Pour effacer ou désactiver les données géométriques d'un attribut `GEOJSON` spécifique pour toutes les unités d'organisation : DELETE /api/organisationUnits/geometry?attributeId={attr-id} -Clearing is always synchronous and returns a similar report as the bulk import. -It does not support any other parameters. No `dry-run` can be performed. -Bulk clearing requires the `F_PERFORM_MAINTENANCE` authority. +Le nettoyage se fait toujours de façon synchrone et renvoie un rapport similaire à celui de l'importation en masse. +Il ne prend en charge aucun autre paramètre. Aucun `essai` ne peut être effectué. +Pour effectuer un nettoyage en masse, l'utilisateur doit disposer de l'autorité `F_PERFORM_MAINTENANCE`. -### GeoJSON Single Data Import { #webapi_geojson_single_import } -The single import allows to update the geometry of a single organisation unit. +### Importation de données uniques avec GeoJSON { #webapi_geojson_single_import } +L'importation unique permet de mettre à jour la géométrie d'une seule unité d'organisation. POST /api/organisationUnits/{id}/geometry -The post body only contains the GeoJSON `geometry` value, for example: +Le corps du message ne contient que la valeur GeoJSON `geometry`, par exemple : ```json { "type": "Polygon", "coordinates": [...] } ``` -Single import only supports `attributeId` and `dryRun` parameters. +L'importation unique ne prend en charge que les paramètres `attributeId` et `dryRun`. -### GeoJSON Single Data Deletion { #webapi_geojson_single_deletion } +### Suppression de données uniques avec GeoJSON { #webapi_geojson_single_deletion } To clear the `geometry` GeoJSON data of an individual organisation unit use: DELETE /api/organisationUnits/{id}/geometry @@ -1207,7 +1188,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. There are two different kind of icons: @@ -1425,7 +1406,7 @@ Table: Style properties | Propriété | Description ; | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -1661,7 +1642,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -1757,9 +1738,9 @@ Sample error response looks like: } ``` -## Indicator Types { #webapi_indicator_types} +## Types d'indicateurs { #webapi_indicator_types} -### Merge indicator types { #webapi_indicator_type_merge} +### Fusionner les types d'indicateurs { #webapi_indicator_type_merge} The indicator type merge endpoint allows you to merge a number of indicator types into a target indicator type. @@ -1788,7 +1769,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -1986,7 +1967,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -2045,7 +2026,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2384,7 +2365,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -2954,7 +2935,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md index a86215ba0..6f34627e9 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md @@ -433,7 +433,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md index 126c57251..82c2b09c4 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md @@ -334,27 +334,27 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | | reportingParams | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | @@ -884,25 +884,25 @@ Tableau : Attributs de la visualisation d'événements | périodes relatives | Un objet représentant les périodes relatives utilisées dans la requête analytique. | | légende | An object representing the definitions for the legend and legend set, display style (FILL or TEXT) and display strategy (FIXED or BY_DATA_ITEM). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index 660951ea3..28fc20046 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/analytics.md" -revision_date: '2024-05-02' +revision_date: '2024-05-31' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Analyse { #analytics } @@ -620,7 +620,7 @@ Tableau : Paramètres de requête pour l'analyse des requêtes d'événement un | Paramètre de requête | Obligatoire | Description | Options | |---|---|---|---| -| ou Mode | Non | Il s'git du mode de sélection des unités d'organisation. La valeur par défaut est DESCENDANTS (descendants), c'est-à-dire toutes les sous-unités dans la hiérarchie. CHILDREN (subordonnées) fait référence aux unités qui se trouvent directement en dessous de l'unité de référence dans la hiérarchie ; SELECTED (sélectionnées) fait référence aux unités d'organisation sélectionnées uniquement. Vous trouverez plus de détails [ici].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ou Mode | Non | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Non | Permet de trier les dimensions par ordre croissant; peut concerner la date de l'événement, le nom et le code de l'unité d'organisation et tout identifiant d'élément. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Non | Permet de trier les dimensions par ordre décroissant ; peut concerner la date de l'événement, le nom et le code de l'unité d'organisation et tout identifiant d'élément. | `ouname` | `programstatus` | `eventstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `eventdate` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly (coordonnées uniquement) | Non | Indique s'il faut uniquement renvoyer les événements qui ont des coordonnées. | faux | vrai | @@ -1429,7 +1429,7 @@ Tableau : Paramètres de requête pour le point d'extrémité de la requête d' | filtre | Non | L'identifiant de dimension comprend les éléments de données, les attributs, les périodes, les unités d'organisation et les ensembles de groupes d'unités d'organisation. Le paramètre peut être répété autant de fois que nécessaire. Des filtres d'éléments peuvent être appliqués à une dimension selon le format ::. Les valeurs des filtres ne sont pas sensibles à la casse. || | programStatus (statut de programme) | Non | Spécifie le statut d’inscription des inscriptions à inclure. | ACTIF | TERMINÉ | ANNULÉ | | relativePeriodDate (Date de la période relative) | chaîne | Non | Identifiant de date, par exemple : "2016-01-01". Il remplace la date de début de la période relative | -| ou Mode | Non | Il s'git du mode de sélection des unités d'organisation. La valeur par défaut est DESCENDANTS (descendants), c'est-à-dire toutes les sous-unités dans la hiérarchie. CHILDREN (subordonnées) fait référence aux unités qui se trouvent directement en dessous de l'unité de référence dans la hiérarchie ; SELECTED (sélectionnées) fait référence aux unités d'organisation sélectionnées uniquement. Vous trouverez plus de détails [ici].(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | DESCENDANTS, CHILDREN, SELECTED | +| ou Mode | Non | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | DESCENDANTS, CHILDREN, SELECTED | | asc | Non | Permet de trier les dimensions par ordre croissant ; peut concerner la date d'inscription, la date d'incident, le nom et le code de l'unité d'organisation. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | desc | Non | Permet de trier les dimensions dans l'ordre décroissant ; peut concerner la date d'inscription, la date d'incident, le nom et le code de l'unité d'organisation. | `ouname` | `programstatus` | `createdbydisplayname` | `lastupdatedbydisplayname` | `enrollmentdate` | `incidentdate` | `lastupdated` | item identifier | | coordinatesOnly (coordonnées uniquement) | Non | Indique s'il faut uniquement renvoyer les inscriptions qui ont des coordonnées. | faux | vrai | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index 983585790..15510c977 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Applications { #apps } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index 05f9bf30d..4dfb4773e 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" revision_date: '2023-06-23' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index 0f15bcb46..62a779441 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Approbation des données { #data-approval } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index 8c6fae677..6df194825 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Saisie de données { #data-entry } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index a68d3010e..fd9239d18 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Échange de données { #data-exchange } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index dec923c83..6b070ac39 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Données { #data } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index d40168fba..2c28da7e3 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Magasin de données { #data-store } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index 47aff1868..461110365 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Validation des données { #data-validation } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md index 05e1a5544..d4aead4a9 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Adresses électronique { #email } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index 84311cffe..f029b8e52 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 889f4999b..017ab005f 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # I18n { #i18n } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index 6d1ad989c..ea430596e 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Aperçu { #webapi } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index b2c8d65bf..4ce1b26ef 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Maintenance { #maintenance } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md index 443cfc227..652a680bd 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md @@ -2,44 +2,44 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Messagerie { #messaging } -## Message conversations { #webapi_message_conversations } +## Conversations par messages { #webapi_message_conversations } -DHIS2 features a mechanism for sending messages for purposes such as -user feedback, notifications, and general information to users. Messages -are grouped into conversations. To interact with message conversations -you can send POST and GET request to the *messageConversations* -resource. +DHIS2 dispose d'un mécanisme permettant d'envoyer des messages à des fins tels que +le retour d'information des utilisateurs, les notifications et les informations générales à l'intention des utilisateurs. Les messages +sont regroupés en conversations. Pour interagir avec les conversations de messages, +vous pouvez envoyer des requêtes POST et GET à la ressource +*messageConversations*. /api/33/messageConversations -Messages are delivered to the DHIS2 message inbox but can also be sent -to the user's email addresses and mobile phones as SMS. In this example, -we will see how we can utilize the Web API to send, read and manage -messages. We will pretend to be the *DHIS2 Administrator* user and send -a message to the *Mobile* user. We will then pretend to be the mobile -user and read our new message. Following this, we will manage the admin -user inbox by marking and removing messages. +Les messages sont transmis à la boîte de réception DHIS2, mais ils peuvent également être envoyés +aux adresses électroniques et aux téléphones portables de l'utilisateur sous forme de SMS. Dans cet exemple, +nous verrons comment utiliser l'API Web pour envoyer, lire et gérer des +messages. Nous allons nous faire passer pour l'utilisateur *Administrateur DHIS2* et envoyer +un message à l'utilisateur *Mobile*. Nous allons ensuite nous faire passer pour l'utilisateur +mobile et lire notre nouveau message. Ensuite, nous allons gérer la boîte de réception de l'utilisateur +administrateur en marquant et en supprimant des messages. -### Writing and reading messages { #webapi_writing_messages } +### Écrire et lire des messages { #webapi_writing_messages } -The resource we need to interact with when sending and reading messages -is the *messageConversations* resource. We start by visiting the Web API -entry point at where we find and follow -the link to the *messageConversations* resource at -. The description -tells us that we can use a POST request to create a new message using -the following XML format for sending to multiple users: +La ressource avec laquelle nous devons interagir pour envoyer et lire des messages +est la ressource *messageConversations*. Nous commençons par visiter le point d'entrée +de l'API Web à l'adresse , où nous trouvons et suivons +le lien vers la ressource *messageConversations* à l'adresse +. La description +nous indique que nous pouvons utiliser une requête POST pour créer un nouveau message +en utilisant le format XML suivant pour l'envoyer à plusieurs utilisateurs : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -48,13 +48,13 @@ the following XML format for sending to multiple users: ``` -For sending to all users contained in one or more user groups, we can -use: +Pour l'envoi à tous les utilisateurs appartenant à un ou plusieurs groupes d'utilisateurs, nous pouvons +utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -63,13 +63,13 @@ use: ``` -For sending to all users connected to one or more organisation units, we -can use: +Pour l'envoi à tous les utilisateurs connectés à une ou plusieurs unités d'organisation, nous +pouvons utiliser : ```xml - This is the subject - This is the text + Voici le sujet + Voici le texte @@ -78,35 +78,35 @@ can use: ``` -Since we want to send a message to our friend the mobile user we need to -look up her identifier. We do so by going to the Web API entry point and -follow the link to the *users* resource at `/api/users`. We continue by -following link to the mobile user at `/api/users/PhzytPW3g2J` where we learn -that her identifier is *PhzytPW3g2J*. We are now ready to put our XML -message together to form a message where we want to ask the mobile user -whether she has reported data for January 2014: +Puisque nous voulons envoyer un message à notre ami l'utilisateur mobile, nous devons +rechercher son identifiant. Nous le faisons en allant au point d'entrée de l'API Web et +en suivant le lien vers la ressource *utilisateurs* à `/api/users`. Nous continuons en +suivant le lien vers l'utilisateur mobile à `/api/users/PhzytPW3g2J` où nous apprenons +que son identifiant est *PhzytPW3g2J*. Nous sommes maintenant prêts à rassembler nos messages +XML pour former un message dans lequel nous voulons demander à l'utilisateur mobile +s'il a déclaré des données pour janvier 2014 : ```xml - Mortality data reporting - Have you reported data for the Mortality data set for January 2014? + Rapport sur les données de mortalité + Avez-vous déclaré des données pour l'ensemble de données sur la mortalité pour janvier 2014 ? ``` -To test this we save the XML content into a file called *message.xml*. -We use cURL to dispatch the message the DHIS2 demo instance where we -indicate that the content-type is XML and authenticate as the *admin* -user: +Pour le tester, nous enregistrons le contenu XML dans un fichier appelé *message.xml*. +Nous utilisons cURL pour envoyer le message à l'instance de démonstration DHIS2 où nous +indiquons que le type de contenu est XML et où nous nous authentifions en tant qu'utilisateur +*admin* : ```bash curl -d @message.xml "https://play.dhis2.org/demo/api/messageConversations" -H "Content-Type:application/xml" -u admin:district -X POST ``` -A corresponding payload in JSON and POST command looks like this: +La charge correspondante en JSON et la commande POST ressemblent à ceci : ```json { @@ -138,23 +138,23 @@ curl -d @message.json "https://play.dhis2.org/demo/api/33/messageConversations" -H "Content-Type:application/json" -u admin:district -X POST ``` -If all is well we receive a *201 Created* HTTP status code. Also, note -that we receive a *Location* HTTP header which value informs us of the -URL of the newly created message conversation resource - this can be -used by a consumer to perform further action. +Si tout se passe bien, nous recevons un code de statut HTTP *201 Créé*. Notez également +que nous recevons un en-tête HTTP *Localisation* qui nous informe de +l'URL de la ressource de conversation de messages nouvellement créée - celle-ci peut être +utilisée par un utilisateur pour effectuer d'autres actions. -We will now pretend to be the mobile user and read the message which was -just sent by dispatching a GET request to the *messageConversations* -resource. We supply an *Accept* header with *application/xml* as the -value to indicate that we are interested in the XML resource -representation and we authenticate as the *mobile* user: +Nous allons maintenant nous faire passer pour l'utilisateur mobile et lire le message qui +vient d'être envoyé en envoyant une requête GET à la ressource *messageConversations*. +Nous fournissons un en-tête *Accepter* avec l'*application/xml* comme +valeur pour indiquer que nous sommes intéressés par la représentation de la ressource +XML et nous nous authentifions en tant qu'utilisateur *mobile* : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations" -H "Accept:application/xml" -u mobile:district ``` -In response we get the following XML: +En réponse, nous obtenons le fichier XML suivant : ```xml ``` -From the response, we are able to read the identifier of the newly sent -message which is *ZjHHSjyyeJ2*. Note that the link to the specific -resource is embedded and can be followed in order to read the full -message. We can reply directly to an existing message conversation once we know -the URL by including the message text as the request payload. We -are now able to construct a URL for sending our reply: +Dans la réponse, nous pouvons lire l'identifiant du nouveau message envoyé, +qui est *ZjHHSjyyeJ2*. Notez que le lien vers la ressource spécifique +est intégré et peut être suivi pour lire le message +complet. Une fois que nous connaissons l'URL, nous pouvons répondre directement à +une conversation sur un message existant en incluant le texte du message dans la charge de la requête. Nous +sommes maintenant en mesure de créer une URL pour envoyer notre réponse : ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -179,44 +179,44 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -If all went according to plan you will receive a *200 OK* status code. +Si tout s'est déroulé comme prévu, vous recevrez un code de statut *200 OK*. -In 2.30 we added an URL search parameter: +Dans la version 2.30, nous avons ajouté un paramètre de recherche d'URL : queryString=?&queryOperator=? -The filter searches for matches in subject, text, and senders for message -conversations. The default query operator is *token*, however other operators -can be defined in the query. +Le filtre recherche des correspondances dans l'objet, le texte et les expéditeurs pour les conversations +de messages. L'opérateur de requête par défaut est *token* (jeton), mais d'autres opérateurs +peuvent être définis dans la requête. -### Managing messages { #webapi_managing_messages } +### Gérer les messages { #webapi_managing_messages } -As users receive and send messages, conversations will start to pile up -in their inboxes, eventually becoming laborious to track. We will now -have a look at managing a user's messages inbox by removing and marking -conversations through the Web-API. We will do so by performing some -maintenance in the inbox of the "DHIS Administrator" user. +Au fur et à mesure que les utilisateurs reçoivent et envoient des messages, les conversations commencent à s'empiler +dans leur boîte de réception, ce qui devient éventuellement difficile à suivre. Nous allons maintenant +voir comment gérer la boîte de réception des messages d'un utilisateur en supprimant et en marquant +des conversations par l'intermédiaire de la Web-API. Pour ce faire, nous allons effectuer quelques +opérations de maintenance dans la boîte de réception de l'utilisateur « Administrateur DHIS ». -First, let's have a look at removing a few messages from the inbox. Be -sure to note that all removal operations described here only remove the -relation between a user and a message conversation. In practical terms -this means that we are not deleting the messages themselves (or any -content for that matter) but are simply removing the message thread from -the user such that it is no longer listed in the -`/api/messageConversations` resource. +Commençons par supprimer quelques messages de la boîte de réception. Notez +bien que toutes les opérations de suppression décrites ici ne suppriment que la +relation entre un utilisateur et une conversation de messages. En termes pratiques, +cela signifie que nous ne supprimons pas les messages eux-mêmes (ni aucun +contenu d'ailleurs) mais que nous supprimons simplement le fil de messages de +l'utilisateur de sorte qu'il ne soit plus listé dans +la ressource `/api/messageConversations`. -To remove a message conversation from a users inbox we need to issue a -*DELETE* request to the resource identified by the id of the message -conversation and the participating user. For example, to remove the user -with id `xE7jOejl9FI` from the conversation with id `jMe43trzrdi`: +Pour supprimer une conversation de messages de la boîte de réception d'un utilisateur, nous devons envoyer une +requête *DELETE* à la ressource identifiée par l'identifiant de la conversation de +messages et l'utilisateur participant. Par exemple, pour supprimer l'utilisateur +avec l'identifiant `xE7jOejl9FI` de la conversation avec l'identifiant `jMe43trzrdi` : ```bash curl "https://play.dhis2.org/demo/api/33/messageConversations/jMe43trzrdi ``` -If the request was successful the server will reply with a *200 OK*. The -response body contains an XML or JSON object (according to the accept -header of the request) containing the id of the removed user. +Si la demande a abouti, le serveur répondra par un *200 OK*. Le +corps de la réponse contient un objet XML ou JSON (selon l'en-tête "accepter" +de la demande) contenant l'identifiant de l'utilisateur supprimé. ```json { @@ -224,8 +224,8 @@ header of the request) containing the id of the removed user. } ``` -On failure the returned object will contain a message payload which -describes the error. +En cas d'échec, l'objet renvoyé contiendra un message qui +décrit l'erreur. ```json { @@ -233,48 +233,48 @@ describes the error. } ``` -The observant reader will already have noticed that the object returned -on success in our example is actually a list of ids (containing a single -entry). This is due to the endpoint also supporting batch removals. The -request is made to the same *messageConversations* resource but follows -slightly different semantics. For batch operations, the conversation ids -are given as query string parameters. The following example removes two -separate message conversations for the current user: +Le lecteur observateur aura déjà remarqué que l'objet renvoyé en cas +de succès dans notre exemple est en fait une liste d'identifiants (contenant une seule +entrée). Ceci est dû au fait que le endpoint prend également en charge les suppressions par lots. La +requête est faite à la même ressource *messageConversations* mais suit +une sémantique légèrement différente. Pour les opérations par lots, les identifiants +de conversation sont donnés en tant que paramètres de la chaîne de requête. L'exemple suivant supprime deux +conversations de messages distinctes pour l'utilisateur actuel : ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm" -X DELETE -u admin:district ``` -If you have sufficient permissions, conversations can be removed on -behalf of another user by giving an optional user id parameter. +Si vous disposez d'autorisations suffisantes, vous pouvez supprimer des conversations au +nom d'un autre utilisateur en indiquant un paramètre facultatif, l'identifiant de l'utilisateur. ```bash curl "https://play.dhis2.org/demo/api/messageConversations?mc=WzMRrCosqc0&mc=lxCjiigqrJm&user=PhzytPW3g2J" -X DELETE -u admin:district ``` -As indicated, batch removals will return the same message format as for -single operations. The list of removed objects will reflect successful -removals performed. Partially erroneous requests (i.e. non-existing id) -will therefore not cancel the entire batch operation. +Comme indiqué, les suppressions par lots renvoient le même format de message que pour +les opérations individuelles. La liste des objets supprimés reflétera les suppressions +effectuées avec succès. Les demandes partiellement erronées (c'est-à-dire les identifiants inexistants) +n'annuleront donc pas l'ensemble de l'opération par lots. -Messages carry a boolean *read* property. This allows tracking whether a -user has seen (opened) a message or not. In a typical application -scenario (e.g. the DHIS2 web portal) a message will be marked read as -soon as the user opens it for the first time. However, users might want -to manage the read or unread status of their messages in order to keep -track of certain conversations. +Les messages comportent une propriété booléenne *read* (lire). Cette propriété permet de savoir si un +utilisateur a vu (ouvert) un message ou non. Dans un scénario d'application +typique (par exemple, le portail web DHIS2), un message est marqué comme +lu dès que l'utilisateur l'ouvre pour la première fois. Cependant, les utilisateurs peuvent vouloir +gérer le statut « lu » ou « non lu » de leurs messages afin de garder une +trace de certaines conversations. -Marking messages read or unread follows similar semantics as batch -removals, and also supports batch operations. To mark messages as read -we issue a *POST* to the `messageConversations/read` resource with a -request body containing one or more message ids. To mark messages as -unread we issue an identical request to the `messageConversations/unread` -resource. As is the case for removals, an optional *user* request parameter -can be given. +Le marquage des messages comme lus ou non lus suit une sémantique similaire à celle des suppressions +de lots, et supporte également les opérations par lots. Pour marquer des messages comme lus, +nous envoyons un *POST* à la ressource `messageConversations/read` avec un +corps de requête contenant un ou plusieurs identifiants de message. Pour marquer des messages comme +non lus, nous envoyons une requête identique à la ressource `messageConversations/unread`. +Comme pour les suppressions, un paramètre de requête optionnel *utilisateur* peut +être fourni. -Let's mark a couple of messages as read by the current user: +Marquons quelques messages comme lus par l'utilisateur actuel : ```bash curl "https://play.dhis2.org/dev/api/messageConversations/read" @@ -282,7 +282,7 @@ curl "https://play.dhis2.org/dev/api/messageConversations/read" -H "Content-Type: application/json" -u admin:district ``` -The response is a *200 OK* with the following JSON body: +La réponse est un *200 OK* avec le contenu JSON suivant : ```json { @@ -290,12 +290,12 @@ The response is a *200 OK* with the following JSON body: } ``` -You can add recipients to an existing message conversation. The resource is located at: +Vous pouvez ajouter des destinataires à une conversation de messages existante. La ressource est située à l'adresse suivante : /api/33/messageConversations/id/recipients -The options for this resource is a list of users, user groups and -organisation units. The request should look like this: +Les options de cette ressource sont une liste d'utilisateurs, de groupes d'utilisateurs et +d'unités d'organisation. La requête doit ressembler à ceci : ```json { @@ -321,23 +321,23 @@ organisation units. The request should look like this: ``` -### Message Attachments { #webapi_message_attachments } +### Pièces jointes aux messages { #webapi_message_attachments } -Creating messages with attachments is done in two steps: uploading the -file to the *attachments* resource, and then including one or several of -the attachment IDs when creating a new message. +La création de messages avec des pièces jointes se fait en deux étapes : le téléchargement du +fichier dans la ressource *attachments* (pièces jointes), puis inclure un ou plusieurs +pièces jointes lors de la création d'un nouveau message. -A POST request to the *attachments* resource will upload the file to the -server. +Une requête POST à la ressource *attachments* téléchargera le fichier sur le +serveur. ``` curl -F file=@attachment.png "https://play.dhis2.org/demo/api/messageConversations/attachments" -u admin:district ``` -The request returns an object that represents the attachment. The id of -this object must be used when creating a message in order to link the -attachment with the message. +La demande renvoie un objet qui représente la pièce jointe. L'identifiant de +cet objet doit être utilisé lors de la création d'un message afin de lier la +pièce jointe au message. ```json { @@ -363,8 +363,8 @@ attachment with the message. } ``` -When creating a new message, the ids can be passed in the request body -to link the uploaded files to the message being created. +Lors de la création d'un nouveau message, les identifiants peuvent être transmis dans le contenu de la requête +pour lier les fichiers téléchargés au message en cours de création. ```json { @@ -395,8 +395,8 @@ to link the uploaded files to the message being created. } ``` -When replying to a message, the ids can be passed as a request -parameter. +Lorsque vous répondez à un message, les identifiants peuvent être transmis en tant que paramètre de la +requête. ```bash curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" @@ -404,51 +404,49 @@ curl -d "Oui, l'ensemble des données sur la mortalité a été déclaré" -H "Content-Type:text/plain" -u mobile:district -X POST ``` -Once a message with an attachment has been created, the attached file -can be accessed with a GET request to the following URL: +Une fois qu'un message avec une pièce jointe a été créé, il est possible d'accéder à la pièce jointe +à l'aide d'une requête GET à l'URL suivante : /api/messageConversations///attachments/ -Where is the *message conversation* ID, is the ID of -the *message* that contains the attachment and is the -ID of the specific *message attachment*. +Où est l'ID de la *conversation du message*, est l'ID du *message* qui contient la pièce jointe et est l'ID de la *pièce jointe* spécifique du message. -### Tickets and Validation Result Notifications { #webapi_messaging_tickets } +### Notifications des tickets et des résultats de validation { #webapi_messaging_tickets } -You can use the "write feedback" tool to create tickets and messages. -The only difference between a ticket and a message is that you can give -a status and a priority to a ticket. To set the status: +Vous pouvez utiliser l'outil « écrire un feedback » pour créer des tickets et des messages. +La seule différence entre un ticket et un message est que vous pouvez donner +un statut et une priorité à un ticket. Pour définir le statut : POST /api/messageConversations//status -To set the priority: +Pour définir la priorité : POST /api/messageConversations//priority -In 2.29, messages generated by validation analysis now also be used in -the status and priority properties. By default, messages generated by -validation analysis will inherit the priority of the validation rule in -question, or the highest importance if the message contains multiple -rules. +Dans la version 2.29, les messages générés par l'analyse de validation peuvent désormais être utilisés dans +les propriétés de statut et de priorité. Par défaut, les messages générés par +l'analyse de validation héritent de la priorité de la règle de validation en +question, ou de la plus grande importance si le message contient plusieurs +règles. -In 2.30, validation rules can be assigned to any user while tickets -still need to be assigned to a user in the system's feedback recipient -group. +Dans la version 2.30, les règles de validation peuvent être affectées à n'importe quel utilisateur, alors que les tickets +doivent toujours être affectés à un utilisateur appartenant au groupe des destinataires du retour d'information du +système. -Table: A list of valid status and priority values +Tableau : Liste des valeurs de statut et de priorité valides -| Statut | Priority | +| Statut | Priorité | |---|---| -| OPEN | LOW | -| PENDING | MEDIUM | -| INVALID | HIGH | -| SOLVED || - -You can also add an internal message to a ticket, which can only be seen -by users who have "Manage tickets" permissions. To create an internal -reply, include the "internal" parameter, and set it to +| OUVRIR | BAS | +| EN ATTENTE | MOYEN | +| INVALIDE | ÉLEVÉ | +| RÉSOLU || + +Vous pouvez également ajouter un message interne à un ticket, qui ne peut être vu que +par les utilisateurs ayant les permissions « Gérer les tickets ». Pour créer une réponse +interne, vous devez inclure le paramètre « interne » et le définir sur: ```bash curl -d "Ceci est un message interne" diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index ed288aca0..9781a5ebf 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Métadonnées Gist API { #gist_api } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index 9109fc02c..29c9a4581 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Métadonnées { #metadata } @@ -86,7 +86,7 @@ Pour que le résultat soit ordonné selon une propriété spécifique : /api/indicators.json?order=shortName:desc -To order the result based on created datetime property first (descending order) and then by name property (ascending order): +Pour que le résultat soit d'abord ordonné selon la propriété créée "date et heure" (ordre décroissant), puis selon la propriété "nom" (ordre croissant) : /api/indicators.json?order=created:desc,name:asc @@ -943,19 +943,18 @@ Tableau : Paramètres d'importation | preheatMode (mode préchauffage) | REFERENCE, ALL, NONE (référence, tous, aucun) | Définit le mode de préchauffage ; il est utilisé pour signaler si le préchauffage doit être fait pour `TOUS` (comme c'était le cas auparavant avec *preheatCache=true*) ou faire un scan plus intelligent des objets pour voir ce qu'il faut préchauffer (actuellement le paramètre par défaut). Il n'est pas recommandé de le définir sur `AUCUN`. | | importStrategy (stratégie d'importation) | CRÉER_ET_METTRE À JOUR, CRÉER, METTRE À JOUR, SUPPRIMER | Définit la stratégie d'importation ; `CREATE_AND_UPDATE` essaiera de trouver une correspondance avec l'identifiant. Si aucune correspondance n'est trouvée, l'objet sera créé. | | Mode atomique | ALL, NONE (tous, aucun) | Définit le mode atomique. Dans l'ancien importateur, nous faisions toujours une importation *best effort* (mode au mieux), ce qui signifie que même si certaines références n'existaient pas, l'importation se faisait quand même (par exemple, des éléments de données manquants dans un groupe d'éléments de données). Par défaut, le nouvel importateur ne permet pas cela et rejette les erreurs de validation. Définir le mode `NONE` (aucun) émulait l'ancien fonctionnement. | -| flushMode | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | +| flushMode (mode de vidage) | AUTO, OBJET | Définit le mode de vidage, qui contrôle quand vider le cache interne. Il est *fortement* recommandé de maintenir ce mode sur `AUTO` (qui est le mode par défaut). N'utilisez `OBJECT` qu'à des fins de débogage, lorsque vous voyez des exceptions liées à l'hibernation et que vous voulez localiser l'emplacement exact où l'empilement se produit (l'hibernation ne se déclenche qu'au moment du vidage, il peut donc être difficile de savoir quel objet a eu des problèmes). | | skipSharing (ignorer le partage) | faux, vrai | Permet d'ignorer les propriétés de partage, d'éviter la fusion des éléments partagées lors des mises à jour et l'ajout d'un accès à un groupe d'utilisateurs lors de la création de nouveaux objets. | | skipValidation (ignorer la validation) | faux, vrai | Permet d'ignorer la validation lors de l'importation. Ce paramètre n'est pas recommandé : `NOT RECOMMENDED`. | -| async | faux, vrai | Asynchronous import, returns immediately with a *Location* header pointing to the location of the *importReport*. The payload also contains a json object of the job created. | -| inclusionStrategy | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* includes properties which are not null, *ALWAYS* include all properties, *NON_EMPTY* includes non empty properties (will not include strings of 0 length, collections of size 0, etc.) | -| userOverrideMode | NONE, CURRENT, SELECTED | Allows you to override the user property of every object you are importing, the options are NONE (do nothing), CURRENT (use import user), SELECTED (select a specific user using overrideUser=X) | -| overrideUser | User ID | If userOverrideMode is SELECTED, use this parameter to select the user you want override with. | +| async | faux, vrai | Importation asynchrone ; la réponse est renvoyée immédiatement avec un en-tête *Emplacement* qui pointe vers l'emplacement du *rapport d'importation*. La charge contient également un objet json de la tâche créée. | +| inclusionStrategy (stratégie d'inclusion) | NON_NULL, ALWAYS, NON_EMPTY | *NON_NULL* inclut les propriétés qui ne sont pas nulles, *ALWAYS* inclut toutes les propriétés, *NON_EMPTY* inclut les propriétés qui ne sont pas vides (n'inclut pas les chaînes de longueur 0, les collections de taille 0, etc.) | +| userOverrideMode (utiliser le mode de remplacement) | AUCUN, ACTUEL, SÉLECTIONNÉ | Ceci vous permet de remplacer la propriété utilisateur de chaque objet que vous importez. Les options sont NONE (ne rien faire), CURRENT (utiliser l'utilisateur d'importation), SELECTED (sélectionner un utilisateur spécifique en utilisant overrideUser=X). | +| overrideUser (remplacer l'utilisateur) | ID de l'utilisateur | Si le mode de remplacement de l'utilisateur est sélectionné, utilisez ce paramètre pour sélectionner l'utilisateur avec lequel vous voulez effectuer le remplacement. | -> **NOTE** When updating objects, all property values will be overwritten even if the new values are `null`. Please use [JSON Patch API](#webapi_partial_updates) in case you want do partial update to an object. +> **REMARQUE** Lors de la mise à jour des objets, toutes les valeurs des propriétés seront écrasées même si les nouvelles valeurs sont `null`. Veuillez utiliser [JSON Patch API](#webapi_partial_updates) si vous voulez faire une mise à jour partielle d'un objet. -An example of a metadata payload to be imported looks like this. Note how -each entity type have their own property with an array of objects: +Voici un exemple de charge d'importation de métadonnées. Vous remarquerez que chaque type d'entité possède sa propre propriété avec un tableau d'objets : ```json { @@ -992,10 +991,7 @@ each entity type have their own property with an array of objects: } ``` -When posting this payload to the metadata endpoint, the response will contain -information about the parameters used during the import and a summary per -entity type including how many objects were created, updated, deleted and -ignored: +Lors de l'envoi de cette charge au point d'extrémité des métadonnées, la réponse contiendra des informations sur les paramètres utilisés lors de l'importation et un récapitulatif par type d'entité, lequel contiendra le nombre d'objets créés, mis à jour, supprimés et ignorés : ```json { @@ -1049,40 +1045,33 @@ ignored: ## GeoJSON import { #geojson-import } -The GeoJSON import is used to attach geometry data to organisation units. +L'importation GeoJSON est utilisée pour relier les données géométriques aux unités d'organisation. -For a bulk import a GeoJSON file with a feature collection is expected. -Each feature in the collection requires a reference to the organisation unit it -should be linked to. +Pour une importation en masse, il faut un fichier GeoJSON avec une collection d'éléments. +Chaque élément de la collection a besoin d'une référence à l'unité d'organisation à laquelle il doit être relié. -By default, the geometry from the file is stored as the `geometry` property of -an organisation unit. To store additional geometries attributes of type -`GEOJSON` can be created. When attributes are use all geometries from a file -are stored for the same attribute which is provided with an additional -parameter `attributeId`. +Par défaut, la géométrie du fichier est stockée en tant que propriété `geometry` d'une unité d'organisation. Pour stocker des géométries supplémentaires, des attributs de type `GEOJSON` peuvent être créés. Lorsque des attributs sont utilisés, toutes les géométries d'un fichier sont stockées pour le même attribut qui est fourni avec un paramètre supplémentaire `attributeId`. -### GeoJSON Bulk Data Import { #webapi_geojson_bulk_import } +### Importation de données en masse avec GeoJSON { #webapi_geojson_bulk_import } -Table: Import Parameters +Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| -| `geoJsonId` | `booléen` | `vrai` | When `true` the `id` property of the GeoJSON features is expected to hold the organisation unit identifier | -| `geoJsonProperty` | `Chaîne` | _undefined_ | If `geoJsonId` is `false` this parameter names the property in the GeoJSON feature's `properties` that holds the organisation unit identifier | -| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | The property of the organisation unit that is referred to by the identifiers used in the GeoJSON file | -| `attributeId` | `Chaîne` | _undefined_ | When set the geometry is stored as value of the attribute referenced by ID | -| `dryRun` | `booléen` | `faux` | When `true` the import is processed without actually updating the organisation units | -| `async` | `booléen` | `faux` | When `true` the import is processed asnychronously | +| `geoJsonId` | `booléen` | `vrai` | Si le paramètre est défini sur `true`, la propriété `id` des éléments GeoJSON est censée contenir l'identifiant de l'unité d'organisation. | +| `geoJsonProperty` | `Chaîne` | _undefined_ | Si `geoJsonId` est défini sur `false`, ce paramètre nomme la propriété dans les `properties` de l'élément GeoJSON qui contient l'identifiant de l'unité d'organisation. | +| `orgUnitProperty` | `enum`: [`id`, `code`, `name`] | `id` | La propriété de l'unité d'organisation à laquelle se réfèrent les identifiants utilisés dans le fichier GeoJSON. | +| `attributeId` | `Chaîne` | _undefined_ | Lorsqu'elle est définie, la géométrie est stockée en tant que valeur de l'attribut référencé par l'ID. | +| `dryRun` | `booléen` | `faux` | Si le paramètre est défini sur `true`, l'importation est traitée sans que les unités d'organisation ne soient mis à jour. | +| `async` | `booléen` | `faux` | Lorsque le paramètre est défini sur `true`, l'importation est traitée de manière asynchrone. | Uasge: POST /api/organisationUnits/geometry -The post body is the GeoJSON file. Content type should be `application/json` or -`application/geo+json`. The file may be `.zip` or `.gzip` compressed. +Le corps du message est le fichier GeoJSON. Le type de contenu doit être `application/json` ou `application/geo+json`. Le fichier peut être compressé en `.zip` ou `.gzip`. -For example, a default file where `id` is used to refer to an organisation unit -id has this structure: +Par exemple, un fichier par défaut dans lequel `id` est utilisé pour faire référence à l'identifiant d'une unité d'organisation a la structure suivante : ```json { @@ -1098,8 +1087,7 @@ id has this structure: } ``` -A file where a feature property is used to refer to the organisation unit code -would have this structure: +Un fichier dans lequel une propriété d'élément est utilisée pour faire référence au code de l'unité d'organisation devrait avoir la structure suivante : ```json { @@ -1114,65 +1102,58 @@ would have this structure: ] } ``` -The `coordinates` in a `geometry` may be pairs or triplets. -If a third dimension is present it is stripped during the import. +Les `coordonnées` d'une `géométrie` peuvent être des paires ou des triplets. +Si une troisième dimension est présente, elle est supprimée lors de l'importation. -A `geometry` may also be `null` to effectively clear or delete the geometry -for specific organisation units. There is a special bulk deletion API that is -described in the next section. +Une `geometry` peut également être `null` pour effacer ou supprimer efficacement la géométrie pour des unités d'organisation spécifiques. Il existe une API spéciale de suppression en masse ; elle est décrite dans la section suivante. -When run synchronously an import report is returned directly. -The HTTP status code is always `OK`, the `status` in the message payload -indicates if all rows were imported successfully. -The import counts statistics contained in the report give further information: +Lorsqu'elle est exécutée de manière synchrone, un rapport d'importation est renvoyé directement. +Le code de statut HTTP est toujours `OK`, le `status` dans le message indique si toutes les lignes ont été importées avec succès. +Les statistiques sur le nombre de lignes importées, contenues dans le rapport donnent des informations supplémentaires : -* `imported`: number of organisation units that were successfully updated with a geometry that did not have one before for the updated property -* `updated`: number of organisation units that were successfully updated with a geometry that did have value for the updated property already -* `ignored`: number of organisation units that failed to update -* `deleted`: number of organisation units that where successfully update with a _empty_ geometry +* `imported` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui n'en avait pas pour la propriété mise à jour. +* `updated` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie qui avait déjà une valeur pour la propriété mise à jour. +* `ignored` : nombre d'unités d'organisation qui n'ont pas été mises à jour +* `deleted` : nombre d'unités d'organisation qui ont été mises à jour avec succès avec une géométrie _vide_. -When the import is run asynchronous the request returns immediately with status -`OK` and job configuration response that contains a relative reference to -the task endpoint that allows to track the status of the asynchronous import. -For example: +Lorsque l'importation est exécutée de manière asynchrone, la requête renvoie immédiatement le statut `OK` de même que la réponse de configuration de la tâche qui contient une référence relative au point d'extrémité de la tâche qui permet de suivre le statut de l'importation asynchrone. Voici un exemple : /api/system/tasks/GEOJSON_IMPORT/{job-id} -The summary that is returned directly for synchronous execution is available at +Le récapitulatif renvoyé directement pour une exécution synchrone est disponible à l'adresse suivante : /api/system/taskSummaries/GEOJSON_IMPORT/{job-id} -once the import is finished. +dès que l'importation est terminée. -### GeoJSON Bulk Data Deletion { #webapi_geojson_bulk_deletion } -To clear or unset the `geometry` data for all organisation units use: +### Suppression de données en masse avec GeoJSON { #webapi_geojson_bulk_deletion } +Pour effacer ou désactiver les données `geometry` pour toutes les unités d'organisation, utilisez : DELETE /api/organisationUnits/geometry -To clear or unset the geometry data for a specific `GEOJSON` attribute for -all organisation units use: +Pour effacer ou désactiver les données géométriques d'un attribut `GEOJSON` spécifique pour toutes les unités d'organisation : DELETE /api/organisationUnits/geometry?attributeId={attr-id} -Clearing is always synchronous and returns a similar report as the bulk import. -It does not support any other parameters. No `dry-run` can be performed. -Bulk clearing requires the `F_PERFORM_MAINTENANCE` authority. +Le nettoyage se fait toujours de façon synchrone et renvoie un rapport similaire à celui de l'importation en masse. +Il ne prend en charge aucun autre paramètre. Aucun `essai` ne peut être effectué. +Pour effectuer un nettoyage en masse, l'utilisateur doit disposer de l'autorité `F_PERFORM_MAINTENANCE`. -### GeoJSON Single Data Import { #webapi_geojson_single_import } -The single import allows to update the geometry of a single organisation unit. +### Importation de données à titre individuel avec GeoJSON { #webapi_geojson_single_import } +L'importation unique permet de mettre à jour la géométrie d'une seule unité d'organisation. POST /api/organisationUnits/{id}/geometry -The post body only contains the GeoJSON `geometry` value, for example: +Le corps du message ne contient que la valeur GeoJSON `geometry`, par exemple : ```json { "type": "Polygon", "coordinates": [...] } ``` -Single import only supports `attributeId` and `dryRun` parameters. +L'importation unique ne prend en charge que les paramètres `attributeId` et `dryRun`. -### GeoJSON Single Data Deletion { #webapi_geojson_single_deletion } +### Suppression de données uniques avec GeoJSON { #webapi_geojson_single_deletion } To clear the `geometry` GeoJSON data of an individual organisation unit use: DELETE /api/organisationUnits/{id}/geometry @@ -1207,7 +1188,7 @@ To get JSON schema for a specific class: GET /api/schemas/dataElement.json -## Icons { #webapi_icons } +## Icônes { #webapi_icons } DHIS2 includes a collection of icons that can be used to give visual context to metadata. There are two different kind of icons: @@ -1425,7 +1406,7 @@ Table: Style properties | Propriété | Description ; | Type | |---|---|---| -| color | A color, represented by a hexadecimal. | String (#000000) | +| color | A color, represented by a hexadecimal. | Chaîne (#000000) | | icon | An icon, represented by a icon-name. | Chaîne | Currently, there is no official list or support for icon-libraries, so @@ -1661,7 +1642,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -1757,9 +1738,9 @@ Sample error response looks like: } ``` -## Indicator Types { #webapi_indicator_types} +## Types d'indicateurs { #webapi_indicator_types} -### Merge indicator types { #webapi_indicator_type_merge} +### Fusionner les types d'indicateurs { #webapi_indicator_type_merge} The indicator type merge endpoint allows you to merge a number of indicator types into a target indicator type. @@ -1788,7 +1769,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -1986,7 +1967,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Split payload fields @@ -2045,7 +2026,7 @@ The payload in JSON format looks like the following: } ``` -The JSON properties are described in the following table. +Les propriétés JSON sont décrites dans le tableau suivant. Table: Merge payload fields @@ -2384,7 +2365,7 @@ To retrieve description of programRule condition you can use POST and provide co /api/programRules/condition/description? -## Forms { #webapi_forms } +## Formulaires { #webapi_forms } To retrieve information about a form (which corresponds to a data set and its sections) you can interact with the `form` resource. The form @@ -2954,7 +2935,7 @@ Certain types of files are blocked from being uploaded for security reasons. The following content types are blocked. -| Content type | Content type | +| Type de contenu | Type de contenu | | ------------------------------------- | ---- | | text/html | application/x-ms-dos-executable | | text/css | application/vnd.microsoft.portable-executable | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__new-tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__new-tracker-md index 75911af7b..3bb425d79 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__new-tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__new-tracker-md @@ -443,7 +443,7 @@ Actuellement, le point d'extrémité de l'importation Tracker prend en charge le | categoryOptionIdScheme (Schéma de l'identifiant d'option de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être ignoré, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `IGNORER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md index 7526bc6f4..8a9a8eecf 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Profil d'unité d'organisation { #org_unit_profile } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index 6b5037d6a..30e7759ff 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index 00f71f43a..8e1f0eed3 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/route.md" revision_date: '2024-05-15' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Route { #route } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index 3d30f83e7..5eec27ffc 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Programmation { #webapi_scheduling } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index a4157afcd..130ddae4a 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Paramètres et configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index e0a55cd9a..302da6777 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Partage { #sharing } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index 7c733faca..635f3d21c 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # SMS { #sms } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index f4407b601..0fa905bfa 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Synchronization { #webapi_synchronization } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md index 533d92045..6f465e714 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Tracker { #webapi_tracker } @@ -18,20 +18,21 @@ tags: > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## Objets Tracker { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -134,7 +135,6 @@ point out any exceptional cases between these two. | programme | Uniquement pour lire les données. Il s'agit du type de programme de l'inscription qui possède l'événement. | Non | Oui | Chaîne : Uid | ABCDEF12345 | | Entité suivie | Uniquement pour lire les données. Il s'agit de l'entité suivie propriétaire de l'événement. Ceci ***ne s'applique pas au `PROGRAMME D'ÉVÉNEMENT`*** | Non | Non | Chaîne : Uid | ABCDEF12345 | | statut | Statut de l'évènement. Il est ACTIF au cas où n'est pas fourni. | Non | Non | Énumération | ACTIF, EFFECTUÉ, VISITÉ, HORAIRE, EN RETARD, SAUTÉ | -| Statut de l'inscription | Uniquement pour lire les données. Il s'agit du statut de l'inscription propriétaire de l'événement. Ceci ***ne s'applique pas au `PROGRAMME D'ÉVÉNEMENT`*** | Non | Non | Énumération | ACTIF, EFFECTUÉ, ANNULÉ | | orgUnit (Unité d'organisation) | Il s'agit de l'unité d'organisation dans laquelle l'utilisateur a enregistré l'événement. | Oui | Non | Chaîne : Uid | ABCDEF12345 | | créé à | Only for reading data. Timestamp when the user created the event. Set on the server. | Non | Oui | Date : ISO 8601 | AAAA-MM-JJThh:mm:ss | | crééAtClient (Création au niveau du client) | Date et heure à laquelle l'utilisateur a créé l'évènement au niveau du client | Non | Non | Date : ISO 8601 | AAAA-MM-JJThh:mm:ss | @@ -194,9 +194,11 @@ of the relationship must conform to are based on the `Relationship Type` of the ### Les attributs { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Propriété | Description ; | Obligatoire | Immuable | Type | Exemple | |---|---|---|---|---|---| @@ -211,18 +213,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Valeurs de données { #data-values } -Alors que les `Attributs` décrivent une `entité suivie` ou une `inscription`, les `valeurs de données` décrivent un `évènement`. La différence majeure est que les `attributs ` ne peuvent avoir qu'une seule valeur pour une `entité suivie` donnée. En revanche, les `valeurs de données` peuvent avoir plusieurs valeurs différentes selon les `événements` - même si les `événements` appartiennent tous à la même `inscription` ou à la même `entité suivie`. +While attributes describe a tracked entity, data values describe an event. | Propriété | Description ; | Obligatoire | Immuable | Type | Exemple | |---|---|---|---|---|---| @@ -237,31 +241,31 @@ Alors que les `Attributs` décrivent une `entité suivie` ou une `inscription`, > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### Remarques { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -272,10 +276,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -317,92 +321,7 @@ and/or enrollment payload. Below is a sample payload. > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Charge utile pour les opérations CRUD sur les listes de tâches des étapes de programme{ #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Tableau : Charge utile - -| Valeurs de charge utile | Description ; | Exemple | -|---|---|---| -| nom | Nom de la liste de tâches. Obligatoire. || -| Description | Il s'agit d'une description de la liste de tâches. || -| programme | Objet contenant l'identifiant du programme. Obligatoire. | {"id" : "uy2gU8kTjF"} | -| Étape du programme | Objet contenant l'identifiant de l'étape de programme. Obligatoire. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria (Critères de requête de l'étape de programme) | Un objet représentant diverses valeurs de filtrage possibles. Voir le tableau de définition des *Critères de requête de l'étape de programme* ci-dessous. - -Tableau : Critères de requête de l'étape de programme - -| Valeurs des critères | Description ; | Exemple | -|---|---|---| -| statut | Il s'agit du statut de l'événement. Les valeurs possibles sont ACTIF, EFFECTUÉ, VISITÉ, PROGRAMMÉ, EN RETARD, SAUTÉ et VISITÉ. | "statut": "VISITÉ" | -| Évènement créé à | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date de création de l'événement. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt (programmé à) | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date de programmation de l'événement. | {"type":"RELATIVE","period":"TODAY"} | -| Statut de l'inscription | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "Statut de l'inscription": "EFFECTUÉ" | -| Suivi | Indique s'il faut filtrer ou non les inscriptions marquées pour le suivi | "suivi": vrai | -| inscrit à | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date d'inscription de l'événement. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| Inscription effectué à | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit (Unité d'organisation) | Un UID d'unité d'organisation valide | "orgUnit": "Rp268JB6Ne4" | -| ouMode (Mode d'unité d'organisation) | Un mode de sélection d'unités d'organisation valide | "ouMode": "SELECTED" | -| Mode d'utilisateur assigné | Il s'agit d'un mode de sélection d'utilisateur valide pour les événements. Les valeurs possibles sont ACTUEL, FOURNI, AUCUN, TOUT et TOUS. S’il est FOURNI (ou nul), il sera attendu dans la charge utile des utilisateurs assignés non vides. | "Mode d'utilisateur assigné" : "FOURNI" | -| assignedUser (Utilisateur assigné) | Une liste des utilisateurs assignés aux événements. À utiliser avec le mode d'utilisateur assigné, fourni ci-dessus. | "Utilisateurs assignés":["DXyJmlo9rge"] | -| Ordre | Liste des champs et de leurs directions en valeurs séparées par des virgules, les résultats seront triés en fonction de cette liste. Un seul élément dans l'ordre est de la forme « orderDimension:direction ». | "ordre": "w75KJ2mc4zz:asc" | -| Ordre d'affichage des colonnes | Ordre de sortie des colonnes | "Ordre de sortie des colonnes":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| Filtres de données | Une liste d'éléments contenant les filtres à utiliser lors de requêtes d'événements | "Filtres de données":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| Filtres des valeurs d'attributs | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "Filtres de valeurs d'attribut":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -Ci-dessous, un exemple de charge : - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Importation Tracker (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -411,9 +330,9 @@ to import i.e. create, update and delete * **Inscriptions** * **Événements** * **Relations** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Paramètres de requête { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -422,16 +341,16 @@ The tracker importer supports the following parameters: | async | Indique si l’importation doit avoir lieu de manière asynchrone ou synchrone. | Booléen | `VRAI`, `FAUX` | | Mode de rapport | Uniquement lors d'une importation synchrone. Voir le "Récapitulatif de l'importation" pour plus d’informations. | Énumération | `COMPLET`, `ERREURS`, `AVERTISSEMENTS` | | Mode d'importation | Can either be `VALIDATE` which will report errors in the payload without making changes to the database or `COMMIT` (default) which will validate the payload and make changes to the database. | Énumération | `VALIDER`, `COMMITER` | -| idScheme (schéma d'identifiants) | Indique le 'schéma d'identification' global à utiliser pour les références de métadonnées lors de l'importation. La valeur par défaut est UID. Elle peut être remplacée pour des métadonnées spécifiques (voir la liste ci-dessous). | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | +| idScheme (schéma d'identification) | Indique le 'schéma d'identification' global à utiliser pour les références de métadonnées lors de l'importation. La valeur par défaut est UID. Elle peut être remplacée pour des métadonnées spécifiques (voir la liste ci-dessous). | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | dataElementIdScheme (Schéma d'identification de l'élément de données) | Indique le schéma d'identification à utiliser pour les éléments de données lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | -| orgUnitIdScheme (Schéma de l'identifiant de l'unité d'organisation) | Indique le schéma d'identification à utiliser pour les unités d'organisation lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | +| orgUnitIdScheme (Schéma d'identification de l'unité d'organisation) | Indique le schéma d'identification à utiliser pour les unités d'organisation lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | programIdScheme (Schéma d'identification des programmes) | Indique le schéma d'identification à utiliser pour les programmes lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | programmeStageIdScheme (Schéma d'identification des étapes de programme) | Indique le schéma d'identification à utiliser pour les étapes de programme lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | -| categoryOptionComboIdScheme (Schéma d'identification des combinaisons d'options de catégorie) | Indique le schéma d'identification à utiliser pour les combinaisons d'options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | +| categoryOptionComboIdScheme (Schéma d'identification de la combinaison d'options de catégorie) | Indique le schéma d'identification à utiliser pour les combinaisons d'options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | categoryOptionIdScheme (Schéma d'identification des options de catégorie) | Indique le schéma d'identification à utiliser pour les options de catégorie lors de l'importation. | Énumération | `UID`, `CODE`, `NOM`, `ATTRIBUT` | | importStrategy (stratégie d'importation) | Indique l'effet que l'importation doit avoir. Les différentes possibilités sont `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER`. Respectivement, elles permettent d'importer de nouvelles données, d'importer des modifications à des données existantes, d'importer de nouvelles données ou des mises à jour à des données existantes et, enfin, de supprimer des données. | Énumération | `CRÉER`, `METTRE À JOUR`, `CRÉER_ET_METTRE À JOUR` et `SUPPRIMER` | | Mode atomique | Indique comment l'importation répond aux erreurs de validation. S'il est défini sur `TOUS`, toutes les données importées doivent être valides avant que chaque donnée ne soit commitée. Par contre s'il est défini sur `OBJET`, seules les données commitées doivent être valides, tandis que d'autres données peuvent être invalides. | Énumération | `TOUS`, `OBJET` | -| flushMode | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | +| flushMode (mode de vidage) | Indique la fréquence de vidange. Il s'agit de la fréquence à laquelle les données sont introduites dans la base de données au cours de l'importation. Il est principalement utilisé à des fins de débogage et ne doit pas être modifié dans un environnement de production. | Énumération | `AUTO`, `OBJET` | | Mode de validation | Indique l'intégralité de l'étape de validation. Il peut être sauté, configuré pour échouer rapidement (retour à la première erreur) ou complet (par défaut), ce qui renverra toutes les erreurs trouvées. | Énumération | `COMPLET`, `ÉCHOUER_RAPIDEMENT`, `SAUTER` | | Validation du modèle de saut | S'il est défini sur 'vrai', la validation du modèle des attributs générés sera sautée. | Booléen | `VRAI`, `FAUX` | | Sauter les effets secondaires | Si défini sur 'vrai', les effets secondaires de l'importation seront ignorés. | Booléen | `VRAI`, `FAUX` | @@ -446,7 +365,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -846,7 +765,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Récapitulatif des importations { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -1292,7 +1211,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Codes d'erreur { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -1422,7 +1341,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | N/A | Message d'erreur non défini. | -### Validation { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -1432,7 +1351,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -1457,8 +1376,8 @@ on which property has a wrong format. Some examples of properties that are valid #### Accès des utilisateurs { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -1511,7 +1430,7 @@ Some examples of configurable validations: Ces configurations apporteront des modifications supplémentaires à la manière dont la validation est effectuée lors de l'importation. -### Règles de programme { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -1567,7 +1486,7 @@ information about side effects can be found in the following section. > > Les règles de programme peuvent être ignorées lors de l'importation à l'aide du paramètre `skipProgramRules` (ignorer les règles de programme). -### Effets secondaires { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -1589,7 +1508,7 @@ Voici donc les effets secondaires actuellement pris en charge : > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assigner un utilisateur à des événements { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -1623,7 +1542,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Exportation Tracker { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Les points d'extrémité de l'exportation Tracker vous permettent de récupérer les objets précédemment importés, à savoir : @@ -1675,9 +1594,9 @@ Le point d'extrémité suivant prend en charge les paramètres normalisés pour The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Paramètre de requête pour filtrer les réponses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } Tous les points d'extrémité d'exportation acceptent un paramètre `fields` (champs) qui contrôle les champs qui seront renvoyés dans la réponse JSON. Le paramètre `fields` accepte une liste de noms de champs ou de modèles séparés par des virgules. Quelques filtres `fields` possibles sont présentés ci-dessous. Consultez la section [filtre de champ de métadonnées (#webapi_metadata_field_filter)] pour obtenir un guide plus complet sur l'utilisation du paramètre `fields`. @@ -1754,8 +1673,8 @@ Le point d'extrémité renvoie une liste d'entités suivies qui correspondent au |`filtre`|`Chaîne`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`Chaîne`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`Chaîne`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| |`programme`|`Chaîne`|`UID` de programme|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`Chaîne`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage` (étape de programme)|`Chaîne`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -1859,7 +1778,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -2121,8 +2040,8 @@ Renvoie une liste d'événements en fonction des filtres. |---|---|---|---| |`orgUnits`|`Chaîne`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`Chaîne`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| |`programme`|`Chaîne`|`uid`| Identifiant de programme| |`programStatus` **deprecated for removal in version 43 use `status`**|`Chaîne`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`statut`|`Chaîne`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -2326,8 +2245,8 @@ Renvoie une liste d'événements en fonction des filtres fournis. |`followUp` (suivi)|`booléen`| `vrai`, `faux` | Détermine si l'événement est pris en compte pour un suivi dans le programme. La valeur par défaut est `vrai`| |`trackedEntity` (entité suivie)|`Chaîne`|`uid`|Identifier of tracked entity| |`orgUnit` (unité d'organisation)|`Chaîne`|`uid`|Identifiant de l'unité d'organisation| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`Chaîne`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|Le mode de sélection des unités d'organisation peut l'être. La valeur par défaut est `SÉLECTIONNÉ`, qui fait uniquement référence aux unités d'organisation sélectionnées.| |`statut`|`Chaîne`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Statut de l'événement| |`occurredAfter` (survenu après)|`DateTime` (date et heure)|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filtre pour les événements survenus après cette date.| |`occurredBefore` (survenu avant)|`DateTime` (date et heure)| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filtre pour les événements survenus jusqu'à cette date.| @@ -2622,13 +2541,13 @@ Les règles suivantes s'appliquent aux paramètres de requête. } ``` -## Contrôle de l'accès au Tracker { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Partage de métadonnées { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -2674,7 +2593,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -2743,13 +2662,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Propriété du programme Tracker { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -2761,7 +2680,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### Annulation de la propriété du Tracker : Briser la glace { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -2774,7 +2693,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### Transfert de la propriété du Tracker { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -2784,7 +2703,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Niveau d'accès { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -2814,7 +2733,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -2830,3 +2749,119 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } + +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. + +### Program stage working lists { #program-stage-working-lists } + +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. + + /api/programStageWorkingLists + +#### Payload { #payload } + +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: + +Tableau : Charge utile + +| Valeurs de charge utile | Description ; | Exemple | +|---|---|---| +| nom | Nom de la liste de tâches. Obligatoire. || +| Description | Il s'agit d'une description de la liste de tâches. || +| programme | Objet contenant l'identifiant du programme. Obligatoire. | {"id" : "uy2gU8kTjF"} | +| Étape du programme | Objet contenant l'identifiant de l'étape de programme. Obligatoire. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria (Critères de requête de l'étape de programme) | Un objet représentant diverses valeurs de filtrage possibles. Voir le tableau de définition des *Critères de requête de l'étape de programme* ci-dessous. + +Tableau : Critères de requête de l'étape de programme + +| Valeurs des critères | Description ; | Exemple | +|---|---|---| +| eventStatus (statut d'événement) | Il s'agit du statut de l'événement. Les valeurs possibles sont ACTIF, EFFECTUÉ, VISITÉ, PROGRAMMÉ, EN RETARD, SAUTÉ et VISITÉ. | "statut": "VISITÉ" | +| Évènement créé à | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date de création de l'événement. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date de programmation de l'événement. | {"type":"RELATIVE","period":"TODAY"} | +| Statut de l'inscription | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "Statut de l'inscription": "EFFECTUÉ" | +| Suivi | Indique s'il faut filtrer ou non les inscriptions marquées pour le suivi | "suivi": vrai | +| inscrit à | L'objet "Période de filtrage des dates" effectue le filtrage sur la base de la date d'inscription de l'événement. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| Inscription effectué à | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit (Unité d'organisation) | Un UID d'unité d'organisation valide | "orgUnit": "Rp268JB6Ne4" | +| ouMode (Mode d'unité d'organisation) | Un mode de sélection d'unités d'organisation valide | "ouMode": "SELECTED" | +| Mode d'utilisateur assigné | Il s'agit d'un mode de sélection d'utilisateur valide pour les événements. Les valeurs possibles sont ACTUEL, FOURNI, AUCUN, TOUT et TOUS. S’il est FOURNI (ou nul), il sera attendu dans la charge utile des utilisateurs assignés non vides. | "Mode d'utilisateur assigné" : "FOURNI" | +| assignedUser (Utilisateur assigné) | Une liste des utilisateurs assignés aux événements. À utiliser avec le mode d'utilisateur assigné, fourni ci-dessus. | "Utilisateurs assignés":["DXyJmlo9rge"] | +| Ordre | Liste des champs et de leurs directions en valeurs séparées par des virgules, les résultats seront triés en fonction de cette liste. Un seul élément dans l'ordre est de la forme « orderDimension:direction ». | "ordre": "w75KJ2mc4zz:asc" | +| Ordre d'affichage des colonnes | Ordre de sortie des colonnes | "Ordre de sortie des colonnes":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| Filtres de données | Une liste d'éléments contenant les filtres à utiliser lors de requêtes d'événements | "Filtres de données":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| Filtres des valeurs d'attributs | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "Filtres de valeurs d'attribut":[{"attribute": "ruQQnf6rswq","eq": "15"}] | + +Ci-dessous, un exemple de charge : + +```json +{ + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" + }, + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" + }, + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ + { + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } +} +``` + diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index 72c529c98..9e5d19927 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/users.md" revision_date: '2024-03-08' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Utilisateurs { #users } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index fd25cfe4e..2bfc1d551 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Visualisations { #visualizations } @@ -334,27 +334,27 @@ Tableau : Attributs de visualisation | legendSet (ensemble de légende) | Un objet représentant les définitions de la légende. | | legendDisplayStyle (style d'affichage de légende) | Le style d'affichage de la légende. Il peut être : FILL ( remplit) ou TEXT ( texte). | | legendDisplayStrategy (stratégie d'affichage de la légende) | Le style d'affichage de la légende. Il peut être : FIXE ou BY_DATA_ITEM (par élément de données). | -| Type d'agrégation | Determines how the values in the pivot table are aggregated. Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| regression | Indicates whether the Visualization contains regression columns. More likely to be applicable to Pivot/Report. Boolean value. | -| externalAccess | Indicates whether the Visualization is available as external read-only. Only applies when no user is logged in. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| Type d'agrégation | Détermine la manière dont les valeurs du tableau croisé dynamique sont agrégées. Options valides : SUM (somme), AVERAGE (moyenne), AVERAGE_SUM_ORG_UNIT ( somme moyenne des unités d'organisation), LAST (dernier), LAST_AVERAGE_ORG_UNIT (dernière moyenne des unités d'organisation), FIRST (premier), FIRST_AVERAGE_ORG_UNIT (première moyenne des unités d'organisation), COUNT (nombre), STDDEV (écart type), VARIANCE (écart), MIN (minimum), MAX (maximum), NONE (aucun), CUSTOM (personnalisé) ou DEFAULT (par défaut). | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| régression | Indique si la visualisation contient des colonnes de régression. Plus susceptible de s'appliquer aux rapports/croisés dynamiques. Valeur booléenne. | +| externalAccess (accès externe) | Indique si la visualisation est disponible en lecture seule externe. Ne s'applique que si aucun utilisateur n'est connecté. Valeur booléenne. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit . Boolean value. | | reportingParams | Object used to define boolean attributes related to reporting. | | rowTotals | Displays (or not) the row totals. Boolean value. | @@ -884,25 +884,25 @@ Tableau : Attributs de la visualisation d'événements | périodes relatives | Un objet représentant les périodes relatives utilisées dans la requête analytique. | | légende | An object representing the definitions for the legend and legend set, display style (FILL or TEXT) and display strategy (FIXED or BY_DATA_ITEM). | | Type d'agrégation | Determines how the values are aggregated (if applicable). Valid options: SUM, AVERAGE, AVERAGE_SUM_ORG_UNIT, LAST, LAST_AVERAGE_ORG_UNIT, FIRST, FIRST_AVERAGE_ORG_UNIT, COUNT, STDDEV, VARIANCE, MIN, MAX, NONE, CUSTOM or DEFAULT. | -| regressionType | A valid regression type: NONE, LINEAR, POLYNOMIAL or LOESS. | -| targetLineValue | The chart target line. Accepts a Double type. | -| targetLineLabel | The chart target line label. | -| rangeAxisLabel | The chart vertical axis (y) label/title. | -| domainAxisLabel | The chart horizontal axis (x) label/title. | -| rangeAxisMaxValue | The chart axis maximum value. Values outside of the range will not be displayed. | -| rangeAxisMinValue | The chart axis minimum value. Values outside of the range will not be displayed. | -| rangeAxisSteps | The number of axis steps between the minimum and maximum values. | -| rangeAxisDecimals | The number of decimals for the axes values. | -| baseLineValue | A chart baseline value. | -| baseLineLabel | A chart baseline label. | -| digitGroupSeparator | The digit group separator. Valid values: COMMA, SPACE or NONE. | -| topLimit | The top limit set for the Pivot table. | -| Critères de mesure | Describes the criteria applied to this measure. | -| percentStackedValues | Uses stacked values or not. More likely to be applied for graphics/charts. Boolean value. | -| noSpaceBetweenColumns | Show/hide space between columns. Boolean value. | -| externalAccess | Indicates whether the EventVisualization is available as external read-only. Boolean value. | -| userOrganisationUnit | Indicates if the user has an organisation unit. Boolean value. | -| userOrganisationUnitChildren | Indicates if the user has a children organisation unit. Boolean value. | +| regressionType (type de régression) | Un type de régression valide : NONE (aucun), LINEAR (linéaire), POLYNOMIAL (polynomial) ou LOESS. | +| targetLineValue (valeur de la ligne cible) | La ligne cible du graphique. Accepte un type Double. | +| targetLineLabel (étiquette de la ligne cible) | L'étiquette de la ligne cible du graphique. | +| rangeAxisLabel (Étiquette de l'axe de la plage ) | L'étiquette/titre de l'axe vertical (y) du graphique. | +| domainAxisLabel (étiquette de l'axe du domaine) | L'étiquette/titre de l'axe horizontal (x) du graphique. | +| rangeAxisMaxValue (Plage de l'axe de la valeur maximale) | La valeur maximale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisMinValue (Plage de l'axe de la Valeur minimale) | La valeur minimale de l'axe du graphique. Les valeurs en dehors de la plage ne seront pas affichées. | +| rangeAxisSteps (Étapes de l'axe de la plage) | Le nombre de pas d'axe entre les valeurs minimale et maximale. | +| rangeAxisDecimals (Décimales de l'axe de la plage) | Le nombre de décimales pour les valeurs des axes. | +| baseLineValue (Valeur de la ligne de base) | Une valeur de référence du graphique. | +| baseLineLabel (étiquette de la ligne de base) | Une étiquette de ligne de base du graphique. | +| digitGroupSeparator (Séparateur de groupes de chiffres) | Séparateur de groupes de chiffres. Valeurs valides : VIRGULE, ESPACE ou AUCUN. | +| topLimit (Limite maximale) | La limite maximale fixée pour le tableau croisé dynamique. | +| Critères de mesure | Décrit les critères appliqués à cette mesure. | +| percentStackedValues (Pourcentage des valeurs empilées) | Utilise ou non des valeurs empilées. Plus susceptible d'être utilisé pour les graphiques. Valeur booléenne. | +| noSpaceBetweenColumns (Aucun espace entre les colonnes) | Afficher/masquer l'espace entre les colonnes. Valeur booléenne. | +| externalAccess (accès externe) | Indicates whether the EventVisualization is available as external read-only. Boolean value. | +| userOrganisationUnit (Unité d'organisation de l'utilisateur) | Indique si l'utilisateur dispose d'une unité d'organisation. Valeur booléenne. | +| userOrganisationUnitChildren (Unité d'organisation subordonnées de l'utilisateur ) | Indique si l'utilisateur a des unités d'organisation subordonnées. Valeur booléenne. | | userOrganisationUnitGrandChildren | Indicates if the user has a grand children organisation unit. Boolean value. | | rowTotals | Displays (or not) the row totals. Boolean value. | | colTotals | Displays (or not) the columns totals. Boolean value. | diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md index 95e4291b1..a3ca934e2 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- DHIS version 2.39 - Gestion +- DHIS version 2.39 --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md index fdefe1537..b6401f816 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/installation.md" revision_date: '2024-02-16' tags: -- DHIS version 2.39 - Gestion +- DHIS version 2.39 --- # Installation { #installation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md index 4371754ea..0e435b97a 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/monitoring.md" revision_date: '2021-06-14' tags: -- DHIS version 2.39 - Gestion +- DHIS version 2.39 --- # Surveillance { #monitoring } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md index 62d9f22da..c17612f2d 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- DHIS version 2.39 - Gestion +- DHIS version 2.39 --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md index f0748ee75..021c0dd3f 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- DHIS version 2.39 - Gestion +- DHIS version 2.39 --- # Utilisation de passerelles pour l'établissement de rapports SMS { #sms_report_sending } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md index f6a03ba79..2ac0c6b69 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/audit.md" revision_date: '2022-10-23' tags: -- DHIS Version 2.40 - Gestion +- DHIS Version 2.40 --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md index 4e1b578be..1c8a6bf65 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- DHIS Version 2.40 - Gestion +- DHIS Version 2.40 --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md index 0508c1f32..7ddbe47fd 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- DHIS Version 2.40 - Gestion +- DHIS Version 2.40 --- # Installation { #installation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md index 954782779..710c0b58a 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- DHIS Version 2.40 - Gestion +- DHIS Version 2.40 --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index 4306607de..acf3d45a6 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/audit.md" revision_date: '2024-05-21' tags: -- Version Master de DHIS2 Central - Gestion +- Version Master de DHIS2 Central --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index 1af78c386..f16962fb0 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- Version Master de DHIS2 Central - Gestion +- Version Master de DHIS2 Central --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index 761fbdf3d..74bf1bff0 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- Version Master de DHIS2 Central - Gestion +- Version Master de DHIS2 Central --- # Installation { #installation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index 7474aaff3..94b249367 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/monitoring.md" revision_date: '2023-09-25' tags: -- Version Master de DHIS2 Central - Gestion +- Version Master de DHIS2 Central --- # Surveillance { #monitoring } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index 196359e1a..f5a134641 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- Version Master de DHIS2 Central - Gestion +- Version Master de DHIS2 Central --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index d0f479a84..3c3a534d4 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- Version Master de DHIS2 Central - Gestion +- Version Master de DHIS2 Central --- # Utilisation de passerelles pour l'établissement de rapports SMS { #sms_report_sending } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index bfe63d8f6..cc2bbbffe 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-browsing.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.0 +- Utilisation --- ## Parcourir l'application Action Tracker { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index 632b3e8d9..e94004900 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-introduction.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.0 +- Utilisation --- # Tableau de bord et Serveur de démo de l'application Linked Action Tracker { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index 7617b8757..9365d3b12 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-maintenance.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.0 +- Utilisation --- # Maintenance de l'application Action Tracker { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index f19818963..4a6b0f957 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-planning.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.0 +- Utilisation --- # Planification des actions dans l'application Action Tracker { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index 00b42d92a..2c5c31de8 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-tracking.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.0 +- Utilisation --- # Suivi des actions dans l'application Action Tracker { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index 54556e50c..40f7a3c9f 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-installation.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Installation de l'application BNA { #installing-the-bna-app } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index 69592b86b..8195b896d 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-maintenance.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Maintenance de l'application BNA { #bna-app-maintenance } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index 138c372a6..6082ffc86 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-analysis-and-interpretation.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Analyse et interprétation de la BNA { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index 533502807..27cd62794 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-architecture.md" revision_date: '2022-03-10' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Architecture de l'application BNA { #bna-app-architecture } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index 23a8005c2..b33264b14 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bottleneck-analysis-dashboard-and-demo-server.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Tableau de bord d'analyse des goulets d'étranglement et Serveur démo { #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index 2aee84524..84b8d4627 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/navigating-the-bna-app.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Configurations des interventions de l'application BNA { #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index abf2969cb..91f8dc118 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/visualization-operations.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Activités relatives à la visualisation { #visualization-operations } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index bde1cdc92..5c2d3bf2c 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/adopting-the-use-of-the-bna-app.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Promouvoir l'utilisation de l'application BNA { #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index 97a30862c..0b15c1cfb 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/capacity-building.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Renforcement des capacités { #capacity-building } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index ace3eff1e..587e21706 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/end-user-training.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Formations des utilisateurs finaux { #end-user-training } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index 9dd3e75f9..5cd209d40 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/guide-to-bna-app-implementation.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Guide de mise en œuvre de l'application BNA { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index c6da5b191..f1c97b049 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/integration-concepts-for-the-bna-app.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Concepts d'intégration de l'application BNA. { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index 0f0b72efe..d74ec50f2 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/opportunities-and-challenges.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Opportunités et Défis { #opportunities-and-challenges } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index 44344e37b..ec9a71306 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/planning-and-organising.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Planification et organisation { #planning-and-organising } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md index 06fe742d6..3cadcffa7 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/setting-up-a-new-bna-app.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Configuration d'une nouvelle application BNA { #setting-up-a-new-bna-app } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md index 42b63e336..28e7bdb9c 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-support-and-scale-up.md" revision_date: '2022-03-22' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Soutien et expansion de l'application BNA { #bna-app-support-and-scale-up } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md index fbcae9145..bdb3b9bd0 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/scale-up-and-sustainability.md" revision_date: '2021-09-09' tags: -- Utilisation - App version 1.2.2 +- Utilisation --- # Expansion et de durabilité { #scale-up-and-sustainability } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md index 86d2b4171..a0893fbb8 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/grant-access-to-user.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- ## 2.4 Grant Access to users { #24-grant-access-to-users } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md index 33a6001c4..50bd31b94 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/interventions-and-indicators-configuration.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- ## 2.2 Interventions and Indicators Configuration { #22-interventions-and-indicators-configuration } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md index c80f076e1..41c7e00f9 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/maps-configuration.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- ### 2.2.3 Map configuration { #223-map-configuration } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md index 56a0b7a12..ed79d8bca 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-app-installation.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- # Chapter 2. Bottleneck Analysis App Administrators’ guide { #chapter-2-bottleneck-analysis-app-administrators-guide } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md index 7ac8c212d..719d13d0e 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/common/about-this-guide-bna1.4.0.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- # À propos de ce guide { #about_this_guide_ } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md index 589945b05..123e5d927 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/introduction-to-bna.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- # Chapter 1. Bottleneck Analysis App { #chapter-1-bottleneck-analysis-app } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md index 5f24634ea..e9efc8584 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-analysis-and-interpretation.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- ## 3.2 BNA Analysis and Interpretation { #32-bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md index 5409827ef..6f7624d08 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-layout.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- # Chapter 3. Bottleneck Analysis App User guide { #chapter-3-bottleneck-analysis-app-user-guide } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md index b8c087751..7233e5756 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/data-analystics.md" revision_date: '2022-12-20' tags: -- Utilisation - Version 1.4.0 de l'application +- Utilisation --- ## 2.6 Standard data analytics { #26-standard-data-analytics } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md index b6efe2e82..3365024a9 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/metadata-package-development/blob/master/metadata/AEFI/immunisation_analysis_app_user_manual.md" revision_date: '2021-03-18' tags: -- Utilisation - App version 1.0.3 +- Utilisation --- # User Manual for the DHIS2 Immunisation Analysis App { #user-manual-for-the-dhis2-immunisation-analysis-app } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md index 054abb6ac..44be27bc9 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/about-this-guide.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- # About this guide { #about-this-guide } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md index c1629c514..f5061bb2a 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-and-translating-scorecard.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- # Accessing and translating the Scorecard { #accessing-and-translating-the-scorecard } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md index f64103be3..606b51dcc 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-scorecard-app.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- # Login DHIS2 system { #login-dhis2-system } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md index ebcd597c8..7c3ac3474 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/creating-scorecard.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- ## Creating the Scorecard { #creating-the-scorecard } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md index 644f19253..37c802a3b 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/introduction-to-scorecard.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- # Introduction to the Scorecard App { #introduction-to-the-scorecard-app } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md index 8398b40fd..8dec85450 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/saving-configurations.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- ## Saving configuration and load the scorecard { #saving-configuration-and-load-the-scorecard } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md index 501aa1415..6c26ed30e 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/scorecard-app-architecture.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- # Scorecard App architecture { #scorecard-app-architecture } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md index c77a248bd..f86998071 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/support-and-maintanace-options.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- # Scorecard App Built-in Support and Maintenance Options { #scorecard-app-built-in-support-and-maintenance-options } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md index aedc238ab..8163ce911 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/viewing-scorecard.md" revision_date: '2021-10-04' tags: -- Utilisation - App version 2.5.0 +- Utilisation --- # Viewing the Scorecard App Analysis outputs { #viewing-the-scorecard-app-analysis-outputs } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md index 55fc98626..c9bfa8dad 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-maintenance.md" revision_date: '2024-02-27' tags: -- Utilisation - App version 2.0 +- Utilisation --- If a Standalone action tracker application is taking too long to load, and you’re not on a slow network, make sure you have cleared your browser cache. diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md index d3b27b617..ebb31862c 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-architecture-and-installation.md" revision_date: '2024-02-22' tags: -- Utilisation - App version 2.0 +- Utilisation --- The Standalone Action Tracker Application is built on an architecture that eases user interactions by having a design concept that promotes the user to follow their intuition complemented with high performance that considers the lowest internet connection scenarios with descriptive notification messages if the user misses a step along the way. diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md index cad4d91b4..24c5292a8 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-browsing.md" revision_date: '2024-02-23' tags: -- Utilisation - App version 2.0 +- Utilisation --- The Standalone Action Tracker App can be found in the Apps menu. if the application has not yet been installed in your DHIS2 instance or the installation has issues, refer to the installation instructions (Section 3.5) of this documentation for further guidance, or contact the DHIS2 administrator for your instance. diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md index 52486a876..c231344f0 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-introduction.md" revision_date: '2024-02-22' tags: -- Utilisation - App version 2.0 +- Utilisation --- # Introduction to the Standalone Action Tracker App { #introduction-to-the-standalone-action-tracker-app } diff --git a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md index 793c725dc..4d7ce9bb5 100644 --- a/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md +++ b/projects/docs-full-site/fr/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-configuration.md" revision_date: '2024-02-27' tags: -- Utilisation - App version 2.0 +- Utilisation --- The Standalone Action Tracker App includes a module for administrators to configure key metadata for the normal user. The administration configurable options include:- diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 76a646ef8..b587a7bf5 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # A propos du serveur de démonstration, du cluster D2 et de la conception de la base de données { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 6973079df..9726e8f53 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # DHIS2 - Foire aux questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md index a77164a15..4bc01f95c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Glossaire du DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 3cdaf6ece..7f7be8f7f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Tutoriels sur le DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 4d76f57a3..c696b66fc 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Notes de mise à jour et de mise à niveau { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md index acd3e37d6..57ba07647 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/managing-dashboards.md" revision_date: '22/10/2021' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Gérer les tableaux de bord { #dashboard } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md index c63e990e0..ee0d1e37c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-visualizer.md" revision_date: '20/01/2022' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utiliser l'application Visualiseur de données { #data_visualizer } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md index 379581c70..23df7bf8f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utilisation de l'application Rapports d'événements { #event_reports_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md index aca1f3e7d..db2b64c8b 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utilisation de l'application Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md index 42f9bb959..8cce9762b 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md index cc219f8b1..9a4e0feb9 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-maps-app.md" revision_date: '2022-03-23' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utiliser l'application Maps { #using_maps } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md index 727ce5d79..1b1079dbe 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Fonctionnalité de Reporting dans l'application Rapports { #using_the_reports_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md index 25da6a892..c06ef821c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Aperçu de la validation des données { #data_approval_overview } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md index 34aa1be90..915c469da 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utilisation de l'application de saisie des données { #data_entry_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md index 16618b4e5..34dd6a462 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Contrôler la qualité des données { #control_data_quality } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index dabf7c199..dfded92cc 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-sharing-of-objects.md" revision_date: '07/10/2021' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # À propos du partage d'objets { #sharing } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md index 4cbe193e8..ff11e0fe6 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-the-gis-app.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Configurer l'application Maps { #gis_creating } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md index 3cb76640c..76986f800 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata.md" revision_date: '2022-10-02' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Configurer les métadonnées { #maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md index 369d4cdda..3757a1d29 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Configurer les programmes dans l'application Maintenance { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md index eb208f9a2..444e5a108 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Configurer la fonctionnalité de rapport { #setting_up_reporting } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md index 7cc65c47f..9d78753a4 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/system-settings.md" revision_date: '2022-04-27' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Paramètres du système { #settings } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md index 727ddbb6b..6a5d3f57f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Autorités des utilisateurs { #user_authorities } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 7b986a2ee..cd940fe96 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-03-10' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Gérer les utilisateurs, les rôles des utilisateurs et les groupes d'utilisateurs { #manage_user_role_group } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md index d77d8de03..37506949e 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/importexport-app.md" revision_date: '2022-02-23' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Application Import/Export { #import_export } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md index ab73780f4..9086780d3 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Configurer la synchronisation des métadonnées { #metadata_sync } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md index 575832a12..6b8327495 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Configuration des SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md index ac3cfd6c7..2a37f6795 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Administration des données { #data_admin } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md index 6d1f58d9d..8bea949d3 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Gestionnaire de base de données { #datastore_manager_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md index aeaf63bec..120803cf6 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- > **Caution** diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md index c8d58f40d..85f4a2577 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Mobile { #mobile } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md index 432f3625d..ed9b4660c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Programmation { #scheduling } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 824a0e8f8..79723ede8 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utilisation de l'application Saisie { #capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 721a78853..0bad2bc46 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utilisation de l'application Saisie d'événements { #event_capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 3f217ad47..2643e8a47 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utilisation de l'application Saisie Tracker { #tracker_capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 419766457..4d7f8843a 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # À propos des dimensions de donnée { #data_dimensions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index a1481c07d..9bfe2638e 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Dimensions supplémentaires des données { #additional_data_dimensions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index a53b848cf..adaa15dca 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Modèle de relation { #relationship_model } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 20839d7fc..86c3241c1 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Messagerie { #messages } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 2d469f359..e08c5bc57 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Jetons d'accès personnels { #personal_access_tokens } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index 7096932a7..60dc4a2f3 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-visualizer.md" revision_date: '20/01/2022' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Utiliser l'application Visualiseur de données { #data_visualizer } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index 3e503a8b8..3c675cb7a 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Utilisation de l'application Rapports d'événements { #event_reports_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index bbbe93c89..b8b14c079 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Utilisation de l'application Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index 3abf4e870..8fbf0c089 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index 5f7850006..65d57b84f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-maps-app.md" revision_date: '2022-09-13' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Utiliser l'application Maps { #using_maps } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index 2cf1f0b32..40b36440b 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Fonctionnalité de Reporting dans l'application Rapports { #using_the_reports_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index 31be1dfa7..08feba128 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Configurer les métadonnées { #maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index 4c43998ee..743846920 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Configurer les programmes dans l'application Maintenance { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index 9963d1e44..9126f480f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Autorités des utilisateurs { #user_authorities } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index 1a1f2c144..80ff37e6f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Application Import/Export { #import_export } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 1d06415e9..d8eeb2598 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Gestionnaire de base de données { #datastore_manager_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index 2bc1df332..9ff0bc383 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- > **Caution** diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index bcfa5291e..cbf7fd4e0 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Mobile { #mobile } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index f95b09891..a59d1345b 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Utilisation de l'application Saisie { #capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 2707d78c6..970971981 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Utilisation de l'application Saisie Tracker { #tracker_capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index b00353686..3b4bea627 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Messagerie { #messages } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md index 6da2fe283..42d88eb24 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Utiliser l'application Visualiseur de données { #data_visualizer } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md index bfe306a6e..37e0e783b 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md index 11d5835d2..e14394d16 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Utiliser l'application Maps { #using_maps } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md index da5f2af2d..b57187849 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata.md" revision_date: '2023-07-20' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Configurer les métadonnées { #maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md index aa47d36e7..a3371ca4e 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Configurer les programmes dans l'application Maintenance { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md index 0211ac75f..8b2c9a310 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Autorités des utilisateurs { #user_authorities } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md index e361cd841..0e0cff2e0 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Utilisation de l'application Data Exchange( Échange de données) { #data_exchange } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md index f9ec810ab..4204c7e3c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Application Import/Export { #import_export } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md index 543828688..abf6bf390 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- > **Caution** diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md index 8a91fc4ab..cbe48b0dc 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Mobile { #mobile } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 5210bc116..45cad0a43 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Utilisation de l'application Saisie { #capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index f13c4a11e..2e1091de8 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # A propos du serveur de démonstration, du cluster D2 et de la conception de la base de données { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 5269a4a82..0a3f3dd61 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # DHIS2 - Foire aux questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index a686be68d..babaa2b32 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Glossaire du DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 01e2e1d33..73a87ee49 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Tutoriels sur le DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 09cd63c88..befbfe0e5 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Notes de mise à jour et de mise à niveau { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index caa6aa72d..e7e6b2a8b 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utiliser l'application Visualiseur de données { #data_visualizer } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index a001bd647..ebc97d941 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utilisation de l'application Rapports d'événements { #event_reports_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 7f936dc28..7c82845be 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utilisation de l'application Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index d7047ecab..7f6d7f963 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index c89538eaf..2577f4fa5 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utiliser l'application Maps { #using_maps } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index edef5bef6..545067cda 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Fonctionnalité de Reporting dans l'application Rapports { #using_the_reports_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 72bd906ca..657bc2a7e 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # À propos du partage d'objets { #sharing } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 0ebb181bf..2545904e8 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configuration des cartes de DHIS2 { #gis_creating } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index 63a510266..f96c14c65 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configurer les métadonnées { #maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index f67de7a4c..4d6afb433 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configurer les programmes dans l'application Maintenance { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 872401aee..585729967 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configurer la fonctionnalité de rapport { #setting_up_reporting } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 4377d075b..6d08fc79d 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Paramètres du système { #settings } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index a49bf7671..2cab9b094 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Autorités des utilisateurs { #user_authorities } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index cec1b1d52..dabdcbbe9 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Gérer les utilisateurs, les rôles des utilisateurs et les groupes d'utilisateurs { #manage_user_role_group } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index fc851150b..42c8dd692 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utilisation de l'application Data Exchange( Échange de données) { #data_exchange } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 462cb4df9..4f2992a3e 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Application Import/Export { #import_export } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index a61a89869..5c697ad79 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configurer la synchronisation des métadonnées { #metadata_sync } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index 66f655258..ae1c54593 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Configuration des SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 00cb46229..e9d508c2c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Administration des données { #data_admin } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index 364be86cf..d0f4cf263 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Gestionnaire de base de données { #datastore_manager_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 48a4690be..b2b8848db 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- > **Caution** diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 26cd39814..b2f777997 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Mobile { #mobile } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index 141e42377..6ae88ca85 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Programmation { #scheduling } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 0a2069952..f8099f423 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utilisation de l'application Saisie { #capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 1b6f25326..894f0cace 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # À propos des dimensions de donnée { #data_dimensions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index c55a50f4f..d65d48201 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Dimensions supplémentaires de données { #additional_data_dimensions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index b2edcf5d3..1299d00b3 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Modèle de relation { #relationship_model } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 9424dcf60..c73a35d7e 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Messagerie { #messages } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index c7bdde342..b478ec45f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Jetons d'accès personnels { #personal_access_tokens } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index c20b5bbcd..0dea3d674 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # A propos du serveur de démonstration, du cluster D2 et de la conception de la base de données { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 0802448e5..8c643c06d 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # DHIS2 - Foire aux questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md index f47bba161..57569be5f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Glossaire du DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index ea1073aa4..22e80b6dd 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Tutoriels sur le DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 662e15216..74b51bbf5 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Notes de mise à jour et de mise à niveau { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index d44300ed5..acd5ed136 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utiliser l'application Visualiseur de données { #data_visualizer } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index cd4885964..adb554d22 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application Rapports d'événements { #event_reports_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index d4cd747c2..38b472b25 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index 0960e7975..5040a026f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index 2a28ae784..1ea68c894 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utiliser l'application Maps { #using_maps } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md index 37386e1d5..7488e4e16 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Fonctionnalité de Reporting dans l'application Rapports { #using_the_reports_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md index 7fb633a0d..b978aa76c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Aperçu de la validation des données { #data_approval_overview } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index 27a1bef4b..2e3203948 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application de saisie des données { #data_entry_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index 154ec4244..3b3eaed5c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Contrôler la qualité des données { #control_data_quality } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 336820052..1b8691edc 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # À propos du partage d'objets { #sharing } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index 1752ed471..ea1cf587b 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Configuration des cartes de DHIS2 { #gis_creating } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index 3c02bc59c..830ed03f8 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Configurer les métadonnées { #maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index 5f4a0b1b3..70a81b4b8 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Configurer les programmes dans l'application Maintenance { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md index 8fa498229..62ea8632d 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Configurer la fonctionnalité de rapport { #setting_up_reporting } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index b358318b2..c320df954 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Paramètres du système { #settings } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index c1c3971a5..dab33e635 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Autorités des utilisateurs { #user_authorities } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index caf4eb5d6..45dd32470 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Gérer les utilisateurs, les rôles des utilisateurs et les groupes d'utilisateurs { #manage_user_role_group } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index 18c1bbf83..d0404524a 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application Data Exchange( Échange de données) { #data_exchange } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index 5fde4b2ce..c43122074 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Application Import/Export { #import_export } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index 2508d150a..ac6d95f28 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata-synchronizing.md" revision_date: '2024-05-28' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Configurer la synchronisation des métadonnées { #metadata_sync } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md index 50b259685..b7d1e58fa 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Configuration des SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index e64367183..3853f7e6a 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Administration des données { #data_admin } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md index 909751324..b9cf9f914 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- > **Caution** diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md index 5942fa91b..ce7b844b1 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Mobile { #mobile } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 3556b427c..1289ee683 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Programmation { #scheduling } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 08cc0c287..49a5f53e1 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application Saisie { #capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 118154475..444f91414 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application Saisie d'événements { #event_capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 2c51bda8b..c798fa9fd 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application Saisie Tracker { #tracker_capture_app } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 01282c98f..cab2f422f 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # À propos des dimensions de donnée { #data_dimensions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index e6e42a4d4..7d32e976c 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Dimensions supplémentaires des données { #additional_data_dimensions } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 0da7d603f..a8bc414f9 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Modèle de relation { #relationship_model } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 45829427e..983983885 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Messagerie { #messages } diff --git a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 36868ff56..81e3823eb 100644 --- a/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Jetons d'accès personnels { #personal_access_tokens } diff --git a/projects/docs-full-site/pt/.cache_timestamp b/projects/docs-full-site/pt/.cache_timestamp index 9dab76ccd..4fdea3a41 100644 --- a/projects/docs-full-site/pt/.cache_timestamp +++ b/projects/docs-full-site/pt/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:23:51Z \ No newline at end of file +2024-06-04T21:23:56Z \ No newline at end of file diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 9e2ce0bef..8ea2af0b7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Usar - DHIS core version 2.38 +- Usar --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index d1ee1fac7..2b232671d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # DHIS2 Perguntas Freqüentes { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md index 71d856590..6b841d251 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Glossário DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 083e09b7f..6b0f5838d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Tutoriais DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 0ec3abd73..3e29253cc 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Notas de lançamento e atualização { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md index 62a306782..3022e5bae 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Gerir painéis { #dashboard } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md index f42e8c5b0..d3027bb8e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Usando o aplicativo Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md index ac17c226e..fde71e97b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Usando o aplicativo Relatórios de eventos { #event_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md index 6a10f1881..d6aa63a6b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Usando o aplicativo Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md index 19936b91f..9566e60e5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md index be22bc5bb..88a631762 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-maps-app.md" revision_date: '2022-03-23' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Usando o aplicativo Maps { #using_maps } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md index 8f41a1184..6da1e6719 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Funcionalidade de relatórios no aplicativo de relatórios { #using_the_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md index 6a9fdd21b..1ac5c24ab 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md index 889136bac..1fd7d3c61 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md index 27adf2d0b..b7397d743 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Usando o aplicativo de entrada de dados { #data_entry_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md index 914ced670..b87c525da 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Controle de qualidade de dados { #control_data_quality } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index e82d90288..952fa0394 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Sobre o compartilhamento de objetos { #sharing } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md index 39cb7a11c..9aded0638 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-the-gis-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Configure o aplicativo Maps { #gis_creating } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md index deb212cc2..390b67a85 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata.md" revision_date: '2022-10-02' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Configurar metadados { #maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md index e3c92cc19..cbf94d5c8 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Configure programas no aplicativo de manutenção { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md index e40cf0555..105ecd55e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Configure a funcionalidade de relatório { #setting_up_reporting } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md index e9b1c8570..5cd29590c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/system-settings.md" revision_date: '2022-04-27' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Configurações do sistema { #settings } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md index ff9e4edff..c4a83b1b4 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Autoridades do usuário { #user_authorities } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 9e4df0bc5..de53ed3d5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-03-10' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Gerenciar usuários, funções e grupos de usuários { #manage_user_role_group } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md index 414dcc79c..e1a17f198 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/importexport-app.md" revision_date: '2022-02-23' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Importar / Exportar aplicativo { #import_export } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md index 945e7ac75..f127d34b9 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Configure a sincronização de metadados { #metadata_sync } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md index b6af6748f..621ceab15 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md index cf2a6cef5..9fb512aed 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Administração de Dados { #data_admin } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md index f5644c61f..29f1a5c40 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md index 60bcad1b2..fef1f6fd5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Usar - DHIS core version 2.38 +- Usar --- > **Caution** diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md index e7c0232b6..107ac729f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Móvel { #mobile } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md index c6791b39b..527fb5e03 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Agendamento { #scheduling } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index b82b2fd1f..e3e07658f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Visualize estatísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 8e96d3e5d..930b55acf 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Usando o aplicativo Capture { #capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 05c4e0cb7..026974bcc 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Usando o aplicativo Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 1af9558f0..199e12fc2 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Usando o aplicativo Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 4cb2d6737..92e6c74aa 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Sobre dimensões de dados { #data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 95b1c2e9e..1e20414f9 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Dimensões de dados adicionais { #additional_data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 0d0d5318f..e0be9f64c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Modelo de relacionamento { #relationship_model } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md index c7dd60b3d..598a434a7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Mensagens { #messages } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 8b7e3f066..7fcd32e75 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 9c540985a..254926b9c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Usar - DHIS core version 2.38 +- Usar --- # Definir as preferências da conta do usuário { #user_account_preferences } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md index 3eb374813..4f3b3802a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Móvel { #mobile } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md index 110ddb76e..132a47e50 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Agendamento { #scheduling } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 802e6115e..3633786a4 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Visualize estatísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 753a4ee33..d7926eb5b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Usando o aplicativo Capture { #capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index b04842e66..cb4024030 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Usando o aplicativo Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index a7445870b..681117b3e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Usando o aplicativo Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 9a344c2ed..639d2e336 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Sobre dimensões de dados { #data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 5387f1757..162bdb0d0 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Dimensões de dados adicionais { #additional_data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 2af73f3c4..c8e43ec71 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Modelo de relacionamento { #relationship_model } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 088d15f45..36b331e03 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Mensagens { #messages } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 2879095c9..14ebf2eba 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 573b847cf..bbd3284d6 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Usar - DHIS core version 2.40 +- Usar --- # Definir as preferências da conta do usuário { #user_account_preferences } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 73dfc958b..40f1b3837 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 08c38084b..145dc521c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # DHIS2 Perguntas Freqüentes { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 1e0c6d6e7..827aca6f2 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Glossário DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index f271a1acf..4a17d9dba 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Tutoriais DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 092034558..d470f4b96 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Notas de lançamento e atualização { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index 7fcf4e7a1..b35613f98 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Gerir painéis { #dashboard } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 946e6194d..9e1896c71 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Uso do aplicativo Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index 4898d23b8..7b09e217f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Relatórios de eventos { #event_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 8e74f6050..53b5c69de 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index 974b86717..8825c31a5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index 0b9515ba3..c39f31c48 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Maps { #using_maps } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index 6748a73c9..c185be12e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Funcionalidade de relatórios no aplicativo de relatórios { #using_the_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index ac1c455fd..5775cb022 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index 6dbbfe0d0..eb2d75ad6 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index 77e97ab75..83cee1c9a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index fe366c51c..f1ce88e54 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo de entrada de dados { #data_entry_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index 43ad5d569..ff581854c 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Controle de qualidade de dados { #control_data_quality } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 22e9c7690..c108d4fea 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Sobre o compartilhamento de objetos { #sharing } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index e0b08b40f..b6d35aebe 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index d091c92b8..a912ca8f3 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configurar metadados { #maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 5211f3cbb..50b7b6e33 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configure programas no aplicativo de manutenção { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index f934d6270..341138133 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configure a funcionalidade de relatório { #setting_up_reporting } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 938205165..ee9d519ff 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configurações do sistema { #settings } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index d41eef82f..2bc79f3a3 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Autoridades do usuário { #user_authorities } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 4b20626af..bec4cf48f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Gerenciar usuários, funções e grupos de usuários { #manage_user_role_group } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index dff53f5a4..69db13e31 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 45dbb0a87..183aa6462 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Importar / Exportar aplicativo { #import_export } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index 86798d433..d0568ec08 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configure a sincronização de metadados { #metadata_sync } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index 51a17482e..cfd884364 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index aa5558c95..1f0b752fa 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Administração de Dados { #data_admin } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index 5c032bac7..c0e69a06f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index e91defd33..600752d3f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Usar - DHIS core version 2.41 +- Usar --- > **Caution** diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 39e7629a4..fed0edef5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Móvel { #mobile } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index 3ed55865b..6f85907d9 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Agendamento { #scheduling } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index b24f5bbb0..0ea320b0b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Visualize estatísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index ee52cbb73..f8c00cc00 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Capture { #capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 7046fcbf4..2129b61a0 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 1f37ba1e8..589ed2da8 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Usando o aplicativo Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index ea92fab54..3f829ad1e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Sobre dimensões de dados { #data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index a90b7c11d..8198ec36b 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Dimensões de dados adicionais { #additional_data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index d5e9ab73b..e120dc605 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Modelo de relacionamento { #relationship_model } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 691b3af2f..c519bd81a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Mensagens { #messages } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 7906daa99..64c0367f5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index e78af83d7..76a4febd7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Usar - DHIS core version 2.41 +- Usar --- # Definir as preferências da conta do usuário { #user_account_preferences } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index c14f620a9..ae1d6b96f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Usar - DHIS core version master +- Usar --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index bdfed365c..795bd3816 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # DHIS2 Perguntas Freqüentes { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md index 8f531f6a2..82d3e8359 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Usar - DHIS core version master +- Usar --- # Glossário DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index b1365816a..5496a05a5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Tutoriais DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index b328a67cc..976a432be 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Notas de lançamento e atualização { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md index 06895d779..795bf7854 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Usar - DHIS core version master +- Usar --- # Gerir painéis { #dashboard } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index 33242e81d..1f2488f93 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Usar - DHIS core version master +- Usar --- # Uso do aplicativo Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index 1f950011f..9c756cb1d 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Usando o aplicativo Relatórios de eventos { #event_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index dcf002b27..031bc6b40 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version master +- Usar --- # Usando o aplicativo Event Visualizer { #event_visualizer_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index f338ab11a..bdec2b7b9 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Usar - DHIS core version master +- Usar --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index 917086f3b..33df46133 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Usar - DHIS core version master +- Usar --- # Usando o aplicativo Maps { #using_maps } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md index 0e7b0adb7..29d829030 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Usar - DHIS core version master +- Usar --- # Funcionalidade de relatórios no aplicativo de relatórios { #using_the_reports_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md index 8f5d036ee..cbe7a4675 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Usar - DHIS core version master +- Usar --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md index 37eb24c84..08ae613cf 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version master +- Usar --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md index a941ab885..966839773 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Usar - DHIS core version master +- Usar --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index a8e287be3..e4e2177b7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Usando o aplicativo de entrada de dados { #data_entry_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index 3a0949faf..b816e9311 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Usar - DHIS core version master +- Usar --- # Controle de qualidade de dados { #control_data_quality } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 659261835..5877a64c5 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Usar - DHIS core version master +- Usar --- # Sobre o compartilhamento de objetos { #sharing } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index 6a8f60eeb..7e2e939e6 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Usar - DHIS core version master +- Usar --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index 5ed71ae92..e1df15fb1 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version master +- Usar --- # Configurar metadados { #maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index f216f22d2..d0493187a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version master +- Usar --- # Configure programas no aplicativo de manutenção { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md index 992428044..7f4bd4c31 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Configure a funcionalidade de relatório { #setting_up_reporting } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index 51289a54d..6230c95d7 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version master +- Usar --- # Configurações do sistema { #settings } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index ebddabd81..b774c041f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version master +- Usar --- # Autoridades do usuário { #user_authorities } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 4fd774164..5bdebead4 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Usar - DHIS core version master +- Usar --- # Gerenciar usuários, funções e grupos de usuários { #manage_user_role_group } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index a6068a78f..8045de7fd 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Usar - DHIS core version master +- Usar --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index 2a629c755..7cafa9db8 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Usar - DHIS core version master +- Usar --- # Importar / Exportar aplicativo { #import_export } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index ff0e70808..8e3fbc9db 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata-synchronizing.md" revision_date: '2024-05-28' tags: -- Usar - DHIS core version master +- Usar --- # Configure a sincronização de metadados { #metadata_sync } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md index 0baa051fc..8e06a8e05 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index 39b2d7d9b..9242dbcf0 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Usar - DHIS core version master +- Usar --- # Administração de Dados { #data_admin } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md index 5adadb13b..f5debc5a2 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md index 9d3919a50..b8e58e7c9 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Usar - DHIS core version master +- Usar --- > **Caution** diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md index 9bba11e39..4e37ee1db 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Móvel { #mobile } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 20373a891..76760ed04 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Usar - DHIS core version master +- Usar --- # Agendamento { #scheduling } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index acd75d749..99e734cf8 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Usar - DHIS core version master +- Usar --- # Visualize estatísticas de uso { #using_usage_analytics } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 0c885deb8..90687041a 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Usar - DHIS core version master +- Usar --- # Usando o aplicativo Capture { #capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index f38aad7bd..4f70c82c8 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Usando o aplicativo Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 22f4695bc..9a934e16f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Usar - DHIS core version master +- Usar --- # Usando o aplicativo Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 1cef6fc95..5035fa029 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Usar - DHIS core version master +- Usar --- # Sobre dimensões de dados { #data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 60816821e..f9a7bedf2 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Usar - DHIS core version master +- Usar --- # Dimensões de dados adicionais { #additional_data_dimensions } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 7793bce52..8817abb81 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Modelo de relacionamento { #relationship_model } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 7499b7cb7..58560974f 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Usar - DHIS core version master +- Usar --- # Mensagens { #messages } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index e40fad0ac..b22dba41e 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Usar - DHIS core version master +- Usar --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index c5f572be3..f5f348c57 100644 --- a/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/pt/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Usar - DHIS core version master +- Usar --- # Definir as preferências da conta do usuário { #user_account_preferences } diff --git a/projects/docs-full-site/ru/.cache_timestamp b/projects/docs-full-site/ru/.cache_timestamp index f07b4b9eb..cc77b2d83 100644 --- a/projects/docs-full-site/ru/.cache_timestamp +++ b/projects/docs-full-site/ru/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:24:43Z \ No newline at end of file +2024-06-04T21:24:54Z \ No newline at end of file diff --git a/projects/docs-full-site/ru/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/ru/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index fbd4b2e7f..8bcd1b598 100644 --- a/projects/docs-full-site/ru/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/ru/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- Develop - DHIS core version master +- Develop --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index 363af6000..29d883c27 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-browsing.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.0 +- Использовать --- ## Browsing the Action Tracker { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index c7ef71609..9e77d892e 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-introduction.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.0 +- Использовать --- # Linked Action Tracker Dashboard and Demo server { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index 6b57afb7a..8cac218b6 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-maintenance.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.0 +- Использовать --- # Action Tracker App Maintenance { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index 50495adb7..aa79a2e33 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-planning.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.0 +- Использовать --- # Action Planning in Action Tracker { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index faccf5263..9b374ecd1 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-tracking.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.0 +- Использовать --- # Action Tracking in Action Tracker { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index 155daf5da..9d5712b1d 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-installation.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Installing the BNA App { #installing-the-bna-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index 4b1b7046b..f299832be 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-maintenance.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # BNA App Maintenance { #bna-app-maintenance } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index 7303e89fe..58ed635ec 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-analysis-and-interpretation.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # BNA Analysis and Interpretation { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index 6424059e2..9bcb1a2ff 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-architecture.md" revision_date: '2022-03-10' tags: -- Использовать - App version 1.2.2 +- Использовать --- # BNA App architecture { #bna-app-architecture } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index 46fe46ce5..b0ada9c8a 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bottleneck-analysis-dashboard-and-demo-server.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Bottleneck Analysis Dashboard and Demo server { #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index df019e998..dcc2ec3ef 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/navigating-the-bna-app.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # BNA App interventions configurations { #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index b36e20c99..67810e16c 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/visualization-operations.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Visualization operations { #visualization-operations } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index 95f178e30..9e562d5a9 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/adopting-the-use-of-the-bna-app.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Adopting the use of the BNA App { #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index 739395fc1..928528b34 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/capacity-building.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Capacity building { #capacity-building } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index 03c2dbcc4..2cb9ad72c 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/end-user-training.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # End User training { #end-user-training } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index 69872a06b..37c7e7472 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/guide-to-bna-app-implementation.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Guide to BNA App Implementation { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index 9153cb594..1ff0b9d7c 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/integration-concepts-for-the-bna-app.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Integration Concepts for the BNA App. { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index 648fb7cef..21fc131c0 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/opportunities-and-challenges.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Opportunities and Challenges { #opportunities-and-challenges } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index 2fa490705..12ec134ef 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/planning-and-organising.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Planning and organising { #planning-and-organising } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md index a68da36ba..e8f753acd 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/setting-up-a-new-bna-app.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Setting-up a new BNA App { #setting-up-a-new-bna-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md index 905d4ba01..c6ecaabd1 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-support-and-scale-up.md" revision_date: '2022-03-22' tags: -- Использовать - App version 1.2.2 +- Использовать --- # BNA App Support and Scale-up { #bna-app-support-and-scale-up } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md index 8fbaaf97d..17a83e516 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/scale-up-and-sustainability.md" revision_date: '2021-09-09' tags: -- Использовать - App version 1.2.2 +- Использовать --- # Scale-up and sustainability { #scale-up-and-sustainability } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md index bc5135c7d..4892892f6 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__access-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/grant-access-to-user.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- ## 2.4 Grant Access to users { #24-grant-access-to-users } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md index 542b67824..ff571e35f 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__interventions-and-indicators-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/interventions-and-indicators-configuration.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- ## 2.2 Interventions and Indicators Configuration { #22-interventions-and-indicators-configuration } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md index 4d50efd7d..676407f2f 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__CONFIGURATION__map-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/maps-configuration.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- ### 2.2.3 Map configuration { #223-map-configuration } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md index 551f92cc4..a583eca0b 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INSTALLATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-app-installation.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- # Chapter 2. Bottleneck Analysis App Administrators’ guide { #chapter-2-bottleneck-analysis-app-administrators-guide } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md index da5b4df78..b3f7caea7 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/common/about-this-guide-bna1.4.0.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- # About this guide { #about_this_guide_ } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md index 6132a7668..85a593c33 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__INTRODUCTION__introduction-to-bna-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/introduction-to-bna.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- # Chapter 1. Bottleneck Analysis App { #chapter-1-bottleneck-analysis-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md index 6c94f44ca..d906a186e 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-analysis-and-interpretation.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- ## 3.2 BNA Analysis and Interpretation { #32-bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md index 698a84d6e..b6f34058d 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__bna-layout-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/bna-layout.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- # Chapter 3. Bottleneck Analysis App User guide { #chapter-3-bottleneck-analysis-app-user-guide } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md index 83b70de2c..2756c3a4d 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__data-analysis-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/data-analystics.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- ## 2.6 Standard data analytics { #26-standard-data-analytics } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md index d9fb9cdb7..661a481af 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-140__USAGE__map-view-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna_v.1.4.0/map-view.md" revision_date: '2022-12-20' tags: -- Использовать - App version 1.4.0 +- Использовать --- Map View diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md index 18a90b574..1a2ad5471 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__IMMUNIZATION-ANALYSIS-APP__APP-VERSION-103__immunization-analysis-app-user-manual-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/metadata-package-development/blob/master/metadata/AEFI/immunisation_analysis_app_user_manual.md" revision_date: '2021-03-18' tags: -- Использовать - App version 1.0.3 +- Использовать --- # User Manual for the DHIS2 Immunisation Analysis App { #user-manual-for-the-dhis2-immunisation-analysis-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md index 8e2cedaaf..7504a0a4b 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__about-this-guide-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/about-this-guide.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # About this guide { #about-this-guide } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md index af7423f5b..59aabd77e 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__accessing-and-transilating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-and-translating-scorecard.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Accessing and translating the Scorecard { #accessing-and-translating-the-scorecard } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md index 5b610f401..eba8461e9 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/accessing-scorecard-app.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Login DHIS2 system { #login-dhis2-system } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md index 2597831aa..05d6ac2d1 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__creating-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/creating-scorecard.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- ## Creating the Scorecard { #creating-the-scorecard } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md index 4bd04cd6c..712d6525f 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__introduction-to-the-scorecard-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/introduction-to-scorecard.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Introduction to the Scorecard App { #introduction-to-the-scorecard-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md index f35b5a4e4..095602ad4 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__saving-configurations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/saving-configurations.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- ## Saving configuration and load the scorecard { #saving-configuration-and-load-the-scorecard } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md index 1c994d2ab..24c13ce20 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__scorecard-app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/scorecard-app-architecture.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Scorecard App architecture { #scorecard-app-architecture } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md index 8c8646259..4f0dca211 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__support-and-maintenance-options-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/support-and-maintanace-options.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Scorecard App Built-in Support and Maintenance Options { #scorecard-app-built-in-support-and-maintenance-options } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md index b88e1494f..12ed8307f 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__INTERACTIVE-SCORECARD-APP__APP-VERSION-250__viewing-scorecard-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/scorecard-v2.5.0/src/commonmark/en/content/scorecard/viewing-scorecard.md" revision_date: '2021-10-04' tags: -- Использовать - App version 2.5.0 +- Использовать --- # Viewing the Scorecard App Analysis outputs { #viewing-the-scorecard-app-analysis-outputs } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md index a5f36267d..25d55ecbb 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-maintenance.md" revision_date: '2024-02-27' tags: -- Использовать - App version 2.0 +- Использовать --- If a Standalone action tracker application is taking too long to load, and you’re not on a slow network, make sure you have cleared your browser cache. diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md index e44e0259c..995b9aa9d 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__architecture-and-installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-architecture-and-installation.md" revision_date: '2024-02-22' tags: -- Использовать - App version 2.0 +- Использовать --- The Standalone Action Tracker Application is built on an architecture that eases user interactions by having a design concept that promotes the user to follow their intuition complemented with high performance that considers the lowest internet connection scenarios with descriptive notification messages if the user misses a step along the way. diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md index 8389a0e0f..428b608e1 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-browsing.md" revision_date: '2024-02-23' tags: -- Использовать - App version 2.0 +- Использовать --- The Standalone Action Tracker App can be found in the Apps menu. if the application has not yet been installed in your DHIS2 instance or the installation has issues, refer to the installation instructions (Section 3.5) of this documentation for further guidance, or contact the DHIS2 administrator for your instance. diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md index f77448b9d..de6cb6a8a 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-APP-DEMO__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-introduction.md" revision_date: '2024-02-22' tags: -- Использовать - App version 2.0 +- Использовать --- # Introduction to the Standalone Action Tracker App { #introduction-to-the-standalone-action-tracker-app } diff --git a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md index cec40877c..98ea8261e 100644 --- a/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md +++ b/projects/docs-full-site/ru/USE__OPTIONAL-APPS__STANDALONE-ACTION-TRACKER-APP__APP-VERSION-20__STANDALONE-ACTION-TRACKER-CONFIGURATION__configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/standalone_action_tracker/sat-app-configuration.md" revision_date: '2024-02-27' tags: -- Использовать - App version 2.0 +- Использовать --- The Standalone Action Tracker App includes a module for administrators to configure key metadata for the normal user. The administration configurable options include:- diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 7dca89511..b01f742a0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index d3fe78f9b..ec94c808d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md index c338d0256..95f829fd6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md index b29fc8207..99942e293 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index b0b52e995..5c6300784 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md index 933b2566c..7680ff307 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md index ede7841d4..99244685c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md index fd7cc9be3..fdbd0c730 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md index 267007b55..db7a93d6d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md index 09f38587c..2823a6ba0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md index 862e73717..70867e4bd 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-maps-app.md" revision_date: '2022-03-23' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md index cc75c95c1..71b7089a6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md index cb3f1e435..540ffe848 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md index 44c63addf..5938411c3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md index dd6c55600..0219ad956 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md index 997978523..e2294a540 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index a04fb8b1b..83fa2957f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md index 06ad9b37a..543aafc46 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-the-gis-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure the Maps app { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md index a0f9badaf..579657daf 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata.md" revision_date: '2022-10-02' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md index cf8ee4ae4..66bd0d80c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md index bc2ca1d30..2d20f766d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md index 0b3d20d42..8c2c4bbea 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/system-settings.md" revision_date: '2022-04-27' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md index c2f2e4294..3ae2bead1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 6f9e08ff9..c7cd05d5d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md index 0f53f25f3..7a3b1f40b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/importexport-app.md" revision_date: '2022-02-23' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md index cbeb5f419..dd88cac7e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md index ae2069fe4..1ca053598 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md index b3538e57f..ff12c7f9f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md index fc9707fc9..817e3480c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md index c92a359ed..10eb23838 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md index 5c52cef73..a032717c9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md index db22d97d8..fe13ba9a5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 555ebb93f..d31573614 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index a58efe8f7..8cf78133a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index c55599452..6ecaa0cb5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 45bc62d4d..e3053c545 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 8e5d0d6b6..ad03eb3db 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 2ae4a48f3..0d7ab33ec 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 41114b5ca..db3413e3a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md index ef5fd8b5e..269105b37 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 19f69258b..3f4841c15 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.38/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index beb171c0f..d7215fd8f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 498e913e2..82c3006f6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 6b7a05ab4..51ce1268c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md index 75d9e7eab..b223a45fb 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md index f9a1488cd..5176eb20f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index bb077ce43..814b1570d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md index d30dbc2b1..bd643f5d1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/managing-dashboards.md" revision_date: '2021-10-22' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index 7c5668ca8..eec3b0641 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-visualizer.md" revision_date: '2022-01-20' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index 87d9b4d60..f806b5eb2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index eb302d2d3..3cefbfa71 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index 1e23ce28a..3a219fa07 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index 23448afdb..48f8e3dc0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-maps-app.md" revision_date: '2022-09-13' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index edf82fc50..562c8fed8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md index 2ef792342..87a004942 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md index 159d7a159..550a391ab 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md index c8687445f..632a634e2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md index 4593e4c2c..633f1b637 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md index 7f8dc09ea..7391cea50 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index f04a34831..31444679c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md index cdfa27290..2eaf180d0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index a60b33572..409832227 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index e16232eeb..c91e9a3aa 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md index 5ab9b0d68..065de4ffa 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md index b3e8a8901..394f787a8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/system-settings.md" revision_date: '2022-09-13' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index e13509bce..d3ed54fe0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 733c2eb33..ab2ec14bf 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md index c855dfca0..918df03a4 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-exchange.md" revision_date: '2023-02-16' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index 8a233478a..7c0e2942b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md index 34a156e86..2e9929998 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md index 1c5dea55d..bd8ff9767 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md index edff38de5..b92529b6b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 36e97d0a9..a64941b98 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index 2925045ee..6baab624b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index a13babe13..d8620f0af 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md index a9b0517b5..230f2fbea 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 1f1bf3bc6..f54a46745 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 796bded94..f644113b6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 3ad9d1569..1b7bd9485 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index c7831cae0..1c4a653b6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 15a411afc..f81e5195c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 0dd1d0d2e..f39789bf6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 29bb0f8ae..08993b81f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index ef2431005..81fe43e7d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index eee45808c..a0c040ee3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 1df47dc24..5203d779a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 487edd4a5..4fd970130 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index f8e2d9d33..45839e727 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md index 19cadb279..483b4dc20 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md index f2dee33ae..e78e65b79 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 4bc9debfc..1033071e2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md index e3c1f38c2..19ac864e2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md index 00943b9e6..0747c2c1c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md index a8c1e945e..ed6183bf8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md index 63fae162d..56686c2ef 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md index 3b6092b1b..b097f0b69 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md index 25253ca90..56f48888c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md index cbff26a94..ba0fb911d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md index 355809f29..aad8428b9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md index 37f3034d6..7d5c16207 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md index 781b71fc8..4aec42489 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md index c4af0b501..20994c00c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md index 1e7422850..97f83d2c6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index e40648ff9..49bbdb36d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md index 0a46e7b66..d38470c8c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md index 8a83abf64..48e4dc7ec 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata.md" revision_date: '2023-07-20' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md index f4221727f..30e5d8eec 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md index 7178774ee..d38abdd22 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md index 3cf42574f..6c8e57411 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/system-settings.md" revision_date: '2024-01-25' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md index 44d405588..6ed6f14a0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index dc665c0c8..dc25b0ce4 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md index 7247234d4..459de2357 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md index ca647c0a5..b753ca50d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md index 9080152ce..74a5e81d1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md index 63165c55d..ce8e14960 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md index 9850e5164..9e98986d8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-administration.md" revision_date: '2023-06-21' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md index 578152f11..e6cc27a73 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md index ec62a9bec..55c23fcc1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md index 2f4a5513a..d5629703e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md index bc1cc5772..fd4bbdc65 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 2c3f8d71a..217145c65 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 4e04c066b..ce9dcd55f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 4b12dfa35..305462a42 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 638808f99..448940bb1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index c87c19a56..96aea458f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 5c1a93a3d..83405ef47 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 98ee96717..d79bfcf05 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 3cbc42c64..033651958 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 6b501c178..bd8a61a84 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index aeb208e1e..aa70370d1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 0a198a9d1..0e20528b9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 826b7e6ed..cb7130215 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 4970aa890..4331e0b02 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index f0c4a25a3..09a902817 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 13d92a5e9..e482b20c2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index 0bd631a51..3580a92c6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 5db4ec8a2..d31598f6f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index d7689421c..399cf443d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 23ae7616f..76a283d5a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index 21499e1bd..4c07697d7 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index 195fe4b9d..7ea240c3e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index 9d9e1e19a..8ff7b6f2b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index 95478d0d4..151338ba5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index df62e36eb..cfe04401f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index 983cf4adc..7b1ec651d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index ad65159c3..03916b3c0 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index b914d55a9..5f71408f6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index ade9a97e7..1c3113813 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 0ad1cc5ac..6ce3665ab 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index fd2b1c027..9d476de72 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 49d3c6368..2932b1be9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index bb63e94d8..1c6ab6604 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 78cd3550b..6357bf9c5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 29f571687..d5eaa5e0b 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 3441178e2..964e4cf2c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index f9e8cf226..3909ef060 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 9c9afb997..5ef413e4a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index eda53ca28..ccc9cca24 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index de8bd3b90..095dd9857 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 5ce574832..0de12c3f3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index 527114593..8456df8b1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index f47685e94..e36bbe294 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 09f2ac277..d30b6d0d3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index ca6d9ef17..e4705ef26 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index bfefd7c53..6147e907c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index f6c3b9ecb..ba0278608 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index bbf170837..89a5d1f06 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 7cee24ef1..e01ea9808 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index ae0c98394..a26f30384 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index b68cfa3c6..07b835fb8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index cfa2b712f..33a5d44bb 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 07e3b735b..0c611a854 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 3d05a998d..4a442c3be 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index e82d3eb9f..9f3722eab 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index fa2c354d9..d240517e3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Использовать - DHIS core version master +- Использовать --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 6ffc2a3a3..4e5a8f7bb 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md index b94c87cb6..bba99cf04 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Использовать - DHIS core version master +- Использовать --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 01b4be345..7f9f74550 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index b1560c848..282caafe6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md index 685af79b0..54ed567ed 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Использовать - DHIS core version master +- Использовать --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index 3404a989c..353b3c612 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index 32a49b369..6a87d2411 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index c3c06f063..c0854d5c4 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index 3a8942d13..d18e91464 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index 651ce0c4f..015b23cf4 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md index 02affac86..ab202eec6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Использовать - DHIS core version master +- Использовать --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md index ddbd84538..b44d8a5cb 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Использовать - DHIS core version master +- Использовать --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md index 1b99e3fe9..419a225fa 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version master +- Использовать --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md index 941831bc7..e88087290 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Использовать - DHIS core version master +- Использовать --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index aa96051fc..40e0f417e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index e2400e36b..397b76d31 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Использовать - DHIS core version master +- Использовать --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 1bd112ce3..d0c9815b9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Использовать - DHIS core version master +- Использовать --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index dd72e9985..1fc652b49 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Использовать - DHIS core version master +- Использовать --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index bb49fd0d7..b164a52d8 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version master +- Использовать --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index a5a6747fe..78f044051 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version master +- Использовать --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md index a2554ad99..335c6ef78 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index 99de21dfe..9f289ea21 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version master +- Использовать --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index 7ee1adcb4..72b38cdd9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version master +- Использовать --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 567e374d9..3bc67765f 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Использовать - DHIS core version master +- Использовать --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index 973bfd87c..0e6b2e71d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index 3bbac50bb..46b68df9d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Использовать - DHIS core version master +- Использовать --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index be7f34332..276f791f5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata-synchronizing.md" revision_date: '2024-05-28' tags: -- Использовать - DHIS core version master +- Использовать --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md index 0346a963a..f371cb7e4 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index 651ba4a73..e61d0ca12 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Использовать - DHIS core version master +- Использовать --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md index 615761dd5..d018ee200 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md index 02b4cf167..00bc5c563 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Использовать - DHIS core version master +- Использовать --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md index 490549f23..aec6a8d3c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 3932bafcc..11dcc999a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Использовать - DHIS core version master +- Использовать --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index f912cb6b9..81410bb6e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Использовать - DHIS core version master +- Использовать --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 6386f3abe..f73ab9aab 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 60584f858..ce82c026c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 39a03d6d9..cf6a904a5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Использовать - DHIS core version master +- Использовать --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 45e796e03..b5e2cda30 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Использовать - DHIS core version master +- Использовать --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 2aed8eea8..cce545aac 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Использовать - DHIS core version master +- Использовать --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index c489cefcb..4c808f81d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 469a57230..049d3b998 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Использовать - DHIS core version master +- Использовать --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 8c8d81105..a8804234e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Использовать - DHIS core version master +- Использовать --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 2b24156f1..40fc44a6c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Использовать - DHIS core version master +- Использовать --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/si/.cache_timestamp b/projects/docs-full-site/si/.cache_timestamp index 154406b93..95fb611ed 100644 --- a/projects/docs-full-site/si/.cache_timestamp +++ b/projects/docs-full-site/si/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:25:39Z \ No newline at end of file +2024-06-04T21:25:34Z \ No newline at end of file diff --git a/projects/docs-full-site/si/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/si/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index fbd4b2e7f..8bcd1b598 100644 --- a/projects/docs-full-site/si/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/si/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- Develop - DHIS core version master +- Develop --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 18e9be8c7..b30dea3ad 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- Use - DHIS core version 2.41 +- Use --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index fb26437d4..3f73fd44b 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index c6fbcb597..d37dc6d10 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- Use - DHIS core version 2.41 +- Use --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 575fc9118..16581ae92 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index e16665726..123c65776 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index 464d94ae2..ce5aec70b 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- Use - DHIS core version 2.41 +- Use --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index db4ed8963..2dd38cbdb 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index b8978480b..0099bce1c 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 48dbfdee8..a177e99d1 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index e11d40608..a825e338b 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index 0629e8d72..c7b9f3c93 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index 73d042d6f..328c184a0 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- Use - DHIS core version 2.41 +- Use --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index 05c94b954..88a1f8cde 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- Use - DHIS core version 2.41 +- Use --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index d47be21a8..9aa84c2f5 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- Use - DHIS core version 2.41 +- Use --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index b2eb9d44f..b90e7379a 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- Use - DHIS core version 2.41 +- Use --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index 4c2f576d9..76e65454f 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index b2b2c8194..fd2ae3160 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- Use - DHIS core version 2.41 +- Use --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index a50bca106..0c443529d 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- Use - DHIS core version 2.41 +- Use --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 887eb37ea..d17b4ccbd 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index d0da3c30f..4e492e6ed 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index d2f7831e3..e685292a3 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure programs in the Maintenance app { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 6786075b2..6b6cbf924 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index 5c9487cd1..d98847f90 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # System settings { #settings } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 70be1dc65..a7c3d7878 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 703da69e4..844ae2f13 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- Use - DHIS core version 2.41 +- Use --- # Manage users, user roles and user groups { #manage_user_role_group } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index 6835e62da..7f9b1dda0 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 70b99bd7b..8463a1d1f 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index 53887d9c9..c8925636c 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index b807f74d8..ecc8ff255 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 10ae5b554..d90a2b30f 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index e556625f2..91eb4e939 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 02b6d19b1..a4c4dbbc1 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- Use - DHIS core version 2.41 +- Use --- > **Caution** diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index ceb87057c..d8fe86d4f 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Mobile { #mobile } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index ce81b04fc..9a6c4c557 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- Use - DHIS core version 2.41 +- Use --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 26f498935..97cdc7f4a 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- Use - DHIS core version 2.41 +- Use --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 61b57676a..513ac2010 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 16ad233c8..6af3da161 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 0a3f465d4..a1a3919a1 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- Use - DHIS core version 2.41 +- Use --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 74d84514b..a1146a4f1 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- Use - DHIS core version 2.41 +- Use --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index dda5e012a..56f2bc46e 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- Use - DHIS core version 2.41 +- Use --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 28645fff6..d7a5bf33b 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index add7a9713..afaa2df3f 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- Use - DHIS core version 2.41 +- Use --- # Messaging { #messages } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index c81cd73b5..55ba690b6 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index adcd05b72..fd2f99f81 100644 --- a/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/si/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- Use - DHIS core version 2.41 +- Use --- # Set user account preferences { #user_account_preferences } diff --git a/projects/docs-full-site/zh/.cache_timestamp b/projects/docs-full-site/zh/.cache_timestamp index 88ff36997..aed47fcef 100644 --- a/projects/docs-full-site/zh/.cache_timestamp +++ b/projects/docs-full-site/zh/.cache_timestamp @@ -1 +1 @@ -2024-06-03T21:25:51Z \ No newline at end of file +2024-06-04T21:25:46Z \ No newline at end of file diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index f959ff215..843ae18de 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/analytics.md" -revision_date: '2024-05-02' +revision_date: '2024-05-31' tags: -- Develop - DHIS核心 主版 +- Develop --- # 分析工具 { #analytics } @@ -816,7 +816,7 @@ Analytics事件API可让您指定一系列查询参数。 | 查询参数 | 需要 | 描述 | 选项 | |---|---|---|---| -| 模式 | 不 | 组织单位的选择方式。默认为 DESCENDANTS，表示层次结构中的所有子单元。 CHILDREN 是指层次结构中的直接子级；选定的仅指选定的组织单位。更多详细信息[此处]。(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | 后裔、子女、精选 | +| 模式 | 不 | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | 后裔、子女、精选 | | 升序 | 不 | 维度按升序排序，可以引用事件日期、组织单位名称和代码以及任何项目标识符。 | `ouname` | `程序状态` | `事件状态` | `由显示名称创建` | `lastupdatedbydisplayname` | `事件日期` | `注册日期` | `事件日期` | `最后更新` |项目标识符 | | 描述 | 不 | 维度按降序排序，可以引用事件日期、组织单位名称和代码以及任何项目标识符。 | `ouname` | `程序状态` | `事件状态` | `由显示名称创建` | `lastupdatedbydisplayname` | `事件日期` | `注册日期` | `事件日期` | `最后更新` |项目标识符 | | 仅坐标 | 不 | 是否只返回有坐标的事件。 | 假的|真的 | @@ -1711,7 +1711,7 @@ A special keyword `NV` can be used to filter by `null` values | 筛选 | 不 | 维度标识符包括数据元素、属性、期间、组织单位和组织单位组集。参数可以重复任意次数。项目过滤器可以应用于维度，格式为::。过滤器值不区分大小写。 || | 程序状态 | 不 | 指定要包括的注册的注册状态。 | 活跃|已完成|取消 | | 相对期间日期 | 细绳 | 不 | 日期标识符，例如：“2016-01-01”。覆盖相对期间的开始日期 | -| 模式 | 不 | 组织单位的选择方式。默认为 DESCENDANTS，表示层次结构中的所有子单元。 CHILDREN 是指层次结构中的直接子级；选定的仅指选定的组织单位。更多详细信息[此处]。(https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_ou_scope) | 后裔、子女、精选 | +| 模式 | 不 | The mode of selecting organisation units. Default is DESCENDANTS, meaning all sub units in the hierarchy. CHILDREN refers to immediate children in the hierarchy; SELECTED refers to the selected organisation units only. More details [here](#webapi_tracker_orgunit_scope) | 后裔、子女、精选 | | 升序 | 不 | 维度按升序排序，可以参考注册日期、事件日期、组织单位名称和代码。 | `ouname` | `程序状态` | `由显示名称创建` | `lastupdatedbydisplayname` | `注册日期` | `事件日期` | `最后更新` |项目标识符 | | 描述 | 不 | 维度按降序排序，可以参考注册日期、事件日期、组织单位名称和代码。 | `ouname` | `程序状态` | `由显示名称创建` | `lastupdatedbydisplayname` | `注册日期` | `事件日期` | `最后更新` |项目标识符 | | 仅坐标 | 不 | 是否仅返回具有坐标的注册。 | 假的|真的 | diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index f1978bfd3..ceff095d0 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/apps.md" revision_date: '2021-06-14' tags: -- Develop - DHIS核心 主版 +- Develop --- # 应用 { #apps } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index 040aee877..599f640d6 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" revision_date: '2023-06-23' tags: -- Develop - DHIS核心 主版 +- Develop --- # 审核 { #audit } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index 30bb95088..8f48a48b5 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- Develop - DHIS核心 主版 +- Develop --- # 数据审批 { #data-approval } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index 54f27adc8..a2fb6f7b3 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- Develop - DHIS核心 主版 +- Develop --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index 7e055598b..2c004bda9 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- Develop - DHIS核心 主版 +- Develop --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index fd0a169ae..7e62951ee 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- Develop - DHIS核心 主版 +- Develop --- # 数据 { #data } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index ebf0ec7eb..2a9888f99 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- Develop - DHIS核心 主版 +- Develop --- # 数据存储 { #data-store } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index 2abd525c8..71a703719 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- Develop - DHIS核心 主版 +- Develop --- # 数据验证 { #data-validation } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index 0308dfb4c..6e1ba9ae1 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- Develop - DHIS核心 主版 +- Develop --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 31044a92f..7618939ef 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- Develop - DHIS核心 主版 +- Develop --- # 国际化 { #i18n } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index 9084edacf..dedf96445 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- Develop - DHIS核心 主版 +- Develop --- # 总览 { #webapi } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index 71ede553f..146dcffa6 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- Develop - DHIS核心 主版 +- Develop --- # 保养 { #maintenance } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index 4d78484b6..82e244e7a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- Develop - DHIS核心 主版 +- Develop --- # 元数据要点 API { #gist_api } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index 308361348..ca3fc511d 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- Develop - DHIS核心 主版 +- Develop --- # 元数据 { #metadata } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md index 4c009e0c9..1bb40eff0 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/organization-unit-profile.md" revision_date: '2021-11-19' tags: -- Develop - DHIS核心 主版 +- Develop --- # 组织部门资料{ #org_unit_profile } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index 3417e861c..dec9fa24d 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- Develop - DHIS核心 主版 +- Develop --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index f6948bed3..9c2e8a994 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/route.md" revision_date: '2024-05-15' tags: -- Develop - DHIS核心 主版 +- Develop --- # Route { #route } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index 841bfef18..5c58b41c7 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- Develop - DHIS核心 主版 +- Develop --- # 排程 { #webapi_scheduling } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index af5346bc9..0d9ed82ad 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- Develop - DHIS核心 主版 +- Develop --- # 设置和配置 { #settings-and-configuration } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index b83bc523d..c96c08bba 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- Develop - DHIS核心 主版 +- Develop --- # 分享中 { #sharing } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index 9ce3ce577..000262d96 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- Develop - DHIS核心 主版 +- Develop --- # 短信 { #sms } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index 27035e03f..f436878a1 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- Develop - DHIS核心 主版 +- Develop --- # 同步化 { #webapi_synchronization } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md index f252068db..f42d08072 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-05-31' +revision_date: '2024-06-03' tags: -- Develop - DHIS核心 主版 +- Develop --- # Tracker { #webapi_tracker } @@ -18,20 +18,21 @@ tags: > * `GET /api/tracker/events` > * `GET /api/tracker/relationships` > -> [Tracker (deprecated)](#webapi_deprecated_tracker) describes the deprecated endpoints +> The deprecated tracker endpoints > > * `GET/POST/PUT/DELETE /api/trackedEntityInstance` > * `GET/POST/PUT/DELETE /api/enrollments` > * `GET/POST/PUT/DELETE /api/events` > * `GET/POST/PUT/DELETE /api/relationships` > -> which have been removed in version **42**! +> have been removed in version **42**! > -> [Migrating to new tracker endpoints](#webapi_tracker_migration) +> [Migrating to new tracker +> endpoints](https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-241/tracker-deprecated.html#webapi_tracker_migration) > should help you get started with your migration. Reach out on the [community of > practice](https://community.dhis2.org) if you need further assistance. -## 跟踪器对象 { #webapi_nti_tracker_objects } +## Tracker Objects { #webapi_tracker_objects } Tracker consists of a few different types of objects that are nested together to represent the data. In this section, we will show and describe each of the objects used in the Tracker API. @@ -134,7 +135,6 @@ point out any exceptional cases between these two. | program | Only for reading data. The type of program the enrollment which owns the event has. | 不 | 是的 | String:Uid | ABCDEF12345 | | trackedEntity | Only for reading data. The tracked entity which owns the event. ***Not applicable for `EVENT PROGRAM`*** | 不 | 不 | String:Uid | ABCDEF12345 | | status | Status of the event. ACTIVE if not supplied. | 不 | 不 | Enum | ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED | -| enrollmentStatus | Only for reading data. The status of the enrollment which owns the event. ***Not applicable for `EVENT PROGRAM`*** | 不 | 不 | 枚举 | ACTIVE, COMPLETED, CANCELLED | | orgUnit | The organisation unit where the user registered the event. | 是的 | 不 | String:Uid | ABCDEF12345 | | createdAt | Only for reading data. Timestamp when the user created the event. Set on the server. | 不 | 是的 | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | createdAtClient | Timestamp when the user created the event on client | 不 | 不 | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | @@ -149,7 +149,7 @@ point out any exceptional cases between these two. | geometry | A geographical representation of the event. Based on the "featureType" of the Program Stage | 不 | 不 | GeoJson | {
"type": "POINT",
"coordinates": [123.0, 123.0]
} | | storedBy | Client reference for who stored/created the event. | 不 | 不 | String:Any | John Doe | | createdBy | Only for reading data. User that created the object. Set on the server | 不 | 是的 | 用户 | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | -| updatedBy | Only for reading data. User that last updated the object. Set on the server | 不 | 是的 | 用户 | {
"uid": "ABCDEF12345",
"用户名": "用户名",
“名字”：“约翰”，
“姓氏”：“Doe”
} | +| updatedBy | Only for reading data. User that last updated the object. Set on the server | 不 | 是的 | 用户 | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | | attributeOptionCombo | Attribute option combo for the event. Default if not supplied or configured. | 不 | 不 | String:Uid | ABCDEF12345 | attributeCategoryOptions | Attribute category option for the event. Default if not supplied or configured. | 不 | 不 | String:Uid | ABCDEF12345 | assignedUser | A reference to a user who has been assigned to the event. | 不 | 不 | 用户 | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | @@ -194,15 +194,17 @@ of the relationship must conform to are based on the `Relationship Type` of the ### 属性 { #attributes } -`Attributes` are the actual values describing the `tracked entities`. They can either be connected -through a `tracked entity type` or a `program`. Implicitly this means `attributes` can be part of -both a `tracked entity` and an `enrollment`. +Attributes are the values describing the tracked entities. Attributes can be associated either +through a tracked entity type or a program. This implies that attributes can be part of both a +tracked entity and an enrollment. Importantly, an attribute can only have one value, even if a +tracked entity has multiple enrollments that define that attribute. This is because the tracked +entity ultimately owns the attribute value. | Property | 描述 | 需要 | Immutable | 类型 | 例 | |---|---|---|---|---|---| | attribute | A reference to the tracked entity attribute represented. | 是的 | 是的 | String:Uid | ABCDEF12345 | | 码 | Only for reading data. The code of the tracked entity attribute. | 不 | 不 | String:Any | ABC | -| displayName | Only for reading data. The displayName of the tracked entity attribute. | 不 | 不 | 字符串：任意 | 名称 | +| displayName | Only for reading data. The displayName of the tracked entity attribute. | 不 | 不 | String:Any | 名称 | | createdAt | Timestamp when the value was added. Set on the server. | 不 | 是的 | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | updatedAt | Timestamp when the value was last updated. Set on the server. | 不 | 是的 | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | storedBy | Client reference for who stored/created the value. | 不 | 不 | String:Any | John Doe | @@ -211,18 +213,20 @@ both a `tracked entity` and an `enrollment`. > **Note** > -> For `attributes` only the "attribute" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating an attribute, only the `attribute` and `value` properties are required. To +> remove an attribute from a tracked entity or enrollment, set the `value` to `null` [see +> example](#delete-attribute-values). > -> In the context of tracker objects, we refer to `Tracked Entity Attributes` and `Tracked Entity -> Attribute Values` as "attributes". However, attributes are also their own thing, related to -> metadata. Therefore, it's vital to separate Tracker attributes and metadata attributes. In the -> tracker API, it is possible to reference the metadata attributes when specifying `idScheme` (See -> request parameters for more information). +> In the context of the tracker, we refer to `Tracked Entity Attributes` and `Tracked Entity +> Attribute Values` simply as attributes. However, it's important to note that attributes and +> attribute values are also concepts within metadata. Therefore, distinguishing between tracker +> attributes and metadata attributes is essential. In the tracker API, you can reference metadata +> attributes by specifying the `idScheme` (see [request +> parameters](#webapi_tracker_import_request_parameters) for more information). ### Data Values { #data-values } -While `Attributes` describes a `tracked entity` or an `enrollment`, `data values` describes an `event`. The major difference is that `attributes` can only have a single value for a given `tracked entity`. In contrast, `data values` can have many different values across different `events` - even if the `events` all belong to the same `enrollment` or `tracked entity`. +While attributes describe a tracked entity, data values describe an event. | Property | 描述 | 需要 | Immutable | 类型 | 例 | |---|---|---|---|---|---| @@ -233,35 +237,35 @@ While `Attributes` describes a `tracked entity` or an `enrollment`, `data values | updatedAt | Timestamp when the value was last updated. Set on the server. | 不 | 是的 | Date:ISO 8601 | YYYY-MM-DDThh:mm:ss | | storedBy | Client reference for who stored/created the value. | 不 | 不 | String:Any | John Doe | | createdBy | Only for reading data. User that created the object. Set on the server | 不 | 是的 | 用户 | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | -| updatedBy | Only for reading data. User that last updated the object. Set on the server | 不 | 是的 | 用户 | {
"uid": "ABCDEF12345",
"用户名": "用户名",
“名字”：“约翰”，
“姓氏”：“Doe”
} | +| updatedBy | Only for reading data. User that last updated the object. Set on the server | 不 | 是的 | 用户 | {
"uid": "ABCDEF12345",
"username": "username",
"firstName": "John",
"surname": "Doe"
} | > **Note** > -> For `data elements` only the "dataElement" and "value" properties are required when adding data. -> "value" can be null, which implies the user should remove the value. +> When adding or updating a data value, only the `dataElement` and `value` properties are required. To +> remove a data value from an event, set the `value` to `null` [see example](#delete-data-values). ### 笔记 { #notes } -DHIS2 tracker allows for capturing of data using data elements and tracked entity attributes. -However, sometimes there could be a situation where it is necessary to record additional information -or comment about the issue at hand. Such additional information can be captured using notes. -Notes are equivalent to data value comments from the Aggregate DHIS2 side. +The Tracker system enables the capture of data using data elements and tracked entity attributes. +However, there are situations where additional information or notes about specific issues need to be +recorded. These additional details can be captured using notes, similar to data value notes in the +DHIS2 aggregate side. -There are two types of notes - notes recorded at the event level and those recorded at the -enrollment level. An enrollment can have one or more events. Comments about each of the events - for -example, why an event was missed, rescheduled, or why only a few data elements were filled and the -like - can be documented using event notes. Each of the events within an enrollment can have its own -story/notes. One can then record, for example, an overall observation of these events using the -parent enrollment note. Enrollment notes are also helpful to document, for example, why an -enrollment is canceled. It is the user's imagination and use-case when and how to use notes. +There are two types of notes: enrollment-level notes and event-level notes. An enrollment can +consist of one or more events, and notes can be recorded for each event to document reasons such as +why an event was missed, rescheduled, or partially completed. Each event within an enrollment can +have its own notes. Additionally, overall observations of these events can be recorded using a +parent enrollment note. Enrollment notes are useful for documenting reasons such as why an +enrollment was canceled. The use of notes is flexible and can be tailored to the user's needs and +specific use cases. -Both enrollment and event can have as many notes as needed - there is no limit. However, it is not -possible to delete or update neither of these notes. They are like a logbook. If one wants to amend -a note, one can do so by creating another note. The only way to delete a note is by deleting the -parent object - either event or enrollment. +Both enrollment and event notes can have an unlimited number of entries; there is no limit to the +number of notes that can be added. However, it is not possible to delete or update these notes once +they are created. They function like a logbook. To amend a note, a new note can be created. The only +way to delete a note is by deleting the parent object, either the event or the enrollment. -Notes do not have their dedicated endpoint; they are exchanged as part of the parent event -and/or enrollment payload. Below is a sample payload. +Notes do not have a dedicated endpoint; they are exchanged as part of the parent event and/or +enrollment payload. Below is a sample payload: ```json { @@ -272,10 +276,10 @@ and/or enrollment payload. Below is a sample payload. "notes": [ { "note": "vxmCvYcPdaW", - "value": "Enrollment note 2." + "value": "Enrollment note 1" }, { - "value": "Enrollment note 1" + "value": "Enrollment note 2." } ], "events": [ @@ -310,99 +314,14 @@ and/or enrollment payload. Below is a sample payload. | Property | 描述 | 需要 | Immutable | 类型 | 例 | |---|---|---|---|---|---| | uid | The identifier of the user. | Yes* | 是的 | String:Uid | ABCDEF12345 | -| 用户名 | Username used by the user. | 是的* | 是的 | String:Any | 123 | +| 用户名 | Username used by the user. | Yes* | 是的 | String:Any | 123 | | firstName | Only for reading data. First name of the user. | 不 | 是的 | String:Any | John | -| surname | Only for reading data. Last name of the user. | 不 | 是的 | 字符串：任意 | Doe | +| surname | Only for reading data. Last name of the user. | 不 | 是的 | String:Any | Doe | > One between `uid` or `username` field must be provided. If both are provided, only username is > considered. -### Program stage working lists { #webapi_working_list_filters } - -The program stage working lists feature within the Capture app is designed to display -pre-established working lists relevant to a particular program stage. This functionality enables -users to save filters and sorting preferences that are related to program stages, facilitating the -organisation and management of their workflow. To interact with them, you'll need to use the -*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing -pattern as any other metadata. When using the */api/sharing* the type parameter will be -*programStageWorkingLists*. - - /api/40/programStageWorkingLists - -##### Payload on CRUD operations to program stage working lists { #payload-on-crud-operations-to-program-stage-working-lists } - -The endpoint above can be used to get all program stage working lists. To get a single one, just add -at the end the id of the one you are interested in. This is the same in case you want to delete it. -On the other hand, if you are looking to create or update a program stage working list, besides the -endpoint mentioned above, you'll need to provide a payload in the following format: - -Table: Payload - -| Payload values | 描述 | 例 | -|---|---|---| -| 名称 | Name of the working list. Required. || -| 描述 | A description of the working list. || -| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | -| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | -| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. - -Table: Program Stage Query Criteria - -| Criteria values | 描述 | 例 | -|---|---|---| -| status | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | -| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | -| scheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | -| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | -| 跟进 | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | -| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | -| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | -| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | -| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | -| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | -| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | -| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | -| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | -| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | -| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | - -See an example payload below: - -```json -{ - "name":"Test WL", - "program":{"id":"uy2gU8kT1jF"}, - "programStage":{"id":"oRySG82BKE6"}, - "description": "Test WL definition", - "programStageQueryCriteria": - { - "status":"VISITED", - "eventCreatedAt":{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}, - "scheduledAt": {"type":"RELATIVE","period":"TODAY"}, - "enrollmentStatus": "COMPLETED", - "followUp" : true, - "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "enrollmentOccurredAt": {"type":"RELATIVE","period":"THIS_MONTH"}, - "orgUnit": "Rp268JB6Ne4", - "ouMode": "SELECTED", - "assignedUserMode":"PROVIDED", - "assignedUsers":["DXyJmlo9rge"], - "order": "w75KJ2mc4zz:asc", - "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"], - "dataFilters":[{ - "dataItem": "GXNUsigphqK", - "ge": "10", - "le": "20" - }], - "attributeValueFilters":[{ - "attribute": "ruQQnf6rswq", - "eq": "15" - }] - } -} -``` - -## Tracker Import (`POST /api/tracker`) { #webapi_nti_import } +## Tracker Import (`POST /api/tracker`) { #webapi_tracker_import } The endpoint `POST /api/tracker` is also called the tracker importer. This endpoint allows clients to import i.e. create, update and delete @@ -411,9 +330,9 @@ to import i.e. create, update and delete * **Enrollments** * **Events** * **Relationships** -* and data embedded in other [tracker objects](#webapi_nti_tracker_objects) +* and data embedded in other [tracker objects](#webapi_tracker_objects) -### Request parameters { #request-parameters } +### Request parameters { #webapi_tracker_import_request_parameters } The tracker importer supports the following parameters: @@ -446,7 +365,7 @@ as before, namely matching done using `UID`. The main difference for the user between synchronous and asynchronous imports is the timing of the API's response. Synchronous imports provide an immediate [import -summary](#webapi_nti_import_summary) once the import is finished. In contrast, asynchronous imports +summary](#webapi_tracker_import_summary) once the import is finished. In contrast, asynchronous imports return a reference to the import job right away. The progress of the import job can be tracked using this `response.location`. Here is an example of an asynchronous import response: @@ -846,7 +765,7 @@ A7rzcnZTe2T,ACTIVE,eBAyeGv0exc,Zj7UnCAulEk,RiLEKhWHlxZ,DwpbWkiqjMy,2023-02-12T23 See [Events CSV](#events-csv) in the export section for a more detailed definition of the CSV fields. -### Import Summary { #webapi_nti_import_summary } +### Import Summary { #webapi_tracker_import_summary } The Tracker API has two primary endpoints for consumers to acquire feedback from their imports. These endpoints are most relevant for async import jobs but are available for sync jobs as well. @@ -1292,7 +1211,7 @@ As previously stated, `GET /tracker/jobs/{uid}/report` can be retrieved using a In addition, all `reportModes` will return `status`, `stats`, `bundleReport` and `message` when applicable. -### Error Codes { #webapi_nti_error_codes } +### Error Codes { #webapi_tracker_error_codes } There are various error codes for different error scenarios. The following table has the list of error codes thrown from the new Tracker API, along with the error messages and some additional @@ -1422,7 +1341,7 @@ otherwise specified. | E5001 | "{0}" `{1}` cannot be deleted because "{2}" `{3}` referenced by it cannot be deleted. | The importer can't deleted a tracker object because a reference cannot be deleted. | | E9999 | 不适用 | Undefined error message. | -### 验证方式 { #webapi_nti_validation } +### Validation { #webapi_tracker_validation } While importing data using the tracker importer, a series of validations are performed to ensure the validity of the data. This section will describe some of the different types of validation performed @@ -1432,7 +1351,7 @@ to provide a better understanding if validation fails for your import. Each of the tracker objects has a few required properties that need to be present when importing data. For an exhaustive list of required properties, have a look at the [Tracker Object -section](#webapi_nti_tracker_objects). +section](#webapi_tracker_objects). When validating required properties, we are usually talking about references to other data or metadata. In these cases, there are three main criteria: @@ -1457,8 +1376,8 @@ on which property has a wrong format. Some examples of properties that are valid #### User access { #user-access } -All data imported will be validated based on the metadata ([Sharing](#webapi_nti_metadata_sharing)) -and the organisation units ([Organisation Unit Scopes](#webapi_nti_orgunit_scope)) referenced in the +All data imported will be validated based on the metadata ([Sharing](#webapi_tracker_metadata_sharing)) +and the organisation units ([Organisation Unit Scopes](#webapi_tracker_orgunit_scope)) referenced in the data. You can find more information about sharing and organisation unit scopes in the following sections. @@ -1511,7 +1430,7 @@ Some examples of configurable validations: These configurations will further change how validation is performed during import. -### Program Rules { #webapi_nti_program_rules } +### Program Rules { #webapi_tracker_program_rules } Users can configure [Program Rules](#webapi_program_rules), which adds conditional behavior to tracker forms. In addition to running these rules in the tracker apps, the tracker importer will @@ -1567,7 +1486,7 @@ information about side effects can be found in the following section. > > Program rules can be skipped during import using the `skipProgramRules` parameter. -### Side Effects { #webapi_nti_side_effects } +### Side Effects { #webapi_tracker_side_effects } After an import has been completed, specific tasks might be triggered as a result of the import. These tasks are what we refer to as "Side effects". These tasks perform operations that do not @@ -1589,7 +1508,7 @@ The following side effects are currently supported: > > Certain configurations can control the execution of side effects. `skipSideEffects` flag can be set during the import to skip side effects entirely. This parameter can be useful if you import something you don't want to trigger notifications for, as an example. -### Assign user to events { #webapi_nti_user_event_assignment } +### Assign user to events { #webapi_tracker_user_event_assignment } Specific workflows benefit from treating events like tasks, and for this reason, you can assign a user to an event. @@ -1623,7 +1542,7 @@ In this example, the user with uid `M0fCOxtkURr` will be assigned to the Event w To use this feature, the relevant program stage needs to have user assignment enabled, and the uid provided for the user must refer to a valid, existing user. -## Tracker Export { #webapi_nti_export } +## Tracker Export { #webapi_tracker_export } Tracker export endpoints allow you to retrieve the previously imported objects which are: @@ -1675,9 +1594,9 @@ The following endpoint supports standard parameters for pagination. The available organisation unit selection modes are `SELECTED`, `CHILDREN`, `DESCENDANTS`, `ACCESSIBLE`, `CAPTURE` and `ALL`. Each mode is explained in detail in [this -section](#webapi_nti_orgunit_scope). +section](#webapi_tracker_orgunit_scope). -#### Request parameter to filter responses { #webapi_nti_field_filter } +#### Request parameter to filter responses { #webapi_tracker_field_filter } All export endpoints accept a `fields` parameter which controls which fields will be returned in the JSON response. `fields` parameter accepts a comma separated list of field names or patterns. A few @@ -1757,8 +1676,8 @@ The endpoint returns a list of tracked entities that match the request parameter |`filter`|`String`|Comma-separated values of attribute filters.|Narrows response to tracked entities matching given filters. A filter is a colon separated property or attribute UID with optional operator and value pairs. Example: `filter=H9IlTX2X6SL:sw:A` with operator starts with `sw` followed by a value. Special characters like `+` need to be percent-encoded so `%2B` instead of `+`. Characters such as `:` (colon) or `,` (comma), as part of the filter value, need to be escaped by `/` (slash). Likewise, `/` needs to be escaped. Multiple operator/value pairs for the same property/attribute like `filter=AuPLng5hLbE:gt:438901703:lt:448901704` are allowed. Repeating the same attribute UID is not allowed. User needs access to the attribute to filter on it.| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return tracked entities belonging to provided organisation units| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return tracked entities belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|Program `UID`|A program `UID` for which tracked entities in the response must be enrolled into.| |`programStatus` **deprecated for removal in version 43 use `enrollmentStatus`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the tracked entities enrollment in the given program.| |`programStage`|`String`|`UID`|A program stage `UID` for which tracked entities in the response must have events for.| @@ -1864,7 +1783,7 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities`. ##### JSON { #json } Responses can be filtered on desired fields, see [Request parameter to filter -responses](#webapi_nti_field_filter) +responses](#webapi_tracker_field_filter) A JSON response can look like the following: @@ -2126,8 +2045,8 @@ Returns a list of events based on filters. |---|---|---|---| |`orgUnits`|`String`|Comma-separated list of organisation unit `UID`s.|Only return enrollments belonging to provided organisation units.| |`orgUnit` **deprecated for removal in version 42 use `orgUnits`**|`String`|Semicolon-separated list of organisation units `UID`s.|Only return enrollments belonging to provided organisation units.| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`program`|`String`|`uid`| Identifier of program| |`programStatus` **deprecated for removal in version 43 use `status`**|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`CANCELLED`|The status of the enrollment.| @@ -2332,8 +2251,8 @@ Returns a list of events based on the provided filters. |`followUp`|`boolean`| `true`|`false` | Whether event is considered for follow up in program. Defaults to `true`| |`trackedEntity`|`String`|`uid`|Identifier of tracked entity| |`orgUnit`|`String`|`uid`|Identifier of organisation unit| -|`orgUnitMode` see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| -|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_nti_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`orgUnitMode` see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| +|`ouMode` **deprecated for removal in version 42 use `orgUnitMode`** see [orgUnitModes](#webapi_tracker_orgunit_scope)|`String`|`SELECTED`|`CHILDREN`|`DESCENDANTS`|`ACCESSIBLE`|`CAPTURE`|`ALL`|The mode of selecting organisation units, can be. Default is `SELECTED`, which refers to the selected organisation units only.| |`status`|`String`|`ACTIVE`|`COMPLETED`|`VISITED`|`SCHEDULE`|`OVERDUE`|`SKIPPED` | Status of event| |`occurredAfter`|`DateTime`|[ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) | Filter for events which occurred after this date.| |`occurredBefore`|`DateTime`| [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601)| Filter for events which occurred up until this date.| @@ -2628,13 +2547,13 @@ The following rules apply to the query parameters. } ``` -## Tracker Access Control { #webapi_nti_access_control } +## Tracker Access Control { #webapi_tracker_access_control } Tracker has a few different concepts in regards to access control, like sharing, organisation unit scopes, ownership, and access levels. The following sections provide a short introduction to the different topics. -### Metadata Sharing { #webapi_nti_metadata_sharing } +### Metadata Sharing { #webapi_tracker_metadata_sharing } Sharing setting is standard DHIS2 functionality that applies to both Tracker and Aggregate metadata/data as well as dashboards and visualization items. At the core of sharing is the ability @@ -2680,7 +2599,7 @@ at hand. For more detailed information about data sharing, check out [Data sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html#data-sharing-for-event-based-programs). -### Organisation Unit Scopes { #webapi_nti_orgunit_scope } +### Organisation Unit Scopes { #webapi_tracker_orgunit_scope } Organisation units are one of the most fundamental objects in DHIS2. They define a universe under which a user is allowed to record and/or read data. There are three types of organisation units that @@ -2749,13 +2668,13 @@ scope is applied to the registration organisation unit of the TrackedEntity. Whe retrieving TrackedEntities, including specific program data, the organisation unit scope is applied to the Owner organisation unit. -### Tracker Program Ownership { #webapi_nti_ownership } +### Tracker Program Ownership { #webapi_tracker_ownership } A new concept called Tracker Ownership is introduced from 2.30. This introduces a new organisation unit association for a TrackedEntity - Program combination. We call this the Owner (or Owning) Organisation unit of a TrackedEntity in the context of a Program. The Owner organisation unit is used to decide access privileges when reading and writing tracker data related to a program. This, -along with the Program's [Access Level](#webapi_nti_access_level) configuration, decides the access +along with the Program's [Access Level](#webapi_tracker_access_level) configuration, decides the access behavior for Program-related data (Enrollments and Events). A user can access a TrackedEntity's Program data if the corresponding Owner OrganisationUnit for that TrackedEntity-Program combination falls under the user's organisation unit scope (Search/Capture). For Programs that are configured @@ -2767,7 +2686,7 @@ Tracker objects, the requested organisation unit must always be within the user' 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. -#### 跟踪器所有权优先：打破常规 { #webapi_nti_tracker_ownership_override } +#### Tracker Ownership Override: Break the Glass { #webapi_tracker_ownership_override } It is possible to temporarily override this ownership privilege for a program that is configured with an access level of *PROTECTED*. Any user will be able to temporarily gain access to the Program @@ -2780,7 +2699,7 @@ can be used: /api/tracker/ownership/override?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&reason=patient+showed+up+for+emergency+care -#### 跟踪器所有权转移 { #webapi_nti_tracker_ownership_transfer } +#### Tracker Ownership Transfer { #webapi_tracker_ownership_transfer } It is possible to transfer the ownership of a TrackedEntity-Program from one organisation unit to another. This will be useful in case of patient referrals or migrations. Only a user who has @@ -2790,7 +2709,7 @@ used: /api/tracker/ownership/transfer?trackedEntity=DiszpKrYNg8&program=eBAyeGv0exc&ou=EJNxP3WreNP -### Access Level { #webapi_nti_access_level } +### Access Level { #webapi_tracker_access_level } DHIS2 treats Tracker data with an extra level of protection. In addition to the standard feature of metadata and data protection through sharing settings, Tracker data are shielded with additional @@ -2820,7 +2739,7 @@ add an audit log entry on the data being accessed by the specific user. This access level is slightly more restricted. Data inside a PROTECTED program can only be accessed by users if the Owner organisation unit falls under the user's capture scope. However, a user who only has the Owner organisation unit in the search scope can gain temporary ownership by [breaking -the glass](#webapi_nti_tracker_ownership_override). The user has to provide a justification of why +the glass](#webapi_tracker_ownership_override). The user has to provide a justification of why they are accessing the data at hand. The system will then put a log of both the justification and access audit and provide temporary access for 3 hours to the user. Note that when breaking the glass, the Owner Organisation Unit remains unchanged, and only the user who has broken the glass @@ -2836,3 +2755,119 @@ who has access to the data can transfer the ownership of a TrackedEntity-Program another Organisation Unit. If ownership is transferred, the Owner Organisation Unit is updated. trackedEntities +## Working Lists { #working-lists } + +Working lists allows users to efficiently organizate their workflow. Users can save filters and +sorting preferences for working with tracked entities, enrollments and events. Tracked entities, +enrollments and events each have a dedicated API to manage working lists. + +### Program stage working lists { #program-stage-working-lists } + +Program stage working lists pre-established working lists relevant to a particular program stage. This functionality enables +users to save filters and sorting preferences that are related to program stages, facilitating the +organisation and management of their workflow. To interact with them, you'll need to use the +*/api/programStageWorkingLists* resource. These lists can be shared and follow the same sharing +pattern as any other metadata. When using the */api/sharing* the type parameter will be +*programStageWorkingLists*. + + /api/programStageWorkingLists + +#### Payload { #payload } + +The endpoint above can be used to get all program stage working lists. To get a single one, append +the working list id. This is the same in case you want to delete it. On the other hand, if you are +looking to create or update a program stage working list, besides the endpoint mentioned above, +you'll need to provide a payload in the following format: + +Table: Payload + +| Payload values | 描述 | 例 | +|---|---|---| +| 名称 | Name of the working list. Required. || +| 描述 | A description of the working list. || +| program | Object containing the id of the program. Required. | {"id" : "uy2gU8kTjF"} | +| programStage | Object containing the id of the program stage. Required. | {"id" : "oRySG82BKE6"} | +| programStageQueryCriteria | An object representing various possible filtering values. See *Program Stage Query Criteria* definition table below. + +Table: Program Stage Query Criteria + +| Criteria values | 描述 | 例 | +|---|---|---| +| eventStatus | The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED | "status":"VISITED" | +| eventCreatedAt | DateFilterPeriod object filtering based on the event creation date. | {"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"} | +| eventOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"TODAY"} | +| eventScheduledAt | DateFilterPeriod object filtering based on the event scheduled date. | {"type":"RELATIVE","period":"TODAY"} | +| enrollmentStatus | Any valid EnrollmentStatus. Possible values are ACTIVE, COMPLETED and CANCELLED. | "enrollmentStatus": "COMPLETED" | +| 跟进 | Indicates whether to filter enrollments marked for follow up or not | "followUp":true | +| enrolledAt | DateFilterPeriod object filtering based on the event enrollment date. | "enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"} | +| enrollmentOccurredAt | DateFilterPeriod object filtering based on the event occurred date. | {"type":"RELATIVE","period":"THIS_MONTH"} | +| orgUnit | A valid organisation unit UID | "orgUnit": "Rp268JB6Ne4" | +| ouMode | A valid OU selection mode | "ouMode": "SELECTED" | +| assignedUserMode | A valid user selection mode for events. Possible values are CURRENT, PROVIDED, NONE, ANY and ALL. If PROVIDED (or null), non-empty assignedUsers in the payload will be expected. | "assignedUserMode":"PROVIDED" | +| assignedUsers | A list of assigned users for events. To be used along with PROVIDED assignedUserMode above. | "assignedUsers":["DXyJmlo9rge"] | +| order | List of fields and its directions in comma separated values, the results will be sorted according to it. A single item in order is of the form "orderDimension:direction". | "order": "w75KJ2mc4zz:asc" | +| displayColumnOrder | Output ordering of columns | "displayColumnOrder":["w75KJ2mc4zz","zDhUuAYrxNC"] | +| dataFilters | A list of items that contains the filters to be used when querying events | "dataFilters":[{"dataItem": "GXNUsigphqK","ge": "10","le": "20"}] | +| attributeValueFilters | A list of attribute value filters. This is used to specify filters for attribute values when listing tracked entities | "attributeValueFilters":[{"attribute": "ruQQnf6rswq","eq": "15"}] | + +See an example payload below: + +```json +{ + "name": "Test WL", + "program": { + "id": "uy2gU8kT1jF" + }, + "programStage": { + "id": "oRySG82BKE6" + }, + "description": "Test WL definition", + "programStageQueryCriteria": { + "eventStatus": "VISITED", + "eventCreatedAt": { + "type": "ABSOLUTE", + "startDate": "2020-03-01", + "endDate": "2022-12-30" + }, + "eventScheduledAt": { + "type": "RELATIVE", + "period": "TODAY" + }, + "enrollmentStatus": "COMPLETED", + "followUp": true, + "enrolledAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "enrollmentOccurredAt": { + "type": "RELATIVE", + "period": "THIS_MONTH" + }, + "orgUnit": "Rp268JB6Ne4", + "ouMode": "SELECTED", + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "DXyJmlo9rge" + ], + "order": "w75KJ2mc4zz:asc", + "displayColumnOrder": [ + "w75KJ2mc4zz", + "zDhUuAYrxNC" + ], + "dataFilters": [ + { + "dataItem": "GXNUsigphqK", + "ge": "10", + "le": "20" + } + ], + "attributeValueFilters": [ + { + "attribute": "ruQQnf6rswq", + "eq": "15" + } + ] + } +} +``` + diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index b5fec1ed7..7c9eb734b 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/users.md" revision_date: '2024-03-08' tags: -- Develop - DHIS核心 主版 +- Develop --- # 用户数 { #users } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index 430410f19..ee0ee3095 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- Develop - DHIS核心 主版 +- Develop --- # 可视化 { #visualizations } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index 067d694f9..164b36b4d 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/audit.md" revision_date: '2024-05-21' tags: -- DHIS核心 主版 - Manage +- DHIS核心 主版 --- # 审核 { #audit } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index 2733718ff..c846b969b 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/user-impersonation.md" revision_date: '2024-02-08' tags: -- DHIS核心 主版 - Manage +- DHIS核心 主版 --- # 使用 DHIS2 中的用户模拟功能{ #user_impersonation } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index a36e6f064..36a18878d 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/installation.md" revision_date: '2024-04-28' tags: -- DHIS核心 主版 - Manage +- DHIS核心 主版 --- # 安装 { #installation } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index a1c3fccf8..fff94635f 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/monitoring.md" revision_date: '2023-09-25' tags: -- DHIS核心 主版 - Manage +- DHIS核心 主版 --- # 监控 { #monitoring } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index 0ba0a2fd4..504c71fb8 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/upgrading.md" revision_date: '2023-05-05' tags: -- DHIS核心 主版 - Manage +- DHIS核心 主版 --- # 正在升级 { #upgrading-dhis2 } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index 6b8ad9863..af1611689 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/sysadmin/SMS-reporting.md" revision_date: '2022-09-13' tags: -- DHIS核心 主版 - Manage +- DHIS核心 主版 --- # 使用网关进行SMS报告 { #sms_report_sending } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index a17352f14..cea2cda82 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-browsing.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.0 +- 使用 --- ## 浏览动作跟踪器 { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index 4f8f1490d..0c8dd1745 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-introduction.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.0 +- 使用 --- # 链接的Action Tracker仪表板和演示服务器 { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index 4eff74494..177730fcd 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-maintenance.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.0 +- 使用 --- # Action Tracker应用维护 { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index 46007180e..eab476612 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-planning.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.0 +- 使用 --- # 动作跟踪器中的动作计划 { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index f16d01e6f..f36c3d5b7 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/action_tracker/at-app-action-tracking.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.0 +- 使用 --- # 动作跟踪器中的动作跟踪 { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index 5f59c66f0..98c70a5a1 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-installation.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # 安装BNA应用程序 { #installing-the-bna-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index 57c171f46..2166f381f 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-maintenance.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # BNA 应用程序维护 { #bna-app-maintenance } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index bcc1538f9..2606928e1 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-analysis-and-interpretation.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # BNA 分析和解释 { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index 2f2d89aa5..ab4883f91 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bna-app-architecture.md" revision_date: '2022-03-10' tags: -- 使用 - App version 1.2.2 +- 使用 --- # BNA 应用架构 { #bna-app-architecture } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index 6bf76278f..daf588de8 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/bottleneck-analysis-dashboard-and-demo-server.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # 瓶颈分析仪表板和演示服务器{ #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index f3b930d90..58b3f6f26 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/navigating-the-bna-app.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # BNA 应用干预配置{ #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index f8be9d386..d3e664f1b 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/visualization-operations.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # 可视化操作{ #visualization-operations } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index 10d360f46..cf2c9010e 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/adopting-the-use-of-the-bna-app.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # 采用 BNA 应用程序{ #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index be993e1ea..db5e6ac47 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/capacity-building.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # 能力建设 { #capacity-building } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index 070c3caef..d5b646d41 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/end-user-training.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # 最终用户培训 { #end-user-training } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index a7499dd93..6e4e25efb 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/guide-to-bna-app-implementation.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # BNA 应用实施指南 { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index ef5ae93ff..c641cf7b7 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/integration-concepts-for-the-bna-app.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # BNA 应用程序的集成概念。 { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index c8e2a7daa..94ae825d2 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/opportunities-and-challenges.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # 机遇与挑战{ #opportunities-and-challenges } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index de4ef37fa..20231ea3d 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/hisptz/unicef-apps-docs/blob/master/src/commonmark/en/content/bna/planning-and-organising.md" revision_date: '2021-09-09' tags: -- 使用 - App version 1.2.2 +- 使用 --- # 规划和组织{ #planning-and-organising } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md index eacd12dbe..f0d36d566 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md index f62f85b66..8f804e8e7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用数据输入应用 { #data_entry_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md index 044fd1388..4140fbbb1 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 控制数据质量 { #control_data_quality } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index c0611ffab..320716cb2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 关于对象共享 { #sharing } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md index 1c3746af8..31efb4f33 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md index 2300ec08e..74613f82e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata.md" revision_date: '2022-10-28' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 配置元数据 { #maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md index 2cfe3528d..7c3393e1e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 在维护应用中配置程序 { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md index 6acba0566..5c2f213d8 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 配置报告功能 { #setting_up_reporting } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md index a9f66a0c3..60137b024 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/system-settings.md" revision_date: '2022-09-13' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 系统设置 { #settings } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md index 22e8165b5..53ec10671 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 用户权限 { #user_authorities } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index c1626500e..756f328c9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 管理用户，用户角色和用户组 { #manage_user_role_group } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md index 931c2b977..fced41c4d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-exchange.md" revision_date: '2023-02-16' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md index cc008d682..646126a89 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 导入/导出应用 { #import_export } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md index 7b3135ef0..99151fd8d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 配置元数据同步 { #metadata_sync } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md index 0e6fb8cbe..e37ad36e9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md index 1df8c1009..21e4d2d1f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/data-administration.md" revision_date: '2024-01-31' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 资料管理 { #data_admin } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md index 1722bad91..bcd0e3aa2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 数据存储管理器 { #datastore_manager_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md index 06a1176cc..4a0aab89e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- > **Caution** diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md index 71b46b4e7..55ff741b2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/mobile.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 移动 { #mobile } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md index 85d736bff..8802520ce 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 排程 { #scheduling } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index d2044dacc..248ef0b70 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 可视化使用情况统计 { #using_usage_analytics } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 6bdf9c1ab..b0c7267fd 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用捕获应用 { #capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 95d29ef18..030bb05dd 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用事件捕获应用 { #event_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index f5a551c52..4454b93b7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 使用Tracker Capture应用 { #tracker_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index b19041fbf..6b3ab9b31 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 关于数据维度 { #data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 7916a6d8f..3d38b12fa 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 附加数据维度 { #additional_data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index ad5ef66a7..05abd14ea 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 关系模型 { #relationship_model } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md index c8087722f..4fb2b59a2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/messaging.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 讯息传递 { #messages } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 8da462e93..981fdbd8f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 14ff4270f..8056e6271 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # 设置用户帐户首选项 { #user_account_preferences } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index caaa00218..657a076e0 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index bb2714784..460b2143e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # DHIS2常见问题 { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md index 6e79f689d..6cde342d6 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # DHIS2词汇表 { #dhis2_glossary } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 87201dfab..1e83a193a 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # DHIS2教程 { #dhis2_tutorials } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 69dd685c6..be2e10da2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 发布和升级说明 { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md index 8a8ca71a8..53f93d343 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 管理仪表板 { #dashboard } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md index 6d4512948..78a6f0242 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 使用数据可视化器应用 { #data_visualizer } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md index 054e00819..c3ffd583e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 使用事件报告应用 { #event_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md index 41b99dd12..079ce8e57 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 使用事件可视化器应用 { #event_visualizer_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md index f8c69b65f..0c0d092fe 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md index 74f05046c..66323946b 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 使用地图应用 { #using_maps } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md index 0b29cbb58..fae7fd31e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 报告应用程序中的报告功能 { #using_the_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md index 074423b43..68291bf48 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md index 9d415051a..e484d3d0c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md index 14cc4f782..7e48087f4 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md index 01daae1eb..683a9cf9c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 使用数据输入应用 { #data_entry_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md index c1fe95dc5..0ce9dc038 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 控制数据质量 { #control_data_quality } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 3518dd01f..9ccb834eb 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 关于对象共享 { #sharing } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md index 6c3aab3b9..8796212c2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md index 12b782857..537e6e5fc 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata.md" revision_date: '2023-07-20' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 配置元数据 { #maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md index fbf093c40..f0ec81df8 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-01-03' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 在维护应用中配置程序 { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md index d7b33fee9..95a13d12f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 配置报告功能 { #setting_up_reporting } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md index 37c6a75e3..cd5e9433f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/system-settings.md" revision_date: '2024-01-25' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 系统设置 { #settings } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md index 7debfb28c..5dade7b47 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 用户权限 { #user_authorities } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 8f54b9e66..20a65c897 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 管理用户，用户角色和用户组 { #manage_user_role_group } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md index ff9d26b7b..316dc1c82 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md index f3cab156c..7002880c4 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 导入/导出应用 { #import_export } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md index e8b3fbe36..c964da70d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 配置元数据同步 { #metadata_sync } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md index dd1097ecc..b3a1eebe8 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md index 27d799780..2b5c3a9a4 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-administration.md" revision_date: '2023-06-21' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 资料管理 { #data_admin } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md index 084281633..4255237f2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 数据存储管理器 { #datastore_manager_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md index 1165f7263..d6d01e5ac 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- > **Caution** diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md index 45a8106dd..ba64292d3 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/mobile.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 移动 { #mobile } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md index 18d0216bd..e6b37cde5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 排程 { #scheduling } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 9427fb7d5..3ecf68cb1 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 可视化使用情况统计 { #using_usage_analytics } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index f7943f696..7489b8e90 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 使用捕获应用 { #capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 802cf6c35..420801392 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 使用事件捕获应用 { #event_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 171f6f1b1..1bc466af0 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 使用Tracker Capture应用 { #tracker_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 7eb0e91a2..00d085648 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 关于数据维度 { #data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index b38007703..3bd6b5741 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 附加数据维度 { #additional_data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 7146ab9b1..92eb543c3 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 关系模型 { #relationship_model } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 20a21b0fc..bac0fda9c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/messaging.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 讯息传递 { #messages } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 3e6868041..dce3d1002 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index cada21dac..e24f9dfd0 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # 设置用户帐户首选项 { #user_account_preferences } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index ef788bd45..6b59d7c52 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # About demo server, D2 cluster and database design { #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index c3aaa7b43..2dce7b051 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # DHIS2常见问题 { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 183bfdd07..6238a81d7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # DHIS2词汇表 { #dhis2_glossary } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 9a3b63ca2..ead525f7e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # DHIS2教程 { #dhis2_tutorials } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 993d29c40..b55ebbee8 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 发布和升级说明 { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index fb54f1f8c..9bd74d5cd 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 管理仪表板 { #dashboard } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 46627c354..fd78efdcc 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用数据可视化器应用 { #data_visualizer } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index fe937e3bf..b5edb0cef 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用事件报告应用 { #event_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 25e7c678c..9fc8fc63b 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用事件可视化器应用 { #event_visualizer_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index 23fd825d3..5738bbe59 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index ff08ba0f1..97e00b9dc 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用地图应用 { #using_maps } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index cd73b6c4d..664794372 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 报告应用程序中的报告功能 { #using_the_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index 99f7e657e..0e61fec09 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index 4bbabf7cd..a70ea2663 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index 1564ece6f..909becf79 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index 43b59eb99..7602c63be 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-data-entry-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用数据输入应用 { #data_entry_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index d1a42bc10..211b6a740 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 控制数据质量 { #control_data_quality } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index e83830a74..3f842219d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 关于对象共享 { #sharing } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 252d15dd7..9e64af6de 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index b028ae8ff..cf44ae57d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 配置元数据 { #maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 650bc115f..3bf5b4e68 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 在维护应用中配置程序 { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 312d92e14..42dd7da4a 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 配置报告功能 { #setting_up_reporting } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index b98d58e11..6596bb0c5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 系统设置 { #settings } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 2c4198a45..99ad5ed0e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 用户权限 { #user_authorities } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index fb749398c..662a0644f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 管理用户，用户角色和用户组 { #manage_user_role_group } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index 2139652fe..b03d51488 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 37588bfc0..50e56b6b3 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 导入/导出应用 { #import_export } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index c6e41f0af..72795b10c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 配置元数据同步 { #metadata_sync } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index 1005a7914..fdb39857f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 519e6488a..1f917be55 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 资料管理 { #data_admin } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index df6b972d3..fa2b60ddb 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 数据存储管理器 { #datastore_manager_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 765228b85..eef87c234 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/app-management-app/blob/master/docs/user/installing-apps.md" revision_date: '2021-09-08' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- > **Caution** diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 83bb02176..7f90d87f7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/mobile.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 移动 { #mobile } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index ed81ec4e5..7def58024 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 排程 { #scheduling } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index fd57e6fc9..4f354e83a 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/usage-analytics-app/blob/master/docs/user/visualize-usage-statistics.md" revision_date: '2021-08-25' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 可视化使用情况统计 { #using_usage_analytics } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 1ccf80440..36b1b2e50 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用捕获应用 { #capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 13bcd2101..beebc3e6f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用事件捕获应用 { #event_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index a8bce7a57..480c0448c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 使用Tracker Capture应用 { #tracker_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index fd1d1e651..e417fbfe5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 关于数据维度 { #data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 1570053ca..6132afce3 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 附加数据维度 { #additional_data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index d667de86a..86c3f6d60 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 关系模型 { #relationship_model } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 25370ed68..2a28aa142 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/messaging.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 讯息传递 { #messages } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index f60ec8ef7..9abb94c7c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 73196f084..300c14661 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/user-profile-app/blob/master/docs/user/set-user-account-preferences.md" revision_date: '2021-10-21' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # 设置用户帐户首选项 { #user_account_preferences } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 0b56ce9ef..54c7ab1fb 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 关于演示服务器、D2 集群和数据库设计{ #moare_about_dhis2_server_database } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 0576eb399..7e52f4e98 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # DHIS2教程 { #dhis2_tutorials } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md index cd7ad204d..0eab2a702 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dashboard-app/blob/master/docs/dashboards.md" revision_date: '2023-06-09' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 管理仪表板 { #dashboard } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index e65447657..326aa8fa9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/data-visualizer-app/blob/master/docs/data-visualizer.md" revision_date: '2024-04-11' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 使用数据可视化器应用 { #data_visualizer } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index e7b1a62ad..1b040c31d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 使用事件报告应用 { #event_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index 665d818d2..d2c388aa9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 使用事件可视化器应用 { #event_visualizer_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index 34df18895..d3a281560 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" revision_date: '2024-01-30' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index 7a1ade951..35f3c6d7b 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-04-10' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 使用地图应用 { #using_maps } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md index aded653d6..bc6499eef 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/approval-app/blob/master/docs/user/approving_data.md" revision_date: '2021-11-17' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md index 7fc6d38fc..a1dfef09b 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index f012c25fc..d918385b9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 控制数据质量 { #control_data_quality } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index fc6e5ea37..bb37cc123 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 关于对象共享 { #sharing } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index 90ae71d32..7f426db20 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-the-gis-app.md" revision_date: '2024-04-05' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 配置 DHIS2 映射 { #gis_creating } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index f0227445c..938843fe9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 配置元数据 { #maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index 7802ae6ba..fdfb07204 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 在维护应用中配置程序 { #configure_programs_in_maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index e4ffd7946..427051ee5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/system-settings.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 系统设置 { #settings } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index c2490fabf..09b02434c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/user-authorities.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 用户权限 { #user_authorities } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 96403ae2a..39e5a21a8 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022年10月12日' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 管理用户，用户角色和用户组 { #manage_user_role_group } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index 58887e6a6..cf00e727d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index 04d9f745b..0df9ee5c7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/importexport-app.md" revision_date: '2024-03-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 导入/导出应用 { #import_export } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index a15941905..312d32831 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/configure-metadata-synchronizing.md" revision_date: '2024-05-28' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 配置元数据同步 { #metadata_sync } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index 7393d74c0..bf64a7a8c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/data-administration.md" revision_date: '2024-05-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 资料管理 { #data_admin } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 7ab0f441f..4f8308f1b 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/scheduling.md" revision_date: '2024-05-27' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 排程 { #scheduling } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 6bc619bf2..92eca6d57 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/capture-app/blob/master/docs/user/using-the-capture-app.md" revision_date: '2024-05-29' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 使用捕获应用 { #capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 1119fda15..8e8d1172e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 附加数据维度 { #additional_data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index bfe230405..eb9d15598 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # Personal access tokens { #personal_access_tokens }