From 93358b421edffb78d503aa24cd3cb4ad7fe11ad2 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 27 Jun 2024 21:25:00 +0000 Subject: [PATCH] chore: autopublish 2024-06-27T21:24:57Z --- .../am_ET/.cache_timestamp | 2 +- .../ar/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../cs/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../es_419/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../fr/.cache_timestamp | 2 +- ...FERENCE__DHIS-CORE-VERSION-232__web-api-md | 55 +- ...FERENCE__DHIS-CORE-VERSION-233__web-api-md | 97 +--- ...FERENCE__DHIS-CORE-VERSION-234__web-api-md | 148 ++--- ...FERENCE__DHIS-CORE-VERSION-235__web-api-md | 148 ++--- ...ENCE__DHIS-CORE-VERSION-MASTER__web-api-md | 169 ++---- ...DHIS-CORE-VERSION-233__developer-manual-md | 97 +--- ...DHIS-CORE-VERSION-234__developer-manual-md | 24 +- ...DHIS-CORE-VERSION-235__developer-manual-md | 24 +- ...DHIS-CORE-VERSION-236__developer-manual-md | 24 +- ...DHIS-CORE-VERSION-237__developer-manual-md | 216 +++----- ...DHIS-CORE-VERSION-238__developer-manual-md | 236 +++----- ...DHIS-CORE-VERSION-239__developer-manual-md | 249 +++------ ...DHIS-CORE-VERSION-240__developer-manual-md | 263 ++++----- ...S-CORE-VERSION-MASTER__developer-manual-md | 104 ++-- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 17 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 15 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 17 +- .../id_ID/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../ko/.cache_timestamp | 2 +- .../ko_KR/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../pt/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../ru/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../si/.cache_timestamp | 2 +- .../ur_PK/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../zh/.cache_timestamp | 2 +- ...CORE-VERSION-238__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-238__dhis2-user-manual-md | 15 +- ...CORE-VERSION-239__dhis2-end-user-manual-md | 15 +- ...HIS-CORE-VERSION-239__dhis2-user-manual-md | 15 +- ...CORE-VERSION-240__dhis2-end-user-manual-md | 13 +- ...HIS-CORE-VERSION-240__dhis2-user-manual-md | 13 +- ...E-VERSION-MASTER__dhis2-end-user-manual-md | 15 +- ...-CORE-VERSION-MASTER__dhis2-user-manual-md | 15 +- .../zh_CN/.cache_timestamp | 2 +- .../zh_TW/.cache_timestamp | 2 +- projects/docs-full-site/ar/.cache_timestamp | 2 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 2 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 4 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 445 +++++++++++++-- projects/docs-full-site/cs/.cache_timestamp | 2 +- ...-API__DHIS-CORE-VERSION-240__data-entry-md | 2 +- ...I__DHIS-CORE-VERSION-240__data-exchange-md | 2 +- ...API__DHIS-CORE-VERSION-240__event-hooks-md | 2 +- ...I__DHIS-CORE-VERSION-240__metadata-gist-md | 2 +- ...HE-API__DHIS-CORE-VERSION-240__metadata-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-240__route-md | 2 +- ...VERSION-240__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 5 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 6 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 4 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 445 +++++++++++++-- ...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 +- ...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 | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...-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 +- ...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 | 16 +- ...-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 +- ...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 | 16 +- ...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 +- ...R__WORKING-WITH-YOUR-ACCOUNT__messaging-md | 2 +- ...TH-YOUR-ACCOUNT__personal-access-tokens-md | 2 +- .../docs-full-site/es_419/.cache_timestamp | 2 +- ...API__DHIS-CORE-VERSION-240__event-hooks-md | 2 +- ...I__DHIS-CORE-VERSION-240__metadata-gist-md | 2 +- ...HE-API__DHIS-CORE-VERSION-240__metadata-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-240__route-md | 2 +- ...VERSION-240__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 5 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 6 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 4 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 445 +++++++++++++-- ...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 +- ...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 | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...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 +- ...VELOPING-WITH-THE-ANDROID-SDK__workflow-md | 2 +- ...THE-API__DHIS-CORE-VERSION-232__web-api-md | 55 +- ...THE-API__DHIS-CORE-VERSION-233__web-api-md | 94 +--- ...THE-API__DHIS-CORE-VERSION-234__web-api-md | 22 +- ...THE-API__DHIS-CORE-VERSION-235__web-api-md | 22 +- ...API__DHIS-CORE-VERSION-236__new-tracker-md | 18 +- ...THE-API__DHIS-CORE-VERSION-236__tracker-md | 22 +- ...HE-API__DHIS-CORE-VERSION-237__metadata-md | 7 +- ...API__DHIS-CORE-VERSION-237__new-tracker-md | 24 +- ...THE-API__DHIS-CORE-VERSION-237__tracker-md | 182 ++----- ...HE-API__DHIS-CORE-VERSION-238__metadata-md | 7 +- ...API__DHIS-CORE-VERSION-238__new-tracker-md | 24 +- ...THE-API__DHIS-CORE-VERSION-238__tracker-md | 200 +++---- ...HE-API__DHIS-CORE-VERSION-239__metadata-md | 11 +- ...API__DHIS-CORE-VERSION-239__new-tracker-md | 24 +- ...THE-API__DHIS-CORE-VERSION-239__tracker-md | 202 +++---- ...API__DHIS-CORE-VERSION-240__event-hooks-md | 2 +- ...I__DHIS-CORE-VERSION-240__metadata-gist-md | 2 +- ...HE-API__DHIS-CORE-VERSION-240__metadata-md | 12 +- ...G-THE-API__DHIS-CORE-VERSION-240__route-md | 2 +- ...VERSION-240__settings-and-configuration-md | 2 +- ...IS-CORE-VERSION-240__tracker-deprecated-md | 241 +++----- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 2 +- ...HE-API__DHIS-CORE-VERSION-241__metadata-md | 89 ++- ...IS-CORE-VERSION-241__tracker-deprecated-md | 319 ++++------- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 17 +- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 6 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 79 ++- ...__DHIS-CORE-VERSION-MASTER__new-tracker-md | 18 +- ...CORE-VERSION-MASTER__tracker-deprecated-md | 307 ++++------- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 474 +++++++++++++--- ...EILLANCE__ACUTE-FEBRILE-ILLNESS__design-md | 2 +- ...ERCULOSIS__TB-CASE-SURVEILLANCE__design-md | 2 +- ...NT__LOGISTICS__cold-chain-equipment-cce-md | 514 +++++++++--------- ...ENT__LOGISTICS__gs1-datamatrix-code-gs1-md | 2 +- ...TICS__health-care-product-catalogue-hpc-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 +- ...EILLANCE__ACUTE-FEBRILE-ILLNESS__design-md | 2 +- ...RVEILLANCE-TRACKER__VERSION-200__design-md | 298 ++++++++++ ...-CASE-SURVEILLANCE__VERSION-200__design-md | 301 ++++++++++ ...ERCULOSIS__TB-CASE-SURVEILLANCE__design-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 +- ...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 | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...-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 +- ...ADDITIONAL-INFORMATION__dhis2-tutorials-md | 2 +- ...ON-241__ANALYSING-DATA__data-visualizer-md | 2 +- ...RSION-241__ANALYSING-DATA__line-listing-md | 16 +- ...-CORE-VERSION-241__ANALYSING-DATA__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 +- ...TAINING-THE-SYSTEM__data-administration-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 +- ...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 | 16 +- ...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 +- projects/docs-full-site/ru/.cache_timestamp | 2 +- ...SION-238__ANALYSING-DATA__event-reports-md | 2 +- ...N-238__ANALYSING-DATA__event-visualizer-md | 2 +- ...RSION-238__ANALYSING-DATA__line-listing-md | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...-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 +- ...ON-MASTER__ANALYSING-DATA__line-listing-md | 14 +- projects/docs-full-site/si/.cache_timestamp | 2 +- projects/docs-full-site/zh/.cache_timestamp | 2 +- ...-API__DHIS-CORE-VERSION-240__data-entry-md | 2 +- ...I__DHIS-CORE-VERSION-240__data-exchange-md | 2 +- ...API__DHIS-CORE-VERSION-240__event-hooks-md | 2 +- ...I__DHIS-CORE-VERSION-240__metadata-gist-md | 2 +- ...HE-API__DHIS-CORE-VERSION-240__metadata-md | 2 +- ...G-THE-API__DHIS-CORE-VERSION-240__route-md | 2 +- ...VERSION-240__settings-and-configuration-md | 2 +- ...THE-API__DHIS-CORE-VERSION-240__tracker-md | 2 +- ...HE-API__DHIS-CORE-VERSION-MASTER__audit-md | 125 ++--- ...DHIS-CORE-VERSION-MASTER__data-exchange-md | 6 +- ...API__DHIS-CORE-VERSION-MASTER__metadata-md | 4 +- ...-API__DHIS-CORE-VERSION-MASTER__tracker-md | 445 +++++++++++++-- ...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 +- ...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 | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...-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 | 16 +- ...-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-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 | 16 +- ...RE-VERSION-MASTER__ANALYSING-DATA__maps-md | 2 +- ...-MASTER__APPROVING-DATA__approving-data-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 +- ...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 +- 1180 files changed, 6606 insertions(+), 4388 deletions(-) create mode 100644 projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE-TRACKER__VERSION-200__design-md create mode 100644 projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE__VERSION-200__design-md diff --git a/projects/dhis2-single-page-docs/am_ET/.cache_timestamp b/projects/dhis2-single-page-docs/am_ET/.cache_timestamp index cdc8a6fa2..a52a9feef 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-26T21:25:56Z \ No newline at end of file +2024-06-27T21:23:52Z \ 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 cdc8a6fa2..a52a9feef 100644 --- a/projects/dhis2-single-page-docs/ar/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ar/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:25:56Z \ No newline at end of file +2024-06-27T21:23:52Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md index af6abfefb..a95b0dc00 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.38 - Use +- DHIS core version 2.38 template: single.html --- @@ -4692,6 +4692,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md index c413b8c18..cbef69e5e 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.38 - Use +- DHIS core version 2.38 template: single.html --- @@ -5124,6 +5124,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md index 9a801889d..c0055fc28 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.39 - Use +- DHIS core version 2.39 template: single.html --- @@ -4439,6 +4439,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md index 69260fb2a..e914b24d1 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-239__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.39 - Use +- DHIS core version 2.39 template: single.html --- @@ -5073,6 +5073,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md index 181971211..010ca14ac 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: - DHIS core version 2.40 - Use @@ -4458,6 +4458,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md index 0e81ae6c6..56309bdcd 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: - DHIS core version 2.40 - Use @@ -5092,6 +5092,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md index 504900c8c..918cfbfa5 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version master - Use +- DHIS core version master template: single.html --- @@ -4453,6 +4453,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md index d142ae88b..ace7d1ae5 100644 --- a/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/ar/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version master - Use +- DHIS core version master template: single.html --- @@ -5088,6 +5088,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/cs/.cache_timestamp b/projects/dhis2-single-page-docs/cs/.cache_timestamp index c96aabcca..c4b44795e 100644 --- a/projects/dhis2-single-page-docs/cs/.cache_timestamp +++ b/projects/dhis2-single-page-docs/cs/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:26:09Z \ No newline at end of file +2024-06-27T21:23:58Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md index 67e52428a..f86181f2c 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.38 - Použití +- DHIS core version 2.38 template: single.html --- @@ -4371,6 +4371,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Použití aplikace Mapy { #using_maps } diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md index e8e379038..cd95347d1 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.38 - Použití +- DHIS core version 2.38 template: single.html --- @@ -4803,6 +4803,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Použití aplikace Mapy { #using_maps } 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 180cffd61..06e50d397 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-06-24' +revision_date: '2024-06-26' tags: -- DHIS základní verze 2.39 - Použití +- DHIS základní verze 2.39 template: single.html --- @@ -4218,6 +4218,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Použití aplikace Mapy { #using_maps } 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 b17e4cd9a..ed6872749 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-06-24' +revision_date: '2024-06-26' tags: -- DHIS základní verze 2.39 - Použití +- DHIS základní verze 2.39 template: single.html --- @@ -4852,6 +4852,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Použití aplikace Mapy { #using_maps } diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md index 17df5d34e..9a7f00c4b 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: - DHIS základní verze 2.40 - Použití @@ -4237,6 +4237,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Použití aplikace Mapy { #using_maps } diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md index 77bd93d57..54e7115ff 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: - DHIS základní verze 2.40 - Použití @@ -4871,6 +4871,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Použití aplikace Mapy { #using_maps } diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md index 98c0de63c..a2e1d608d 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS template: single.html --- @@ -4232,6 +4232,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Použití aplikace Mapy { #using_maps } diff --git a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md index 3892d9f73..43cdb8b84 100644 --- a/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- Hlavní verze jádra DHIS - Použití +- Hlavní verze jádra DHIS template: single.html --- @@ -4867,6 +4867,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Použití aplikace Mapy { #using_maps } diff --git a/projects/dhis2-single-page-docs/es_419/.cache_timestamp b/projects/dhis2-single-page-docs/es_419/.cache_timestamp index 88eb1c590..0013a0c7f 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-26T21:26:21Z \ No newline at end of file +2024-06-27T21:24:04Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md index 1f9f1524b..a5620d29c 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.38 - Uso +- DHIS core version 2.38 template: single.html --- @@ -4692,6 +4692,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md index fbbeea70a..acc794611 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-238__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.38 - Uso +- DHIS core version 2.38 template: single.html --- @@ -5124,6 +5124,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } 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 42c14b5d5..d6cae9669 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-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.39 - Uso +- DHIS core version 2.39 template: single.html --- @@ -4439,6 +4439,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } 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 a13dcc9ea..191761229 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-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version 2.39 - Uso +- DHIS core version 2.39 template: single.html --- @@ -5073,6 +5073,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md index 2886dfa82..d083eab76 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-end-user-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: - DHIS core version 2.40 - Uso @@ -4458,6 +4458,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md index 5f1d30550..09857b628 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-240__dhis2-user-manual-md @@ -1,5 +1,5 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: - DHIS core version 2.40 - Uso @@ -5092,6 +5092,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md index 91027b255..56117721d 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-end-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version master - Uso +- DHIS core version master template: single.html --- @@ -4453,6 +4453,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md index b6121776b..512ef5979 100644 --- a/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md +++ b/projects/dhis2-single-page-docs/es_419/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__dhis2-user-manual-md @@ -1,8 +1,8 @@ --- -revision_date: '2024-06-24' +revision_date: '2024-06-26' tags: -- DHIS core version master - Uso +- DHIS core version master template: single.html --- @@ -5088,6 +5088,17 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) # Using the Maps app { #using_maps } diff --git a/projects/dhis2-single-page-docs/fr/.cache_timestamp b/projects/dhis2-single-page-docs/fr/.cache_timestamp index ff80df5bc..7e7fe88fd 100644 --- a/projects/dhis2-single-page-docs/fr/.cache_timestamp +++ b/projects/dhis2-single-page-docs/fr/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:26:31Z \ No newline at end of file +2024-06-27T21:24:11Z \ 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 b13adef5d..4ba493292 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 @@ -14419,8 +14419,7 @@ tracked entity instances and programs are supported. -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : { "trackedEntity": "tracked-entity-id", @@ -14432,9 +14431,7 @@ For creating a new person in the system, you will be working with the } ] } -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : { "type": "Point", @@ -14454,8 +14451,7 @@ URL: /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : { "trackedEntity": "nEenWmSyUEp", @@ -14478,8 +14474,7 @@ To push this to the server you can use the cURL command like curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST -H "Content-Type: application/json" -u admin:district -v -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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() { "trackedEntityInstances": [ @@ -14542,9 +14537,7 @@ attributes/relationships in the current payload. A request parameter of 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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### Deleting a tracked entity instance { #webapi_deleting_tei } @@ -14558,8 +14551,7 @@ method. The URL is equal to the one above used for update. -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme { "trackedEntity": "tracked-entity-id", @@ -14581,8 +14573,7 @@ instance and at the same time enroll into a program. } ] } -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. curl -X POST -d @tei.json -H "Content-Type: application/json" -u user:pass http://server/api/29/trackedEntityInstances @@ -14591,8 +14582,7 @@ updating a new tracked entity instance. -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. { "trackedEntityType": "nEenWmSyUEp", @@ -14670,8 +14660,7 @@ the same time enroll into a program and create an event. Note: The example above can fail if provided UIDs are not present in the system. -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. curl -X POST -d @tei.json -H "Content-Type: application/json" -u user:pass http://server/api/29/trackedEntityInstances @@ -14684,9 +14673,7 @@ Tracked entity instance attributes that is using automatic generation of unique values has three endpoints that is 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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. > **Note** > @@ -14697,17 +14684,11 @@ when upgrading to 2.29. > 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 } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/29/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -14730,8 +14711,7 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : The expiration time can also be overridden at the time of generation, by adding the ?expiration=\ to the @@ -14760,8 +14740,7 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : Similar to the /generate endpoint, this endpoint can also specify the expiration time in the same way. By adding the @@ -14797,7 +14776,7 @@ expiration time in the same way. By adding the } ] -##### Reserved values { #reserved-values } +##### Valeurs réservées { #reserved-values } Reserved values is currently not accessible trough the api, however they are returned by the *generate* and *generateAndReserve*endpoints. The @@ -14850,7 +14829,7 @@ that was 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 } +#### Attributs d'image { #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 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 062f9f8d2..8ff162054 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 @@ -14989,19 +14989,13 @@ Pour obtenir la réponse dans le format PDF, vous pouvez envoyer une requête *P -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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. ### 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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances @@ -15009,8 +15003,7 @@ tracked entity instances and programs are supported. -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -15024,9 +15017,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -15045,8 +15036,7 @@ You can post the payload the the following URL: /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -15065,15 +15055,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -15127,35 +15116,21 @@ 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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. + +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### 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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -15179,8 +15154,7 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -15191,8 +15165,7 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -15269,8 +15242,7 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -15285,9 +15257,7 @@ Tracked entity instance attributes that is using automatic generation of unique values has three endpoints that is 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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. > **Note** > @@ -15298,17 +15268,11 @@ when upgrading to 2.29. > 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 } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -15333,11 +15297,9 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -15364,8 +15326,7 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : Similar to the /generate endpoint, this endpoint can also specify the expiration time in the same way. By adding the `?expiration=` @@ -15402,7 +15363,7 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #reserved-values } Reserved values is currently not accessible trough the api, however they are returned by the `generate` and `generateAndReserve` endpoints. The @@ -15455,14 +15416,9 @@ that was 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 } +#### Attributs d'image { #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. +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'image. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" @@ -15480,8 +15436,7 @@ curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image? -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances 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 66359c623..f5b8263e1 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 @@ -16099,19 +16099,13 @@ Pour obtenir la réponse dans le format PDF, vous pouvez envoyer une requête *P -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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. ### 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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances @@ -16119,8 +16113,7 @@ tracked entity instances and programs are supported. -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -16134,9 +16127,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -16155,8 +16146,7 @@ You can post the payload the following URL: /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -16175,15 +16165,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -16220,52 +16209,31 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. #### 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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. + +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### 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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -16289,8 +16257,7 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -16301,8 +16268,7 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -16379,8 +16345,7 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -16391,34 +16356,23 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -16437,17 +16391,11 @@ variables should only be supplied if you know what you are doing. -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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -16466,16 +16414,9 @@ adding the `?expiration=` to the request. -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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : Similar to the /generate endpoint, this endpoint can also specify the expiration time in the same way. By adding the `?expiration=` @@ -16512,11 +16453,9 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### { # } @@ -16560,19 +16499,11 @@ following table explains the properties of the reserved value object: -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. +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. -#### Image attributes { #image-attributes } +#### Attributs d'image { #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. +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'image. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" @@ -16590,8 +16521,7 @@ curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image? -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances 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 5534a0e1d..3e915007a 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 @@ -16478,19 +16478,13 @@ Pour obtenir la réponse dans le format PDF, vous pouvez envoyer une requête *P -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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. ### 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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances @@ -16498,8 +16492,7 @@ tracked entity instances and programs are supported. -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -16513,9 +16506,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -16534,8 +16525,7 @@ You can post the payload the following URL: /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -16554,15 +16544,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -16599,52 +16588,31 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. #### 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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. + +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### 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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -16668,8 +16636,7 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -16680,8 +16647,7 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -16758,8 +16724,7 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -16770,34 +16735,23 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -16816,17 +16770,11 @@ variables should only be supplied if you know what you are doing. -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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -16845,16 +16793,9 @@ adding the `?expiration=` to the request. -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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : Similar to the /generate endpoint, this endpoint can also specify the expiration time in the same way. By adding the `?expiration=` @@ -16891,11 +16832,9 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### { # } @@ -16939,19 +16878,11 @@ following table explains the properties of the reserved value object: -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. +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. -#### Image attributes { #image-attributes } +#### Attributs d'image { #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. +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'image. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" @@ -16969,8 +16900,7 @@ curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image? -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances 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 272ff14f7..1f65ff125 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 @@ -1475,12 +1475,7 @@ Le format de la charge est le suivant : -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : @@ -17696,19 +17691,13 @@ Pour supprimer le contenu JavaScript, vous pouvez utiliser une requête de type -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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. ### 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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances @@ -17716,8 +17705,7 @@ tracked entity instances and programs are supported. -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -17731,9 +17719,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -17742,18 +17728,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -17772,15 +17755,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -17817,52 +17799,31 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. #### 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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. + +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### 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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -17886,8 +17847,7 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -17898,8 +17858,7 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -17976,8 +17935,7 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -17988,34 +17946,23 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -18034,17 +17981,11 @@ variables should only be supplied if you know what you are doing. -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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -18063,20 +18004,11 @@ adding the `?expiration=` to the request. -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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -18109,11 +18041,9 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### { # } @@ -18157,19 +18087,11 @@ following table explains the properties of the reserved value object: -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. +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. -#### Image attributes { #image-attributes } +#### Attributs d'image { #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. +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'image. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" @@ -18187,8 +18109,7 @@ curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image? -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances 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 062f9f8d2..8ff162054 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 @@ -14989,19 +14989,13 @@ Pour obtenir la réponse dans le format PDF, vous pouvez envoyer une requête *P -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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. ### 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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances @@ -15009,8 +15003,7 @@ tracked entity instances and programs are supported. -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -15024,9 +15017,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -15045,8 +15036,7 @@ You can post the payload the the following URL: /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -15065,15 +15055,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -15127,35 +15116,21 @@ 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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. + +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### 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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -15179,8 +15154,7 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -15191,8 +15165,7 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -15269,8 +15242,7 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -15285,9 +15257,7 @@ Tracked entity instance attributes that is using automatic generation of unique values has three endpoints that is 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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. > **Note** > @@ -15298,17 +15268,11 @@ when upgrading to 2.29. > 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 } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -15333,11 +15297,9 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -15364,8 +15326,7 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : Similar to the /generate endpoint, this endpoint can also specify the expiration time in the same way. By adding the `?expiration=` @@ -15402,7 +15363,7 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #reserved-values } Reserved values is currently not accessible trough the api, however they are returned by the `generate` and `generateAndReserve` endpoints. The @@ -15455,14 +15416,9 @@ that was 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 } +#### Attributs d'image { #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. +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'image. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" @@ -15480,8 +15436,7 @@ curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image? -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances 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 c26d2769e..707d33d73 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 @@ -14549,17 +14549,17 @@ For PDF you can send a _POST_ request to the following URL with content-type `ap -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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 } +### Gestion des instances d'entités suivies { #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 } +#### Création d'une nouvelle instance d'entité suivie { #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: @@ -14611,7 +14611,7 @@ For example, let us create a new instance of a person tracked entity and specify } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```bash curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST @@ -14657,7 +14657,7 @@ To create multiple instances in one request you can wrap the payload in an outer 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 } +#### Mise à jour d'une instance d'entité suivie { #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: @@ -14667,11 +14667,11 @@ The payload has to contain all, even non-modified, attributes and relationships. 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 } +#### Suppression d'une instance d'entité suivie { #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 } +#### Création et inscription des instances d'entités suivies { #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. @@ -14709,7 +14709,7 @@ 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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. @@ -14795,7 +14795,7 @@ 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 } +#### Attributs d'instances d'entités suivies générés { #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. @@ -14820,7 +14820,7 @@ This endpoint will return a map of required and optional values, that the server } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. @@ -14841,7 +14841,7 @@ The expiration time can also be overridden at the time of generation, by adding } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). @@ -14943,7 +14943,7 @@ The API also supports a _dimension_ parameter. It can take three possible values curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=medium" ``` -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } +#### Requête pour des instances d'entité suivie { #webapi_tracked_entity_instance_query } To query for tracked entity instances you can interact with the `/api/trackedEntityInstances` resource. 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 2b0c73c5d..4eccbde0f 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 @@ -14855,17 +14855,17 @@ For PDF you can send a _POST_ request to the following URL with content-type `ap -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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 } +### Gestion des instances d'entités suivies { #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 } +#### Création d'une nouvelle instance d'entité suivie { #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: @@ -14917,7 +14917,7 @@ For example, let us create a new instance of a person tracked entity and specify } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```bash curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST @@ -14963,7 +14963,7 @@ To create multiple instances in one request you can wrap the payload in an outer 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 } +#### Mise à jour d'une instance d'entité suivie { #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: @@ -14973,11 +14973,11 @@ The payload has to contain all, even non-modified, attributes and relationships. 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 } +#### Suppression d'une instance d'entité suivie { #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 } +#### Création et inscription des instances d'entités suivies { #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. @@ -15015,7 +15015,7 @@ 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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. @@ -15101,7 +15101,7 @@ 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 } +#### Attributs d'instances d'entités suivies générés { #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. @@ -15126,7 +15126,7 @@ This endpoint will return a map of required and optional values, that the server } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. @@ -15147,7 +15147,7 @@ The expiration time can also be overridden at the time of generation, by adding } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). @@ -15249,7 +15249,7 @@ The API also supports a _dimension_ parameter. It can take three possible values curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=medium" ``` -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } +#### Requête pour des instances d'entité suivie { #webapi_tracked_entity_instance_query } To query for tracked entity instances you can interact with the `/api/trackedEntityInstances` resource. 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 d6106af90..4e61afe4d 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 @@ -16736,17 +16736,17 @@ Pour supprimer le contenu JavaScript, vous pouvez utiliser une requête de type # Tracker { #tracker } -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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 } +### Gestion des instances d'entités suivies { #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 } +#### Création d'une nouvelle instance d'entité suivie { #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: @@ -16798,7 +16798,7 @@ For example, let us create a new instance of a person tracked entity and specify } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```bash curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST @@ -16844,7 +16844,7 @@ To create multiple instances in one request you can wrap the payload in an outer 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 } +#### Mise à jour d'une instance d'entité suivie { #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: @@ -16854,11 +16854,11 @@ The payload has to contain all, even non-modified, attributes and relationships. 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 } +#### Suppression d'une instance d'entité suivie { #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 } +#### Création et inscription des instances d'entités suivies { #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. @@ -16896,7 +16896,7 @@ 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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. @@ -16982,7 +16982,7 @@ 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 } +#### Attributs d'instances d'entités suivies générés { #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. @@ -17007,7 +17007,7 @@ This endpoint will return a map of required and optional values, that the server } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. @@ -17028,7 +17028,7 @@ The expiration time can also be overridden at the time of generation, by adding } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). @@ -17130,7 +17130,7 @@ The API also supports a _dimension_ parameter. It can take three possible values curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=medium" ``` -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } +#### Requête pour des instances d'entité suivie { #webapi_tracked_entity_instance_query } To query for tracked entity instances you can interact with the `/api/trackedEntityInstances` resource. 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 50e9061f1..97f243d0a 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 @@ -1167,12 +1167,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : @@ -13093,24 +13088,17 @@ Pour supprimer le contenu JavaScript, vous pouvez utiliser une requête de type ## 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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. ### 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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -13124,9 +13112,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -13135,18 +13121,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -13165,15 +13148,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -13210,46 +13192,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. #### 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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. + +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### 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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -13273,8 +13234,7 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -13283,8 +13243,7 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -13361,8 +13320,7 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -13371,34 +13329,23 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" #### 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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -13415,17 +13362,11 @@ variables should only be supplied if you know what you are doing. ##### 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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -13442,20 +13383,11 @@ adding the `?expiration=` to the request. ##### 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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -13488,48 +13420,37 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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éé | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créé | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" @@ -13537,8 +13458,7 @@ curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image? #### Tracked entity instance query { #webapi_tracked_entity_instance_query } -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances @@ -15642,15 +15562,15 @@ The following table highlights the differences between the previous tracker impo |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Inscription**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`| |**Manifestation**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`| |**Remarque**|`storedDate`|`storedAt`| -|**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`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`| ### Tracker Export changelog (`GET`) { #tracker-export-changelog-get } @@ -15658,7 +15578,7 @@ The `GET` endpoints all conform to the same naming conventions reported in the p These tables highlight the old endpoint differences in request parameters for `GET` endpoints compared to the new -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| |`uo`|`orgUnit` (unité d'organisation)| @@ -15666,21 +15586,21 @@ These tables highlight the old endpoint differences in request parameters for `G |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`uo`|`orgUnit` (unité d'organisation)| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| 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 cca901730..4ab32f6f9 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 @@ -1203,12 +1203,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : @@ -14337,26 +14332,19 @@ Pour supprimer le contenu JavaScript, vous pouvez utiliser une requête de type # Tracker { #tracker } -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. -### Tracked entity instance management { #webapi_tracked_entity_instance_management } +### Gestion des instances d'entités suivies { #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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances -#### Creating a new tracked entity instance { #webapi_creating_tei } +#### Création d'une nouvelle instance d'entité suivie { #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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -14370,9 +14358,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -14381,18 +14367,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -14411,15 +14394,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -14456,46 +14438,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. -#### Updating a tracked entity instance { #webapi_updating_tei } +#### Mise à jour d'une instance d'entité suivie { #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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. -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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. -#### Deleting a tracked entity instance { #webapi_deleting_tei } +#### Suppression d'une instance d'entité suivie { #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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } +#### Création et inscription des instances d'entités suivies { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -14519,18 +14480,16 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -14607,44 +14566,32 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Attributs d'instances d'entités suivies générés { #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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -14659,19 +14606,13 @@ variables should only be supplied if you know what you are doing. } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -14686,22 +14627,13 @@ adding the `?expiration=` to the request. } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -14734,57 +14666,45 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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éé | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créé | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" ``` -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } +#### Requête pour des instances d'entité suivie { #webapi_tracked_entity_instance_query } -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances @@ -16931,15 +16851,15 @@ The following table highlights the differences between the previous tracker impo |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`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`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created`
`lastUpdated`
`createByUserInfo` (créé avec les informations d'utilisateur)
`lastUpdatedByUserInfo` (dernière mise à jour avec les informations d'utilisateur)|`createdAt`
`updatedAt`
`createdBy` (créé par)
`updatedBy` (mis à jour par)| +|**Inscription**|`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`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| > **Note** > @@ -16961,7 +16881,7 @@ The `GET` endpoints all conform to the same naming conventions reported in the p These tables highlight the old endpoint differences in request parameters for `GET` endpoints compared to the new -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| |`uo`|`orgUnit` (unité d'organisation)| @@ -16969,21 +16889,21 @@ These tables highlight the old endpoint differences in request parameters for `G |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`uo`|`orgUnit` (unité d'organisation)| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| 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 8fe5961d8..d0b75f356 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 @@ -1229,12 +1229,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : @@ -1639,9 +1634,9 @@ Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| | `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. | +| `geoJsonProperty` | `Chaîne` | _non défini_ | 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. | +| `attributeId` | `Chaîne` | _non défini_ | 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. | @@ -15093,26 +15088,19 @@ Pour supprimer le contenu JavaScript, vous pouvez utiliser une requête de type > feature you will have to postpone the migration until a new SYNC feature is > in place. -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. -### Tracked entity instance management { #webapi_tracked_entity_instance_management } +### Gestion des instances d'entités suivies { #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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances -#### Creating a new tracked entity instance { #webapi_creating_tei } +#### Création d'une nouvelle instance d'entité suivie { #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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -15126,9 +15114,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -15137,18 +15123,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -15167,15 +15150,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -15212,46 +15194,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. -#### Updating a tracked entity instance { #webapi_updating_tei } +#### Mise à jour d'une instance d'entité suivie { #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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. -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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. -#### Deleting a tracked entity instance { #webapi_deleting_tei } +#### Suppression d'une instance d'entité suivie { #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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } +#### Création et inscription des instances d'entités suivies { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -15275,18 +15236,16 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -15363,44 +15322,32 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Attributs d'instances d'entités suivies générés { #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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -15415,19 +15362,13 @@ variables should only be supplied if you know what you are doing. } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -15442,22 +15383,13 @@ adding the `?expiration=` to the request. } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -15490,69 +15422,54 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créés | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" ``` -#### File attributes { #file-attributes } +#### Attributs de fichier { #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. +Travailler avec les attributs de fichier ressemble beaucoup à travailler avec les valeurs de données d'image. La valeur d'un attribut de type fichier est l'identifiant de la ressource de fichier associée. Une requête GET à l'adresse +`/api/trackedEntityInstances///file` renvoie le contenu du fichier. ```bash curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file ``` -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } +#### Requête pour des instances d'entité suivie { #webapi_tracked_entity_instance_query } -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances @@ -17718,15 +17635,15 @@ The following table highlights the differences between the previous tracker impo |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`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`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created`
`lastUpdated`
`createByUserInfo` (créé avec les informations d'utilisateur)
`lastUpdatedByUserInfo` (dernière mise à jour avec les informations d'utilisateur)|`createdAt`
`updatedAt`
`createdBy` (créé par)
`updatedBy` (mis à jour par)| +|**Inscription**|`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`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| > **Note** > @@ -17748,7 +17665,7 @@ The `GET` endpoints all conform to the same naming conventions reported in the p These tables highlight the old endpoint differences in request parameters for `GET` endpoints compared to the new -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| |`uo`|`orgUnit` (unité d'organisation)| @@ -17756,21 +17673,21 @@ These tables highlight the old endpoint differences in request parameters for `G |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`uo`|`orgUnit` (unité d'organisation)| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| 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 017678a01..76b0559f1 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 @@ -1610,9 +1610,9 @@ Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| | `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. | +| `geoJsonProperty` | `Chaîne` | _non défini_ | 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. | +| `attributeId` | `Chaîne` | _non défini_ | 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. | @@ -3561,7 +3561,7 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | PHONE_NUMBER | La validation est basée sur cette expression rationnelle `^[0-9+\\N-(\N-)#\N.\Ns\N/ext-]{6,50}$`. La longueur maximale est de 50.
Exemples : +4733987937, (+47) 3398 7937, (47) 3398 7937.123 | EMAIL | Format général des email : abc@email.com | BOOLÉEN | `vrai` or `faux` -| TRUE_ONLY (vrai uniquement) | Only accept `true` +| TRUE_ONLY (vrai uniquement) | N'accepte que `true` | DATE | Utiliser le format `yyyy-MM-dd` | DATETIME (date et heure) | Utiliser le format `yyyy-MM-dd HH:mm:ssZ` ou `yyyy-MM-dd 'T'HH:mm:ss` | TEMPS | Utiliser le format `HH:mm` @@ -3572,11 +3572,11 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | INTEGER_POSITIVE | La valeur est un nombre entier positif | INTEGER_NEGATIVE | La valeur est un nombre entier négatif | INTEGER_ZERO_OR_POSITIVE | La valeur est un entier positif ou nul -| TRACKER_ASSOCIATE | Aucun +| TRACKER_ASSOCIÉ | Aucun | NOM D'UTILISATEUR | La valeur est un nom d'utilisateur pour un `utilisateur` existant | COORDINATE | Aucun | ORGANISATION_UNIT | La valeur est un UID valide d'une `unité d'organisation` existante -| REFERENCE | Aucun +| RÉFÉRENCE | Aucun | AGE | La valeur est une date de naissance. Utiliser le même format que pour le type DATE. | URL | La valeur est une URL valide | FILE_RESOURCE | La valeur est un UID valide d'une `ressource de fichier` existante @@ -17496,15 +17496,15 @@ Les noms des propriétés d'API ont été modifiés afin qu'ils soient cohérent |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`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`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created`
`lastUpdated`
`createByUserInfo` (créé avec les informations d'utilisateur)
`lastUpdatedByUserInfo` (dernière mise à jour avec les informations d'utilisateur)|`createdAt`
`updatedAt`
`createdBy` (créé par)
`updatedBy` (mis à jour par)| +|**Inscription**|`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`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| > **Note** > @@ -17520,31 +17520,28 @@ Les noms des propriétés d'API ont été modifiés afin qu'ils soient cohérent >} >``` -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } +### Journal des modifications (changelog) de l'importation Tracker (`POST`) { #tracker-import-changelog-post } -The previous tracker import endpoints +Les précédents points d'extrémité de l'importation Tracker * `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 +sont remplacés par le nouveau point d'extrémité * `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. +[Importation Tracker] (https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) décrit comment utiliser ce nouveau point d'extrémité. -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } +### Journal des modifications de l'exportation Tracker (`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. +En plus des noms modifiés indiqués dans [Noms de propriétés](#webapi_tracker_migration_names), certains paramètres de requête ont également été modifiés. The following tables list the differences in old and new request parameters for `GET` enpoints. -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| @@ -17553,48 +17550,41 @@ The following tables list the differences in old and new request parameters for |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`uo`|`orgUnit` (unité d'organisation)| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. -### Tracked entity instance management { #webapi_tracked_entity_instance_management } +### Gestion des instances d'entités suivies { #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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances -#### Creating a new tracked entity instance { #webapi_creating_tei } +#### Création d'une nouvelle instance d'entité suivie { #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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -17608,9 +17598,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -17619,18 +17607,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -17649,15 +17634,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -17694,46 +17678,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. -#### Updating a tracked entity instance { #webapi_updating_tei } +#### Mise à jour d'une instance d'entité suivie { #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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. -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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. -#### Deleting a tracked entity instance { #webapi_deleting_tei } +#### Suppression d'une instance d'entité suivie { #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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } +#### Création et inscription des instances d'entités suivies { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -17757,18 +17720,16 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -17845,44 +17806,32 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Attributs d'instances d'entités suivies générés { #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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -17897,19 +17846,13 @@ variables should only be supplied if you know what you are doing. } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -17924,22 +17867,13 @@ adding the `?expiration=` to the request. } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -17972,69 +17906,54 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créés | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" ``` -#### File attributes { #file-attributes } +#### Attributs de fichier { #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. +Travailler avec les attributs de fichier ressemble beaucoup à travailler avec les valeurs de données d'image. La valeur d'un attribut de type fichier est l'identifiant de la ressource de fichier associée. Une requête GET à l'adresse +`/api/trackedEntityInstances///file` renvoie le contenu du fichier. ```bash curl "http://server/api/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/file ``` -#### Tracked entity instance query { #webapi_tracked_entity_instance_query } +#### Requête pour des instances d'entité suivie { #webapi_tracked_entity_instance_query } -To query for tracked entity instances you can interact with the -`/api/trackedEntityInstances` resource. +Pour rechercher des instances d'entités suivies, vous pouvez interagir avec la ressource `/api/trackedEntityInstances`. /api/33/trackedEntityInstances 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 6098d68fc..0e3e5cc4a 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 @@ -628,7 +628,7 @@ Tableau : Paramètres de requête | pagination | vrai | faux | vrai | Indique s'il faut renvoyer les listes d'éléments sous forme de pages. | | page | nombre | 1 | Définit le numéro de page à renvoyer. | | taille de la page | nombre | 50 | Définit le nombre d'éléments à renvoyer pour chaque page. | -| Ordre | property:asc/iasc/desc/idesc || Order the output using a specified order, only properties that are both persisted and simple (no collections, idObjects etc) are supported. iasc and idesc are case insensitive sorting. If it is wanted to sort for more than one property, separate them using a comma. | +| Ordre | property:asc/iasc/desc/idesc || Ordonne la sortie dans un ordre spécifique. Seules les propriétés qui sont à la fois persistantes et simples (pas de collections, d'identifiants d'objets, etc.) sont prises en charge. iasc et idesc sont des tris insensibles à la casse. Si vous souhaitez trier plusieurs propriétés, séparez-les par une virgule. | Voici un exemple de comment ces paramètres peuvent être utilisés pour obtenir une liste complète de groupes d'éléments de données dans un format de réponse XML : @@ -1038,7 +1038,7 @@ Le _nom de l'entité_ utilise la notation camel case. Par exemple, le point d'ex /api/dataElements -> **_NOTE:_** When updating objects, all existing property values will be overwritten, even if the new value is null. Please use [JSON Patch API](#webapi_partial_updates) in case you want do partial update to an object. +>**_NOTE:_** Lors de la mise à jour des objets, toutes les valeurs des propriétés existantes seront écrasées, même si la nouvelle valeur est nulle. Veuillez utiliser l'[API de patch JSON](#webapi_partial_updates) si vous souhaitez effectuer une mise à jour partielle d'un objet. ### Création et mise à jour des paramètres { #webapi_metadata_create_update } @@ -1215,12 +1215,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : @@ -1623,9 +1618,9 @@ Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| | `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. | +| `geoJsonProperty` | `Chaîne` | _non défini_ | 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. | +| `attributeId` | `Chaîne` | _non défini_ | 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. | @@ -2175,11 +2170,11 @@ L'opération de fusion transfère toutes les associations de métadonnées de l' Les métadonnées suivantes sont mises à jour : -| Métadonnées | Propriété | Action taken | +| Métadonnées | Propriété | Mesure prise | |---------------------|--------------------------------------------|-----------------------------------------------------------------------------| | IndicatorGroup | membres | Indicateur source supprimé, indicateur cible ajouté | | Ensemble de données | des indicateurs | Indicateur source supprimé, indicateur cible ajouté | -| DataDimensionalItem | n/a | Tous les éléments de données associés à des sources seront reliés à la cible. | +| Élément dimensionnel de données | n/a | Tous les éléments de données associés à des sources seront reliés à la cible. | | Section | des indicateurs | Indicateur source supprimé, indicateur cible ajouté | | Configuration | Indicateurs infrastructurels (Groupe d'indicateurs) | Indicateur source supprimé, indicateur cible ajouté | | Indicateur | numérateur / dénominateur | Remplace toute référence source par la référence cible | @@ -3919,7 +3914,7 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | PHONE_NUMBER | La validation est basée sur cette expression rationnelle `^[0-9+\\N-(\N-)#\N.\Ns\N/ext-]{6,50}$`. La longueur maximale est de 50.
Exemples : +4733987937, (+47) 3398 7937, (47) 3398 7937.123 | EMAIL | Format général des email : abc@email.com | BOOLÉEN | `vrai` or `faux` -| TRUE_ONLY (vrai uniquement) | Only accept `true` +| TRUE_ONLY (vrai uniquement) | N'accepte que `true` | DATE | Utiliser le format `yyyy-MM-dd` | DATETIME (date et heure) | Utiliser le format `yyyy-MM-dd HH:mm:ssZ` ou `yyyy-MM-dd 'T'HH:mm:ss` | TEMPS | Utiliser le format `HH:mm` @@ -3930,11 +3925,11 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | INTEGER_POSITIVE | La valeur est un nombre entier positif | INTEGER_NEGATIVE | La valeur est un nombre entier négatif | INTEGER_ZERO_OR_POSITIVE | La valeur est un entier positif ou nul -| TRACKER_ASSOCIATE | Aucun +| TRACKER_ASSOCIÉ | Aucun | NOM D'UTILISATEUR | La valeur est un nom d'utilisateur pour un `utilisateur` existant | COORDINATE | Aucun | ORGANISATION_UNIT | La valeur est un UID valide d'une `unité d'organisation` existante -| REFERENCE | Aucun +| RÉFÉRENCE | Aucun | AGE | La valeur est une date de naissance. Utiliser le même format que pour le type DATE. | URL | La valeur est une URL valide | FILE_RESOURCE | La valeur est un UID valide d'une `ressource de fichier` existante @@ -3972,7 +3967,7 @@ En cas de succès, la réponse contiendra un nouveau `UID` de `Programme` et res La réponse contiendra également un en-tête `Location` (emplacement) avec un lien vers le `Programme` nouvellement créé. Par exemple, si le programme est exécuté localement, la valeur de `Location` sera `http://localhost:9090/api/programs/Program456b`. -#### Copy options { #copy-options } +#### Options de copie { #copy-options } L'API permet d'utiliser un préfixe personnalisé à titre facultatif, lequel sera ajouté aux propriétés suivantes. @@ -4010,7 +4005,7 @@ Si une propriété a dépassé sa limite de caractères, une erreur sera renvoy } ``` -If trying to copy a Program that is not found, a response like this will be returned: +Si l'utilisateur essaie de copier un programme qui n'est pas trouvé, une réponse de ce type sera renvoyée : ```json { "httpStatus": "Not Found", @@ -4035,10 +4030,10 @@ Un `Utilisateur` aura besoin des autorisations suivantes pour pouvoir copier un Un `Programme` doit avoir un des statuts suivants pour pouvoir être copié : - Accès public en `lecture` et en `écriture` -- A specific `User` to have sharing `read` & `write` access -- A `User` is part of a `UserGroup` that has sharing `read` & `write` access +- Un `Utilisateur` spécifique autorisé à partager les accès en `lecture` et en `écriture`. +- Un `utilisateur` faisant partie d'un `groupe d'utilisateurs` et qui est autorisé à partager les accès en `lecture` et en `écriture`. -If a `User` does not have the correct permissions, a `Forbidden` response is returned like so: +Si un `utilisateur` n'a pas les bonnes autorisations, une réponse `Forbidden` (d'interdiction) est renvoyée comme suit : ```json { @@ -4050,49 +4045,49 @@ If a `User` does not have the correct permissions, a `Forbidden` response is ret } ``` -### Points to note { #points-to-note } +### Points à noter { #points-to-note } -#### Deep and shallow copy { #deep-and-shallow-copy } +#### Copie profonde et copie superficielle { #deep-and-shallow-copy } -When a `Program` is copied, certain properties of the `Program` need different kinds of copying. It is important to be aware of what has been deep-copied and what has been shallow-copied. -First of all let's explain the difference between deep and shallow copying in this context. +Lorsqu'un `Programme` est copié, certaines propriétés du `Programme` nécessitent des types de copie différents. Il est important de savoir ce qui a été copié en profondeur et ce qui a été copié superficiellement. +Tout d'abord, expliquons la différence entre la copie profonde et la copie superficielle dans ce contexte. -##### Deep copy { #deep-copy } +##### Copie profonde { #deep-copy } -A deep copy in this context means that a completely new instance of a `Program` or `Program` property has been created with its own unique identifiers. These include amongst others: +Dans ce contexte, une copie profonde signifie qu'une instance entièrement nouvelle d'un `Programme` ou d'une propriété de `Programme` a été créée avec ses propres identifiants uniques. Il s'agit entre autres de : - identifiant - uid -Deep copies of `Program` properties will all belong to the newly-created `Program` copy. +Les copies profondes des propriétés de `programme` feront toutes partie de la copie du `programme` nouvellement créée. -##### Shallow copy { #shallow-copy } +##### Copie superficielle { #shallow-copy } -A shallow copy in this context means that an existing `Program` property will be reused by the newly-created `Program` or `Program` property. +Dans ce contexte, une copie superficielle signifie qu'une propriété de `programme` existante sera réutilisée par le `programme` ou la propriété de `programme` nouvellement créé(e). -#### Properties that get deep copied { #properties-that-get-deep-copied } +#### Propriétés qui ont été copiées en profondeur { #properties-that-get-deep-copied } -All properties below have been deep copied. Anything not in included in this table means that it has been shallow copied. +Toutes les propriétés ci-dessous ont été copiées en profondeur. Si une propriété ne figure pas dans ce tableau, cela signifie qu'elle a été copié superficiellement. -| Objet | Property of | +| Objet | Propriété de | |--------------------------------|--------------| | Programme | | -| ProgramSection | Programme | +| Section de programme | Programme | | Indicateur de programme | Programme | -| ProgramRuleVariable | Programme | +| Variable de règle de programme | Programme | | Étape du programme | Programme | -| ProgramStageSection | Étape du programme | -| ProgramStageSectionDataElement | Étape du programme | +| Section d'une étape de programme | Étape du programme | +| Élément de données d'une section d'étape de programme | Étape du programme | | Inscription | | -> **Note** +> **Remarque** > -> The following properties have been set as empty as an initial approach. This approach should keep things simple to start off with. +> Les propriétés suivantes ont été définies comme vides dans une première approche. Cette approche devrait permettre de simplifier les choses pour commencer. | Objet | Propriété | |-------------------------------|-------------------| -| Indicateur de programme | groups | -| ProgramStageSection | programIndicators | +| Indicateur de programme | groupes | +| Section d'une étape de programme | Indicateurs de programme | | Inscription | événements | @@ -18277,7 +18272,7 @@ To override the expiration time, add `?expiration=` to the reque } ``` -#### Generate and reserve value endpoint { #webapi_generate_reserve_values } +#### Point d'extrémité de génération et de réservation de valeur { #webapi_generate_reserve_values } Offline clients can use this endpoint to reserve a number of unique IDs for later use when registering new tracked entity instances. The number of IDs to generate can be specified with the `numberToReserve` parameter (default is 1). @@ -18315,27 +18310,22 @@ To override the default expiration time of 60 days, add `?expiration=/merge | Parameter name | Description | Type | Allowed values | @@ -3060,28 +3358,47 @@ To merge a Potential Duplicate, i.e. the two tracked entities the Potential Dupl The endpoint accepts a single parameter, `mergeStrategy`, which determines the strategy used when merging. For the `AUTO` strategy, the server will attempt to merge the two tracked entities automatically without user input. This strategy only allows merging tracked entities without conflicting data (see examples below). The `MANUAL` strategy 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 evaluates the mergability of the two tracked entities and merges them if they are deemed mergable. The mergability is based on whether the two tracked entities have any conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible conflicts include: + +The automatic merge evaluates the mergability of the two tracked entities and merges them if they +are deemed mergeable. The mergability is based on whether the two tracked entities have any +conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible +conflicts include: + - The same attribute has different values in each tracked entity. - Both tracked entities are enrolled in the same program. - Tracked entities have different types. If any conflict is encountered, an error message 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 to the original. This includes attribute values, enrollments (including events), and relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is marked as `MERGED`. - -When requesting an automatic merge, a payload is not required and will be ignored. +When no conflicts are found, all data in the duplicate that is not already in the original will be +moved to the original. This includes attribute values, enrollments (including events), and +relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is +marked as `MERGED`. When requesting an automatic merge, a payload is not required and will be +ignored. #### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when there are resolvable conflicts or when not all the data needs to be moved during the 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 involves the user explicitly requesting to move data, there are some additional checks: -- 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 entities (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) + +The manual merge is suitable when there are resolvable conflicts or when not all the data needs to +be moved during the 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 involves the user explicitly requesting to move data, there are some +additional checks: + +- 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 entities (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 entities 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 was just created, but not enrolled for example. +When a manual merge is requested without a payload, we are telling the API to merge the two tracked +entities 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 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: -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"], @@ -3090,12 +3407,20 @@ Otherwise, if a manual merge is requested with a payload, the payload refers to } ``` -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. +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 entities 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 entities 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. +Currently it is not possible to merge tracked entities 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 +entities 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. diff --git a/projects/docs-full-site/cs/.cache_timestamp b/projects/docs-full-site/cs/.cache_timestamp index 7b27a057d..450e0b703 100644 --- a/projects/docs-full-site/cs/.cache_timestamp +++ b/projects/docs-full-site/cs/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:20:56Z \ No newline at end of file +2024-06-27T21:19:18Z \ No newline at end of file diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md index 84f067650..29dd5bd21 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md index f26906271..e8d1d0b28 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Výměna dat { #data-exchange } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md index 22e257f7a..353f7aab1 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md index 78dae008a..31cb40459 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md index 449e89e3d..5492dd0bb 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata.md" revision_date: '2024-04-26' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Metadata { #metadata } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 6bc6f728a..0bcb86a31 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/route.md" revision_date: '2023-05-09' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Route { #route } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index 7f22482ed..5b0453b93 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-01-26' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Nastavení a konfigurace { #settings-and-configuration } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index a30980a43..4b368b91f 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" revision_date: '2024-05-23' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Trasovač { #tracker } 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..fc6fc9845 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" -revision_date: '2023-06-23' +revision_date: '2024-06-24' tags: - Vývoj - Hlavní verze jádra DHIS @@ -43,6 +43,7 @@ Example: Get audits for data element `BOSZApCrBni`, org unit `DiszpKrYNg8` and c /api/33/audits/dataValue?de=BOSZApCrBni&ou=DiszpKrYNg8&co=TkDhg29x18A ### Audity hodnot dat trasovaných entit { #webapi_tracked_entity_data_value_audits } +**deprecated for removal in version 43 use [tracked entity data value change log endpoint](https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md#event-data-value-change-logs--webapi_event_data_value_change_logs-)** Koncový bod pro audity hodnot dat sledovaných entit se nachází na: @@ -77,6 +78,8 @@ Example: Get audits for org unit `O6uvpzGd5pu` including descendant org units in ### Audity hodnot atributu trasované entity { #webapi_tracked_entity_attribute_value_audits } +**deprecated for removal in version 43 use [tracked entity attribute change log endpoint](https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md#tracked-entity-attribute-value-change-logs--webapi_tracker_attribute_change_logs-)** + The endpoint for tracked entity attribute value audits is located at: ``` 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..10205974b 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" -revision_date: '2023-09-27' +revision_date: '2024-06-26' tags: - Vývoj - Hlavní verze jádra DHIS @@ -396,6 +396,7 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.filters.items | Array/String | Ne | Item identifiers for the filter. | | source.requests.inputIdScheme | Řetězec | Ne | Input ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputDataElementIdScheme | Řetězec | Ne | Output data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | +| source.requests.outputDataItemIdScheme | Řetězec | Ne | Output data item ID scheme applies to data elements, indicators and program indicators, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Řetězec | Ne | Output org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Řetězec | Ne | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target | Objekt | Ano | Target for aggregate data exchange. | @@ -410,6 +411,9 @@ The aggregate data exchange data model / payload is described in the following s | source.target.request.orgUnitIdScheme | Řetězec | Ne | Input org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Řetězec | Ne | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.idScheme | Řetězec | Ne | Input general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | +| source.target.request.importStrategy | Řetězec | Ne | Import strategy, can be `CREATE_AND_UPDATE`, `CREATE`, `UPDATE`, `DELETE`. | +| source.target.request.skipAudit | Boolean | Ne | Přeskočit audit, což znamená, že hodnoty auditu nebudou generovány. Zlepšuje výkon za cenu schopnosti auditovat změny. Vyžaduje oprávnění „F_SKIP_DATA_IMPORT_AUDIT“. | +| source.target.request.dryRun | Boolean | Ne | Zda uložit změny na serveru nebo jen vrátit souhrn importu. | ### Error handling { #error-handling } 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..92e383dba 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 @@ -1,12 +1,12 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" -revision_date: '2024-05-21' +revision_date: '2024-06-03' tags: - Vývoj - Hlavní verze jádra DHIS --- -# Metadata { #metadata } +# Metadata { #webapi_metadata } ## Schémata identifikátorů { #webapi_identifier_schemes } 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 394d936f7..5f7a8c888 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,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-06-20' +revision_date: '2024-06-26' tags: - Vývoj - Hlavní verze jádra DHIS @@ -162,7 +162,6 @@ point out any exceptional cases between these two. `Relationships` are objects that link together two other tracker objects. The constraints each side of the relationship must conform to are based on the `Relationship Type` of the `Relationship`. - | Vlastnictví | Popis | Požadované | Neměnný | Typ | Příklad | |---|---|---|---|---|---| | vztah | Identifikátor vztahu. Vygenerováno, pokud není dodáno. | Ne | Ano | String:Uid | ABCDEF12345 | @@ -2137,6 +2136,67 @@ Příklad odpovědi json: The response will be the same as the collection endpoint but referring to a single tracked entity, although it might have multiple rows for each attribute. +#### Tracked entity attribute value change logs { #webapi_tracker_attribute_change_logs } +`GET /api/tracker/trackedEntities/{uid}/changeLogs` + +This endpoint retrieves change logs for the attributes of a specific tracked entity. It returns a list of all tracked entity attributes that have changed over time for that entity. + +|Parametr|Typ|Povolené hodnoty| +|---|---|---| +|path `/{uid}`|`String`|Tracked entity `UID`.| +|`program`|`String`|Program `UID` (optional).| + +##### Tracked entity attribute value change logs response example { #tracked-entity-attribute-value-change-logs-response-example } + +Příklad odpovědi json: + +```json +{ + "pager":{ + "page":1, + "pageSize":10 + }, + "changeLogs":[ + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:51:16.433", + "type":"UPDATE", + "change":{ + "dataValue":{ + "dataElement":"bx6fsa0t90x", + "previousValue":"true", + "currentValue":"false" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:50:32.966", + "type":"CREATE", + "change":{ + "dataValue":{ + "dataElement":"ebaJjqltK5N", + "currentValue":"0" + } + } + } + ] +} +``` + +The change log type can be `CREATE`, `UPDATE`, or `DELETE`. +`CREATE` and `DELETE` will always hold a single value: the former shows the current value, and the latter shows the value that was deleted. UPDATE will hold two values: the previous and the current. + ### Enrollments (`GET /api/tracker/enrollments`) { #enrollments-get-apitrackerenrollments } Pro zápisy jsou vyhrazeny dva koncové body: @@ -2582,6 +2642,83 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities` The response will be the same as the collection endpoint but referring to a single event, although it might have multiple rows for each data element value. +#### Event data value change logs { #webapi_event_data_value_change_logs } +`GET /api/tracker/events/{uid}/changeLogs` + +This endpoint retrieves change logs for the data values of a specific event. It returns a list of all event data values that have changed over time for that particular event. + +|Parametr|Typ|Povolené hodnoty| +|---|---|---| +|path `/{uid}`|`String`|Event `UID`.| + +##### Event data value change logs response example { #event-data-value-change-logs-response-example } + +Příklad odpovědi json: + +```json +{ + "pager":{ + "page":1, + "pageSize":10 + }, + "changeLogs":[ + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T15:43:36.342", + "type":"DELETE", + "change":{ + "dataValue":{ + "dataElement":"UXz7xuGCEhU", + "previousValue":"12" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T15:43:27.175", + "type":"CREATE", + "change":{ + "dataValue":{ + "dataElement":"UXz7xuGCEhU", + "currentValue":"12" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:51:16.433", + "type":"UPDATE", + "change":{ + "dataValue":{ + "dataElement":"bx6fsa0t90x", + "previousValue":"true", + "currentValue":"false" + } + } + } + ] +} +``` + +The change log type can be `CREATE`, `UPDATE`, or `DELETE`. +`CREATE` and `DELETE` will always hold a single value: the former shows the current value, and the latter shows the value that was deleted. UPDATE will hold two values: the previous and the current. + + ### Relationships (`GET /api/tracker/relationships`) { #relationships-get-apitrackerrelationships } Relationships are links between two entities in the Tracker. These entities can be tracked entities, @@ -2865,71 +3002,138 @@ 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. +Working lists allow users to efficiently organize their workflow by saving filters and sorting +preferences for tracked entities, enrollments, and events. Each type of working list—tracked +entities, enrollments, and events—has a dedicated API for management. + +Working lists are [metadata](#webapi_metadata), making them shareable and subject to the same +[sharing](#webapi_sharing) patterns as other metadata. When using the +[`/api/sharing`](#webapi_sharing) endpoint, the type parameter should be set to the name of the +working list API. For example, use trackedEntityInstanceFilter for [tracked entity working +lists](#tracked-entity-instance-filters). + +Since working lists are metadata refer to [metadata](#webapi_metadata) on how to create, update and +delete metadata. The following sections describe the payloads of each of the working lists +endpoints. + +### Tracked entity working lists { #tracked-entity-working-lists } + +Create, update and delete tracked entity working lists using + + /api/trackedEntityInstanceFilters + +#### Payload { #payload } + +Tabulka: Datový obsah + +| Vlastnictví | Popis | Příklad | +|---|---|---| +|název|Name of the working list. Required.|| +|popis|A description of the working list.|| +|sortOrder|The sort order of the working list.|| +|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 + +| Vlastnictví | Popis | Příklad | +|---|---|---| +|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 tracked entities enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED|| +|followUp|When this parameter is true, the working list only returns tracked entities that have an enrollment with `folloWup=true`.|| +|organisationUnit|Chcete-li zadat uid organizační jednotky|`{"organisationUnit": "a3kGcGDCuk7"}`| +|ouMode|To specify the organisation unit selection mode. Possible values are SELECTED| CHILDREN|DESCENDANTS|ACCESSIBLE|CAPTURE|ALL|`"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"`| +|programStage|To specify a programStage uid to filter on. tracked entities will be filtered based on presence of enrollment in the specified program stage.|`"programStage"="a3kGcGDCuk6"`| +|trackedEntityType|To specify a trackedEntityType filter tracked entities on.|`{"trackedEntityType"="a3kGcGDCuk6"}`| +|trackedEntities|To specify a list of trackedEntityInstances to use when querying tracked entities.|`"trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"]`| +|enrollmentCreatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on enrollment created date.|`"enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" }`| +|enrollmentIncidentDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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" }`| +|eventStatus|The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED|`"status":"VISITED"`| +|eventDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on event date.|`"eventDate": {"startBuffer": -5,"endBuffer": 5, "type": "RELATIVE" }`| +|lastUpdatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on last updated date.|`"lastUpdatedDate": {"startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" }`| + +Tabulka: Definice filtrů událostí + +| Vlastnictví | Popis | Příklad | +|---|---|---| +|programStage|Which programStage the tracked entity 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|FilterPeriod 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"]`| + +Table: FilterPeriod definition + +| Vlastnictví | Popis | Příklad | +|---|---|---| +|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| + +#### Query Request Parameters { #query-request-parameters } + +Tabulka: Instance sledované entity filtruje parametry dotazu + +| Parametr dotazu | Popis | +|---|---| +|program|Identifikátor programu. Omezí filtry na daný program.| ### 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*. +Create, update and delete program stage working lists using /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. +|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"}] | +|eventStatus|The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED|`"status":"VISITED"`| +|eventCreatedAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object filtering based on the event creation date.|`{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}`| +|eventOccurredAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object filtering based on the event occurred date.|`{"type":"RELATIVE","period":"TODAY"}`| +|eventScheduledAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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](#webapi_tracker_workinglists_common_objects) object filtering based on the event enrollment date.|`"enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}`| +|enrollmentOccurredAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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", + "description": "Test WL definition", "program": { "id": "uy2gU8kT1jF" }, "programStage": { "id": "oRySG82BKE6" }, - "description": "Test WL definition", "programStageQueryCriteria": { "eventStatus": "VISITED", "eventCreatedAt": { @@ -2979,11 +3183,98 @@ See an example payload below: } ``` -## Potenciální duplikáty { #potential-duplicates } +### Event working lists { #event-working-lists } + +Create, update and delete event working lists using + + /api/eventFilters + +#### Payload { #payload } + +Tabulka: Datový obsah + +| Vlastnictví | Popis | Příklad | +|---|---|---| +|název|Name of the working list.|"name":"Můj pracovní seznam"| +|popis|A description of the working list.|"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 + +| Vlastnictví | Popis | Příklad | +|---|---|---| +|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"]| +|displayColumnOrder |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](#webapi_tracker_workinglists_common_objects) 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](#webapi_tracker_workinglists_common_objects) object date filtering based on event date.|"eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" }| +|dueDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on due date.|"dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" }| +|lastUpdatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on last updated date.|"lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" }| + +See an example payload below: + +```json +{ + "name": "event working list", + "program": "VBqh0ynB2wv", + "eventQueryCriteria": { + "eventDate": { + "period": "LAST_WEEK", + "type": "RELATIVE" + }, + "dataFilters": [ + { + "ge": "35", + "le": "70", + "dataItem": "qrur9Dvnyt5" + } + ], + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "CotVI2NX0rI", + "xE7jOejl9FI" + ], + "status": "ACTIVE", + "order": "occurredAt:desc", + "displayColumnOrder": [ + "occurredAt", + "status", + "assignedUser", + "qrur9Dvnyt5", + "oZg33kd9taw" + ] + } +} +``` + +### Common Objects { #webapi_tracker_workinglists_common_objects } -Potential duplicates are records identified by the data deduplication feature as possibly being duplicates. Due to the nature of this feature, the API endpoint has certain restrictions. +Tabulka: Definice objektu DateFilterPeriod -A potential duplicate represents a pair of records suspected to be duplicates. +| Vlastnictví | Popis | Příklad | +|---|---|---| +|typ|Určete, zda je typ období typu ABSOLUTE | RELATIVNÍ|`"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`| + + +## Potenciální duplikáty { #potential-duplicates } + +Potential duplicates are records identified by the data deduplication feature as possibly being +duplicates. Due to the nature of this feature, the API endpoint has certain restrictions. A +potential duplicate represents a pair of records suspected to be duplicates. To retrieve a list of potential duplicates, use the following endpoint: @@ -3017,7 +3308,8 @@ To create a new potential duplicate, use this endpoint: POST /api/potentialDuplicates -The payload you provide must include the UIDs of the original and duplicate tracked entities. New potential duplicates are open by default. +The payload you provide must include the UIDs of the original and duplicate tracked entities. New +potential duplicates are open by default. ```json { @@ -3029,7 +3321,7 @@ The payload you provide must include the UIDs of the original and duplicate trac | Stavový kód | Popis |---|---| | 400 | Input original or duplicate is null or has invalid uid -| 403 | User do not have access to read origianl or duplicate TEs +| 403 | User do not have access to read original or duplicate TEs | 404 | TE not found | 409 | Pair of original and duplicate TEs already existing @@ -3047,9 +3339,15 @@ To update the status of a potential duplicate, use the following endpoint: | 400 | Nelze aktualizovat potenciální duplikát, který je již ve stavu MERGED ### Merging Tracked Entities { #merging-tracked-entities } -Tracked entities can be merged together if they are deemed viable. To initiate a merge, the first step is to define two tracked entities as a Potential Duplicate. The merge endpoint moves data from the duplicate tracked entity to the original tracked entity and deletes the remaining data of the duplicate. -To merge a Potential Duplicate, i.e. the two tracked entities the Potential Duplicate represents, use the following endpoint: +Tracked entities can be merged together if they are deemed viable. To initiate a merge, the first +step is to define two tracked entities as a Potential Duplicate. The merge endpoint moves data from +the duplicate tracked entity to the original tracked entity and deletes the remaining data of the +duplicate. + +To merge a Potential Duplicate, i.e. the two tracked entities the Potential Duplicate represents, +use the following endpoint: + POST /api/potentialDuplicates//merge | Název parametru | Popis | Typ | Povolené hodnoty | @@ -3059,28 +3357,47 @@ To merge a Potential Duplicate, i.e. the two tracked entities the Potential Dupl The endpoint accepts a single parameter, `mergeStrategy`, which determines the strategy used when merging. For the `AUTO` strategy, the server will attempt to merge the two tracked entities automatically without user input. This strategy only allows merging tracked entities without conflicting data (see examples below). The `MANUAL` strategy 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 evaluates the mergability of the two tracked entities and merges them if they are deemed mergable. The mergability is based on whether the two tracked entities have any conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible conflicts include: + +The automatic merge evaluates the mergability of the two tracked entities and merges them if they +are deemed mergeable. The mergability is based on whether the two tracked entities have any +conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible +conflicts include: + - The same attribute has different values in each tracked entity. - Both tracked entities are enrolled in the same program. - Tracked entities have different types. If any conflict is encountered, an error message 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 to the original. This includes attribute values, enrollments (including events), and relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is marked as `MERGED`. - -When requesting an automatic merge, a payload is not required and will be ignored. +When no conflicts are found, all data in the duplicate that is not already in the original will be +moved to the original. This includes attribute values, enrollments (including events), and +relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is +marked as `MERGED`. When requesting an automatic merge, a payload is not required and will be +ignored. #### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when there are resolvable conflicts or when not all the data needs to be moved during the 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 involves the user explicitly requesting to move data, there are some additional checks: -- Vztah nemůže být mezi originálem a duplikátem (To má za následek neplatný vztah odkazující na sebe) -- Relationship cannot be of the same type and to the same object in both tracked entities (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) + +The manual merge is suitable when there are resolvable conflicts or when not all the data needs to +be moved during the 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 involves the user explicitly requesting to move data, there are some +additional checks: + +- 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 entities (IE. +between original and other, and duplicate and other; This would result in a duplicate relationship) 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 entities 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 was just created, but not enrolled for example. +When a manual merge is requested without a payload, we are telling the API to merge the two tracked +entities 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 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: -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"], @@ -3089,12 +3406,20 @@ V opačném případě, pokud je požadováno ruční sloučení s datovou čás } ``` -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. +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 entities 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 entities 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. +Currently it is not possible to merge tracked entities 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 +entities 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. 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 652e97e1d..7325e2160 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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # 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 c267c5bd8..782119f99 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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # 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 8c9078b67..d3fc41c8c 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-06-18' tags: -- Správa - Hlavní verze jádra DHIS +- Správa --- # 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 ea00e1e21..0ac3bbabb 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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # 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 e989ab67d..baffc0516 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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # 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 f1fb76312..6eeba277b 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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # 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__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 0ee7e2b6d..da3af1042 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: '2024-06-07' 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..0089148a2 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Použití - DHIS core version 2.38 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 574676342..14f2b4ada 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-06-24' 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..44cfb0324 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Použití - DHIS základní verze 2.39 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 da155d9c0..76ad60aeb 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-06-24' 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..1588a814f 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Použití - DHIS základní verze 2.40 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 0db2c2e67..6fcd15e7d 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-06-24' 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/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 1a81ea50f..a99e6fd5d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS základní verze 2.40 +- Použití --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index c18bdd894..2a1174a98 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS základní verze 2.40 +- Použití --- # Vztahový model { #relationship_model } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md index b29af872f..533af8aad 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS základní verze 2.40 +- Použití --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 9caa21330..de2335a1c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS základní verze 2.40 +- Použití --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 918e22036..a926c1d75 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index c8c79bce1..6ecdd5c28 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md index 3d792c6de..43f1de65a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 49aac097e..22809706f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index c712d94dc..0b93363a3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md index 2a155eb8c..6c6712ad8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 468799fe3..11844e121 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md index 070eea840..feb9528d1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md index 409488539..569dffd51 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index 514af0024..c856f19a5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md index 73181c298..be5e00fe5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md index e5f72e43a..cd469d2f4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md index c68b6c223..5a6dab5ca 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md index 01311194b..f72c7129f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md index eb7745ce3..efd8c2166 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md index e28bb9405..8e8bb4118 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md index c9e54f040..1d1573b84 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 3eddcc2ac..164b836e3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md index 9093dbab7..f3dc2211b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md index 3709512b1..524ad04e1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md index 48251d3bf..7b83f6d0f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md index 8d0093878..c6671d6de 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md index e5747e8ef..68c7718f6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md index 8e6e04943..401d1292a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index edf8ec7dd..a0188d9ef 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md index 8acedcc1e..fceb679ad 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md index 8d841fde5..36b2f04ec 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md index b8f993362..23aeeab28 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md index c56756b54..ebbe4532c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md index 6748a32bf..57ea36d97 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md index 2ee4d924b..43dd9affb 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-241__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 1f6057e82..1509c636e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md index 8cb6374b3..71a26030a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md index 0969c376d..33aacfe13 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 0e5690148..6df6851c3 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 25a3d3e04..e0f85f44c 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/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-06-24' tags: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 34e58a03f..b92c1da36 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 1b75a884d..5d2f00b41 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 64dbbf8a6..87a6e1a4e 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 5edd4117b..02eb3fcc8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index b549b70ca..419e15fa1 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Vztahový model { #relationship_model } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md index c60691232..f0d59c5c6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index df481a720..9cef82508 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- Použití --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 7f0623e48..74a3c476d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-241__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/cs/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: -- Použití - DHIS core version 2.41 +- 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-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 52a822485..edf288d38 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index fcab6866b..71e83e543 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/cs/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: '2024-06-07' tags: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md index 1b9f6853d..6ce71742d 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Slovník DHIS2 { #dhis2_glossary } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md index 1f7559455..6a80a62ca 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Výukové programy DHIS2 { #dhis2_tutorials } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md index 152cfcaf0..19b375c55 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Správa ovládacích panelů { #dashboard } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md index 4909dd156..723eb73d6 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Použití aplikace Data Visualizer { #data_visualizer } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md index f751a5e74..9c2e5e2ac 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md index 90f3e11d0..683f59975 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index 3d01df4ec..920acf5c2 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md index cd0d9ea3e..7042d04aa 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Použití aplikace Mapy { #using_maps } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md index 0c912f9f8..d69d383d8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__APPROVING-DATA__approving-data-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md index cf2dc1dae..544bae39b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Schválení dat { #data_approval_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md index 4db844049..da136f9a5 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md index d28cdd6eb..059d58982 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index b38ae3e1c..995f4ca61 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/cs/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: '2024-06-18' tags: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md index 6098c3698..b0378c825 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Kontrola kvality dat { #control_data_quality } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index c27350a7f..a04b4ea1a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # O sdílení objektů { #sharing } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md index 86e4aa565..2964e5897 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md index bbcdd326a..becce7714 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Nakonfigurujte metadata { #maintenance_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md index 55aeb5f67..77551eb25 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/cs/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-06-18' tags: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md index 1627731ee..61740a247 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Nakonfigurujte funkčnost sestavy { #setting_up_reporting } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md index 6d7fed935..d13ee02b0 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Nastavení systému { #settings } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md index f21a7e5e8..813135fe4 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Uživatelské oprávnění { #user_authorities } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 75bd6389e..6ddee3839 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md index 42376b0a4..69d79e9df 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md index e50bafe69..a74d2d372 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Aplikace Import / export { #import_export } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md index 7c59f30fe..bbf0873a8 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Konfigurace synchronizace metadat { #metadata_sync } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md index e3b6a9362..1baa7d93b 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Konfigurace SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md index d069c3104..28b647a8a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Správa dat { #data_admin } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md index eeb5b3861..b1c5bf440 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- 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-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md index 240f1262c..2839df5e7 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- > **Caution** diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md index 92dd071d4..a66e9e375 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Mobilní IT { #mobile } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md index 3b82f8ecb..5376d2bea 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Plánování { #scheduling } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 14d7662cd..d8a86a331 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Vizualizujte statistiky využití { #using_usage_analytics } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index 3fd054e8f..a27baba7f 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/cs/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-06-24' tags: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Použití aplikace Capture { #capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 56eb2d23f..5ffa08119 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Použití aplikace Event Capture { #event_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 68785c60c..b58e4ec07 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Použití aplikace Tracker Capture { #tracker_capture_app } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index e6636295d..0556c3d21 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # O dimenzích dat { #data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 1f1d48d8e..ae5867e5a 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Další dimenze dat { #additional_data_dimensions } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 6093c03a2..d6fbc83cf 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Zprávy { #messages } diff --git a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 4676f6d8e..83c953641 100644 --- a/projects/docs-full-site/cs/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/cs/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: -- Použití - Hlavní verze jádra DHIS +- Použití --- # Osobní přístupové tokeny { #personal_access_tokens } diff --git a/projects/docs-full-site/es_419/.cache_timestamp b/projects/docs-full-site/es_419/.cache_timestamp index 380a66ca2..e1d3379fd 100644 --- a/projects/docs-full-site/es_419/.cache_timestamp +++ b/projects/docs-full-site/es_419/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:21:45Z \ No newline at end of file +2024-06-27T21:20:13Z \ No newline at end of file diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md index fac60843f..041626580 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md index 7b3d9d7d7..f937cb8f8 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md index fb47c73c0..def002337 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata.md" revision_date: '2024-04-26' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Metadata { #metadata } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 558507390..76db044d8 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/route.md" revision_date: '2023-05-09' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Route { #route } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index 7df394985..8b6b1da19 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-01-26' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Settings and configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index 1f6288c37..8627243eb 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Tracker { #tracker } 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..ff004af42 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" -revision_date: '2023-06-23' +revision_date: '2024-06-24' tags: - Desarrollar - DHIS core version master @@ -43,6 +43,7 @@ Example: Get audits for data element `BOSZApCrBni`, org unit `DiszpKrYNg8` and c /api/33/audits/dataValue?de=BOSZApCrBni&ou=DiszpKrYNg8&co=TkDhg29x18A ### Auditorías de valor de datos de entidades Tracked { #webapi_tracked_entity_data_value_audits } +**deprecated for removal in version 43 use [tracked entity data value change log endpoint](https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md#event-data-value-change-logs--webapi_event_data_value_change_logs-)** The endpoint for tracked entity data value audits is located at: @@ -77,6 +78,8 @@ Example: Get audits for org unit `O6uvpzGd5pu` including descendant org units in ### Auditorías de valor de atributo de entidad Tracked { #webapi_tracked_entity_attribute_value_audits } +**deprecated for removal in version 43 use [tracked entity attribute change log endpoint](https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md#tracked-entity-attribute-value-change-logs--webapi_tracker_attribute_change_logs-)** + The endpoint for tracked entity attribute value audits is located at: ``` 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..8e6456afb 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" -revision_date: '2023-09-27' +revision_date: '2024-06-26' tags: - Desarrollar - DHIS core version master @@ -396,6 +396,7 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.filters.items | Array/String | No | Item identifiers for the filter. | | source.requests.inputIdScheme | Cadena | No | Input ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputDataElementIdScheme | Cadena | No | Output data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | +| source.requests.outputDataItemIdScheme | Cadena | No | Output data item ID scheme applies to data elements, indicators and program indicators, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | Cadena | No | Output org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | Cadena | No | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target | Object | Sí | Target for aggregate data exchange. | @@ -410,6 +411,9 @@ The aggregate data exchange data model / payload is described in the following s | source.target.request.orgUnitIdScheme | Cadena | No | Input org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | Cadena | No | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.idScheme | Cadena | No | Input general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | +| source.target.request.importStrategy | Cadena | No | Import strategy, can be `CREATE_AND_UPDATE`, `CREATE`, `UPDATE`, `DELETE`. | +| source.target.request.skipAudit | Booleano | No | Skip audit, meaning audit values will not be generated. Improves performance at the cost of ability to audit changes. Requires authority "F_SKIP_DATA_IMPORT_AUDIT". | +| source.target.request.dryRun | Booleano | No | Whether to save changes on the server or just return the import summary. | ### Error handling { #error-handling } 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..9e71c1b4f 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 @@ -1,12 +1,12 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" -revision_date: '2024-05-21' +revision_date: '2024-06-03' tags: - Desarrollar - DHIS core version master --- -# Metadata { #metadata } +# Metadata { #webapi_metadata } ## Identifier schemes { #webapi_identifier_schemes } 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 0b616169b..63a8107f7 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,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-06-20' +revision_date: '2024-06-26' tags: - Desarrollar - DHIS core version master @@ -162,7 +162,6 @@ point out any exceptional cases between these two. `Relationships` are objects that link together two other tracker objects. The constraints each side of the relationship must conform to are based on the `Relationship Type` of the `Relationship`. - | Property | Descripción | Requerido | Immutable | Tipo | Example | |---|---|---|---|---|---| | relationship | The identifier of the relationship. Generated if not supplied. | No | Sí | String:Uid | ABCDEF12345 | @@ -2138,6 +2137,67 @@ An example of a json response: The response will be the same as the collection endpoint but referring to a single tracked entity, although it might have multiple rows for each attribute. +#### Tracked entity attribute value change logs { #webapi_tracker_attribute_change_logs } +`GET /api/tracker/trackedEntities/{uid}/changeLogs` + +This endpoint retrieves change logs for the attributes of a specific tracked entity. It returns a list of all tracked entity attributes that have changed over time for that entity. + +|Parámetros|Tipo|Allowed values| +|---|---|---| +|path `/{uid}`|`String`|Tracked entity `UID`.| +|`program`|`String`|Program `UID` (optional).| + +##### Tracked entity attribute value change logs response example { #tracked-entity-attribute-value-change-logs-response-example } + +An example of a json response: + +```json +{ + "pager":{ + "page":1, + "pageSize":10 + }, + "changeLogs":[ + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:51:16.433", + "type":"UPDATE", + "change":{ + "dataValue":{ + "dataElement":"bx6fsa0t90x", + "previousValue":"true", + "currentValue":"false" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:50:32.966", + "type":"CREATE", + "change":{ + "dataValue":{ + "dataElement":"ebaJjqltK5N", + "currentValue":"0" + } + } + } + ] +} +``` + +The change log type can be `CREATE`, `UPDATE`, or `DELETE`. +`CREATE` and `DELETE` will always hold a single value: the former shows the current value, and the latter shows the value that was deleted. UPDATE will hold two values: the previous and the current. + ### Enrollments (`GET /api/tracker/enrollments`) { #enrollments-get-apitrackerenrollments } Two endpoints are dedicated to enrollments: @@ -2583,6 +2643,83 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities` The response will be the same as the collection endpoint but referring to a single event, although it might have multiple rows for each data element value. +#### Event data value change logs { #webapi_event_data_value_change_logs } +`GET /api/tracker/events/{uid}/changeLogs` + +This endpoint retrieves change logs for the data values of a specific event. It returns a list of all event data values that have changed over time for that particular event. + +|Parámetros|Tipo|Allowed values| +|---|---|---| +|path `/{uid}`|`String`|Event `UID`.| + +##### Event data value change logs response example { #event-data-value-change-logs-response-example } + +An example of a json response: + +```json +{ + "pager":{ + "page":1, + "pageSize":10 + }, + "changeLogs":[ + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T15:43:36.342", + "type":"DELETE", + "change":{ + "dataValue":{ + "dataElement":"UXz7xuGCEhU", + "previousValue":"12" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T15:43:27.175", + "type":"CREATE", + "change":{ + "dataValue":{ + "dataElement":"UXz7xuGCEhU", + "currentValue":"12" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:51:16.433", + "type":"UPDATE", + "change":{ + "dataValue":{ + "dataElement":"bx6fsa0t90x", + "previousValue":"true", + "currentValue":"false" + } + } + } + ] +} +``` + +The change log type can be `CREATE`, `UPDATE`, or `DELETE`. +`CREATE` and `DELETE` will always hold a single value: the former shows the current value, and the latter shows the value that was deleted. UPDATE will hold two values: the previous and the current. + + ### Relationships (`GET /api/tracker/relationships`) { #relationships-get-apitrackerrelationships } Relationships are links between two entities in the Tracker. These entities can be tracked entities, @@ -2866,71 +3003,138 @@ 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. +Working lists allow users to efficiently organize their workflow by saving filters and sorting +preferences for tracked entities, enrollments, and events. Each type of working list—tracked +entities, enrollments, and events—has a dedicated API for management. + +Working lists are [metadata](#webapi_metadata), making them shareable and subject to the same +[sharing](#webapi_sharing) patterns as other metadata. When using the +[`/api/sharing`](#webapi_sharing) endpoint, the type parameter should be set to the name of the +working list API. For example, use trackedEntityInstanceFilter for [tracked entity working +lists](#tracked-entity-instance-filters). + +Since working lists are metadata refer to [metadata](#webapi_metadata) on how to create, update and +delete metadata. The following sections describe the payloads of each of the working lists +endpoints. + +### Tracked entity working lists { #tracked-entity-working-lists } + +Create, update and delete tracked entity working lists using + + /api/trackedEntityInstanceFilters + +#### Payload { #payload } + +Table: Payload + +| Property | Descripción | Example | +|---|---|---| +|name|Name of the working list. Required.|| +|Descripción|A description of the working list.|| +|sortOrder|The sort order of the working list.|| +|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 + +| Property | Descripción | Example | +|---|---|---| +|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 tracked entities enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED|| +|followUp|When this parameter is true, the working list only returns tracked entities that have an enrollment with `folloWup=true`.|| +|organisationUnit|To specify the uid of the organisation unit|`{"organisationUnit": "a3kGcGDCuk7"}`| +|ouMode|To specify the organisation unit 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"`| +|programStage|To specify a programStage uid to filter on. tracked entities will be filtered based on presence of enrollment in the specified program stage.|`"programStage"="a3kGcGDCuk6"`| +|trackedEntityType|To specify a trackedEntityType filter tracked entities on.|`{"trackedEntityType"="a3kGcGDCuk6"}`| +|trackedEntities|To specify a list of trackedEntityInstances to use when querying tracked entities.|`"trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"]`| +|enrollmentCreatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on enrollment created date.|`"enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" }`| +|enrollmentIncidentDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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" }`| +|eventStatus|The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED|`"status":"VISITED"`| +|eventDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on event date.|`"eventDate": {"startBuffer": -5,"endBuffer": 5, "type": "RELATIVE" }`| +|lastUpdatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on last updated date.|`"lastUpdatedDate": {"startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" }`| + +Table: Event filters definition + +| Property | Descripción | Example | +|---|---|---| +|programStage|Which programStage the tracked entity 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|FilterPeriod 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: FilterPeriod definition + +| Property | Descripción | Example | +|---|---|---| +|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| + +#### Query Request Parameters { #query-request-parameters } + +Table: Tracked entity instance filters query parameters + +| Query parameter | Descripción | +|---|---| +|program|Program identifier. Restricts filters to the given program.| ### 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*. +Create, update and delete program stage working lists using /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. +|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"}] | +|eventStatus|The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED|`"status":"VISITED"`| +|eventCreatedAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object filtering based on the event creation date.|`{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}`| +|eventOccurredAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object filtering based on the event occurred date.|`{"type":"RELATIVE","period":"TODAY"}`| +|eventScheduledAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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](#webapi_tracker_workinglists_common_objects) object filtering based on the event enrollment date.|`"enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}`| +|enrollmentOccurredAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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", + "description": "Test WL definition", "program": { "id": "uy2gU8kT1jF" }, "programStage": { "id": "oRySG82BKE6" }, - "description": "Test WL definition", "programStageQueryCriteria": { "eventStatus": "VISITED", "eventCreatedAt": { @@ -2980,11 +3184,98 @@ See an example payload below: } ``` -## Potential Duplicates { #potential-duplicates } +### Event working lists { #event-working-lists } + +Create, update and delete event working lists using + + /api/eventFilters + +#### Payload { #payload } + +Table: Payload + +| Property | Descripción | Example | +|---|---|---| +|name|Name of the working list.|"name":"My working list"| +|Descripción|A description of the working list.|"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 + +| Property | Descripción | Example | +|---|---|---| +|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"]| +|displayColumnOrder |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](#webapi_tracker_workinglists_common_objects) 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](#webapi_tracker_workinglists_common_objects) object date filtering based on event date.|"eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" }| +|dueDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on due date.|"dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" }| +|lastUpdatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on last updated date.|"lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" }| + +See an example payload below: + +```json +{ + "name": "event working list", + "program": "VBqh0ynB2wv", + "eventQueryCriteria": { + "eventDate": { + "period": "LAST_WEEK", + "type": "RELATIVE" + }, + "dataFilters": [ + { + "ge": "35", + "le": "70", + "dataItem": "qrur9Dvnyt5" + } + ], + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "CotVI2NX0rI", + "xE7jOejl9FI" + ], + "status": "ACTIVE", + "order": "occurredAt:desc", + "displayColumnOrder": [ + "occurredAt", + "status", + "assignedUser", + "qrur9Dvnyt5", + "oZg33kd9taw" + ] + } +} +``` + +### Common Objects { #webapi_tracker_workinglists_common_objects } -Potential duplicates are records identified by the data deduplication feature as possibly being duplicates. Due to the nature of this feature, the API endpoint has certain restrictions. +Table: DateFilterPeriod object definition -A potential duplicate represents a pair of records suspected to be duplicates. +| Property | Descripción | Example | +|---|---|---| +|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`| + + +## Potential Duplicates { #potential-duplicates } + +Potential duplicates are records identified by the data deduplication feature as possibly being +duplicates. Due to the nature of this feature, the API endpoint has certain restrictions. A +potential duplicate represents a pair of records suspected to be duplicates. To retrieve a list of potential duplicates, use the following endpoint: @@ -3018,7 +3309,8 @@ To create a new potential duplicate, use this endpoint: POST /api/potentialDuplicates -The payload you provide must include the UIDs of the original and duplicate tracked entities. New potential duplicates are open by default. +The payload you provide must include the UIDs of the original and duplicate tracked entities. New +potential duplicates are open by default. ```json { @@ -3030,7 +3322,7 @@ The payload you provide must include the UIDs of the original and duplicate trac | Status code | Descripción |---|---| | 400 | Input original or duplicate is null or has invalid uid -| 403 | User do not have access to read origianl or duplicate TEs +| 403 | User do not have access to read original or duplicate TEs | 404 | TE not found | 409 | Pair of original and duplicate TEs already existing @@ -3048,9 +3340,15 @@ To update the status of a potential duplicate, use the following endpoint: | 400 | You can't update a potential duplicate that is already in a MERGED status ### Merging Tracked Entities { #merging-tracked-entities } -Tracked entities can be merged together if they are deemed viable. To initiate a merge, the first step is to define two tracked entities as a Potential Duplicate. The merge endpoint moves data from the duplicate tracked entity to the original tracked entity and deletes the remaining data of the duplicate. -To merge a Potential Duplicate, i.e. the two tracked entities the Potential Duplicate represents, use the following endpoint: +Tracked entities can be merged together if they are deemed viable. To initiate a merge, the first +step is to define two tracked entities as a Potential Duplicate. The merge endpoint moves data from +the duplicate tracked entity to the original tracked entity and deletes the remaining data of the +duplicate. + +To merge a Potential Duplicate, i.e. the two tracked entities the Potential Duplicate represents, +use the following endpoint: + POST /api/potentialDuplicates//merge | Parameter name | Descripción | Tipo | Allowed values | @@ -3060,28 +3358,47 @@ To merge a Potential Duplicate, i.e. the two tracked entities the Potential Dupl The endpoint accepts a single parameter, `mergeStrategy`, which determines the strategy used when merging. For the `AUTO` strategy, the server will attempt to merge the two tracked entities automatically without user input. This strategy only allows merging tracked entities without conflicting data (see examples below). The `MANUAL` strategy 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 evaluates the mergability of the two tracked entities and merges them if they are deemed mergable. The mergability is based on whether the two tracked entities have any conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible conflicts include: + +The automatic merge evaluates the mergability of the two tracked entities and merges them if they +are deemed mergeable. The mergability is based on whether the two tracked entities have any +conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible +conflicts include: + - The same attribute has different values in each tracked entity. - Both tracked entities are enrolled in the same program. - Tracked entities have different types. If any conflict is encountered, an error message 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 to the original. This includes attribute values, enrollments (including events), and relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is marked as `MERGED`. - -When requesting an automatic merge, a payload is not required and will be ignored. +When no conflicts are found, all data in the duplicate that is not already in the original will be +moved to the original. This includes attribute values, enrollments (including events), and +relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is +marked as `MERGED`. When requesting an automatic merge, a payload is not required and will be +ignored. #### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when there are resolvable conflicts or when not all the data needs to be moved during the 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 involves the user explicitly requesting to move data, there are some additional checks: -- 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 entities (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) + +The manual merge is suitable when there are resolvable conflicts or when not all the data needs to +be moved during the 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 involves the user explicitly requesting to move data, there are some +additional checks: + +- 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 entities (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 entities 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 was just created, but not enrolled for example. +When a manual merge is requested without a payload, we are telling the API to merge the two tracked +entities 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 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: -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"], @@ -3090,12 +3407,20 @@ Otherwise, if a manual merge is requested with a payload, the payload refers to } ``` -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. +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 entities 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 entities 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. +Currently it is not possible to merge tracked entities 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 +entities 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. 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 fd1b0cc2a..b67387985 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: -- Gestionar - DHIS core version master +- Gestionar --- # 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 7856db8f7..d21b0bddd 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: -- Gestionar - DHIS core version master +- Gestionar --- # 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 d32e75d6d..a35db3974 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-06-18' tags: -- Gestionar - DHIS core version master +- Gestionar --- # 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 ef19e985b..68a962358 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: -- Gestionar - DHIS core version master +- Gestionar --- # 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 0636518b0..bc28984a9 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: -- Gestionar - DHIS core version master +- Gestionar --- # 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 d0f802b8b..0bea08d7e 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: -- Gestionar - DHIS core version master +- Gestionar --- # 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__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 c6dd2e7c2..d938f9aa0 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: '2024-06-07' 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..7ef4fec97 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Uso - DHIS core version 2.38 +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 6ee5b28f4..f1ac210b0 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-06-24' 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..52045bfa6 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Uso - DHIS core version 2.39 +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 ea92dfc93..7cc7d1668 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-06-24' 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..265056a4f 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Uso - DHIS core version 2.40 +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 c7f56ca33..3e0f3ca02 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-06-24' 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..80bd82ea6 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Uso - DHIS core version 2.41 +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 99bae5c3a..b5a2d0563 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-06-24' 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 7abd3928a..b3af01cd4 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: '2024-06-07' 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..e2c3b1434 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Uso - DHIS core version master +- Uso --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 f9c4f679f..428bb8594 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: '2024-06-18' 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 8fef68c14..89cd06e50 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-06-18' 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 a45c2f8e1..9194f4580 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-06-24' 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 1b28ecd06..2af754c46 100644 --- a/projects/docs-full-site/fr/.cache_timestamp +++ b/projects/docs-full-site/fr/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:22:39Z \ No newline at end of file +2024-06-27T21:21:13Z \ No newline at end of file diff --git a/projects/docs-full-site/fr/DEVELOP__DEVELOPING-WITH-THE-ANDROID-SDK__workflow-md b/projects/docs-full-site/fr/DEVELOP__DEVELOPING-WITH-THE-ANDROID-SDK__workflow-md index 193298ba6..cb8996925 100644 --- a/projects/docs-full-site/fr/DEVELOP__DEVELOPING-WITH-THE-ANDROID-SDK__workflow-md +++ b/projects/docs-full-site/fr/DEVELOP__DEVELOPING-WITH-THE-ANDROID-SDK__workflow-md @@ -582,7 +582,7 @@ The SDK supports all types of relationships. They are downloaded when syncing an | | TEI | Inscription | Événement | |--------------------|:----------:|:------------:|:----------:| | **TEI** | X | X | X | -| **Enrollment** | X | X | X | +| **Inscription** | X | X | X | | **Manifestation** | X | X | X | _Supported relationships_ 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 230fc1f7e..35df4122d 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 @@ -14418,8 +14418,7 @@ tracked entity instances and programs are supported. -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : { "trackedEntity": "tracked-entity-id", @@ -14431,9 +14430,7 @@ For creating a new person in the system, you will be working with the } ] } -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : { "type": "Point", @@ -14453,8 +14450,7 @@ URL: /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : { "trackedEntity": "nEenWmSyUEp", @@ -14477,8 +14473,7 @@ To push this to the server you can use the cURL command like curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST -H "Content-Type: application/json" -u admin:district -v -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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() { "trackedEntityInstances": [ @@ -14541,9 +14536,7 @@ attributes/relationships in the current payload. A request parameter of 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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### Deleting a tracked entity instance { #webapi_deleting_tei } @@ -14557,8 +14550,7 @@ method. The URL is equal to the one above used for update. -It is also possible to both create (and update) a tracked entity -instance and at the same time enroll into a program. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme { "trackedEntity": "tracked-entity-id", @@ -14580,8 +14572,7 @@ instance and at the same time enroll into a program. } ] } -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. curl -X POST -d @tei.json -H "Content-Type: application/json" -u user:pass http://server/api/29/trackedEntityInstances @@ -14590,8 +14581,7 @@ updating a new tracked entity instance. -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. { "trackedEntityType": "nEenWmSyUEp", @@ -14669,8 +14659,7 @@ the same time enroll into a program and create an event. Note: The example above can fail if provided UIDs are not present in the system. -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. curl -X POST -d @tei.json -H "Content-Type: application/json" -u user:pass http://server/api/29/trackedEntityInstances @@ -14683,9 +14672,7 @@ Tracked entity instance attributes that is using automatic generation of unique values has three endpoints that is 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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. > **Note** > @@ -14696,17 +14683,11 @@ when upgrading to 2.29. > 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 } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/29/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -14729,8 +14710,7 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : The expiration time can also be overridden at the time of generation, by adding the ?expiration=\ to the @@ -14759,8 +14739,7 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : Similar to the /generate endpoint, this endpoint can also specify the expiration time in the same way. By adding the @@ -14796,7 +14775,7 @@ expiration time in the same way. By adding the } ] -##### Reserved values { #reserved-values } +##### Valeurs réservées { #reserved-values } Reserved values is currently not accessible trough the api, however they are returned by the *generate* and *generateAndReserve*endpoints. The @@ -14849,7 +14828,7 @@ that was 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 } +#### Attributs d'image { #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 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 45d3d8fcf..d92a88944 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 @@ -14988,19 +14988,13 @@ Pour obtenir la réponse dans le format PDF, vous pouvez envoyer une requête *P -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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. ### 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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances @@ -15008,8 +15002,7 @@ tracked entity instances and programs are supported. -For creating a new person in the system, you will be working with the -*trackedEntityInstances* resource. A template payload can be seen below: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -15023,9 +15016,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -15044,8 +15035,7 @@ You can post the payload the the following URL: /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -15064,15 +15054,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -15126,35 +15115,21 @@ 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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. + +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### 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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -15178,8 +15153,7 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -15190,8 +15164,7 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" -It is also possible to create (and update) a tracked entity instance, at -the same time enroll into a program and create an event. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -15268,8 +15241,7 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -15284,9 +15256,7 @@ Tracked entity instance attributes that is using automatic generation of unique values has three endpoints that is 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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. > **Note** > @@ -15297,17 +15267,11 @@ when upgrading to 2.29. > 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 } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -15332,11 +15296,9 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -15363,8 +15325,7 @@ 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: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : Similar to the /generate endpoint, this endpoint can also specify the expiration time in the same way. By adding the `?expiration=` @@ -15401,7 +15362,7 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #reserved-values } Reserved values is currently not accessible trough the api, however they are returned by the `generate` and `generateAndReserve` endpoints. The @@ -15454,14 +15415,9 @@ that was 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 } +#### Attributs d'image { #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. +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'image. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?height=200&width=200" 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 d1be2e1f5..33a38a8f6 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 @@ -14548,17 +14548,17 @@ For PDF you can send a _POST_ request to the following URL with content-type `ap -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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 } +### Gestion des instances d'entités suivies { #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 } +#### Création d'une nouvelle instance d'entité suivie { #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: @@ -14610,7 +14610,7 @@ For example, let us create a new instance of a person tracked entity and specify } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```bash curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST @@ -14656,7 +14656,7 @@ To create multiple instances in one request you can wrap the payload in an outer 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 } +#### Mise à jour d'une instance d'entité suivie { #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: @@ -14666,11 +14666,11 @@ The payload has to contain all, even non-modified, attributes and relationships. 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 } +#### Suppression d'une instance d'entité suivie { #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 } +#### Création et inscription des instances d'entités suivies { #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. @@ -14708,7 +14708,7 @@ 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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. @@ -14794,7 +14794,7 @@ 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 } +#### Attributs d'instances d'entités suivies générés { #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. @@ -14819,7 +14819,7 @@ This endpoint will return a map of required and optional values, that the server } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. @@ -14840,7 +14840,7 @@ The expiration time can also be overridden at the time of generation, by adding } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). 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 3df4ac367..71cb9462a 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 @@ -14854,17 +14854,17 @@ For PDF you can send a _POST_ request to the following URL with content-type `ap -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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 } +### Gestion des instances d'entités suivies { #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 } +#### Création d'une nouvelle instance d'entité suivie { #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: @@ -14916,7 +14916,7 @@ For example, let us create a new instance of a person tracked entity and specify } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```bash curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST @@ -14962,7 +14962,7 @@ To create multiple instances in one request you can wrap the payload in an outer 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 } +#### Mise à jour d'une instance d'entité suivie { #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: @@ -14972,11 +14972,11 @@ The payload has to contain all, even non-modified, attributes and relationships. 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 } +#### Suppression d'une instance d'entité suivie { #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 } +#### Création et inscription des instances d'entités suivies { #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. @@ -15014,7 +15014,7 @@ 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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. @@ -15100,7 +15100,7 @@ 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 } +#### Attributs d'instances d'entités suivies générés { #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. @@ -15125,7 +15125,7 @@ This endpoint will return a map of required and optional values, that the server } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. @@ -15146,7 +15146,7 @@ The expiration time can also be overridden at the time of generation, by adding } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). 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 821b30c0e..e12740dfc 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 @@ -35,15 +35,15 @@ The following table highlights the differences between the previous tracker impo | Objet Tracker | Avant | Maintenant | | --- | --- | --- | -| **Attribut** | `created`
`lastUpdated` | `createdAt`
`updatedAt` | -| **DataValue** | `created`
`lastUpdated` | `createdAt`
`updatedAt` | -| **Enrollment** | `created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate` | `createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt` | +| **Attribut** | `created` (créé)
`lastUpdated` (dernière mise à jour) | `createdAt` (créé à)
`updatedAt` (mis à jour à) | +| **Valeur de données** | `created` (créé)
`lastUpdated` (dernière mise à jour) | `createdAt` (créé à)
`updatedAt` (mis à jour à) | +| **Inscription** | `created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate` | `createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt` | | **Manifestation** | `trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate` | `trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt` | | **Remarque** | `storedDate`
`lastUpdated` | `storedAt`
`updatedAt` | -| **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` | `trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient` | +| **Propriétaire du programme** | `ownerOrgUnit`
`trackedEntityInstance` | `orgUnit`
`trackedEntity` | +| **Élément de relation** | `trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event` | `trackedEntity`
`enrollment`
`event` | +| **Relation** | `created` (créé)
`lastUpdated` (dernière mise à jour) | `createdAt` (créé à)
`updatedAt` (mis à jour à) | +| **Entité suivie** | `trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient` | `trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient` | ### Tracker Export changelog (`GET`) { #tracker-export-changelog-get } @@ -67,7 +67,7 @@ These tables highlight the old endpoint differences in request parameters for `G | `trackedEntityInstance` | `trackedEntity` (entité suivie) | | `startDate`
`endDate` | `occurredAfter`
`occurredBefore` | | `dueDateStart`
`dueDateEnd` | `scheduledAfter`
`scheduledBefore` | -| `dernière mise à jour` | Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +| `dernière mise à jour` | Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| | `lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration` | `updatedAfter`
`updatedBefore`
`updatedWithin` | #### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } @@ -76,7 +76,7 @@ These tables highlight the old endpoint differences in request parameters for `G | --- | --- | | `trackedEntityInstance` | `trackedEntity` (entité suivie) | | `uo` | `orgUnit` (unité d'organisation) | -| `programStartDate`
`programEndDate` | Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +| `programStartDate`
`programEndDate` | Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| | `programEnrollmentStartDate`
`programEnrollmentEndDate` | `enrollmentEnrolledAfter`
`enrollmentEnrolledBefore` | | `programIncidentStartDate`
`programIncidentEndDate` | `enrollmentOccurredAfter`
`enrollmentOccurredBefore` | | `eventStartDate`
`eventEndDate` | `eventOccurredAfter`
`eventOccurredBefore` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__tracker-md index c7749ff49..150271916 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-236__tracker-md @@ -8,17 +8,17 @@ tags: # Tracker { #tracker } -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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 } +### Gestion des instances d'entités suivies { #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 } +#### Création d'une nouvelle instance d'entité suivie { #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: @@ -70,7 +70,7 @@ For example, let us create a new instance of a person tracked entity and specify } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```bash curl -d @tei.json "https://play.dhis2.org/demo/api/trackedEntityInstances" -X POST @@ -116,7 +116,7 @@ To create multiple instances in one request you can wrap the payload in an outer 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 } +#### Mise à jour d'une instance d'entité suivie { #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: @@ -126,11 +126,11 @@ The payload has to contain all, even non-modified, attributes and relationships. 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 } +#### Suppression d'une instance d'entité suivie { #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 } +#### Création et inscription des instances d'entités suivies { #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. @@ -168,7 +168,7 @@ 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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. @@ -254,7 +254,7 @@ 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 } +#### Attributs d'instances d'entités suivies générés { #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. @@ -279,7 +279,7 @@ This endpoint will return a map of required and optional values, that the server } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. @@ -300,7 +300,7 @@ The expiration time can also be overridden at the time of generation, by adding } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). 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 6fc6a24a9..fab257e5c 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 @@ -618,12 +618,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : 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 d17e010c7..a6476080a 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 @@ -36,15 +36,15 @@ The following table highlights the differences between the previous tracker impo |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**DataValue**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| -|**Enrollment**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Inscription**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`| |**Manifestation**|`trackedEntityInstance`
`eventDate`
`dueDate`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`completedDate`|`trackedEntity`
`occurredAt`
`scheduledAt`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`completedAt`| |**Remarque**|`storedDate`|`storedAt`| -|**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`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`| ### Tracker Export changelog (`GET`) { #tracker-export-changelog-get } @@ -52,7 +52,7 @@ The `GET` endpoints all conform to the same naming conventions reported in the p These tables highlight the old endpoint differences in request parameters for `GET` endpoints compared to the new -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| |`uo`|`orgUnit` (unité d'organisation)| @@ -60,21 +60,21 @@ These tables highlight the old endpoint differences in request parameters for `G |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`uo`|`orgUnit` (unité d'organisation)| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__tracker-md index 906903501..3e37ba7f9 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-237__tracker-md @@ -10,24 +10,17 @@ tags: ## 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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. ### 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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -41,9 +34,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -52,18 +43,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -82,15 +70,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -127,46 +114,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. #### 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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. + +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. #### 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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -190,8 +156,7 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -200,8 +165,7 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" #### 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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -278,8 +242,7 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```bash curl -X POST -d @tei.json -H "Content-Type: application/json" @@ -288,34 +251,23 @@ curl -X POST -d @tei.json -H "Content-Type: application/json" #### 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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -332,17 +284,11 @@ variables should only be supplied if you know what you are doing. ##### 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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -359,20 +305,11 @@ adding the `?expiration=` to the request. ##### 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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -405,48 +342,37 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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éé | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créé | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" 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 ea1e58c5d..79a2c7f49 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 @@ -613,12 +613,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : 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 6b3dff874..fd097fe1a 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 @@ -34,15 +34,15 @@ The following table highlights the differences between the previous tracker impo |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`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`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created`
`lastUpdated`
`createByUserInfo` (créé avec les informations d'utilisateur)
`lastUpdatedByUserInfo` (dernière mise à jour avec les informations d'utilisateur)|`createdAt`
`updatedAt`
`createdBy` (créé par)
`updatedBy` (mis à jour par)| +|**Inscription**|`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`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| > **Note** > @@ -64,7 +64,7 @@ The `GET` endpoints all conform to the same naming conventions reported in the p These tables highlight the old endpoint differences in request parameters for `GET` endpoints compared to the new -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| |`uo`|`orgUnit` (unité d'organisation)| @@ -72,21 +72,21 @@ These tables highlight the old endpoint differences in request parameters for `G |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`uo`|`orgUnit` (unité d'organisation)| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md index 80b7edb40..76c5c510b 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md @@ -8,26 +8,19 @@ tags: # Tracker { #tracker } -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. -### Tracked entity instance management { #webapi_tracked_entity_instance_management } +### Gestion des instances d'entités suivies { #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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances -#### Creating a new tracked entity instance { #webapi_creating_tei } +#### Création d'une nouvelle instance d'entité suivie { #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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -41,9 +34,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -52,18 +43,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -82,15 +70,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -127,46 +114,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. -#### Updating a tracked entity instance { #webapi_updating_tei } +#### Mise à jour d'une instance d'entité suivie { #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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. -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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. -#### Deleting a tracked entity instance { #webapi_deleting_tei } +#### Suppression d'une instance d'entité suivie { #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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } +#### Création et inscription des instances d'entités suivies { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -190,18 +156,16 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -278,44 +242,32 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Attributs d'instances d'entités suivies générés { #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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -330,19 +282,13 @@ variables should only be supplied if you know what you are doing. } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -357,22 +303,13 @@ adding the `?expiration=` to the request. } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -405,48 +342,37 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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éé | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créé | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" 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 a449083b9..d0fe63235 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 @@ -640,12 +640,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : @@ -1050,9 +1045,9 @@ Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| | `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. | +| `geoJsonProperty` | `Chaîne` | _non défini_ | 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. | +| `attributeId` | `Chaîne` | _non défini_ | 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. | 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 1e4af30ec..b8f6d445a 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 @@ -34,15 +34,15 @@ The following table highlights the differences between the previous tracker impo |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`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`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created`
`lastUpdated`
`createByUserInfo` (créé avec les informations d'utilisateur)
`lastUpdatedByUserInfo` (dernière mise à jour avec les informations d'utilisateur)|`createdAt`
`updatedAt`
`createdBy` (créé par)
`updatedBy` (mis à jour par)| +|**Inscription**|`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`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| > **Note** > @@ -64,7 +64,7 @@ The `GET` endpoints all conform to the same naming conventions reported in the p These tables highlight the old endpoint differences in request parameters for `GET` endpoints compared to the new -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| |`uo`|`orgUnit` (unité d'organisation)| @@ -72,21 +72,21 @@ These tables highlight the old endpoint differences in request parameters for `G |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`uo`|`orgUnit` (unité d'organisation)| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__tracker-md index fb72b5f3c..444713f73 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__tracker-md @@ -23,26 +23,19 @@ tags: > feature you will have to postpone the migration until a new SYNC feature is > in place. -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. -### Tracked entity instance management { #webapi_tracked_entity_instance_management } +### Gestion des instances d'entités suivies { #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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances -#### Creating a new tracked entity instance { #webapi_creating_tei } +#### Création d'une nouvelle instance d'entité suivie { #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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -56,9 +49,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -67,18 +58,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -97,15 +85,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -142,46 +129,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. -#### Updating a tracked entity instance { #webapi_updating_tei } +#### Mise à jour d'une instance d'entité suivie { #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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. -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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. -#### Deleting a tracked entity instance { #webapi_deleting_tei } +#### Suppression d'une instance d'entité suivie { #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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } +#### Création et inscription des instances d'entités suivies { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -205,18 +171,16 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -293,44 +257,32 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Attributs d'instances d'entités suivies générés { #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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -345,19 +297,13 @@ variables should only be supplied if you know what you are doing. } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -372,22 +318,13 @@ adding the `?expiration=` to the request. } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -420,54 +357,43 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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éé | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créé | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" ``` -#### File attributes { #file-attributes } +#### Attributs de fichier { #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 diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md index a50632f0e..393a6703e 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md index 86c8a8623..b2dfe18ce 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Métadonnées Gist API { #gist_api } 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 72891a53c..fa19eb0e9 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata.md" revision_date: '2024-04-26' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Métadonnées { #metadata } @@ -1046,9 +1046,9 @@ Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| | `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. | +| `geoJsonProperty` | `Chaîne` | _non défini_ | 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. | +| `attributeId` | `Chaîne` | _non défini_ | 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. | @@ -2997,7 +2997,7 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | PHONE_NUMBER | La validation est basée sur cette expression rationnelle `^[0-9+\\N-(\N-)#\N.\Ns\N/ext-]{6,50}$`. La longueur maximale est de 50.
Exemples : +4733987937, (+47) 3398 7937, (47) 3398 7937.123 | EMAIL | Format général des email : abc@email.com | BOOLÉEN | `vrai` or `faux` -| TRUE_ONLY (vrai uniquement) | Only accept `true` +| TRUE_ONLY (vrai uniquement) | N'accepte que `true` | DATE | Utiliser le format `yyyy-MM-dd` | DATETIME (date et heure) | Utiliser le format `yyyy-MM-dd HH:mm:ssZ` ou `yyyy-MM-dd 'T'HH:mm:ss` | TEMPS | Utiliser le format `HH:mm` @@ -3008,11 +3008,11 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | INTEGER_POSITIVE | La valeur est un nombre entier positif | INTEGER_NEGATIVE | La valeur est un nombre entier négatif | INTEGER_ZERO_OR_POSITIVE | La valeur est un entier positif ou nul -| TRACKER_ASSOCIATE | Aucun +| TRACKER_ASSOCIÉ | Aucun | NOM D'UTILISATEUR | La valeur est un nom d'utilisateur pour un `utilisateur` existant | COORDINATE | Aucun | ORGANISATION_UNIT | La valeur est un UID valide d'une `unité d'organisation` existante -| REFERENCE | Aucun +| RÉFÉRENCE | Aucun | AGE | La valeur est une date de naissance. Utiliser le même format que pour le type DATE. | URL | La valeur est une URL valide | FILE_RESOURCE | La valeur est un UID valide d'une `ressource de fichier` existante diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 702e7d31c..e696b159b 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/route.md" revision_date: '2023-05-09' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Route { #route } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index d0b04a7e5..403267d98 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-01-26' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Paramètres et configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md index 2d280ae2a..22200523d 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md @@ -47,15 +47,15 @@ Les noms des propriétés d'API ont été modifiés afin qu'ils soient cohérent |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`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`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created`
`lastUpdated`
`createByUserInfo` (créé avec les informations d'utilisateur)
`lastUpdatedByUserInfo` (dernière mise à jour avec les informations d'utilisateur)|`createdAt`
`updatedAt`
`createdBy` (créé par)
`updatedBy` (mis à jour par)| +|**Inscription**|`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`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| > **Note** > @@ -71,31 +71,28 @@ Les noms des propriétés d'API ont été modifiés afin qu'ils soient cohérent >} >``` -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } +### Journal des modifications (changelog) de l'importation Tracker (`POST`) { #tracker-import-changelog-post } -The previous tracker import endpoints +Les précédents points d'extrémité de l'importation Tracker * `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 +sont remplacés par le nouveau point d'extrémité * `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. +[Importation Tracker] (https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) décrit comment utiliser ce nouveau point d'extrémité. -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } +### Journal des modifications de l'exportation Tracker (`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. +En plus des noms modifiés indiqués dans [Noms de propriétés](#webapi_tracker_migration_names), certains paramètres de requête ont également été modifiés. The following tables list the differences in old and new request parameters for `GET` enpoints. -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| @@ -104,48 +101,41 @@ The following tables list the differences in old and new request parameters for |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| |`uo`|`orgUnit` (unité d'organisation)| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| |`lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. -### Tracked entity instance management { #webapi_tracked_entity_instance_management } +### Gestion des instances d'entités suivies { #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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances -#### Creating a new tracked entity instance { #webapi_creating_tei } +#### Création d'une nouvelle instance d'entité suivie { #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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -159,9 +149,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -170,18 +158,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -200,15 +185,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -245,46 +229,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. -#### Updating a tracked entity instance { #webapi_updating_tei } +#### Mise à jour d'une instance d'entité suivie { #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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. -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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. -#### Deleting a tracked entity instance { #webapi_deleting_tei } +#### Suppression d'une instance d'entité suivie { #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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } +#### Création et inscription des instances d'entités suivies { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -308,18 +271,16 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -396,44 +357,32 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Attributs d'instances d'entités suivies générés { #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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -448,19 +397,13 @@ variables should only be supplied if you know what you are doing. } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -475,22 +418,13 @@ adding the `?expiration=` to the request. } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -523,54 +457,43 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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éé | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créé | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" ``` -#### File attributes { #file-attributes } +#### Attributs de fichier { #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 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 f2e26824e..8c6f1b1df 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" revision_date: '2024-05-23' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Tracker { #tracker } 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 d82960172..28f24dde1 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 @@ -64,7 +64,7 @@ Tableau : Paramètres de requête | pagination | vrai | faux | vrai | Indique s'il faut renvoyer les listes d'éléments sous forme de pages. | | page | nombre | 1 | Définit le numéro de page à renvoyer. | | taille de la page | nombre | 50 | Définit le nombre d'éléments à renvoyer pour chaque page. | -| Ordre | property:asc/iasc/desc/idesc || Order the output using a specified order, only properties that are both persisted and simple (no collections, idObjects etc) are supported. iasc and idesc are case insensitive sorting. If it is wanted to sort for more than one property, separate them using a comma. | +| Ordre | property:asc/iasc/desc/idesc || Ordonne la sortie dans un ordre spécifique. Seules les propriétés qui sont à la fois persistantes et simples (pas de collections, d'identifiants d'objets, etc.) sont prises en charge. iasc et idesc sont des tris insensibles à la casse. Si vous souhaitez trier plusieurs propriétés, séparez-les par une virgule. | Voici un exemple de comment ces paramètres peuvent être utilisés pour obtenir une liste complète de groupes d'éléments de données dans un format de réponse XML : @@ -474,7 +474,7 @@ Le _nom de l'entité_ utilise la notation camel case. Par exemple, le point d'ex /api/dataElements -> **_NOTE:_** When updating objects, all existing property values will be overwritten, even if the new value is null. Please use [JSON Patch API](#webapi_partial_updates) in case you want do partial update to an object. +>**_NOTE:_** Lors de la mise à jour des objets, toutes les valeurs des propriétés existantes seront écrasées, même si la nouvelle valeur est nulle. Veuillez utiliser l'[API de patch JSON](#webapi_partial_updates) si vous souhaitez effectuer une mise à jour partielle d'un objet. ### Création et mise à jour des paramètres { #webapi_metadata_create_update } @@ -651,12 +651,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : @@ -1056,12 +1051,12 @@ Par défaut, la géométrie du fichier est stockée en tant que propriété `geo Tableau : Paramètres d'importation -| Nom ; | Type | Par défaut | Description ; | +| Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| | `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. | +| `geoJsonProperty` | `String` | _non défini_ | 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. | +| `attributeId` | `String` | _non défini_ | 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. | @@ -1611,11 +1606,11 @@ L'opération de fusion transfère toutes les associations de métadonnées de l' Les métadonnées suivantes sont mises à jour : -| Métadonnées | Propriété | Action taken | +| Métadonnées | Propriété | Mesure prise | |---------------------|--------------------------------------------|-----------------------------------------------------------------------------| | Groupe d'indicateurs | membres | Indicateur source supprimé, indicateur cible ajouté | | Ensemble de données | indicateurs | Indicateur source supprimé, indicateur cible ajouté | -| DataDimensionalItem | n/a | Tous les éléments de données associés à des sources seront reliés à la cible. | +| Élément dimensionnel de données | n/a | Tous les éléments de données associés à des sources seront reliés à la cible. | | Section | indicateurs | Indicateur source supprimé, indicateur cible ajouté | | Configuration | Indicateurs infrastructurels (Groupe d'indicateurs) | Indicateur source supprimé, indicateur cible ajouté | | Indicateur | numérateur / dénominateur | Remplace toute référence source par la référence cible | @@ -3351,11 +3346,11 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da |---| --- | | TEXT | Aucun | LONG_TEXT (texte long) | Aucun -| LETTER | Longueur de la valeur = 1 ET il s'agit d'une lettre -| PHONE_NUMBER | La validation est basée sur cette expression rationnelle `^[0-9+\\N-(\N-)#\N.\Ns\N/ext-]{6,50}$`. La longueur maximale est de 50.
Exemples : +4733987937, (+47) 3398 7937, (47) 3398 7937.123 +| LETTRE | Longueur de la valeur = 1 ET il s'agit d'une lettre +| NUMÉRO_DE TÉLÉPHONE | La validation est basée sur cette expression rationnelle `^[0-9+\\N-(\N-)#\N.\Ns\N/ext-]{6,50}$`. La longueur maximale est de 50.
Exemples : +4733987937, (+47) 3398 7937, (47) 3398 7937.123 | EMAIL | Format général des email : abc@email.com | BOOLÉEN | `vrai` or `faux` -| TRUE_ONLY (vrai uniquement) | Only accept `true` +| TRUE_ONLY (vrai uniquement) | N'accepte que `true` | DATE | Utiliser le format `yyyy-MM-dd` | DATETIME (date et heure) | Utiliser le format `yyyy-MM-dd HH:mm:ssZ` ou `yyyy-MM-dd 'T'HH:mm:ss` | TEMPS | Utiliser le format `HH:mm` @@ -3366,12 +3361,12 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | INTEGER_POSITIVE | La valeur est un nombre entier positif | INTEGER_NEGATIVE | La valeur est un nombre entier négatif | INTEGER_ZERO_OR_POSITIVE | La valeur est un entier positif ou nul -| TRACKER_ASSOCIATE | Aucun +| TRACKER_ASSOCIÉ | Aucun | NOM D'UTILISATEUR | La valeur est un nom d'utilisateur pour un `utilisateur` existant -| COORDINATE | Aucun +| COORDONNÉE | Aucun | ORGANISATION_UNIT | La valeur est un UID valide d'une `unité d'organisation` existante -| REFERENCE | Aucun -| AGE | La valeur est une date de naissance. Utiliser le même format que pour le type DATE. +| RÉFÉRENCE | Aucun +| ÂGE | La valeur est une date de naissance. Utiliser le même format que pour le type DATE. | URL | La valeur est une URL valide | FILE_RESOURCE | La valeur est un UID valide d'une `ressource de fichier` existante | IMAGE | La valeur est un UID valide d'une `ressource de fichier` existante @@ -3408,7 +3403,7 @@ En cas de succès, la réponse contiendra un nouveau `UID` de `Programme` et res La réponse contiendra également un en-tête `Location` (emplacement) avec un lien vers le `Programme` nouvellement créé. Par exemple, si le programme est exécuté localement, la valeur de `Location` sera `http://localhost:9090/api/programs/Program456b`. -#### Copy options { #copy-options } +#### Options de copie { #copy-options } L'API permet d'utiliser un préfixe personnalisé à titre facultatif, lequel sera ajouté aux propriétés suivantes. @@ -3446,7 +3441,7 @@ Si une propriété a dépassé sa limite de caractères, une message d'erreur se } ``` -If trying to copy a Program that is not found, a response like this will be returned: +Si l'utilisateur essaie de copier un programme qui n'est pas trouvé, une réponse de ce type sera renvoyée : ```json { "httpStatus": "Not Found", @@ -3471,10 +3466,10 @@ Un `Utilisateur` aura besoin des autorisations suivantes pour pouvoir copier un Un `Programme` doit avoir un des statuts suivants pour pouvoir être copié : - Accès public en `lecture` et en `écriture` -- A specific `User` to have sharing `read` & `write` access -- A `User` is part of a `UserGroup` that has sharing `read` & `write` access +- Un `Utilisateur` spécifique autorisé à partager les accès en `lecture` et en `écriture`. +- Un `utilisateur` faisant partie d'un `groupe d'utilisateurs` et qui est autorisé à partager les accès en `lecture` et en `écriture`. -If a `User` does not have the correct permissions, a `Forbidden` response is returned like so: +Si un `utilisateur` n'a pas les bonnes autorisations, une réponse `Forbidden` (d'interdiction) est renvoyée comme suit : ```json { @@ -3486,48 +3481,48 @@ If a `User` does not have the correct permissions, a `Forbidden` response is ret } ``` -### Points to note { #points-to-note } +### Points à noter { #points-to-note } -#### Deep and shallow copy { #deep-and-shallow-copy } +#### Copie profonde et copie superficielle { #deep-and-shallow-copy } -When a `Program` is copied, certain properties of the `Program` need different kinds of copying. It is important to be aware of what has been deep-copied and what has been shallow-copied. -First of all let's explain the difference between deep and shallow copying in this context. +Lorsqu'un `Programme` est copié, certaines propriétés du `Programme` nécessitent des types de copie différents. Il est important de savoir ce qui a été copié en profondeur et ce qui a été copié superficiellement. +Tout d'abord, expliquons la différence entre la copie profonde et la copie superficielle dans ce contexte. -##### Deep copy { #deep-copy } +##### Copie profonde { #deep-copy } -A deep copy in this context means that a completely new instance of a `Program` or `Program` property has been created with its own unique identifiers. These include amongst others: +Dans ce contexte, une copie profonde signifie qu'une instance entièrement nouvelle d'un `Programme` ou d'une propriété de `Programme` a été créée avec ses propres identifiants uniques. Il s'agit entre autres de : -- identifiant +- id - uid -Deep copies of `Program` properties will all belong to the newly-created `Program` copy. +Les copies profondes des propriétés de `programme` feront toutes partie de la copie du `programme` nouvellement créée. -##### Shallow copy { #shallow-copy } +##### Copie superficielle { #shallow-copy } -A shallow copy in this context means that an existing `Program` property will be reused by the newly-created `Program` or `Program` property. +Dans ce contexte, une copie superficielle signifie qu'une propriété de `programme` existante sera réutilisée par le `programme` ou la propriété de `programme` nouvellement créé(e). -#### Properties that get deep copied { #properties-that-get-deep-copied } +#### Propriétés qui ont été copiées en profondeur { #properties-that-get-deep-copied } -All properties below have been deep copied. Anything not in included in this table means that it has been shallow copied. +Toutes les propriétés ci-dessous ont été copiées en profondeur. Si une propriété ne figure pas dans ce tableau, cela signifie qu'elle a été copié superficiellement. -| Objet | Property of | +| Objet | Propriété de | |--------------------------------|--------------| | Programme | | -| ProgramSection | Programme | +| Section de programme | Programme | | Indicateur de programme | Programme | -| ProgramRuleVariable | Programme | -| Étape du programme | Programme | -| ProgramStageSection | Étape du programme | -| ProgramStageSectionDataElement | Étape du programme | +| Variable de règle de programme | Programme | +| Étape de programme | Programme | +| Section d'une étape de programme | Étape de programme | +| Élément de données d'une section d'étape de programme | Étape de programme | | Inscription | | -> **Note** +> **Remarque** > -> The following properties have been set as empty as an initial approach. This approach should keep things simple to start off with. +> Les propriétés suivantes ont été définies comme vides dans une première approche. Cette approche devrait permettre de simplifier les choses pour commencer. | Objet | Propriété | |-------------------------------|-------------------| -| Indicateur de programme | groups | -| ProgramStageSection | programIndicators | +| Indicateur de programme | groupes | +| Section d'une étape de programme | Indicateurs de programme | | Inscription | événements | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md index 9f3998456..a31a9262a 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md @@ -52,143 +52,131 @@ Les noms des propriétés d'API ont été modifiés afin qu'ils soient cohérent |Objet Tracker|Avant|Maintenant| |---|---|---| |**Attribut**|`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`*| +|**Valeur de données**|`created`
`lastUpdated`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`updatedAt`
`createdBy`
`updatedBy`| +|**Inscription**|`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`trackedEntityInstance`
`enrollmentDate`
`incidentDate`
`completedDate`
`createByUserInfo`
`lastUpdatedByUserInfo`|`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`trackedEntity`
`enrolledAt`
`occurredAt`
`completedAt`
`createdBy`
`updatedBy`| +|**Événement**|`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`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created`
`lastUpdated`|`createdAt`
`updatedAt`| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| -> **Note** +> **Remarque** > -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): +> La propriété `assignedUser` (utilisateur assigné) était auparavant une chaîne de caractères et est maintenant un objet de la forme suivante (type `utilisateur`) : > ```json > { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } +> "assignedUser" : { +> "uid" : "ABCDEF12345", +> "username" : "username", +> "firstName" : "John", +> "nom de famille" : "Doe" +> } > } > ``` -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } +### Point-virgule comme séparateur pour les identifiants (UID) { #semicolon-as-separator-for-identifiers-uid } -Fields or query parameter 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. +Les champs ou les paramètres de requête acceptant plusieurs valeurs, comme les UID, sont désormais séparés par une virgule au lieu d'un point-virgule. Cela permet de s'assurer que les UID soient systématiquement séparés par une virgule dans tous les points d'extrémité de DHIS2. -The following fields are affected +Les champs suivants sont concernés -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship +* `event.attributeCategoryOptions` (ainsi qu'un événement renvoyé dans le cadre d'une relation `from`/`to`) -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } +### Journal des modifications (changelog) de l'importation Tracker (`POST`) { #tracker-import-changelog-post } -The previous tracker import endpoints +Les précédents points d'extrémité de l'importation Tracker * `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 +sont remplacés par le nouveau point d'extrémité * `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. +[Importation Tracker] (https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) décrit comment utiliser ce nouveau point d'extrémité. -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } +### Journal des modifications de l'exportation Tracker (`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. +En plus des noms modifiés indiqués dans [Noms de propriétés](#webapi_tracker_migration_names), certains paramètres de requête ont également été modifiés. -The following tables list the differences in old and new request parameters for `GET` endpoints. +Les tableaux suivants énumèrent les différences entre les anciens et les nouveaux paramètres de requête pour les points d'extrémité `GET`. -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| -|`assignedUser` (utilisateur assigné)|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribut`|Removed - use `filter` instead| +|`assignedUser` (utilisateur assigné)|`assignedUsers`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| +|`attachment`|Supprimé| +|`attribut`|Supprimé - utiliser `filter` à la place| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes` (inclure tous les attributs)|Removed| +|`includeAllAttributes`|Supprimé| |`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| |`ouMode`|`orgUnitMode`| -|`uo`|`orgUnits`
Values are now separated by comma instead of semicolon.| +|`uo`|`orgUnits`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| -|`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.| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`requête`|Supprimé - utiliser `filter` à la place| +|`skipMeta`|Supprimé| +|`skipPaging`|`paging`
C'est l'inverse, donc `paging=false` remplace `skipPaging=true`.| +|`trackedEntityInstance`|`trackedEntities`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| -|`inscription`|`enrollments`
Values are now separated by comma instead of semicolon.| +|`enrollment`|`enrollments`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| |`ouMode`|`orgUnitMode`| -|`uo`|`orgUnits`
Values are now separated by comma instead of semicolon.| +|`uo`|`orgUnits`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| -|`skipPaging` (ignorer la pagination)|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`trackedEntityInstance`|`trackedEntity` (entité suivie)| +|`skipPaging`|`paging`
C'est l'inverse, donc `paging=false` remplace `skipPaging=true`.| +|`trackedEntityInstance`|`trackedEntity`| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| -|`assignedUser` (utilisateur assigné)|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| +|`assignedUser`|`assignedUsers`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| +|`attachment`|Supprimé| |`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| +|`attributeCos`|`attributeCategoryOptions`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`événement`|`events`
Values are now separated by comma instead of semicolon.| +|`event`|`events`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`lastUpdated`|Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| |`ouMode`|`orgUnitMode`| -|`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`.| +|`skipEventId`|Supprimé| +|`skipMeta`|Supprimé| +|`skipPaging`|`paging`
C'est l'inverse, donc `paging=false` remplace `skipPaging=true`.| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| |`startDate`
`endDate`|`occurredAfter`
`occurredBefore`| -|`trackedEntityInstance`|`trackedEntity` (entité suivie)| +|`trackedEntityInstance`|`trackedEntity`| -#### Request parameter changes for `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } |Avant|Maintenant| |---|---| -|`skipPaging` (ignorer la pagination)|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| -|`tei`|`trackedEntity` (entité suivie)| +|`skipPaging`|`paging`
C'est l'inverse, donc `paging=false` remplace `skipPaging=true`.| +|`tei`|`trackedEntity`| -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. -### Tracked entity instance management { #webapi_tracked_entity_instance_management } +### Gestion des instances d'entités suivies { #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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances -#### Creating a new tracked entity instance { #webapi_creating_tei } +#### Création d'une nouvelle instance d'entité suivie { #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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -202,9 +190,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -213,18 +199,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -243,15 +226,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -288,46 +270,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. -#### Updating a tracked entity instance { #webapi_updating_tei } +#### Mise à jour d'une instance d'entité suivie { #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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. -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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. -#### Deleting a tracked entity instance { #webapi_deleting_tei } +#### Suppression d'une instance d'entité suivie { #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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } +#### Création et inscription des instances d'entités suivies { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme. ```json { @@ -351,18 +312,16 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -439,44 +398,32 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Attributs d'instances d'entités suivies générés { #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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. De ce fait, des valeurs doivent être fournies pour ces variables lorsque l'on veut générer et réserver des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -491,19 +438,13 @@ variables should only be supplied if you know what you are doing. } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -518,22 +459,13 @@ adding the `?expiration=` to the request. } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut qui est de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -566,54 +498,43 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées -| Propriété | Description ; | +| 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| key | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| value | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| created | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Celui-ci peut accepter trois types de valeurs (les lettres majuscules sont importantes) : `PETITE` (254x254), `MOYENNE` (512x512), `GRANDE` (1024x1024) ou `ORIGINALE`. Les attributs de type image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" ``` -#### File attributes { #file-attributes } +#### Attributs de fichier { #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 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 cc3983b91..ca4b5adb2 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" -revision_date: '2023-06-23' +revision_date: '2024-06-24' tags: - Développement - Version Master de DHIS2 Central @@ -43,6 +43,7 @@ Example: Get audits for data element `BOSZApCrBni`, org unit `DiszpKrYNg8` and c /api/33/audits/dataValue?de=BOSZApCrBni&ou=DiszpKrYNg8&co=TkDhg29x18A ### Tracked entity data value audits { #webapi_tracked_entity_data_value_audits } +**deprecated for removal in version 43 use [tracked entity data value change log endpoint](https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md#event-data-value-change-logs--webapi_event_data_value_change_logs-)** The endpoint for tracked entity data value audits is located at: @@ -60,9 +61,9 @@ Table: Tracked entity data value query parameters | ps | Program stage ID | One or more program sages of the audit event program | | date de début | Start date | Return only audit records created after date | | date de fin | End date | Return only audit records created before date | -| ou Mode | Organisation unit selection mode | SELECTED \| DESCENDANTS | +| ouMode (Mode d'unité d'organisation) | Organisation unit selection mode | SELECTED \| DESCENDANTS | | auditType | UPDATE | DELETE | Filter by one or more audit types | -| skipPaging | faux | vrai | Turn paging on / off | +| skipPaging | faux | vrai | Turn paging on / off | | pagination | faux \| vrai | Whether to enable or disable paging | | page | Nombre | Numéro de page (par défaut 1) | | taille de la page | Nombre | Taille de la page (par défaut 50) | @@ -77,6 +78,8 @@ Example: Get audits for org unit `O6uvpzGd5pu` including descendant org units in ### Tracked entity attribute value audits { #webapi_tracked_entity_attribute_value_audits } +**deprecated for removal in version 43 use [tracked entity attribute change log endpoint](https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md#tracked-entity-attribute-value-change-logs--webapi_tracker_attribute_change_logs-)** + The endpoint for tracked entity attribute value audits is located at: ``` @@ -90,7 +93,7 @@ Table: Tracked entity attribute value query parameters | tea | Tracked entity attribute ID | One or more tracked entity attribute identifiers | | trackedEntities | Tracked entity ID | One or more tracked entity identifiers (comma separated) | | auditType | UPDATE | DELETE | Filter by one or more audit types | -| skipPaging | faux | vrai | Turn paging on / off | +| skipPaging | faux | vrai | Turn paging on / off | | pagination | faux \| vrai | Whether to enable or disable paging | | page | Nombre | Numéro de page (par défaut 1) | | taille de la page | Nombre | Taille de la page (par défaut 50) | @@ -120,7 +123,7 @@ Table: Tracked entity audit query parameters | auditType | SEARCH | READ | Filter by one or more audit types | | date de début | Start date | Start date for audits in `yyyy-mm-dd` format | | date de fin | End date | End date for audits in `yyyy-mm-dd` format | -| skipPaging | faux | vrai | Turn paging on / off. | +| skipPaging | faux | vrai | Turn paging on / off. | | pagination | faux \| vrai | Whether to enable or disable paging | | page | Nombre | Page number (default 1) | | taille de la page | Nombre | Page size (default 50) | @@ -150,7 +153,7 @@ Table: Tracked entity instance audit query parameters | auditType | SEARCH | READ | Filter by one or more audit types | | date de début | Start date | Start date for audits in `yyyy-mm-dd` format | | date de fin | End date | End date for audits in `yyyy-mm-dd` format | -| skipPaging | faux | vrai | Turn paging on / off. | +| skipPaging | faux | vrai | Turn paging on / off. | | pagination | faux \| vrai | Whether to enable or disable paging | | page | Nombre | Page number (default 1) | | taille de la page | Nombre | Page size (default 50) | @@ -182,7 +185,7 @@ Tableau : Paramètres de requête pour l'approbation des données | aoc | Attribute option combo ID | One or more attribute option combination identifiers | | date de début | Start date | Start date for approvals in `yyyy-mm-dd` format | | date de fin | End date | End date for approvals in `yyyy-mm-dd` format | -| skipPaging | faux | vrai | Turn paging on / off | +| skipPaging | faux | vrai | Turn paging on / off | | page | Nombre | Numéro de page (par défaut 1) | | taille de la page | Nombre | Taille de la page (par défaut 50) | 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..7ac949f78 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" -revision_date: '2023-09-27' +revision_date: '2024-06-26' tags: - Développement - Version Master de DHIS2 Central @@ -396,6 +396,7 @@ Le modèle de données d'échange de données agrégées / charge utile est déc | source.requests.filters.items (éléments des filtres de requêtes source) | Tableau/Chaîne | Non | Identifiants des éléments du filtre. | | source.requests.inputIdScheme ( Schéma d'identification d'entrée de la requête source ) | Chaîne | Non | Le schéma d'ID d'entrée peut être `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputDataElementIdScheme ( Schéma d'identification de l'élément de données de sortie des requêtes source) | Chaîne | Non | Le schéma de l'identifiant de l'élément de données de sortie peut être `UID`, `CODE`, `ATTRIBUTE:{ID}`. | +| source.requests.outputDataItemIdScheme | Chaîne | Non | Output data item ID scheme applies to data elements, indicators and program indicators, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme ( Schéma d'identification de l'unité d'organisation de sortie des requêtes source) | Chaîne | Non | Le schéma d'identification de l'unité d'organisation de sortie, peut être `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme (Schéma d'identification de sortie des requêtes source) | Chaîne | Non | Le schéma d'identification général de sortie peut être `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.cible | Objet | Oui | Cible pour l'échange de données agrégées. | @@ -410,6 +411,9 @@ Le modèle de données d'échange de données agrégées / charge utile est déc | source.target.request.orgUnitIdScheme ( Schéma de la requête d'identification de l'unité d'organisation de la source cible) | Chaîne | Non | Le schéma d'identification de l'unité d'organisation d'entrée, peut être `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme ( Schéma de la requête d'identification de la combinaison d'option de catégorie de la source cible) | Chaîne | Non | Le schéma d'identification de la combinaison d'options de catégorie d'entrée peut être `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.idScheme ( Schéma de la requête d'identificationn de la source cible ) | Chaîne | Non | Le schéma d'identification général de l'entrée peut être `UID`, `CODE`, `ATTRIBUTE:{ID}`. | +| source.target.request.importStrategy | Chaîne | Non | Import strategy, can be `CREATE_AND_UPDATE`, `CREATE`, `UPDATE`, `DELETE`. | +| source.target.request.skipAudit | Booléen | Non | "Ignorer l'audit" signifie que les valeurs d'audit ne seront pas générées. Améliore les performances au détriment de la capacité à auditer les modifications. Nécessite l'autorité "F_SKIP_DATA_IMPORT_AUDIT". | +| source.target.request.dryRun | Booléen | Non | Pour sauvegarder les modifications sur le serveur ou pour renvoyer le résumé de l'importation. | ### Gerer les erreurs { #error-handling } 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 8cecf7ca1..b002a4423 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 @@ -1,12 +1,12 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" -revision_date: '2024-05-21' +revision_date: '2024-06-03' tags: - Développement - Version Master de DHIS2 Central --- -# Métadonnées { #metadata } +# Metadata { #webapi_metadata } ## Schémas d'identification { #webapi_identifier_schemes } @@ -64,7 +64,7 @@ Tableau : Paramètres de requête | pagination | vrai | faux | vrai | Indique s'il faut renvoyer les listes d'éléments sous forme de pages. | | page | nombre | 1 | Définit le numéro de page à renvoyer. | | taille de la page | nombre | 50 | Définit le nombre d'éléments à renvoyer pour chaque page. | -| Ordre | property:asc/iasc/desc/idesc || Order the output using a specified order, only properties that are both persisted and simple (no collections, idObjects etc) are supported. iasc and idesc are case insensitive sorting. If it is wanted to sort for more than one property, separate them using a comma. | +| Ordre | property:asc/iasc/desc/idesc || Ordonne la sortie dans un ordre spécifique. Seules les propriétés qui sont à la fois persistantes et simples (pas de collections, d'identifiants d'objets, etc.) sont prises en charge. iasc et idesc sont des tris insensibles à la casse. Si vous souhaitez trier plusieurs propriétés, séparez-les par une virgule. | Voici un exemple de comment ces paramètres peuvent être utilisés pour obtenir une liste complète de groupes d'éléments de données dans un format de réponse XML : @@ -474,7 +474,7 @@ Le _nom de l'entité_ utilise la notation camel case. Par exemple, le point d'ex /api/dataElements -> **_NOTE:_** When updating objects, all existing property values will be overwritten, even if the new value is null. Please use [JSON Patch API](#webapi_partial_updates) in case you want do partial update to an object. +>**_NOTE:_** Lors de la mise à jour des objets, toutes les valeurs des propriétés existantes seront écrasées, même si la nouvelle valeur est nulle. Veuillez utiliser l'[API de patch JSON](#webapi_partial_updates) si vous souhaitez effectuer une mise à jour partielle d'un objet. ### Création et mise à jour des paramètres { #webapi_metadata_create_update } @@ -651,12 +651,7 @@ Le format de la charge est le suivant : ### Validation des charges { #webapi_validating_payloads } -DHIS 2 supports system wide validation of metadata payloads, which means -that create and update operations on the API endpoints will be checked for -valid payload before allowing changes to be made. To find out what validations -are in place for a specific endpoint, have a look at the `/api/schemas` -endpoint, i.e. to figure out which constraints a data element have, you -would go to `/api/schemas/dataElement`. +DHIS 2 permet de valider des métadonnées à l'échelle du système, ce qui signifie que les opérations de création et de mise à jour sur les points d'extrémité d'API devront être valides avant que les modifications ne soient autorisées. Pour connaître les validations disponibles pour un point d'extrémité spécifique, consultez ce point d'extrémité : `/api/schemas`. C'est-à-dire que pour connaître les contraintes d'un élément de données, vous devez vous rendre dans `/api/schemas/dataElement`. Vous pouvez également valider votre charge manuellement en l'envoyant au point d'extrémité du schéma approprié. Si vous vouliez valider la constante dans la section de création précédente, vous devriez l'envoyer comme ceci : @@ -1059,9 +1054,9 @@ Tableau : Paramètres d'importation | Nom | Type | Par défaut | Description | |-------------------|--------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------| | `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. | +| `geoJsonProperty` | `Chaîne` | _non défini_ | 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. | +| `attributeId` | `Chaîne` | _non défini_ | 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. | @@ -1611,11 +1606,11 @@ L'opération de fusion transfère toutes les associations de métadonnées de l' Les métadonnées suivantes sont mises à jour : -| Métadonnées | Propriété | Action taken | +| Métadonnées | Propriété | Mesure prise | |---------------------|--------------------------------------------|-----------------------------------------------------------------------------| | IndicatorGroup | membres | Indicateur source supprimé, indicateur cible ajouté | | Ensemble de données | des indicateurs | Indicateur source supprimé, indicateur cible ajouté | -| DataDimensionalItem | n/a | Tous les éléments de données associés à des sources seront reliés à la cible. | +| Élément dimensionnel de données | n/a | Tous les éléments de données associés à des sources seront reliés à la cible. | | Section | des indicateurs | Indicateur source supprimé, indicateur cible ajouté | | Configuration | Indicateurs infrastructurels (Groupe d'indicateurs) | Indicateur source supprimé, indicateur cible ajouté | | Indicateur | numérateur / dénominateur | Remplace toute référence source par la référence cible | @@ -3355,7 +3350,7 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | PHONE_NUMBER | La validation est basée sur cette expression rationnelle `^[0-9+\\N-(\N-)#\N.\Ns\N/ext-]{6,50}$`. La longueur maximale est de 50.
Exemples : +4733987937, (+47) 3398 7937, (47) 3398 7937.123 | EMAIL | Format général des email : abc@email.com | BOOLÉEN | `vrai` or `faux` -| TRUE_ONLY (vrai uniquement) | Only accept `true` +| TRUE_ONLY (vrai uniquement) | N'accepte que `true` | DATE | Utiliser le format `yyyy-MM-dd` | DATETIME (date et heure) | Utiliser le format `yyyy-MM-dd HH:mm:ssZ` ou `yyyy-MM-dd 'T'HH:mm:ss` | TEMPS | Utiliser le format `HH:mm` @@ -3366,11 +3361,11 @@ Le paramètre `fields` peut être utilisé pour restreindre les champs inclus da | INTEGER_POSITIVE | La valeur est un nombre entier positif | INTEGER_NEGATIVE | La valeur est un nombre entier négatif | INTEGER_ZERO_OR_POSITIVE | La valeur est un entier positif ou nul -| TRACKER_ASSOCIATE | Aucun +| TRACKER_ASSOCIÉ | Aucun | NOM D'UTILISATEUR | La valeur est un nom d'utilisateur pour un `utilisateur` existant | COORDINATE | Aucun | ORGANISATION_UNIT | La valeur est un UID valide d'une `unité d'organisation` existante -| REFERENCE | Aucun +| RÉFÉRENCE | Aucun | AGE | La valeur est une date de naissance. Utiliser le même format que pour le type DATE. | URL | La valeur est une URL valide | FILE_RESOURCE | La valeur est un UID valide d'une `ressource de fichier` existante @@ -3408,7 +3403,7 @@ En cas de succès, la réponse contiendra un nouveau `UID` de `Programme` et res La réponse contiendra également un en-tête `Location` (emplacement) avec un lien vers le `Programme` nouvellement créé. Par exemple, si le programme est exécuté localement, la valeur de `Location` sera `http://localhost:9090/api/programs/Program456b`. -#### Copy options { #copy-options } +#### Options de copie { #copy-options } L'API permet d'utiliser un préfixe personnalisé à titre facultatif, lequel sera ajouté aux propriétés suivantes. @@ -3446,7 +3441,7 @@ Si une propriété a dépassé sa limite de caractères, une erreur sera renvoy } ``` -If trying to copy a Program that is not found, a response like this will be returned: +Si l'utilisateur essaie de copier un programme qui n'est pas trouvé, une réponse de ce type sera renvoyée : ```json { "httpStatus": "Not Found", @@ -3471,10 +3466,10 @@ Un `Utilisateur` aura besoin des autorisations suivantes pour pouvoir copier un Un `Programme` doit avoir un des statuts suivants pour pouvoir être copié : - Accès public en `lecture` et en `écriture` -- A specific `User` to have sharing `read` & `write` access -- A `User` is part of a `UserGroup` that has sharing `read` & `write` access +- Un `Utilisateur` spécifique autorisé à partager les accès en `lecture` et en `écriture`. +- Un `utilisateur` faisant partie d'un `groupe d'utilisateurs` et qui est autorisé à partager les accès en `lecture` et en `écriture`. -If a `User` does not have the correct permissions, a `Forbidden` response is returned like so: +Si un `utilisateur` n'a pas les bonnes autorisations, une réponse `Forbidden` (d'interdiction) est renvoyée comme suit : ```json { @@ -3486,48 +3481,48 @@ If a `User` does not have the correct permissions, a `Forbidden` response is ret } ``` -### Points to note { #points-to-note } +### Points à noter { #points-to-note } -#### Deep and shallow copy { #deep-and-shallow-copy } +#### Copie profonde et copie superficielle { #deep-and-shallow-copy } -When a `Program` is copied, certain properties of the `Program` need different kinds of copying. It is important to be aware of what has been deep-copied and what has been shallow-copied. -First of all let's explain the difference between deep and shallow copying in this context. +Lorsqu'un `Programme` est copié, certaines propriétés du `Programme` nécessitent des types de copie différents. Il est important de savoir ce qui a été copié en profondeur et ce qui a été copié superficiellement. +Tout d'abord, expliquons la différence entre la copie profonde et la copie superficielle dans ce contexte. -##### Deep copy { #deep-copy } +##### Copie profonde { #deep-copy } -A deep copy in this context means that a completely new instance of a `Program` or `Program` property has been created with its own unique identifiers. These include amongst others: +Dans ce contexte, une copie profonde signifie qu'une instance entièrement nouvelle d'un `Programme` ou d'une propriété de `Programme` a été créée avec ses propres identifiants uniques. Il s'agit entre autres de : - identifiant - uid -Deep copies of `Program` properties will all belong to the newly-created `Program` copy. +Les copies profondes des propriétés de `programme` feront toutes partie de la copie du `programme` nouvellement créée. -##### Shallow copy { #shallow-copy } +##### Copie superficielle { #shallow-copy } -A shallow copy in this context means that an existing `Program` property will be reused by the newly-created `Program` or `Program` property. +Dans ce contexte, une copie superficielle signifie qu'une propriété de `programme` existante sera réutilisée par le `programme` ou la propriété de `programme` nouvellement créé(e). -#### Properties that get deep copied { #properties-that-get-deep-copied } +#### Propriétés qui ont été copiées en profondeur { #properties-that-get-deep-copied } -All properties below have been deep copied. Anything not in included in this table means that it has been shallow copied. +Toutes les propriétés ci-dessous ont été copiées en profondeur. Si une propriété ne figure pas dans ce tableau, cela signifie qu'elle a été copié superficiellement. -| Objet | Property of | +| Objet | Propriété de | |--------------------------------|--------------| | Programme | | -| ProgramSection | Programme | +| Section de programme | Programme | | Indicateur de programme | Programme | -| ProgramRuleVariable | Programme | +| Variable de règle de programme | Programme | | Étape du programme | Programme | -| ProgramStageSection | Étape du programme | -| ProgramStageSectionDataElement | Étape du programme | +| Section d'une étape de programme | Étape du programme | +| Élément de données d'une section d'étape de programme | Étape du programme | | Inscription | | -> **Note** +> **Remarque** > -> The following properties have been set as empty as an initial approach. This approach should keep things simple to start off with. +> Les propriétés suivantes ont été définies comme vides dans une première approche. Cette approche devrait permettre de simplifier les choses pour commencer. | Objet | Propriété | |-------------------------------|-------------------| -| Indicateur de programme | groups | -| ProgramStageSection | programIndicators | +| Indicateur de programme | groupes | +| Section d'une étape de programme | Indicateurs de programme | | Inscription | événements | 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 d6050513b..2210c3599 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 @@ -33,15 +33,15 @@ The following table highlights the differences between the previous tracker impo | Objet Tracker | Avant | Maintenant | | --- | --- | --- | -| **Attribut** | `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` | +| **Attribut** | `created` (créé)
`lastUpdated` (dernière mise à jour) | `createdAt` (créé à)
`updatedAt` (mis à jour à) | +| **Valeur de données** | `created`
`lastUpdated`
`createByUserInfo` (créé avec les informations d'utilisateur)
`lastUpdatedByUserInfo` (dernière mise à jour avec les informations d'utilisateur) | `createdAt`
`updatedAt`
`createdBy` (créé par)
`updatedBy` (mis à jour par) | +| **Inscription** | `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` | +| **Propriétaire du programme** | `ownerOrgUnit`
`trackedEntityInstance` | `orgUnit`
`trackedEntity` | +| **Élément de relation** | `trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event` | `trackedEntity`
`enrollment`
`event` | +| **Relation** | `created` (créé)
`lastUpdated` (dernière mise à jour) | `createdAt` (créé à)
`updatedAt` (mis à jour à) | +| **Entité suivie** | `trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo` | `trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy` | > **Note** > @@ -80,7 +80,7 @@ These tables highlight the old endpoint differences in request parameters for `G | `trackedEntityInstance` | `trackedEntity` (entité suivie) | | `startDate`
`endDate` | `occurredAfter`
`occurredBefore` | | `dueDateStart`
`dueDateEnd` | `scheduledAfter`
`scheduledBefore` | -| `dernière mise à jour` | Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +| `dernière mise à jour` | Supprimé - obsolète, voir :
  • `updatedAfter`
  • `updatedBefore`
| | `lastUpdatedStartDate`
`lastUpdateEndDate`
`lastUpdateDuration` | `updatedAfter`
`updatedBefore`
`updatedWithin` | #### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } @@ -89,7 +89,7 @@ These tables highlight the old endpoint differences in request parameters for `G | --- | --- | | `trackedEntityInstance` | `trackedEntity` (entité suivie) | | `uo` | `orgUnit` (unité d'organisation) | -| `programStartDate`
`programEndDate` | Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +| `programStartDate`
`programEndDate` | Supprimé - obsolète, voir
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| | `programEnrollmentStartDate`
`programEnrollmentEndDate` | `enrollmentEnrolledAfter`
`enrollmentEnrolledBefore` | | `programIncidentStartDate`
`programIncidentEndDate` | `enrollmentOccurredAfter`
`enrollmentOccurredBefore` | | `eventStartDate`
`eventEndDate` | `eventOccurredAfter`
`eventOccurredBefore` | diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-deprecated-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-deprecated-md index 3aca23029..ad5a08ceb 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-deprecated-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__tracker-deprecated-md @@ -54,147 +54,137 @@ Les noms des propriétés d'API ont été modifiés afin qu'ils soient cohérent |Objet Tracker|Avant|Maintenant| |---|---|---| -|**Attribut**|`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`| +|**Attribut**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Valeur de données**|`created`
`lastUpdated`
`createByUserInfo` (créé avec les informations d'utilisateur)
`lastUpdatedByUserInfo` (dernière mise à jour avec les informations d'utilisateur)|`createdAt`
`updatedAt`
`createdBy` (créé par)
`updatedBy` (mis à jour par)| +|**Inscription**|`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`| +|**Propriétaire du programme**|`ownerOrgUnit`
`trackedEntityInstance`|`orgUnit`
`trackedEntity`| +|**Élément de relation**|`trackedEntityInstance.trackedEntityInstance`
`enrollment.enrollment`
`event.event`|`trackedEntity`
`enrollment`
`event`| +|**Relation**|`created` (créé)
`lastUpdated` (dernière mise à jour)|`createdAt` (créé à)
`updatedAt` (mis à jour à)| +|**Entité suivie**|`trackedEntityInstance`
`created`
`createdAtClient`
`lastUpdated`
`lastUpdatedAtClient`
`createByUserInfo`
`lastUpdatedByUserInfo`|`trackedEntity`
`createdAt`
`createdAtClient`
`updatedAt`
`updatedAtClient`
`createdBy`
`updatedBy`| -> **Note** +> **Remarque** > -> Property `assignedUser` was a string before and is now an object of the following shape (type `User`): +> La propriété `assignedUser` (utilisateur assigné) était auparavant une chaîne de caractères et est maintenant un objet de la forme suivante (type `User`) : > ```json > { -> "assignedUser": { -> "uid": "ABCDEF12345", -> "username": "username", -> "firstName": "John", -> "surname": "Doe" -> } +> "assignedUser" : { +> "uid" : "ABCDEF12345", +> "username" : "username", +> "firstName" : "John", +> "nom de famille" : "Doe" +> } > } > ``` -### Semicolon as separator for identifiers (UID) { #semicolon-as-separator-for-identifiers-uid } +### Point-virgule comme séparateur pour les identifiants (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 +Les champs suivants sont concernés -* `event.attributeCategoryOptions` (as well as an event returned as part of a relationship +* `event.attributeCategoryOptions` (ainsi qu'un événement renvoyé dans le cadre d'une relation `from`/`to`) -### Tracker import changelog (`POST`) { #tracker-import-changelog-post } +### Journal des modifications (changelog) de l'importation Tracker (`POST`) { #tracker-import-changelog-post } -The previous tracker import endpoints +Les précédents points d'extrémité de l'importation Tracker * `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 +sont remplacés par le nouveau point d'extrémité * `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. +[Importation Tracker] (https://docs.dhis2.org/en/develop/using-the-api/dhis-core-version-master/tracker.html#webapi_nti_import) décrit comment utiliser ce nouveau point d'extrémité. -### Tracker export changelog (`GET`) { #tracker-export-changelog-get } +### Journal des modifications de l'exportation Tracker (`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. +En plus des noms modifiés indiqués dans [Noms de propriétés](#webapi_tracker_migration_names), certains paramètres de requête ont également été modifiés. -The following tables list the differences in old and new request parameters for `GET` endpoints. +Les tableaux suivants énumèrent les différences entre les anciens et les nouveaux paramètres de requête pour les points d'extrémité `GET`. -#### Request parameter changes for `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/trackedEntities` { #request-parameter-changes-for-get-apitrackertrackedentities } |Avant|Maintenant| |---|---| -|`assignedUser` (utilisateur attribué)|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| -|`attribut`|Removed - use `filter` instead| +|`assignedUser` (utilisateur attribué)|`assignedUsers`
Les valeurs sont désormais séparées par une virgule au lieu d'un point-virgule.| +|`attachment`|Supprimé| +|`attribut`|Supprimé - utiliser `filter` à la place| |`eventStartDate`
`eventEndDate`|`eventOccurredAfter`
`eventOccurredBefore`| -|`includeAllAttributes` (inclure tous les attributs)|Removed| +|`includeAllAttributes` (inclure tous les attributs)|Supprimé| |`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| |`ouMode`|`orgUnitMode`| -|`uo`|`orgUnits`
Values are now separated by comma instead of semicolon.| +|`uo`|`orgUnits`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`programEnrollmentStartDate`
`programEnrollmentEndDate`|`enrollmentEnrolledAfter`
`enrollmentEnrolledBefore`| |`programIncidentStartDate`
`programIncidentEndDate`|`enrollmentOccurredAfter`
`enrollmentOccurredBefore`| -|`programStartDate`
`programEndDate`|Removed - obsolete, see
  • `enrollmentEnrolledAfter`
  • `enrollmentEnrolledBefore`
| +|`programStartDate`
`programEndDate`|Supprimé - obsolète, voir
  • `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.| +|`requête`|Supprimé - utiliser `filter` à la place| +|`skipMeta` (ignorer les métadonnées)|Supprimé| +|`skipPaging` (ignorer la pagination)|`paging`
C'est l'inverse, donc `paging=false` remplace `skipPaging=true`.| +|`trackedEntityInstance`|`trackedEntities`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| -#### Request parameter changes for `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/enrollments` { #request-parameter-changes-for-get-apitrackerenrollments } |Avant|Maintenant| |---|---| -|`inscription`|`enrollments`
Values are now separated by comma instead of semicolon.| +|`inscription`|`enrollments`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`lastUpdated`
`lastUpdatedDuration`|`updatedAfter`
`updatedWithin`| |`ouMode`|`orgUnitMode`| -|`uo`|`orgUnits`
Values are now separated by comma instead of semicolon.| +|`uo`|`orgUnits`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`programStartDate`
`programEndDate`|`enrolledAfter`
`enrolledBefore`| |`programStatus` (statut de programme)|`statut`| -|`skipPaging` (ignorer la pagination)|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| +|`skipPaging` (ignorer la pagination)|`paging`
C'est l'inverse, donc `paging=false` remplace `skipPaging=true`.| |`trackedEntityInstance`|`trackedEntity` (entité suivie)| -#### Request parameter changes for `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/events` { #request-parameter-changes-for-get-apitrackerevents } |Avant|Maintenant| |---|---| -|`assignedUser` (utilisateur assigné)|`assignedUsers`
Values are now separated by comma instead of semicolon.| -|`attachment`|Removed| +|`assignedUser` (utilisateur assigné)|`assignedUsers`
Les valeurs sont désormais séparées par une virgule au lieu d'un point-virgule.| +|`attachment`|Supprimé| |`attributeCc`|`attributeCategoryCombo`| -|`attributeCos`|`attributeCategoryOptions`
Values are now separated by comma instead of semicolon.| +|`attributeCos`|`attributeCategoryOptions`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`dueDateStart`
`dueDateEnd`|`scheduledAfter`
`scheduledBefore`| -|`événement`|`events`
Values are now separated by comma instead of semicolon.| +|`événement`|`events`
Les valeurs sont désormais séparées par une virgule et non par un point-virgule.| |`lastUpdatedStartDate`
`lastUpdatedEndDate`
`lastUpdatedDuration`|`updatedAfter`
`updatedBefore`
`updatedWithin`| -|`dernière mise à jour`|Removed - obsolete, see:
  • `updatedAfter`
  • `updatedBefore`
| +|`dernière mise à jour`|Supprimé - obsolète, voir :
  • `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`.| +|`skipEventId` (ignorer l'identifiant de l'élément)|Supprimé| +|`skipMeta` (ignorer les métadonnées)|Supprimé| +|`skipPaging` (ignorer la pagination)|`paging`
C'est l'inverse, donc `paging=false` remplace `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 } +#### Modifications apportées aux paramètres de requête pour `GET /api/tracker/relationships` { #request-parameter-changes-for-get-apitrackerrelationships } |Avant|Maintenant| |---|---| -|`skipPaging` (ignorer la pagination)|`paging`
Is the inverse so `paging=false` replaces `skipPaging=true`.| +|`skipPaging` (ignorer la pagination)|`paging`
C'est l'inverse, donc `paging=false` remplace `skipPaging=true`.| |`tei`|`trackedEntity` (entité suivie)| -## Tracker Web API { #webapi_tracker_api } +## API Web du Tracker { #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. +L'API Web du Tracker est constitué de 3 points d'extrémité qui ont un support CRUD complet (créer, lire, mettre à jour, supprimer). Les 3 points d'extrémité sont `/api/trackedEntityInstances`, `/api/enrollments` et `/api/events` et ils prennent en charge les instances d'entités suivies, les inscriptions et les événements. -### Tracked entity instance management { #webapi_tracked_entity_instance_management } +### Gestion des instances d'entités suivies { #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. +Les instances d'entités suivies bénéficient d'une prise en charge CRUD complète dans l'API. Avec l'API d'inscription, la plupart des opérations nécessaires pour travailler avec les instances d'entités suivies et les programmes sont prises en charge. /api/33/trackedEntityInstances -#### Creating a new tracked entity instance { #webapi_creating_tei } +#### Création d'une nouvelle instance d'entité suivie { #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: +Pour créer une nouvelle personne dans le système, vous devez utiliser la ressource *trackedEntityInstances* (instances d'entités suivies). Un modèle de charge est présenté ci-dessous : ```json { @@ -208,9 +198,7 @@ For creating a new person in the system, you will be working with the } ``` -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: +Le champ "geometry" accepte un objet GeoJson, dont le type doit correspondre au featureType (type de fonctionnalité) du TrackedEntityType (type d'entité suivie). Voici un exemple d'objet GeoJson : ```json { @@ -219,18 +207,15 @@ definition. An example GeoJson object looks like this: } ``` -The "coordinates" field was introduced in 2.29, and accepts a coordinate -or a polygon as a value. +Le champ "coordinates" a été introduit dans la version 2.29 et accepte comme valeur une coordonnée ou un polygone. -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: +Pour obtenir les ID de `relationship` et `attributes`, vous pouvez consulter respectivement les ressources `relationshipTypes` et `trackedEntityAttributes`. +Pour créer une instance d'entité suivie, vous devez utiliser la méthode HTTP *POST*. +Vous pouvez envoyer la charge à l'URL suivante : /api/trackedEntityInstances -For example, let us create a new instance of a person tracked entity and -specify its first name and last name attributes: +Par exemple, créons une nouvelle instance pour une entité suivie de personne et spécifions ses attributs 'prénom' et 'nom' : ```json { @@ -249,15 +234,14 @@ specify its first name and last name attributes: } ``` -To push this to the server you can use the cURL command like this: +Pour envoyer ces données au serveur, vous pouvez utiliser la commande cURL comme suit : ```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:[]() +Pour créer plusieurs instances à l'aide d'une seule requête, vous pouvez envelopper la charge dans un tableau extérieur comme ceci et effectuer une requête POST à la même ressource comme ci-dessus :[]() ```json { @@ -294,46 +278,25 @@ an outer array like this and POST to the same resource as above:[]() } ``` -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. +Le système ne permet pas la création d'une instance d'entité suivie (ainsi que l'inscription et l'événement) avec un UID déjà utilisé dans le système. Cela signifie que les UID ne peuvent pas être réutilisés. -#### Updating a tracked entity instance { #webapi_updating_tei } +#### Mise à jour d'une instance d'entité suivie { #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: +Pour la mise à jour d'une instance d'entité suivie, la charge est identique à celle de la section précédente. La différence est que vous devez utiliser la méthode HTTP *PUT* pour la requête lors de l'envoi de la charge. Vous devrez également ajouter l'identifiant de la personne à la ressource *trackedEntityInstances* dans l'URL comme suit, où `` doit être remplacé par l'identifiant de l'instance d'entité suivie : /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. +La charge doit contenir tous les attributs et relations, même ceux qui n'ont pas été modifiés. Les attributs ou les relations qui étaient présents auparavant et qui ne sont plus présents dans la charge actuelle seront supprimés du système. Cela signifie que si des attributs/relations sont vides dans la charge actuelle, tous les attributs/relations existants seront supprimés du système. Depuis la version 2.31, il est possible d'ignorer les attributs/relations vides dans la charge en cours d'utilisation. Vous pouvez définir le paramètre de requête `ignoreEmptyCollection` sur `true` si vous ne voulez pas envoyer des attributs ou des relations et que vous ne voulez pas non plus qu'ils soient supprimés du système. -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. +Il n'est pas autorisé de mettre à jour une instance d'entité suivie déjà supprimée. Il n'est pas non plus autorisé de marquer une instance d'entité suivie comme supprimée via une requête de mise à jour. Les mêmes règles s'appliquent aux inscriptions et aux événements. -#### Deleting a tracked entity instance { #webapi_deleting_tei } +#### Suppression d'une instance d'entité suivie { #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. +Pour supprimer une instance d'entité suivie, envoyez une requête à l'URL qui identifie cette instance d'entité suivie avec la méthode *DELETE*. L'URL est la même que celle utilisée plus haut pour la mise à jour. -#### Create and enroll tracked entity instances { #webapi_create_enroll_tei } +#### Création et inscription des instances d'entités suivies { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie et de l'inscrire en même temps à un programme ```json { @@ -357,18 +320,16 @@ instance and at the same time enroll into a program. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Exemple complet de charge comprenant : l'instance d'entité suivie, l'inscription et l'événement. { #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. +Il est également possible de créer (et de mettre à jour) une instance d'entité suivie, de l'inscrire en même temps à un programme et de créer un événement. ```json { @@ -445,44 +406,32 @@ the same time enroll into a program and create an event. } ``` -You would send this to the server as you would normally when creating or -updating a new tracked entity instance. +Vous l'enverrez au serveur comme vous le feriez normalement lors de la création ou de la mise à jour d'une nouvelle instance d'entité suivie. ```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 } +#### Attributs d'instances d'entités suivies générés { #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. +Les attributs d'instances d'entités suivies dont les valeurs uniques sont générées automatiquement ont trois points d'extrémité qui sont utilisés par les applications. Ces points d'extrémité sont tous utilisés pour générer et réserver des valeurs. -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. +Dans la version 2.29, nous avons introduit TextPattern pour définir et générer ces modèles. Tous les modèles existants seront convertis en modèles TextPattern valides lors de la mise à jour vers la version 2.29. -> **Note** +> **Remarque** > -> 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. +> À partir de la version 2.29, tous ces points d'extrémité vous demanderont d'inclure toutes les +> variables rapportées par le point d'extrémité `requiredValues` et qui sont listées comme +> obligatoires. Les modèles existants, composés uniquement de `#`, seront mis à jour +> vers la nouvelle syntaxe TextPattern `RANDOM()`. Le > segment RANDOM +du TextPattern n'est pas une variable obligatoire, donc ce > point d'extrémité fonctionnera comme auparavant pour les modèles définis avant la version 2.29. -##### Finding required values { #finding-required-values } +##### Recherche des valeurs obligatoires { #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. +Un TextPattern peut contenir des variables qui changent en fonction de différents facteurs. Certains de ces facteurs sont inconnus du serveur. Pour cela, les valeurs de ces variables doivent être fournies lors de la génération et de la réservation des valeurs. -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. +Cet point d'extrémité va renvoyer un plan de valeurs obligatoires et optionnelles, que le serveur va intégrer dans le TextPattern lorsqu'il génère de nouvelles valeurs. Les variables obligatoires doivent être fournies pour la génération, mais les variables optionnelles ne doivent être fournies que si vous savez ce que vous faites. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/requiredValues @@ -497,19 +446,13 @@ variables should only be supplied if you know what you are doing. } ``` -##### Generate value endpoint { #webapi_generate_values } +##### Point d'extrémité de de génération de valeur { #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. +Les applications web en ligne et les autres clients qui souhaitent générer une valeur qui sera utilisée immédiatement peuvent utiliser le point d'extrémité de génération simple. Ce point d'extrémité génère une valeur dont l'unicité est garantie au moment de la génération. La valeur ne sera pas non plus réservée. Depuis la version 2.29, ce point d'extrémité réserve également la valeur générée pendant 3 jours. -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -The expiration time can also be overridden at the time of generation, by -adding the `?expiration=` to the request. +Le délai d'expiration peut également être modifié au moment de la génération, en ajoutant l'option `?expiration=` à la requête. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generate?ORG_UNIT_CODE=OSLO @@ -524,22 +467,13 @@ adding the `?expiration=` to the request. } ``` -##### Generate and reserve value endpoint { #webapi_generate_reserve_values } +##### Point d'extrémité de génération et de réservation de valeur { #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). +Le point d'extrémité de génération et de réservation est utilisé par les clients hors ligne qui ont besoin d'enregistrer des entités suivies avec des identifiants uniques. Ils réservent un certain nombre d'identifiants uniques que ce dispositif utilisera ensuite lors de l'enregistrement de nouvelles instances d'entités suivies. Une requête est envoyée à ce point d'extrémité afin de récupérer un certain nombre de valeurs réservées pour les instances d'entités suivies. Un paramètre facultatif, "numberToReserve", indique le nombre d'identifiants à générer (par défaut, ce paramètre est défini sur 1). -If your TextPattern includes required values, you can pass them as -parameters like the example below: +Si votre TextPattern comprend des valeurs obligatoires, vous pouvez les utiliser comme paramètres dans l'exemple ci-dessous : -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. +Comme pour le point d'extrémité de génération, ce point d'extrémité peut également spécifier le délai d'expiration de la même manière. En ajoutant `?expiration=`, vous pouvez remplacer le délai par défaut de 60 jours. GET /api/33/trackedEntityAttributes/Gs1ICEQTPlG/generateAndReserve?numberToReserve=3&ORG_UNIT_CODE=OSLO @@ -572,54 +506,43 @@ you can override the default 60 days. ] ``` -##### Reserved values { #reserved-values } +##### Valeurs réservées { #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: +Les valeurs réservées ne sont actuellement pas accessibles via l'API, mais elles sont renvoyées par les points d'extrémité `generate` (génération) et `generate And Reserve` (génération et réservation). Le tableau suivant explique les propriétés de l'objet de valeur réservée : ##### -Table: Reserved values +Tableau : Valeurs réservées | 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. +| ownerObject | Le type de métadonnées référencé lors de la génération et de la réservation de la valeur. Actuellement, seul TRACKEDENTITYATTRIBUTE (attribut d'entité suivie) est pris en charge. | +| ownerUid | L'uid de l'objet de métadonnées référencé lors de la génération et de la réservation de la valeur. | +| clé | Une valeur partiellement générée où les segments générés ne sont pas encore ajoutés. | +| valeur | La valeur réservée. C'est la valeur que vous envoyez au serveur lorsque vous stockez des données. | +| créés | Date et heure à laquelle la réservation a été effectuée | +| expiryDate | Date et heure à partir de laquelle la réservation ne sera plus valable. | + +Les réservations expirées sont supprimées quotidiennement. Si un modèle change, les valeurs déjà réservées seront acceptées lors du stockage des données, même si elles ne correspondent pas au nouveau modèle, tant que la réservation n'a pas expiré. + +#### Attributs d'image { #image-attributes } + +Travailler avec des attributs d'image ressemble beaucoup à travailler avec des valeurs de données de fichier. La valeur d'un attribut de type image est l'identifiant de la ressource de fichier associée. Une requête GET au point d'extrémité `/api/trackedEntityInstances///image` renverra l'image proprement dite. Les paramètres facultatifs height (hauteur) et width (largeur) peuvent être utilisés pour spécifier les dimensions de l'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. +L'API prend également en charge un paramètre *dimension*. Il peut prendre trois valeurs possibles (attention aux lettres majuscules) : `SMALL` (254x254), `MEDIUM` (512x512), `LARGE` (1024x1024) ou `ORIGINAL`. Les attributs de type d'image seront stockés dans des tailles pré-générées et seront fournis par requête en fonction de la valeur du paramètre `dimension`. ```bash curl "http://server/api/33/trackedEntityInstances/ZRyCnJ1qUXS/zDhUuAYrxNC/image?dimension=MEDIUM" ``` -#### File attributes { #file-attributes } +#### Attributs de fichier { #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 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 750df9dd1..86642b1a7 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,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-06-20' +revision_date: '2024-06-26' tags: - Développement - Version Master de DHIS2 Central @@ -161,7 +161,6 @@ signalera les cas exceptionnels entre ces deux. Les `Relations` sont des objets qui relient deux autres objets Tracker. Les contraintes auxquelles chaque côté de la relation doit se conformer sont basées sur le `Type de relation` de la `Relation`. - | Propriété | Description ; | Obligatoire | Immuable | Type | Exemple | |---|---|---|---|---|---| | relation | L'identifiant de la relation. Il est généré au cas où il n'est pas fourni | Non | Oui | Chaîne : Uid | ABCDEF12345 | @@ -1479,7 +1478,7 @@ To override the expiration time, add `?expiration=` to the reque } ``` -#### Generate and reserve value endpoint { #webapi_generate_reserve_values } +#### Point d'extrémité de génération et de réservation de valeur { #webapi_generate_reserve_values } Offline clients can use this endpoint to reserve a number of unique IDs for later use when registering new tracked entity instances. The number of IDs to generate can be specified with the `numberToReserve` parameter (default is 1). @@ -1517,27 +1516,22 @@ To override the default expiration time of 60 days, add `?expiration=/merge | Nom du paramètre | Description | Type | Valeurs autorisées | @@ -3051,28 +3344,47 @@ To merge a Potential Duplicate, i.e. the two tracked entities the Potential Dupl The endpoint accepts a single parameter, `mergeStrategy`, which determines the strategy used when merging. For the `AUTO` strategy, the server will attempt to merge the two tracked entities automatically without user input. This strategy only allows merging tracked entities without conflicting data (see examples below). The `MANUAL` strategy 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 evaluates the mergability of the two tracked entities and merges them if they are deemed mergable. The mergability is based on whether the two tracked entities have any conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible conflicts include: + +The automatic merge evaluates the mergability of the two tracked entities and merges them if they +are deemed mergeable. The mergability is based on whether the two tracked entities have any +conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible +conflicts include: + - The same attribute has different values in each tracked entity. - Both tracked entities are enrolled in the same program. - Tracked entities have different types. If any conflict is encountered, an error message 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 to the original. This includes attribute values, enrollments (including events), and relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is marked as `MERGED`. - -When requesting an automatic merge, a payload is not required and will be ignored. +When no conflicts are found, all data in the duplicate that is not already in the original will be +moved to the original. This includes attribute values, enrollments (including events), and +relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is +marked as `MERGED`. When requesting an automatic merge, a payload is not required and will be +ignored. #### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when there are resolvable conflicts or when not all the data needs to be moved during the 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 involves the user explicitly requesting to move data, there are some additional checks: -- 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 entities (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) + +The manual merge is suitable when there are resolvable conflicts or when not all the data needs to +be moved during the 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 involves the user explicitly requesting to move data, there are some +additional checks: + +- 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 entities (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 entities 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 was just created, but not enrolled for example. +When a manual merge is requested without a payload, we are telling the API to merge the two tracked +entities 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 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: -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"], @@ -3081,12 +3393,20 @@ Otherwise, if a manual merge is requested with a payload, the payload refers to } ``` -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. +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 entities 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 entities 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. +Currently it is not possible to merge tracked entities 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 +entities 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. diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__design-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__design-md index 0f081a2fd..39becf328 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__design-md +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__design-md @@ -54,7 +54,7 @@ Besides screening data, all other data are collected according to the below data |Structure|Description| |---------|-----------| -|**Enrollment**|The stage collects the basic TEI attributes. Please note that some of the attributes show the *'GEN - '* prefix. To know more about the [Common Metadata Library](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
**The stage is non-repeatable**.| +|**Inscription**|The stage collects the basic TEI attributes. Please note that some of the attributes show the *'GEN - '* prefix. To know more about the [Common Metadata Library](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
**The stage is non-repeatable**.| |**Case report**|The stage collects basic information on the patient's signs and symptoms, exposure and preventive measures.
Only one AFI event can be recorded for every TEI. In case of a new AFI even for the same TEI, a new TEI has to be enrolled.
**The stage is non-repeatable**.| |**Specimen collection & transport**|The stage collects basic information on specimen collection and transportation.
**The stage is repeatable** in case more than one specimen collection/transportation is required per TEI.| |**Laboratory testing & result**|The stage collects basic information on tests performed and pathogens identified.
**The stage is repeatable** in case more than one specimen is processed per TEI.| diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-CASE-SURVEILLANCE__design-md index 3be58451c..201e5df0d 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-CASE-SURVEILLANCE__design-md +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__TUBERCULOSIS__TB-CASE-SURVEILLANCE__design-md @@ -78,7 +78,7 @@ This document is intended for audiences responsible for implementing TB data sys | **Structure** | **Description** | |-------------------------------|----------| -| **Enrollment** | The stage collects the basic TEI attributes. Please note that some of the attributes show the “GEN - “ prefix. To know more about the [**Common Metadata Library**](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
The stage is non-repeatable. | +| **Inscription** | The stage collects the basic TEI attributes. Please note that some of the attributes show the “GEN - “ prefix. To know more about the [**Common Metadata Library**](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
The stage is non-repeatable. | | **Diagnostic Laboratory Results** | In order to display the whole list of tests available for **diagnostic purposes**, the user should report first the “Sample information” section.
**The stage is repeatable**. The repeatability was set to allow countries to implement the tracker as per the local workflows and preferences - depending on whether there is the need to track ALL the samples (good and bad quality) or just the “good” samples, the stage can be repeated accordingly. | | **Diagnosis and notification** | The stage collects the baseline information, the risk factors, the potential HIV (co-)infection, and the diagnostic decision. The decision-maker will either **diagnose a suspected case with TB and notify** them, or will confirm the absence of infection. **SMS templates** for notifying the cases or confirming the absence of infection are included in the metadata package.
**The stage is non-repeatable**. | | **Treatment** | The stage collects the information necessary for the overview of the **patient’s regimen** and status during their course of treatment.
**The stage is repeatable** but limited to two events and one treatment regimen change. | diff --git a/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__cold-chain-equipment-cce-md b/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__cold-chain-equipment-cce-md index d9ed805a3..37fab2afd 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__cold-chain-equipment-cce-md +++ b/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__cold-chain-equipment-cce-md @@ -135,24 +135,24 @@ Ces métadonnées sont nécessaires (uniquement) pour configurer un formulaire d >>**Unités d'organisation sélectionnées** : (à sélectionner de la même manière que pour le programme Tracker) #### 1.2 Catégorie { #12-category } ->**Name \(*)**: **Cold chain appliance report** ->**Short name \(*)**: "Cold chain appliance report - CCE" ->**Data dimension type \(*)**: "Disaggregation" ->**Category options**: *note the order of "Category options"* ->>"Temperature / count" ->>"Temperature / minimum" ->>"Temperature / average" ->>"Temperature / maximum" ->>"Temperature count - below 0° C" ->>"Temperature count - 0-2° C" ->>"Temperature count - 2-8° C" ->>"Temperature count - above 8° C" ->>"Temperature alarm / count" ->>"CCE Inspection / count" ->>"CCE Status functional / count" ->>"CCE Status non-functional / count" ->>"Repair request / count" ->>"Corrective maintenance / count" +>**Nom \(*)**: **Rapport sur les appareils de la chaîne du froid** +>**Nom court \(*)**: "Rapport sur les appareils de la chaîne du froid - CCE" +>**Type de dimension des données \(*)**: "Désagrégation" +>**Options de catégorie**: *noter l'ordre des "options de catégorie"* +>>"Température / nombre" +>>"Température / minimale" +>>"Température / moyenne" +>>"Température / maximale" +>>"Nombre de températures - inférieur à 0° C" +>>"Nombre de températures - 0-2° C" +>>"Nombre de températures - 2-8° C" +>>"Nombre de températures - supérieur à 8° C" +>>"Alarme de température / nombre" +>>"Inspection du CCE / nombre" +>>"État fonctionnel du CCE / nombre" +>>"État non fonctionnel du CCE / nombre" +>>"Requête de réparation / nombre" +>>"Maintenance corrective / nombre" #### 1.3 Combinaison de catégories { #13-category-combination } >**Nom \(*)**: **Rapport sur les appareils de la chaîne du froid** @@ -162,128 +162,128 @@ Ces métadonnées sont nécessaires (uniquement) pour configurer un formulaire d ### 2 ÉLÉMENT DE DONNÉES { #2-data-element } #### 2.1 Élément de données - "Agrégé" { #21-data-element-aggregate } ->**1 Refrigerator 1 - DLY** ->>**Name \(*)**: "Refrigerator 1 - DLY" ->>**Short name \(*)**: "Refrigerator 1 - DLY - CCE" ->>**Domain Type \(*)**: "Aggregate" ->>**Value type \(*)**: "Number" ->>**Aggregation type (*)**: "Sum" ->>**Store zero data values**: tag ->>**Category combination \(*)**: "Cold chain appliance report" ->>**Aggregation levels**: "Facility" -> ->**2 Refrigerator 1 - MTH** ->>**Name \(*)**: "Refrigerator 1 - MTH" ->>**Short name \(*)**: "Refrigerator 1 - MTH - CCE" ->>**Domain Type \(*)**: "Aggregate" ->>**Value type \(*)**: "Number" ->>**Aggregation type (*)**: "Sum" ->>**Store zero data values**: tag ->>**Category combination \(*)**: "Cold chain appliance report" ->>**Aggregation levels**: "Facility" -> ->**3 Refrigerator 2 - DLY** ->>**Name \(*)**: "Refrigerator 2 - DLY" ->>**Short name \(*)**: "Refrigerator 2 - DLY - CCE" ->>**Domain Type \(*)**: "Aggregate" ->>**Value type \(*)**: "Number" ->>**Aggregation type (*)**: "Sum" ->>**Store zero data values**: tag ->>**Category combination \(*)**: "Cold chain appliance report" ->>**Aggregation levels**: "Facility" -> ->**4 Refrigerator 1 - MTH** ->>**Name \(*)**: "Refrigerator 2 - MTH" ->>**Short name \(*)**: "Refrigerator 2 - MTH - CCE" ->>**Domain Type \(*)**: "Aggregate" ->>**Value type \(*)**: "Number" ->>**Aggregation type (*)**: "Sum" ->>**Store zero data values**: tag ->>**Category combination \(*)**: "Cold chain appliance report" ->>**Aggregation levels**: "Facility" +>**1 Réfrigérateur 1 - DLY** +>>**Nom \(*)**: "Réfrigérateur 1 - DLY" +>>**Nom court \(*)**: "Réfrigérateur 1 - DLY - CCE" +>>**Type de domaine \(*)**: "Agrégé" +>>**Type de valeur \(*)**: "Nombre" +>>**Type d'agrégation (*)**: "Somme" +>>**Stocker des valeurs de données nulles**: étiquette +>>**Combinaison de catégories \(*)**: "Rapport sur les appareils de la chaîne du froid" +>>**Niveaux d'agrégation**: "Établissement" +> +>**2 Réfrigérateur 1 - MTH** +>>**Nom \(*)**: "Réfrigérateur 1 - MTH" +>>**Nom court \(*)**: "Réfrigérateur 1 - MTH - CCE" +>>**Type de domaine \(*)**: "Agrégé" +>>**Type de valeur \(*)**: "Nombre" +>>**Type d'agrégation (*)**: "Somme" +>>**Stocker des valeurs de données nulles**: étiquette +>>**Combinaison de catégories \(*)**: "Rapport sur les appareils de la chaîne du froid" +>>**Niveaux d'agrégation**: "Établissement" +> +>**3 Réfrigérateur 2 - DLY** +>>**Nom \(*)**: "Réfrigérateur 2 - DLY" +>>**Nom court \(*)**: "Réfrigérateur 2 - DLY - CCE" +>>**Type de domaine \(*)**: "Agrégé" +>>**Type de valeur \(*)**: "Nombre" +>>**Type d'agrégation (*)**: "Somme" +>>**Stocker des valeurs de données nulles**: étiquette +>>**Combinaison de catégories \(*)**: "Rapport sur les appareils de la chaîne du froid" +>>**Niveaux d'agrégation**: "Établissement" +> +>**4 Réfrigérateur 1 - MTH** +>>**Nom \(*)**: "Réfrigérateur 2 - MTH" +>>**Nom court \(*)**: "Réfrigérateur 2 - MTH - CCE" +>>**Type de domaine \(*)**: "Agrégé" +>>**Type de valeur \(*)**: "Nombre" +>>**Type d'agrégation (*)**: "Somme" +>>**Stocker des valeurs de données nulles**: étiquette +>>**Combinaison de catégories \(*)**: "Rapport sur les appareils de la chaîne du froid" +>>**Niveaux d'agrégation**: "Établissement" #### 2.2 Élément de données - "Tracker" { #22-data-element-tracker } ->**Name** ->>"Alarm cause" / "Long text" ->>"Alarm corrective action" / "Long text" ->>"Alarm escalated to supervisor" / "Yes/No" ->>"Alarm resolved" / "Yes/No" ->>"Alarm type" / "Long text" ->>"Appliance functional 0/1" ->>"Appliance functional/non-functional" / Option set "Appliance functional / non-functional" ->>"Assessment of technical fault" / "Long text" ->>"Audible or visible alarm" / Option set "Audible or visible alarm" ->>“Clean refrigerator with water and mild detergent" / "Yes/No" ->>“Clean the grill on the side of the refrigerator" / "Yes/No" ->>"Cold chain appliance installation report" / "Long text" ->>"Cold chain appliance product number" / "Long text" ->>"Cold chain appliance restored to service" / "Yes/No" ->>"Cold chain technician" / "User name" ->>"Daily inspection completed" / "Yes/No" ->>"Daily tasks completed" / "Yes/No" ->>"Defect image" / "Image" ->>"Equipment removed from cold chain appliance inventory" / "Yes/No" ->>"Equipment restored to service" / "Yes/No" ->>"Interventions" / "Long text" ->>“Lid gasket checked for sealing when the lid is closed” / "Yes/No" ->>"Method of disposal" / "Long text" ->>“Monthly tasks” / “Long text” ->>"Reason for disposal" / "Long text" ->>"Reason for repair request" / "Long text" ->>"Received at" / "Organisation unit" ->>"Received from" / "Organisation unit" ->>"Repair request completed" ->>"Repair request submitted" ->>"Sent from" / "Organisation unit" ->>"Technical fault resolved" / "Yes/No" ->>"Temperature recording" / "Number" ->>"Transferred to" / "Organisation unit" ->>"Urgency of repair request" / "Long text" ->>"Water droplets wiped off from the inside wall" / "Yes/No" ->>"Water removed at the bottom of the refrigerator" / "Yes/No" ->>"Weekly tasks" / “Text” -> ->**Short name \(*)**: same as "Name (\*) - CCE" ->**Domain Type \(*)**: "Tracker" ->**Value type \(*)**: see above ->**Aggregation type (*)**: "None" +>**Nom** +>>"Cause de l'alarme" / "Texte long" +>>"Action corrective de l'alarme" / "Texte long" +>>"Alarme transmise au superviseur" / "Oui/Non" +>>"Alarme réglée" / "Oui/Non" +>>"Type d'alarme" / "Texte long" +>>"Appareils fonctionnels 0/1" +>>"Appareil fonctionnel/non fonctionnel" / Ensemble d'options "Appareil fonctionnel/non fonctionnel" +>>"Évaluation de la défaillance technique" / "Texte long" +>>"Alarme sonore ou visible" / Ensemble d'options "Alarme sonore ou visible" +>>“Nettoyer le réfrigérateur avec de l'eau et un détergent doux" / "Oui/Non" +>>“Nettoyer la grille sur le côté du réfrigérateur" / "Oui/Non" +>>"Rapport d'installation d'appareils de la chaîne du froid" / "Texte long" +>>"Numéro de référence de l'appareil de la chaîne du froid" / "Texte long" +>>"Remise en service d'un appareil de la chaîne du froid" / "Oui/Non" +>>"Technicien de la chaîne du froid" / "Nom d'utilisateur" +>>"Inspection quotidienne terminée" / "Oui/Non" +>>"Tâches quotidiennes terminées" / "Oui/Non" +>>"Image de défaut" / "Image" +>>"Équipements retirés de l'inventaire des appareils de la chaîne du froid" / "Oui/Non" +>>"Remise en service de l'équipemente" / "Oui/Non" +>>"Interventions" / "Texte long" +>>“Vérification de l'étanchéité du joint du couvercle lorsqu'il est fermé” / "Oui/Non" +>>"Méthode d'élimination" / "Texte long" +>>“Tâches mensuelles” / “Texte long” +>>"Raison de l'élimination" / "Texte long" +>>"Raison de la requête de réparation" / "Texte long" +>>"Reçu à" / "Unité d'organisation" +>>"Reçu de" / "Unité d'organisation" +>>"Requête de réparation terminée" +>>"Requête de réparation soumise" +>>"Envoyé depuis" / "Unité d'organisation" +>>"Erreur technique résolue" / "Oui/Non" +>>"Enregistrement de la température" / "Nombre" +>>"Transféré à" / "Unité d'organisation" +>>"Urgence de la requête de réparation" / "Texte long" +>>"Gouttes d'eau essuyées sur la paroi intérieure" / "Oui/Non" +>>"Eau retirée du fond du réfrigérateur" / "Oui/Non" +>>"Tâches hebdomadaires" / “Texte” +> +>**Nom court \(*)**:Identique à "Nom (\*) - CCE" +>**Type de domaine \(*)**: "Tracker" +>**Type de valeur \(*)**: voir ci-dessus +>**Type d'agrégation (*)**: "Aucun" ### 3 DATA SET { #3-data-set } *Notez que, mis à part le "type de période", les deux ensembles de données "quotidiens" et "mensuels" sont identiques.* #### 3.1 Ensemble de données { #31-data-set } ->**1 Cold chain appliance report - Daily** ->>**Name \(*)**: "Cold chain appliance report - Daily" ->>**Short name \(*)**: "Cold chain appliance report - Daily - CCE" ->>**Expiry days**: "1" ->>**Open future periods for data entry**: "1" ->>**Days after period to qualify for timely submission**: "1" ->>**Period type**: "Daily" ->>**Category combination**: "None" ->>**Data elements** ->>>"Refrigerator 1 - DLY" ->>>"Refrigerator 2 - DLY" ->> ->>**Organisation units selected**: (select as for the Tracker Program) -> ->**2 Cold chain appliance report - Monthly** ->>**Name \(*)**: "Cold chain appliance report - Monthly" ->>**Short name \(*)**: "Cold chain appliance report - Daily - Monthly" ->>**Expiry days**: "1" ->>**Open future periods for data entry**: "1" ->>**Days after period to qualify for timely submission**: "1" ->>**Period type**: "Monthly" ->>**Category combination**: "None" ->>**Data elements** ->>>"Refrigerator 1 - MTH" ->>>"Refrigerator 2 - MTH" ->> ->>**Organisation units selected**: (select as for the Tracker Program) +>**1 Rapport sur les appareils de la chaîne du froid - Quotidien** +>>**Nom \(*)**: "Rapport sur les appareils de la chaîne du froid - Quotidien" +>>**Nom court \(*)**: "Rapport sur les appareils de la chaîne du froid - Quotidien - CCE" +>>**Dates d'expiration**: "1" +>>**Ouvrir des périodes futures pour la saisie des données**: "1" +>>**Jours après la période pour bénéficier d'une soumission dans les délais**: "1" +>>**Type de période**: "Quotidien" +>>**Combinaison de catégories**: "Aucune" +>>**Éléments de données** +>>>"Réfrigérateur 1 - DLY" +>>>"Réfrigérateur 2 - DLY" +>> +>>**Unités d'organisation sélectionnées** : ( sélectionnez de la même manière que pour le programme Tracker) +> +>**2 Rapport sur les appareils de la chaîne du froid - Mensuel** +>>**Nom \(*)**: "Rapport sur les appareils de la chaîne du froid - Mensuel" +>>**Nom court \(*)**: "Rapport sur les appareils de la chaîne du froid - Mensuel" +>>**Dates d'expiration**: "1" +>>**Ouvrir des périodes futures pour la saisie des données**: "1" +>>**Jours après la période pour bénéficier d'une soumission dans les délais**: "1" +>>**Type de période**: "Mensuel" +>>**Combinaison de catégories**: "Aucune" +>>**Éléments de données** +>>>"Réfrigérateur 1 - MTH" +>>>"Réfrigérateur 2 - MTH" +>> +>>**Unités d'organisation sélectionnées** : ( sélectionnez de la même manière que pour le programme Tracker) ### 4 INDICATEUR { #4-indicator } #### 4.1 Indicateur de programme { #41-program-indicator } -*Note that the Program Indicators are only given for "Refrigerator 1" but are entirely analogous for "Refrigerator 2" etc. except for the "Refrigerator number" in the "Edit filter".* -*Note that the various IDs will differ in every DHIS2 instance and the entities are given separately where that is necessary for the configuration.* +*Notez que les indicateurs de programme ne sont donnés que pour le "Réfrigérateur 1" mais sont entièrement analogues pour le "Réfrigérateur 2", etc. à l'exception du "Numéro du réfrigérateur" dans le "Filtre d'édition".* +*Notez que les divers identifiants seront différents dans chaque instance de DHIS2 et que les entités sont données séparément lorsque cela est nécessaire pour la configuration.* >**1. événement alarme du CCE (Équipement de la chaîne du froid) / nombre - Réfrigérateur 1 - PI** >>**1 Détails de l'indicateur de programme** @@ -810,143 +810,143 @@ Ces métadonnées sont nécessaires (uniquement) pour configurer un formulaire d ### 6 PROGRAMME { #6-program } #### 6.1 Programme { #61-program } ->**1 Program details** ->>**Name (*)**: "Cold chain appliance lifecycle management" ->>**Short name (*)**: " Cold chain appliance lifecycle management" ->>**Color**: "#64B5F6" ->>**Icon**: "cold chain outline" ->>**Tracked entity type (*)**: select "Cold chain appliance" ->>**Category combination (*)**: select "None" ->>**Display front page list**: tag -> ->**2 Enrollment details** ->>**Allow future enrollment dates**: do not tag ->>**Allow future incident dates**: do not tag ->>**Only enrol once (per tracked entity instance lifetime)**: do not tag ->>**Show incident date**: tag ->>**Description of incident date**: "Cold chain appliance management" ->>**Description of enrollment date**: leave blank ->>**Ignore overdue events**: leave untagged ->>**Feature type**: "Point" ->>**Related program**: (blank) ->> ->>*Note that the "Feature type" will prompt the user to enter the geolocation during registration (by entering longitude and latitude on the web or selecting the pin icon on a mobile device).* -> ->**3 Attributes** ->>**1 Assign attributes** ->>>**Program tracked entity attributes**: select and arrange in the following order: ->>>>"Appliance image" ->>>>"Place of installation" ->>>>"PQS code category" ->>>>"PQS code" ->>>>"Type of appliance" ->>>>“Company” ->>>>"Manufactured in" ->>>>"Manufacturer's reference" ->>>>"Production date" ->>>>"Product number" +>**1 Détails du programme** +>>**Nom (*)**: "Gestion du cycle de vie des appareils de la chaîne du froid" +>>**Nom court (*)**: " Gestion du cycle de vie des appareils de la chaîne du froid" +>>**Couleur**: "#64B5F6" +>>**Icône**: "aperçu de la chaîne du froid" +>>**Type d'entité suivie (*)**: sélectionnez "Appareil de la chaîne du froid" +>>**Combinaison de catégories (*)**: sélectionnez "Aucun" +>>**Afficher la liste des pages de garde** : marquer +> +>**2 Modalités d'inscription** +>>**Autoriser les dates d'inscription ultérieures** : ne pas marquer +>>**Autoriser les dates d'incidents futurs** : ne pas marquer +>>**One s'inscrire qu'une seule fois (par durée de vie de l'instance d'entité suivie)** : ne pas marquer +>>**Afficher la date de l'incident** : marquer +>>**Description de la date d'incident** : "Gestion des appareils de la chaîne du froid" +>>**Description de la date d'inscription** : laisser vide +>>**Ignorer les événements en retard** : ne pas les marquer +>>**Type de caractéristique** : "Point" +>>**Programme connexe** : ( vide ) +>> +>>*Notez que le "type de caractéristique" invitera l'utilisateur à saisir la géolocalisation lors de l'enregistrement (en saisissant la longitude et la latitude sur le web ou en sélectionnant l'icône de l'épingle sur un appareil mobile).* +> +>**3 Attributs** +>>**1 Affecter des attributs** +>>>**Attributs de l'entité suivie du programme** : sélectionner et classer dans l'ordre suivant: +>>>>"Image de l'appareil" +>>>>"Lieu d'installation" +>>>>"Catégorie de code du PQS" +>>>>"Code du PQS" +>>>>"Type d'appareil" +>>>>“Société” +>>>>"Fabriqué à" +>>>>"Référence du fabricant" +>>>>"Date de production" +>>>>"Numéro du produit" >>>>"GTIN" ->>>>"Serial number" +>>>>"Numéro de série" >>>>"GS1 GIAI" ->>>>"Unique identifier" +>>>>"Identifiant unique" >>> ->>>**Display in list**: tag all ->>>**Mobile render type**: see above ->> ->>**2 Create registration form** ->>>**Name**: "Cold chain appliance lifecycle management" ->>>**ADD SECTION TO FORM** ->>>>"Appliance image" ->>>>"Place of installation" ->>>>"PQS code category" ->>>>"PQS code" ->>>>"Type of appliance" ->>>>“Company” ->>>>"Manufactured in" ->>>>"Manufacturer's reference" ->>>>"Production date" ->>>>"Product number" +>>>**Afficher dans la liste** : marquer tout +>>>**Type d'affichage mobile** : voir ci-dessus +>> +>>**2 Créer un formulaire d'inscription** +>>>**Nom**: "Gestion du cycle de vie des appareils de la chaîne du froid" +>>>**AJOUTER UNE SECTION AU FORMULAIRE** +>>>>"Image de l'appareil" +>>>>"Lieu d'installation" +>>>>"Catégorie de code du PQS" +>>>>"Code du PQS" +>>>>"Type d'appareil" +>>>>“Société” +>>>>"Fabriqué à" +>>>>"Référence du fabricant" +>>>>"Date de production" +>>>>"Numéro du produit" >>>>"GTIN" ->>>>"Serial number" +>>>>"Numéro de série" >>>"GS1 GIAI" ->>>>"Unique identifier" -> ->**4 Program stages** ->>**1 Stage details** ->>>**Name** ->>>>"Cold chain appliance transfer" / "Repeatable" ->>>>"Cold chain appliance installation" / "Repeatable" ->>>>"Cold chain appliance inspection" / "Repeatable" ->>>>"Cold chain appliance weekly preventive maintenance" / "Repeatable" ->>>>"Cold chain appliance monthly preventive maintenance" / "Repeatable" ->>>>"Cold chain appliance alert" / "Repeatable" ->>>>"Cold chain appliance repair request" / "Repeatable" ->>>>"Cold chain appliance corrective maintenance" / "Repeatable" ->>>>"Cold chain appliance disposal" / not repeatable +>>>>"Identifiant unique" +> +>**4 Étapes du programme** +>>**1 Détails de l'étape** +>>>**Nom** +>>>>"Transfert d'appareils de la chaîne du froid" / "Répétable" +>>>>"Installation d'appareils de la chaîne du froid" / "Répétable" +>>>>"Contrôle des appareils de la chaîne du froid" / "Répétable" +>>>>"Entretien préventif hebdomadaire des appareils de la chaîne du froid" / "Répétable" +>>>>"Entretien préventif mensuel des appareils de la chaîne du froid" / "Répétable" +>>>>"Alerte relative aux appareils de la chaîne du froid" / "Répétable" +>>>>"Requête de réparation des appareils de la chaîne du froid" / "Répétable" +>>>>"Maintenance corrective des appareils de la chaîne du froid" / "Répétable" +>>>>"Élimination des appareils de la chaîne du froid" / non répétable >>> ->>>**Repeatable**: see above ->> ->>**2 Assign data elements** ->>>**Cold chain appliance transfer** ->>>"Sent from" ->>>"Transferred to" ->>>"Received from" ->>>"Received at" +>>>**Répétable**: voir ci-dessus +>> +>>**2 Affecter des éléments de données** +>>>**Transfert d'appareils de la chaîne du froid** +>>>"Envoyé depuis" +>>>"Transféré à" +>>>"Reçu de" +>>>"Reçu à" >>> ->>>**Cold chain appliance installation** ->>>"Cold chain appliance installation report" +>>>**Installation d'appareils de la chaîne du froid** +>>>"Rapport d'installation d'appareils de la chaîne du froid" >>> ->>>**Cold chain appliance inspection** ->>>"Daily inspection completed" ->>>"Functional status" +>>>**Contrôle des appareils de la chaîne du froid** +>>>"Inspection quotidienne terminée" +>>>"État fonctionnel" >>> ->>>**Cold chain appliance weekly preventive maintenance** ->>>"Water removed at the bottom of the refrigerator" ->>>"Water droplets wiped off from the inside wall" ->>>"Lid gasket checked for sealing when the lid is closed" +>>>**Entretien préventif hebdomadaire des appareils de la chaîne du froid** +>>>"Eau retirée du fond du réfrigérateur" +>>>"Gouttes d'eau essuyées sur la paroi intérieure" +>>>"Vérification de l'étanchéité du joint du couvercle lorsqu'il est fermé" >>> ->>>**Cold chain appliance monthly preventive maintenance** ->>>“Clean refrigerator with water and mild detergent” ->>>“Clean the grill on the side of the refrigerator” +>>>**Entretien préventif mensuel des appareils de la chaîne du froid** +>>>“Nettoyer le réfrigérateur avec de l'eau et un détergent doux” +>>>“Nettoyer la grille sur le côté du réfrigérateur” >>> ->>>**Cold chain appliance alarm** ->>>"Alarm type" ->>>"Alarm cause" ->>>"Alarm corrective action" ->>>"Alarm resolved" ->>>"Alarm escalated to supervisor" +>>>**Alarme des appareils de la chaîne du froid** +>>>"Type d'alarme" +>>>"Cause de l'alarme" +>>>"Action corrective de l'alarme" +>>>"Alarme réglée" +>>>"Alarme transmise au superviseur" >>> ->>>**Cold chain appliance repair request** ->>>"Reason for repair request" ->>>"Urgency of repair request" ->>>“Defect image” ->>>“Cold chain technician” +>>>**Demande de réparation d'appareils de la chaîne du froid** +>>>"Motif de la demande de réparation" +>>>"Urgence de la demande de réparation" +>>>“Image de défaut” +>>>“Technicien de la chaîne du froid” >>> ->>>**Cold chain appliance corrective maintenance** ->>>"Assessment of technical fault" +>>>**Entretien correctif des appareils de la chaîne du froid** +>>>"Évaluation de la défaillance technique" >>>"Interventions" ->>>"Technical fault resolved" ->>>"Equipment restored to service" +>>>"Défaillance technique résolue" +>>>"Remise en service de l'équipement" >>> ->>>**Cold chain appliance disposal** ->>>"Reason for disposal" ->>>"Method of disposal" ->>>"Equipment removed from cold chain appliance inventory" +>>>**Élimination des appareils de la chaîne du froid** +>>>"Motif de l'élimination" +>>>"Méthode d'élimination" +>>>"Équipements retirés de l'inventaire des appareils de la chaîne du froid" >> ->>**Display in report**: make visible for all items ->>**Mobile render type**: "Default" ->>**Desktop render type**: "Default" +>>**Afficher dans le rapport** : rendre visible tous les éléments +>>**Type d'affichage mobile** : " Par défaut" +>>**Type d'affichage du bureau** : " Par défaut" >> ->>**3 Create data entry form** ->>>**"BASIC"** is configured by default, no configuration is needed. +>>**3 Créer un formulaire de saisie de données** +>>>**"BASIC"** est configuré par défaut, aucune autre configuration n'est nécessaire. > ->**5 Access** ->>**Organisation units**: tag the health care facility for assigning to the DHIS2 Capture. ->>**Roles and access**: "Biomedical equipment life cycle management" appears by default ->>**SELECT ALL** +>**5 Accès** +>>**Unités d'organisation** : marquer l'établissement de soins de santé pour l'affecter à l'application DHIS2 Capture. +>>**Rôles et accès** : "Gestion du cycle de vie des équipements biomédicaux" apparaît par défaut +>>**SELECTIONNER TOUT** > >**6 Notifications** ->(not applicable) +>(non applicable) #### 6.2 Attribut d'entité suivie { #62-tracked-entity-attribute } >**Name (*)**: @@ -1151,8 +1151,8 @@ Ces métadonnées sont nécessaires (uniquement) pour configurer un formulaire d >>>>**Code \(*)**: "Non-functional" #### 7.3 Prédicteur { #73-predictor } -*Note that the Predictors are only given for "Refrigerator 1" but are entirely analogous for "Refrigerator 2" etc. except for selecting the corresponding Program Indicator with "Refrigerator 2" in the "Generator"*. -*Note that the Predictors are only given for the "Daily" "Period type" denoted by "DLY" (and for "Refrigerator 1") but are entirely analogous for "Monthly" "Period type" denoted by "MTH" except for selecting the corresponding "Output data element" of "Refrigerator 1 - MTH" and selecting "Monthly" as "Period type"* +*Notez que les prédicteurs ne sont donnés que pour le "Réfrigérateur 1" mais sont entièrement analogues pour le "Réfrigérateur 2" etc. sauf pour la sélection de l'indicateur de programme correspondant avec le "Réfrigérateur 2" dans le "Générateur "*. +*Notez que les prédicteurs ne sont donnés que pour le "type de période" "quotidienne" désigné par "DLY" (et pour le "réfrigérateur 1") mais sont entièrement analogues pour le "type de période" "mensuelle" désigné par "MTH", sauf en sélectionnant l'"élément de données de sortie" correspondant du "réfrigérateur 1 - MTH" et en sélectionnant "mensuel" comme "type de période "*. >**1 T2A - Réfrigérateur 1 - état fonctionnel du CCE / nombre - DLY** >>**Nom \(*)**: "T2A - Réfrigérateur 1 - état fonctionnel du CCE / nombre - DLY" >>**Nom court \(*)**: "T2A - Réf 1 - état fonctionnel du CCE / nombre - DLY" @@ -1725,12 +1725,12 @@ LL 11 - **Name**: "CCE Cold chain appliance corrective maintenance" -### 4 Data visualizer { #4-data-visualizer } +### 4 Visualiseur de données { #4-data-visualizer } >**Nom**: XXX >>XXX > -### 5 Event report { #5-event-report } +### 5 Rapports d'événements { #5-event-report } >**Nom**: XXX >>XXX > @@ -1754,13 +1754,13 @@ LL 11 - **Name**: "CCE Cold chain appliance corrective maintenance"
-## DHIS2 user interfaces { #dhis2-user-interfaces } +## Interfaces utilisateur de DHIS2 { #dhis2-user-interfaces } **Portail web / Programme Tracker** ![](media/image92.png) -**Web portal / Line listing** +**Portail web / Liste de lignes** ![](media/image66.png) @@ -1774,13 +1774,13 @@ LL 11 - **Name**: "CCE Cold chain appliance corrective maintenance" ![](media/image84.png) -## Workflow for registering new appliances { #workflow-for-registering-new-appliances } +## Processus d'enregistrement de nouveaux appareils { #workflow-for-registering-new-appliances } -While details on all DHIS2 workflows are available in the general DHIS2 documentation and although the "cloning" of appliances uses only native DHIS2 functionality, it is an "edge case", a very specific use of the "Relationship" function and therefore the steps are explained below: +La documentation générale de DHIS2 contient des détails sur toutes les procédures de travail de DHIS2 et bien que le "clonage" d'appareils n'utilise que la fonctionnalité native de DHIS2, il s'agit d'un "cas particulier", d'une utilisation très spécifique de la fonction "Relation", et les étapes sont donc expliquées ci-dessous : -The workflow below explains the workflow for the following example: +La procédure ci-dessous explique la procédure à suivre pour l'exemple suivant : -A new icelined refrigerator (E003/007) has been delivered to the health facility (OU) "0001 CH Mahosot". The user "registers" and "enrols" this new appliance using the default specifications from the catalogue of PQS pre-qualified appliances in the "World Health Organization PQS catalogue". These "generic" appliance specifications are then "copied" for creating a new appliance at the "0001 CH Mahosot" before adding the appliance specific attributes such as the serial number or the manufacturing date. User: +Un nouveau réfrigérateur (E003/007) a été livré à l'établissement de santé (UO) "0001 CH Mahosot". L'utilisateur "enregistre" et "inscrit" ce nouvel appareil en utilisant les spécifications par défaut du catalogue des appareils préqualifiés PQS dans le "catalogue PQS de l'Organisation Mondiale de la Santé". Ces spécifications "génériques" sont ensuite "copiées" pour créer un nouvel appareil au "0001 CH Mahosot" avant d'ajouter les attributs spécifiques de l'appareil tels que le numéro de série ou la date de fabrication. L'utilisateur : - Opens the DHIS2 Capture Android app on a mobile device and authenticates: the DHIS2 home screen opens showing all Programs and Data sets diff --git a/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__gs1-datamatrix-code-gs1-md b/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__gs1-datamatrix-code-gs1-md index 17b73695e..d3e62023d 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__gs1-datamatrix-code-gs1-md +++ b/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__gs1-datamatrix-code-gs1-md @@ -268,7 +268,7 @@ The Program rule in this Event program allows parsing all GS1 AIs which are mand >>**Source type \(*)**: "Data element in current event" >>**Data element**: "GS1 DataMatrix code data string" -#### DHIS2 user interfaces { #dhis2-user-interfaces } +#### Interfaces utilisateur de DHIS2 { #dhis2-user-interfaces } **Portail web / Programme Tracker** diff --git a/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__health-care-product-catalogue-hpc-md b/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__health-care-product-catalogue-hpc-md index 0c2c9bf7d..45bb0fc9a 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__health-care-product-catalogue-hpc-md +++ b/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__health-care-product-catalogue-hpc-md @@ -223,7 +223,7 @@ Les paramètres de métadonnées requis sont présentés dans l'ordre dans leque >>**Display in list**: tag all >>**Searchable**: tag all -## DHIS2 user interfaces { #dhis2-user-interfaces } +## Interfaces utilisateur de DHIS2 { #dhis2-user-interfaces } **Web portal / Capture app**![](media/image73.png) 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 6447bdc22..838c793ff 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 c164ad77a..1ae6c0f0a 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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # 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 f16962fb0..1af78c386 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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # 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 42db67698..8635217cf 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-06-18' tags: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # 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 94b249367..7474aaff3 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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # 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 f5a134641..196359e1a 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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # 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 3c3a534d4..d0f479a84 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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # Utilisation de passerelles pour l'établissement de rapports SMS { #sms_report_sending } diff --git a/projects/docs-full-site/fr/TOPICS__METADATA__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__design-md b/projects/docs-full-site/fr/TOPICS__METADATA__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__design-md index 854bfa3ba..008716c0b 100644 --- a/projects/docs-full-site/fr/TOPICS__METADATA__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__design-md +++ b/projects/docs-full-site/fr/TOPICS__METADATA__DISEASE-SURVEILLANCE__ACUTE-FEBRILE-ILLNESS__design-md @@ -54,7 +54,7 @@ Besides screening data, all other data are collected according to the below data |Structure|Description| |---------|-----------| -|**Enrollment**|The stage collects the basic TEI attributes. Please note that some of the attributes show the *'GEN - '* prefix. To know more about the [Common Metadata Library](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
**The stage is non-repeatable**.| +|**Inscription**|The stage collects the basic TEI attributes. Please note that some of the attributes show the *'GEN - '* prefix. To know more about the [Common Metadata Library](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
**The stage is non-repeatable**.| |**Case report**|The stage collects basic information on the patient's signs and symptoms, exposure and preventive measures.
Only one AFI event can be recorded for every TEI. In case of a new AFI even for the same TEI, a new TEI has to be enrolled.
**The stage is non-repeatable**.| |**Specimen collection & transport**|The stage collects basic information on specimen collection and transportation.
**The stage is repeatable** in case more than one specimen collection/transportation is required per TEI.| |**Laboratory testing & result**|The stage collects basic information on tests performed and pathogens identified.
**The stage is repeatable** in case more than one specimen is processed per TEI.| diff --git a/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE-TRACKER__VERSION-200__design-md b/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE-TRACKER__VERSION-200__design-md new file mode 100644 index 000000000..23fdf2114 --- /dev/null +++ b/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE-TRACKER__VERSION-200__design-md @@ -0,0 +1,298 @@ +--- +edit_url: "https://github.com/dhis2-metadata/TB_CS/blob/master/docs/tb_cs-design-2.0.0.md" +revision_date: "2022-10-03" +--- + +# TB Case Surveillance - System Design Document { #tb-cs-design } + +## Introduction { #introduction } + +The **TB Case Surveillance Tracker (TB-CS) digital data package for DHIS2** is based on the [**WHO recording and reporting framework**](https://apps.who.int/iris/handle/10665/79199) from 2013. It provides a set of recommended metadata (data elements, program rules, etc) to enable electronic capture of individual/case-based TB surveillance data. The tracker metadata is configured to ensure that aggregated standard quarterly TB report indicators on notifications, first-line outcomes and second-line outcomes as defined by the WHO Definitions and reporting framework for TB (2013) can be automatically generated from the individual data captured. The TB Case Surveillance Tracker is not intended to support patient management or patient care. This requires more detailed analysis of roles, responsibilities, workflows and decision-making within the settings in which such systems would be implemented. + +The system design document explains how the tracker program was configured to meet the data entry and analysis requirements and support a typical workflow. The document does not include an exhaustive listing of all metadata captured. This document also does not consider the resources and infrastructure needed to implement such a system, such as servers, power, internet connections, backups, training and user support. More information on the TB programme technical aspects informing this system design is available in the [**WHO publication on electronic recording and reporting for tuberculosis care and control**](http://www.who.int/tb/publications/electronic_recording_reporting/en/). Supplementary implementation guidance for DHIS2 can be found in the [**General DHIS2 Implementation Guide**](https://docs.dhis2.org/en/implement/configuring-the-android-app/about-this-guide.html) and [**DHIS2 tracker implementation guide**](https://docs.dhis2.org/en/implement/understanding-dhis2-implementation/a-quick-guide-to-dhis2-implementation.html). + +## Aperçu de la conception du système { #system-design-overview } + +### Contexte { #background } + +Reliable epidemiological data is required for staff at all levels of a national TB programme to plan and provide effective tuberculosis care and control services, as well as monitor the performance of programmatic actions. A case-based surveillance system has clear advantages over an aggregate data collection system. Like an aggregate surveillance system a minimum set of epidemiological indicators can be captured, validated, aggregated, calculated and displayed but these can be disaggregated by any combination of time, location/area, age, sex, case type, previous treatment history, HIV status, drug resistance status and treatment regimens. This helps us to understand TB epidemiology in depth and monitor changes over time. It is expected that case-based electronic data will result in **improved data quality** because the number of data entry steps are reduced, automatic calculations and validations can be built into the system, inconsistent, erroneous or incomplete data can be corrected or completed rapidly for an individual record and de-duplication can be carried out to remove duplicate records. A case-based surveillance system should also allow the linking of surveillance records to the same case even if a TB case is transferred or referred between facilities during the course of treatment. See principle 2.4, page 16, of [**Policy on the Protection of Personal Data of Persons of Concern to UNHCR**](http://www.refworld.org/docid/55643c1d4.html). + +### Cas d’utilisation { #use-case } + +The TB Case Surveillance Tracker enables **registration and longitudinal tracking of TB cases from the point of notification to final case outcome, inclusive of laboratory results**. The program captures a minimum set of data points required for epidemiological analysis of case surveillance data as described in the background section. These include baseline and demographic information about the case, risk factors, laboratory results for diagnosis and routine check-ups, drug resistance type classification, treatment regimens provided, and case outcome. **This tracker program is not designed to support clinical management nor patient care**. Rather, the program serves as an electronic registry that supports decentralized electronic data capture of case surveillance data down to health facility and laboratory levels. + +## Structure du programme { #program-structure } + +The revised TB CS tracker program has been designed to reflect a **more generic workflow** able to integrate data entry both from the health facility side (e.g. clinicians and nurses), and the laboratory side. Workflows in countries may vary and the case surveillance program should be adapted as needed to local context. + +> **IMPORTANT** +> +> Please note that given the generic design of the tracker, this system design guide contains throughout the sections useful information, considerations, and justifications that can be of great importance for the implementation. The document should therefore be thoroughly revised both by the requesting and implementing parties. + +![Theoretical workflow](resources/images/tb_cs_001.png) + +Following this initial workflow, the program has been structured as follows: + +![Data flow within the tracker stages](resources/images/tb_cs_029.png) + +### Logique de la structure du programme { #rationale-for-program-structure } + +The design of the tracker has been improved to expand the information that could potentially be collected from the laboratory side. The expansion touched of course the metadata, which is now more comprehensive and allows to **discern between diagnostic and monitoring tests**, but it also created a more generic baseline upon which implementers and countries could build their own workflow. Depending on the local needs, the “Diagnostic laboratory results” and the “Diagnosis and notification” stages could have different orders; depending on the local resources and connectivity, the data entry could be centralized or decentralized between the laboratory and the health facility; depending on the local data flow, the data could be entered live or retrospectively. + +In particular, there could theoretically be **three general scenarios** that could change the flow and the order of the stages: + +1. **The laboratory staff receives the tests requests and the “Diagnostic Laboratory Results” is the very first step** in the journey of the suspected case upon their enrollment. This scenario represents the theoretical work flow and should be the target to which countries should aim in the long-term investment in the digitalization of routine health data. + + - In this case the “Enrollment” and “ Diagnostic Laboratory Results” stages are completed directly by the laboratory staff. The “Diagnosis and notification” stage can then occur in parallel or after the registration of the laboratory results. At this point the case can either become an official TB case, in which case they will have to receive a TB registration number in their enrollment stage, or they will receive negative laboratory results and be denotified. + +2. **The suspected case gets enrolled and registered from the clinical side of the workflow before the samples are sent to the laboratory.** + + - In this case the “Enrollment” and the “Diagnosis and notification” stages are completed first. + - The “Diagnostic Laboratory Results” gets completed by the laboratory staff. + - The clinicians will complete the “Diagnosis and notification“ stage confirming or not their diagnosis and notifying the case if necessary. If the latter happens, the clinician will have to reopen the “Enrollment” and assign a TB registration number to the now-confirmed case. + + Please note that scenarios 1 and 2 are based on the assumption that the laboratory staff has the capacity to enter the data in the system locally and directly in their own facility. + + Should this capacity be inadequate for the local context, then scenario number 3 would occur: + +3. **The data entry is centralized and there is no differentiation between laboratory and clinical staff** - the data entry relies on one (or multiple) data encoder. In this case the stages should be arranged in order to match the local flow of information and data. + +Independently from the best fitting scenario for a defined local context,**the adaptation of the tracker workflow and its stages should also take in consideration whether the data entry will occur in real time or if it will rely on batch retrospective data entry**. + +## Utilisateurs cibles { #intended-users } + +This document is intended for audiences responsible for implementing TB data systems and/or HMIS in countries, including: + +- **System admins/HMIS focal points**: those responsible for installing metadata packages, designing and maintaining HMIS and/or TB data systems +- **TB program focal points** responsible for overseeing data collection, management, analysis and reporting functions of the national TB programme +- **Implementation support specialist**s, e.g. those providing technical assistance to the TB programme or the core HMIS unit to support & maintain DHIS2 as a national health information system and/or TB data system + +## Configuration du programme tracker { #tracker-program-configuration } + +![Overview of stages and sections](resources/images/tb_cs_030.png) + +| **Structure** | **Description** | +| --- | --- | +| **Inscription** | The stage collects the basic TEI attributes. Please note that some of the attributes show the “GEN - “ prefix. To know more about the [**Common Metadata Library**](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
The stage is non-repeatable. | +| **Diagnostic Laboratory Results** | In order to display the whole list of tests available for **diagnostic purposes**, the user should report first the “Sample information” section.
**The stage is repeatable**. The repeatability was set to allow countries to implement the tracker as per the local workflows and preferences - depending on whether there is the need to track ALL the samples (good and bad quality) or just the “good” samples, the stage can be repeated accordingly. | +| **Diagnosis and notification** | The stage collects the baseline information, the risk factors, the potential HIV (co-)infection, and the diagnostic decision. The decision-maker will either **diagnose a suspected case with TB and notify** them, or will confirm the absence of infection. **SMS templates** for notifying the cases or confirming the absence of infection are included in the metadata package.
**The stage is non-repeatable**. | +| **Treatment** | The stage collects the information necessary for the overview of the **patient’s regimen** and status during their course of treatment.
**The stage is repeatable** but limited to two events and one treatment regimen change. | +| **Monitoring Laboratory Results** | In order to display the available tests for monitoring purposes (sputum microcopy and culture tests), the user should report first the “Sample information” section. The stage only displays the tests used for **monitoring confirmed cases** rather than all the tests that can be requested for the follow-up of the patient. The stage will display just the sputum microscopy for cases on fist-line treatment regimen, while will add the culture to teh microscopy for DRTB patients.
**The stage is repeatable**. | +| **Outcome** | The stage collects the final outcome of a confirmed case. In this stage the patients can be denotified if they result not being a TB case or in order to remove a duplicate enrollment.
**The stage is non-repeatable**. | + +### Stage Details { #stage-details } + +#### Inscription { #enrollment } + +When a client is enrolled in the TB case surveillance as a tracked entity instance (TEI), TEI attributes are recorded to form the case profile. + +![Enrollment stage](resources/images/tb_cs_003.png) + +**The enrollment date has been set up as a placeholder** allowing the users to utilize it according to the needs of implementation. It can be used as date of registration in DHIS2 or as date of first consultation, visit or investigation. When enrolling confirmed TB cases only, it is possible to keep using enrollment date as date of diagnosis. In this case, the Laboratory tracker should be isolated from the TB case surveillance module and set up as a separate program. + +**Note that the TB registration number has been left empty**. If the data entry is occurring in real time, at this stage the clinician/data entry operator cannot know whether the suspected case is confirmed or not. The users will have to reopen the enrollment and assign to the confirmed patient a registration number after having received the diagnostic laboratory results. + +If the data entry is retrospective and done in batch, the data encoder will already know whether the patient has been confirmed or not, and will be able to already assign a registration number accordingly. For this reason the TB registration number has not been set as a compulsory attribute. + +Upon the completion of the enrollment, the **landing page for the next stages appears blank**. This has been set for countries to be able to implement the tracker according to their own work flows as described in the “Rationale for Program Structure” chapter of this guide. The next stages can therefore be the “Diagnostic Laboratory Results” or the “Diagnosis and notification” stages, either in this order, or in the opposite order. + +#### Diagnostic Laboratory Results { #diagnostic-laboratory-results } + +![Diagnostic test stage](resources/images/tb_cs_004.png) + +The full list of diagnostic tests will automatically appear only if the sample is flagged as received and if the quality is good. The stage includes the following tests: + +- Sputum smear microscopy; +- TB-LAMP; +- LF-LAM; +- Xpert MTB/RIF; +- Xpert MTB/RIF Ultra; +- Truenat; +- Culture in solid media (e.g. LJ); +- Culture in liquid media (e.g. MGIT); +- Initial phenotypic DST in solid media (e.g. LJ); +- Initial phenotypic DST in liquid media (e.g. MGIT); +- Subsequent phenotypic DST in solid media (e.g. LJ); +- Subsequent phenotypic DST in liquid media (e.g. MGIT); +- First-line LPA; +- Second-line LPA + +As an example of the data entry for two of the tests: + +![Smear microscopy](resources/images/tb_cs_005.png) + +![Xpert MTB/RIF](resources/images/tb_cs_006.png) + +**Date of test results** (including inoculation date for culture tests) has to be provided for each test. The purpose of this is to: + +- assign the test event to the right period of time in analytics; +- help monitoring the delay between reception and result dates. + +The suggested design of the diagnostic laboratory stage is to enter final valid test results only. + +**Examples:** + +- 1 sample - 1 microscopy test: Record test results for the applicable test in the data entry form. + +- 1 sample - 1 microscopy and 1 Xpert MTB/RIF test: Record microscopy and Xpert MTB/RIF results in the data entry form. + +- 1 sample - 2 repeated microscopy tests, where test 1 is invalid and test 2 is valid: Record results of test 2 (valid test result) in the data entry form. + +This recommendation minimizes the data entry workload, and aligns with the basic requirement of not using tracker as a lab management tool. + +If locally there is a need to monitor the workload of the lab outside the local lab management system, it is possible to add a data element in each test section and record the number of tests that had to be run before receiving a final result. If the local needs request a more detailed collection of samples tested independent of the results, the tracker could be uptaken to record multiple tests per sample and per case. + +**Implementers should therefore investigate the analytic needs of the implementing country and adjust the indicators related to the number of tests and results accordingly.** + +#### Diagnosis and Notification { #diagnosis-and-notification } + +According to current tracker design, the Diagnosis and Notification event may be created before or after the Diagnostic laboratory Results event. + +**The Diagnosis and Notification event date is a placeholder** that can be utilized according to the implementation needs. It can be used as the date of initial visit, consultation or sample collection. + +> **IMPORTANT** +> +> If data entry is happening based on paper forms or data import, and the event date is used as date of data entry in DHIS2, there is a chance that the registration event will appear after other events in the timeline, which may be misleading for users. + +The registration stage provides an overview of the baseline information, the eventual risk factors, whether the suspected case is HIV(+), and, most importantly, the section on diagnostic decisions. + +![Baseline info](resources/images/tb_cs_007.png) + +The system will **automatically provide a warning message with the definition of the selected history of previous treatment**. The definitions have been set as per the WHO global guidelines and should be adapted to the local context. A question on whether the patient has ever received 2nd line treatment before will appear should “Relapse”, “Treatment after failure or LTFU”, or “Other previously treated” is selected as history. + +![Baseline info for 2-line treatment](resources/images/tb_cs_079.png) + +![Risk factors and HIV status](resources/images/tb_cs_008.png) + +In case of confirmed seropositivity of the patient the system will prompt an expansion of the HIV information and will request the date of the last test and whether the patient is enrolled in an ART cohort. If the latest HIV test date is **older than 6 months** from the date of diagnosis, a warning message will prompt the clinician to schedule another HIV test for the patient. + +At this point, if the laboratory results are available, the clinician/data entry clerk should be able to report the diagnostic decision. + +![Diagnosis of a presumptive case](resources/images/tb_cs_080.png) + +![Diagnosis](resources/images/tb_cs_009.png) + +Once **the case is notified**, the user needs to fill in the fields in the Diagnostic decision section. + +If positive laboratory test results are available and entered in the “Diagnostic Laboratory Results” stage, **bacteriological confirmation will be assigned automatically**. If the local guidelines require the clinician to enter this information manually, the PRs linked to the confirmation method can be removed. + +A **notification is sent to the patient** if the “Notify the case?” checkbox is clicked, the diagnosis, date of diagnosis, the notification date and the patient’s telephone number are recorded in the system. + +If the test results are negative but the case is **diagnosed clinically**, the patient can be notified as “clinically diagnosed”. + +![Clinical diagnosis](resources/images/tb_cs_010.png) + +If the laboratory **results are negative and no notification is necessary**, the user should tick “NO” in the “Do you want to notify the case?”. This was the case is excluded from analysis of TB cases. **An SMS is sent to the patient if the patient is not diagnosed** + +![The suspected case results as negative](resources/images/tb_cs_011.png) + +Once a presumptive case is bacteriologically confirmed or clinically diagnosed, they should receive a **TB registration number**. This information is also highlighted as a **reminder in the Feedback** window on the top right corner of the data entry screen just above the enrollment information. The clinician/data entry clerk should therefore reopen the enrollment window and assign a TB registration number according to the national guidelines. Although the default configuration leaves this space blank and editable, implementers might want to consider if an automatic assignment of a number (or alphanumeric sequence) would be appropriate as per the local workflow. + +![TB registration number assignment for clinically and bacteriologically diagnosed cases](resources/images/tb_cs_019.png) + +The same info will also appear as an **error message** under the “Date of diagnosis” as a reminder to assign a Tb registration number to the newly identified case. + +![Error message for the TB registration number assignment for clinically and bacteriologically diagnosed cases](resources/images/tb_cs_020.png) + +#### Treatment { #treatment } + +![Treatment](resources/images/tb_cs_012.png) + +In this stage the clinician/data entry clerk will report the **regimen of the patient** - 1st or 2nd line treatment. As the tests did not detect any resistance, the patient is automatically assigned the DS (drug susceptible) option. The clinician can tick the box in the section to overwrite the automatic assignment and manually assign the right classification according to their clinical opinion. The automatic classification could also be completely removed, which will in turn compel the clinician to manually assign a classification based on the laboratory results for every patient. The treatment end date should be applied only if it is needed to overwrite the current treatment - e.g. the patient needs to be put on 2nd line from 1st line treatment regimen. The decision of being able to change the treatment rather than the notification and diagnosis stage was taken in odrder to have more flexibility in case of mistakes and to keep the history of the patient rather than overwriting and removing the past diagnoses. + +The date of treatment initiation (event date) is important for the calculation of the delay between diagnosis and the debut of the treatment. The Treatment Status section contains **automatically assigned standard calculations of treatment durations and treatment initiation delays in days**. The event due date is configured with the description ‘expected date of outcome. By default, the **due date for the outcome section is scheduled for 180 days after the date of treatment initiation - this is to be considered as a placeholder and the 180 days threshold should be replaced with whichever period is defined in the national guidelines.** The Outcome stage due date may be changed manually, but can only be rescheduled once. For a user, this may be done after Treatment has been initiated and the DE in the Treatment stage ‘Outcome Due’ has been generated. When an Outcome stage is overdue (the current date is later than the calculated DE ‘Outcome due’ from the Treatment stage, a message is displayed in the Feedback Widget. + +#### Monitoring Laboratory Results { #monitoring-laboratory-results } + +The structure of the monitoring stage is **virtually identical to the diagnostic laboratory stage**. The main difference is the list of tests - the monitoring lab stage includes only the ones that are relevant for monitoring purposes. Please note that if the patient is flagged as DS (drug susceptible), only the microscopy test will automatically appear in the monitoring lab stage as per WHO guidelines. As aforementioned, should the patient be a DRTB case, the list of tests will also display the cultures in solid and liquid media. + +#### Outcome { #outcome } + +As aforementioned, the outcome stage is a **non repeatable stage** where the confirmed positive cases end their treatment. Depending on the amount of time passed since the enrollment, the clinician/data entry clerk can select all the outcomes or only the outcomes that can be acceptable within a given time. + +- If the outcome for the patient is registered within 6 months from their diagnosis, the only available options will be “dead” and “LTFU”. +- Above the 6 months threshold, the outcomes list expands and also includes the “cured”, “not evaluated” and “completed” options. +- The “failed” outcome can only be entered 5 months after the date of diagnosis. + +**The number of months has been set as placeholder** while following the global guidelines, though the value should be updated according to the relevant national guidelines. Every outcome will automatically display a warning box with the definition of the chosen option. The definitions follow the standard explanation detailed in the WHO guidelines. Similarly, the definitions should also be replaced or expanded based on the ones present in the national guidelines. + +![Outcome](resources/images/tb_cs_014.png) + +The outcome can also be used to denotify a case. A denotification is applied if a suspected patient is not a case, or to remove a duplicate enrollment. Removed duplicates will not be considered nor counted towards the total reports, though the number of denotified duplicates will be available in order to monitor the quality of the data and of the data entry. + +## Additional Features { #additional-features } + +### Real Time Notifications { #real-time-notifications } + +Should the system be used for real time data entry and surveillance, there are four predefined notifications in the default configuration of the tracker. These can and should be customized to better mirror the local context and needs. + +- **TB CS - Case notification** - this SMS notification is sent to the presumptive case by alerting the recepient that the lab results are available and he/she should contact the health facility. The notification is sent only if the phone number of the presumptive case and the notification date have a valid value. +- **TB CS - Poor sample quality notification** - this is an internal system notification sent to the TB Admin user group whenever a sample that was received at the lab does not meet the quality standards for processing and is registered as “bad quality”. The notification should prompt the clinician to collect another sample from the same case for either diagnosis or monitoring purposes. +- **TB CS - De-notification (presumptive case)** - this SMS notification is sent to the presumptive case prompting him/her to contact the health facility. The notification is triggered only if the case is denotified from the “Outcome” stage and the phone number of the case was registered at enrollment. +- **TB CS - Denotification (notified case)** - this SMS notification is sent to a already notified case who was mistakenly notified due to double data entry or any other human or system error. + +### Les constantes { #constants } + +The package includes a **set of tests and a list of drugs that can be modified** by the implementing country according to national context (e.g. which drugs and tests are used/available in the country). The use of constants enables a system admin in an implementing country to easily _‘turn on’ or ‘turn off’_ types of drugs and tests depending on availability in the country. When the complete package is installed into a DHIS2 instance, all data elements for all tests and drugs included in this package are included in the system. By default, all constants are set to ‘1’ (enabling the related data elements for data entry) and can be configured to ‘0’ by an implementer or system admin according to country context if not needed (disabling the related data elements for data entry). If a test or drug later becomes available in the country, an admin can simply re-enable the data elements by changing the constant from a value of ‘0’ to a value of ‘1’. + +![Example of a constant](resources/images/tb_cs_018.png) + +### Top Bar Widget { #top-bar-widget } + +The top bar widget **can be either displayed or hidden**. In the default configuration of the tracker, the top bar is visible and configured to display the relevant information in the following order: 1) date of diagnosis, 2) TB registration number, 3) months since diagnosis, 4) patient’s age (months). 5) patient’s age (years), 6) HIV status, 7) resistance classification (at diagnosis), 8) case classification, 9) treatment regimen, and 10) resistance. + +The order, the amount of info to be displayed, and the variables to display can be customized locally. + +![Top bar info](resources/images/tb_cs_015.png) + +### Feedback Widget { #feedback-widget } + +Upon the completion of the enrollment process, the feedback text box will be displayed and available on the **top right corner of the screen**. Just like the other widgets, t**he feedback box can be removed**, though in the default configuration of the tracker it is displayed and used to flash important messages and notes to the user entering the data. + +![Feedback text box](resources/images/tb_cs_016.png) + +## Analyse { #analytics } + +### Indicateurs de programme { #program-indicators } + +The full list of program indicators and indicators is available in the [metadata Reference File](resources/tb_cs-metadata.xlsx). + +### Reporting Case-based Data into Aggregate TB Reports { #reporting-case-based-data-into-aggregate-tb-reports } + +The TB case-based surveillance tracker captures data that can be fed into standard, aggregate reporting (i.e. monthly, quarterly, or more frequently as determined by the country). An aggregate TB system design in DHIS2 can be accessed at who.dhis2.org/documentation/#tb. + +The package includes 2 groups of program indicators that are mapped to the corresponding data elements and category option combinations of the data sets in the TB aggregate package. + +The current TB CS tracker supports data transfer for the following data sets: + +- TB - Case notification (quarterly) +- TB - RR/MDR-TB case detection and treatment (yearly) +- TB - Treatment outcomes (quarterly) +- TB - Treatment outcomes - second line (yearly) +- TB - Laboratory (monthly) + +The mapping is based on codes of metadata objects. The process of data transfer is described in the installation guide. + +### Règles de programme { #program-rules } + +Program rules are used extensively in the TB Case Surveillance tracker to show/hide data elements to optimize the data entry form, show warnings/feedback to the data entry user and autocalculate & assign data values to data elements. A complete list of program rules can be found in the metadata reference file. + +## Tableaux de bord { #dashboards } + +TB Case surveillance tracker version 2.0.0 includes a dashboard for monitoring TB sample processing and test results (**TB-LAB - Laboratory**) summarizing the key indicators for the monitoring of the laboratory activities (volumes test, cases, or samples, positivity rates, turnaround times, and results). The dashboard presents first the overall data for any test type and is then sectioned by test type (smear microscopy, GeneXpert, GeneXpert Ultra, and culture tests - solid and liquid media). The sections are labeled with a text box indicating the test type. Depending on the local context, type of implementation, and test availability, the dashboard can and should be adapted to better mirror the implementation’s needs. Moreover, **should the TB Case surveillance tracker be used as a standalone module without aggregate data transfer, it is possible to utilize the existing indicators and configure custom visualizations and dashboards**. + +## Groupes d’utilisateurs { #user-groups } + +The following user groups are included in the TB Case Surveillance Tracker Package: + +- TB Admin: can edit/view metadata; no access to data [all program stages] +- TB Data capture: can view metadata, can capture data [all program stages], no access to dashboards +- TB Access: cam view metadata, can view data [all program stages] +- TB lab access: cam view metadata, can view data [? program stages], access to laboratory dashboards +- TB lab data capture: can view metadata, can capture data [TB registration and Laboratory stages] + +## Références { #references } + +**UN High Commissioner for Refugees (UNHCR)**, (2015). Policy on the Protection of Personal Data of Persons of Concern to UNHCR. URL: [accessed 20 July 2022] + +**World Health Organization**, (2013). Definitions and reporting framework for tuberculosis – 2013 revision (updated December 2014 and January 2020). URL: [accessed 20 July 2022] diff --git a/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE__VERSION-200__design-md b/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE__VERSION-200__design-md new file mode 100644 index 000000000..2f4a04032 --- /dev/null +++ b/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE__VERSION-200__design-md @@ -0,0 +1,301 @@ +--- +edit_url: "https://github.com/dhis2-metadata/TB_CS/blob/master/docs/tb_cs-design-2.0.0.md" +revision_date: "2022-12-13" +tags: + - Version 2.0.0 + - Métadonnées +--- + +# TB Case Surveillance - System Design Document { #tb-cs-design-200 } + +## Introduction { #introduction } + +The **TB Case Surveillance Tracker (TB-CS) digital data package for DHIS2** is based on the [WHO recording and reporting framework](https://apps.who.int/iris/handle/10665/79199) from 2013. It provides a set of recommended metadata (data elements, program rules, etc) to enable electronic capture of individual/case-based TB surveillance data. The tracker metadata is configured to ensure that aggregated standard quarterly TB report indicators on notifications, first-line outcomes and second-line outcomes as defined by the WHO Definitions and reporting framework for TB (2013) can be automatically generated from the individual data captured. The TB Case Surveillance Tracker is not intended to support patient management or patient care. This requires more detailed analysis of roles, responsibilities, workflows and decision-making within the settings in which such systems would be implemented. + +The system design document explains how the tracker program was configured to meet the data entry and analysis requirements and support a typical workflow. The document does not include an exhaustive listing of all metadata captured. This document also does not consider the resources and infrastructure needed to implement such a system, such as servers, power, internet connections, backups, training and user support. More information on the TB programme technical aspects informing this system design is available in the [WHO publication on electronic recording and reporting for tuberculosis care and control](https://apps.who.int/iris/handle/10665/44840). Supplementary implementation guidance for DHIS2 can be found in the [General DHIS2 Implementation Guide](https://docs.dhis2.org/en/implement/configuring-the-android-app/about-this-guide.html) and [DHIS2 tracker implementation guide](https://docs.dhis2.org/en/implement/understanding-dhis2-implementation/a-quick-guide-to-dhis2-implementation.html). + +## Aperçu de la conception du système { #system-design-overview } + +### Contexte { #background } + +Reliable epidemiological data is required for staff at all levels of a national TB programme to plan and provide effective tuberculosis care and control services, as well as monitor the performance of programmatic actions. A case-based surveillance system has clear advantages over an aggregate data collection system. Like an aggregate surveillance system a minimum set of epidemiological indicators can be captured, validated, aggregated, calculated and displayed but these can be disaggregated by any combination of time, location/area, age, sex, case type, previous treatment history, HIV status, drug resistance status and treatment regimens. This helps us to understand TB epidemiology in depth and monitor changes over time. It is expected that case-based electronic data will result in **improved data quality** because the number of data entry steps are reduced, automatic calculations and validations can be built into the system, inconsistent, erroneous or incomplete data can be corrected or completed rapidly for an individual record and de-duplication can be carried out to remove duplicate records. A case-based surveillance system should also allow the linking of surveillance records to the same case even if a TB case is transferred or referred between facilities during the course of treatment. See principle 2.4, page 16, of [**Policy on the Protection of Personal Data of Persons of Concern to UNHCR**](http://www.refworld.org/docid/55643c1d4.html). + +### Cas d’utilisation { #use-case } + +The TB Case Surveillance Tracker enables **registration and longitudinal tracking of TB cases from the point of notification to final case outcome, inclusive of laboratory results**. The program captures a minimum set of data points required for epidemiological analysis of case surveillance data as described in the background section. These include baseline and demographic information about the case, risk factors, laboratory results for diagnosis and routine check-ups, drug resistance type classification, treatment regimens provided, and case outcome. **This tracker program is not designed to support clinical management nor patient care**. Rather, the program serves as an electronic registry that supports decentralized electronic data capture of case surveillance data down to health facility and laboratory levels. + +## Structure du programme { #program-structure } + +The revised TB CS tracker program has been designed to reflect a **more generic workflow** able to integrate data entry both from the health facility side (e.g. clinicians and nurses), and the laboratory side. Workflows in countries may vary and the case surveillance program should be adapted as needed to local context. + +> **IMPORTANT** +> +> Please note that given the generic design of the tracker, this system design guide contains throughout the sections useful information, considerations, and justifications that can be of great importance for the implementation. The document should therefore be thoroughly revised both by the requesting and implementing parties. + +![Theoretical workflow](resources/images/tb_cs_001.png) + +Following this initial workflow, the program has been structured as follows: + +![Data flow within the tracker stages](resources/images/tb_cs_029.png) + +### Logique de la structure du programme { #rationale-for-program-structure } + +The design of the tracker has been improved to expand the information that could potentially be collected from the laboratory side. The expansion touched of course the metadata, which is now more comprehensive and allows to **discern between diagnostic and monitoring tests**, but it also created a more generic baseline upon which implementers and countries could build their own workflow. Depending on the local needs, the “Diagnostic laboratory results” and the “Diagnosis and notification” stages could have different orders; depending on the local resources and connectivity, the data entry could be centralized or decentralized between the laboratory and the health facility; depending on the local data flow, the data could be entered live or retrospectively. + +In particular, there could theoretically be **three general scenarios** that could change the flow and the order of the stages: + +1. **The laboratory staff receives the tests requests and the “Diagnostic Laboratory Results” is the very first step** in the journey of the suspected case upon their enrollment. This scenario represents the theoretical work flow and should be the target to which countries should aim in the long-term investment in the digitalization of routine health data. + + - In this case the “Enrollment” and “ Diagnostic Laboratory Results” stages are completed directly by the laboratory staff. The “Diagnosis and notification” stage can then occur in parallel or after the registration of the laboratory results. At this point the case can either become an official TB case, in which case they will have to receive a TB registration number in their enrollment stage, or they will receive negative laboratory results and be denotified. + +2. **The suspected case gets enrolled and registered from the clinical side of the workflow before the samples are sent to the laboratory.** + + - In this case the “Enrollment” and the “Diagnosis and notification” stages are completed first. + - The “Diagnostic Laboratory Results” gets completed by the laboratory staff. + - The clinicians will complete the “Diagnosis and notification“ stage confirming or not their diagnosis and notifying the case if necessary. If the latter happens, the clinician will have to reopen the “Enrollment” and assign a TB registration number to the now-confirmed case. + + Please note that scenarios 1 and 2 are based on the assumption that the laboratory staff has the capacity to enter the data in the system locally and directly in their own facility. + + Should this capacity be inadequate for the local context, then scenario number 3 would occur: + +3. **The data entry is centralized and there is no differentiation between laboratory and clinical staff** - the data entry relies on one (or multiple) data encoder. In this case the stages should be arranged in order to match the local flow of information and data. + +Independently from the best fitting scenario for a defined local context,**the adaptation of the tracker workflow and its stages should also take in consideration whether the data entry will occur in real time or if it will rely on batch retrospective data entry**. + +## Utilisateurs cibles { #intended-users } + +This document is intended for audiences responsible for implementing TB data systems and/or HMIS in countries, including: + +- **System admins/HMIS focal points**: those responsible for installing metadata packages, designing and maintaining HMIS and/or TB data systems +- **TB program focal points** responsible for overseeing data collection, management, analysis and reporting functions of the national TB programme +- **Implementation support specialists**, e.g. those providing technical assistance to the TB programme or the core HMIS unit to support & maintain DHIS2 as a national health information system and/or TB data system + +## Configuration du programme tracker { #tracker-program-configuration } + +![Overview of stages and sections](resources/images/tb_cs_030.png) + +| **Structure** | **Description** | +| --- | --- | +| **Inscription** | The stage collects the basic TEI attributes. Please note that some of the attributes show the “GEN - “ prefix. To know more about the [**Common Metadata Library**](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
The stage is non-repeatable. | +| **Diagnostic Laboratory Results** | In order to display the whole list of tests available for **diagnostic purposes**, the user should report first the “Sample information” section.
**The stage is repeatable**. The repeatability was set to allow countries to implement the tracker as per the local workflows and preferences - depending on whether there is the need to track ALL the samples (good and bad quality) or just the “good” samples, the stage can be repeated accordingly. | +| **Diagnosis and notification** | The stage collects the baseline information, the risk factors, the potential HIV (co-)infection, and the diagnostic decision. The decision-maker will either **diagnose a suspected case with TB and notify** them, or will confirm the absence of infection. **SMS templates** for notifying the cases or confirming the absence of infection are included in the metadata package.
**The stage is non-repeatable**. | +| **Treatment** | The stage collects the information necessary for the overview of the **patient’s regimen** and status during their course of treatment.
**The stage is repeatable** but limited to two events and one treatment regimen change. | +| **Monitoring Laboratory Results** | In order to display the available tests for monitoring purposes (sputum microcopy and culture tests), the user should report first the “Sample information” section. The stage only displays the tests used for **monitoring confirmed cases** rather than all the tests that can be requested for the follow-up of the patient. The stage will display just the sputum microscopy for cases on fist-line treatment regimen, while will add the culture to teh microscopy for DRTB patients.
**The stage is repeatable**. | +| **Outcome** | The stage collects the final outcome of a confirmed case. In this stage the patients can be denotified if they result not being a TB case or in order to remove a duplicate enrollment.
**The stage is non-repeatable**. | + +### Stage Details { #stage-details } + +#### Inscription { #enrollment } + +When a client is enrolled in the TB case surveillance as a tracked entity instance (TEI), TEI attributes are recorded to form the case profile. + +![Enrollment stage](resources/images/tb_cs_003.png) + +**The enrollment date has been set up as a placeholder** allowing the users to utilize it according to the needs of implementation. It can be used as date of registration in DHIS2 or as date of first consultation, visit or investigation. When enrolling confirmed TB cases only, it is possible to keep using enrollment date as date of diagnosis. In this case, the Laboratory tracker should be isolated from the TB case surveillance module and set up as a separate program. + +**Note that the TB registration number has been left empty**. If the data entry is occurring in real time, at this stage the clinician/data entry operator cannot know whether the suspected case is confirmed or not. The users will have to reopen the enrollment and assign to the confirmed patient a registration number after having received the diagnostic laboratory results. + +If the data entry is retrospective and done in batch, the data encoder will already know whether the patient has been confirmed or not, and will be able to already assign a registration number accordingly. For this reason the TB registration number has not been set as a compulsory attribute. + +Upon the completion of the enrollment, the **landing page for the next stages appears blank**. This has been set for countries to be able to implement the tracker according to their own work flows as described in the “Rationale for Program Structure” chapter of this guide. The next stages can therefore be the “Diagnostic Laboratory Results” or the “Diagnosis and notification” stages, either in this order, or in the opposite order. + +#### Diagnostic Laboratory Results { #diagnostic-laboratory-results } + +![Diagnostic test stage](resources/images/tb_cs_004.png) + +The full list of diagnostic tests will automatically appear only if the sample is flagged as received and if the quality is good. The stage includes the following tests: + +- Sputum smear microscopy; +- TB-LAMP; +- LF-LAM; +- Xpert MTB/RIF; +- Xpert MTB/RIF Ultra; +- Truenat; +- Culture in solid media (e.g. LJ); +- Culture in liquid media (e.g. MGIT); +- Initial phenotypic DST in solid media (e.g. LJ); +- Initial phenotypic DST in liquid media (e.g. MGIT); +- Subsequent phenotypic DST in solid media (e.g. LJ); +- Subsequent phenotypic DST in liquid media (e.g. MGIT); +- First-line LPA; +- Second-line LPA + +As an example of the data entry for two of the tests: + +![Smear microscopy](resources/images/tb_cs_005.png) + +![Xpert MTB/RIF](resources/images/tb_cs_006.png) + +**Date of test results** (including inoculation date for culture tests) has to be provided for each test. The purpose of this is to: + +- assign the test event to the right period of time in analytics; +- help monitoring the delay between reception and result dates. + +The suggested design of the diagnostic laboratory stage is to enter final valid test results only. + +**Examples:** + +- 1 sample - 1 microscopy test: Record test results for the applicable test in the data entry form. + +- 1 sample - 1 microscopy and 1 Xpert MTB/RIF test: Record microscopy and Xpert MTB/RIF results in the data entry form. + +- 1 sample - 2 repeated microscopy tests, where test 1 is invalid and test 2 is valid: Record results of test 2 (valid test result) in the data entry form. + +This recommendation minimizes the data entry workload, and aligns with the basic requirement of not using tracker as a lab management tool. + +If locally there is a need to monitor the workload of the lab outside the local lab management system, it is possible to add a data element in each test section and record the number of tests that had to be run before receiving a final result. If the local needs request a more detailed collection of samples tested independent of the results, the tracker could be uptaken to record multiple tests per sample and per case. + +**Implementers should therefore investigate the analytic needs of the implementing country and adjust the indicators related to the number of tests and results accordingly.** + +#### Diagnosis and Notification { #diagnosis-and-notification } + +According to current tracker design, the Diagnosis and Notification event may be created before or after the Diagnostic laboratory Results event. + +**The Diagnosis and Notification event date is a placeholder** that can be utilized according to the implementation needs. It can be used as the date of initial visit, consultation or sample collection. + +> **IMPORTANT** +> +> If data entry is happening based on paper forms or data import, and the event date is used as date of data entry in DHIS2, there is a chance that the registration event will appear after other events in the timeline, which may be misleading for users. + +The registration stage provides an overview of the baseline information, the eventual risk factors, whether the suspected case is HIV(+), and, most importantly, the section on diagnostic decisions. + +![Baseline info](resources/images/tb_cs_007.png) + +The system will **automatically provide a warning message with the definition of the selected history of previous treatment**. The definitions have been set as per the WHO global guidelines and should be adapted to the local context. A question on whether the patient has ever received 2nd line treatment before will appear should “Relapse”, “Treatment after failure or LTFU”, or “Other previously treated” is selected as history. + +![Baseline info for 2-line treatment](resources/images/tb_cs_079.png) + +![Risk factors and HIV status](resources/images/tb_cs_008.png) + +In case of confirmed seropositivity of the patient the system will prompt an expansion of the HIV information and will request the date of the last test and whether the patient is enrolled in an ART cohort. If the latest HIV test date is **older than 6 months** from the date of diagnosis, a warning message will prompt the clinician to schedule another HIV test for the patient. + +At this point, if the laboratory results are available, the clinician/data entry clerk should be able to report the diagnostic decision. + +![Diagnosis of a presumptive case](resources/images/tb_cs_080.png) + +![Diagnosis](resources/images/tb_cs_009.png) + +Once **the case is notified**, the user needs to fill in the fields in the Diagnostic decision section. + +If positive laboratory test results are available and entered in the “Diagnostic Laboratory Results” stage, **bacteriological confirmation will be assigned automatically**. If the local guidelines require the clinician to enter this information manually, the PRs linked to the confirmation method can be removed. + +A **notification is sent to the patient** if the “Notify the case?” checkbox is clicked, the diagnosis, date of diagnosis, the notification date and the patient’s telephone number are recorded in the system. + +If the test results are negative but the case is **diagnosed clinically**, the patient can be notified as “clinically diagnosed”. + +![Clinical diagnosis](resources/images/tb_cs_010.png) + +If the laboratory **results are negative and no notification is necessary**, the user should tick “NO” in the “Do you want to notify the case?”. This was the case is excluded from analysis of TB cases. **An SMS is sent to the patient if the patient is not diagnosed** + +![The suspected case results as negative](resources/images/tb_cs_011.png) + +Once a presumptive case is bacteriologically confirmed or clinically diagnosed, they should receive a **TB registration number**. This information is also highlighted as a **reminder in the Feedback** window on the top right corner of the data entry screen just above the enrollment information. The clinician/data entry clerk should therefore reopen the enrollment window and assign a TB registration number according to the national guidelines. Although the default configuration leaves this space blank and editable, implementers might want to consider if an automatic assignment of a number (or alphanumeric sequence) would be appropriate as per the local workflow. + +![TB registration number assignment for clinically and bacteriologically diagnosed cases](resources/images/tb_cs_019.png) + +The same info will also appear as an **error message** under the “Date of diagnosis” as a reminder to assign a Tb registration number to the newly identified case. + +![Error message for the TB registration number assignment for clinically and bacteriologically diagnosed cases](resources/images/tb_cs_020.png) + +#### Treatment { #treatment } + +![Treatment](resources/images/tb_cs_012.png) + +In this stage the clinician/data entry clerk will report the **regimen of the patient** - 1st or 2nd line treatment. As the tests did not detect any resistance, the patient is automatically assigned the DS (drug susceptible) option. The clinician can tick the box in the section to overwrite the automatic assignment and manually assign the right classification according to their clinical opinion. The automatic classification could also be completely removed, which will in turn compel the clinician to manually assign a classification based on the laboratory results for every patient. The treatment end date should be applied only if it is needed to overwrite the current treatment - e.g. the patient needs to be put on 2nd line from 1st line treatment regimen. The decision of being able to change the treatment rather than the notification and diagnosis stage was taken in odrder to have more flexibility in case of mistakes and to keep the history of the patient rather than overwriting and removing the past diagnoses. + +The date of treatment initiation (event date) is important for the calculation of the delay between diagnosis and the debut of the treatment. The Treatment Status section contains **automatically assigned standard calculations of treatment durations and treatment initiation delays in days**. The event due date is configured with the description ‘expected date of outcome. By default, the **due date for the outcome section is scheduled for 180 days after the date of treatment initiation - this is to be considered as a placeholder and the 180 days threshold should be replaced with whichever period is defined in the national guidelines.** The Outcome stage due date may be changed manually, but can only be rescheduled once. For a user, this may be done after Treatment has been initiated and the DE in the Treatment stage ‘Outcome Due’ has been generated. When an Outcome stage is overdue (the current date is later than the calculated DE ‘Outcome due’ from the Treatment stage, a message is displayed in the Feedback Widget. + +#### Monitoring Laboratory Results { #monitoring-laboratory-results } + +The structure of the monitoring stage is **virtually identical to the diagnostic laboratory stage**. The main difference is the list of tests - the monitoring lab stage includes only the ones that are relevant for monitoring purposes. Please note that if the patient is flagged as DS (drug susceptible), only the microscopy test will automatically appear in the monitoring lab stage as per WHO guidelines. As aforementioned, should the patient be a DRTB case, the list of tests will also display the cultures in solid and liquid media. + +#### Outcome { #outcome } + +As aforementioned, the outcome stage is a **non repeatable stage** where the confirmed positive cases end their treatment. Depending on the amount of time passed since the enrollment, the clinician/data entry clerk can select all the outcomes or only the outcomes that can be acceptable within a given time. + +- If the outcome for the patient is registered within 6 months from their diagnosis, the only available options will be “dead” and “LTFU”. +- Above the 6 months threshold, the outcomes list expands and also includes the “cured”, “not evaluated” and “completed” options. +- The “failed” outcome can only be entered 5 months after the date of diagnosis. + +**The number of months has been set as placeholder** while following the global guidelines, though the value should be updated according to the relevant national guidelines. Every outcome will automatically display a warning box with the definition of the chosen option. The definitions follow the standard explanation detailed in the WHO guidelines. Similarly, the definitions should also be replaced or expanded based on the ones present in the national guidelines. + +![Outcome](resources/images/tb_cs_014.png) + +The outcome can also be used to denotify a case. A denotification is applied if a suspected patient is not a case, or to remove a duplicate enrollment. Removed duplicates will not be considered nor counted towards the total reports, though the number of denotified duplicates will be available in order to monitor the quality of the data and of the data entry. + +## Additional Features { #additional-features } + +### Real Time Notifications { #real-time-notifications } + +Should the system be used for real time data entry and surveillance, there are four predefined notifications in the default configuration of the tracker. These can and should be customized to better mirror the local context and needs. + +- **TB CS - Case notification** - this SMS notification is sent to the presumptive case by alerting the recepient that the lab results are available and he/she should contact the health facility. The notification is sent only if the phone number of the presumptive case and the notification date have a valid value. +- **TB CS - Poor sample quality notification** - this is an internal system notification sent to the TB Admin user group whenever a sample that was received at the lab does not meet the quality standards for processing and is registered as “bad quality”. The notification should prompt the clinician to collect another sample from the same case for either diagnosis or monitoring purposes. +- **TB CS - De-notification (presumptive case)** - this SMS notification is sent to the presumptive case prompting him/her to contact the health facility. The notification is triggered only if the case is denotified from the “Outcome” stage and the phone number of the case was registered at enrollment. +- **TB CS - Denotification (notified case)** - this SMS notification is sent to a already notified case who was mistakenly notified due to double data entry or any other human or system error. + +### Les constantes { #constants } + +The package includes a **set of tests and a list of drugs that can be modified** by the implementing country according to national context (e.g. which drugs and tests are used/available in the country). The use of constants enables a system admin in an implementing country to easily _‘turn on’ or ‘turn off’_ types of drugs and tests depending on availability in the country. When the complete package is installed into a DHIS2 instance, all data elements for all tests and drugs included in this package are included in the system. By default, all constants are set to ‘1’ (enabling the related data elements for data entry) and can be configured to ‘0’ by an implementer or system admin according to country context if not needed (disabling the related data elements for data entry). If a test or drug later becomes available in the country, an admin can simply re-enable the data elements by changing the constant from a value of ‘0’ to a value of ‘1’. + +![Example of a constant](resources/images/tb_cs_018.png) + +### Top Bar Widget { #top-bar-widget } + +The top bar widget **can be either displayed or hidden**. In the default configuration of the tracker, the top bar is visible and configured to display the relevant information in the following order: 1) date of diagnosis, 2) TB registration number, 3) months since diagnosis, 4) patient’s age (months). 5) patient’s age (years), 6) HIV status, 7) resistance classification (at diagnosis), 8) case classification, 9) treatment regimen, and 10) resistance. + +The order, the amount of info to be displayed, and the variables to display can be customized locally. + +![Top bar info](resources/images/tb_cs_015.png) + +### Feedback Widget { #feedback-widget } + +Upon the completion of the enrollment process, the feedback text box will be displayed and available on the **top right corner of the screen**. Just like the other widgets, t**he feedback box can be removed**, though in the default configuration of the tracker it is displayed and used to flash important messages and notes to the user entering the data. + +![Feedback text box](resources/images/tb_cs_016.png) + +## Analyse { #analytics } + +### Indicateurs de programme { #program-indicators } + +The full list of program indicators and indicators is available in the [metadata Reference File](resources/tb_cs-metadata.xlsx). + +### Reporting Case-based Data into Aggregate TB Reports { #reporting-case-based-data-into-aggregate-tb-reports } + +The TB case-based surveillance tracker captures data that can be fed into standard, aggregate reporting (i.e. monthly, quarterly, or more frequently as determined by the country). An aggregate TB system design in DHIS2 can be accessed at who.dhis2.org/documentation/#tb. + +The package includes 2 groups of program indicators that are mapped to the corresponding data elements and category option combinations of the data sets in the TB aggregate package. + +The current TB CS tracker supports data transfer for the following data sets: + +- TB - Case notification (quarterly) +- TB - RR/MDR-TB case detection and treatment (yearly) +- TB - Treatment outcomes (quarterly) +- TB - Treatment outcomes - second line (yearly) +- TB - Laboratory (monthly) + +The mapping is based on codes of metadata objects. The process of data transfer is described in the installation guide. + +### Règles de programme { #program-rules } + +Program rules are used extensively in the TB Case Surveillance tracker to show/hide data elements to optimize the data entry form, show warnings/feedback to the data entry user and autocalculate & assign data values to data elements. A complete list of program rules can be found in the metadata reference file. + +## Tableaux de bord { #dashboards } + +TB Case surveillance tracker version 2.0.0 includes a dashboard for monitoring TB sample processing and test results (**TB-LAB - Laboratory**) summarizing the key indicators for the monitoring of the laboratory activities (volumes test, cases, or samples, positivity rates, turnaround times, and results). The dashboard presents first the overall data for any test type and is then sectioned by test type (smear microscopy, GeneXpert, GeneXpert Ultra, and culture tests - solid and liquid media). The sections are labeled with a text box indicating the test type. Depending on the local context, type of implementation, and test availability, the dashboard can and should be adapted to better mirror the implementation’s needs. Moreover, **should the TB Case surveillance tracker be used as a standalone module without aggregate data transfer, it is possible to utilize the existing indicators and configure custom visualizations and dashboards**. + +## Groupes d’utilisateurs { #user-groups } + +The following user groups are included in the TB Case Surveillance Tracker Package: + +- TB Admin: can edit/view metadata; no access to data [all program stages] +- TB Data capture: can view metadata, can capture data [all program stages], no access to dashboards +- TB Access: cam view metadata, can view data [all program stages] +- TB lab access: cam view metadata, can view data [? program stages], access to laboratory dashboards +- TB lab data capture: can view metadata, can capture data [TB registration and Laboratory stages] + +## Références { #references } + +**UN High Commissioner for Refugees (UNHCR)**, (2015). Policy on the Protection of Personal Data of Persons of Concern to UNHCR. URL: [accessed 20 July 2022] + +**World Health Organization**, (2013). Definitions and reporting framework for tuberculosis – 2013 revision (updated December 2014 and January 2020). URL: [accessed 20 July 2022] diff --git a/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE__design-md index 4fee9f565..c712ffa2e 100644 --- a/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE__design-md +++ b/projects/docs-full-site/fr/TOPICS__METADATA__TUBERCULOSIS__TB-CASE-SURVEILLANCE__design-md @@ -78,7 +78,7 @@ This document is intended for audiences responsible for implementing TB data sys | **Structure** | **Description** | |-------------------------------|----------| -| **Enrollment** | The stage collects the basic TEI attributes. Please note that some of the attributes show the “GEN - “ prefix. To know more about the [**Common Metadata Library**](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
The stage is non-repeatable. | +| **Inscription** | The stage collects the basic TEI attributes. Please note that some of the attributes show the “GEN - “ prefix. To know more about the [**Common Metadata Library**](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/common-metadata-library/design.html), please refer to the link provided.
The stage is non-repeatable. | | **Diagnostic Laboratory Results** | In order to display the whole list of tests available for **diagnostic purposes**, the user should report first the “Sample information” section.
**The stage is repeatable**. The repeatability was set to allow countries to implement the tracker as per the local workflows and preferences - depending on whether there is the need to track ALL the samples (good and bad quality) or just the “good” samples, the stage can be repeated accordingly. | | **Diagnosis and notification** | The stage collects the baseline information, the risk factors, the potential HIV (co-)infection, and the diagnostic decision. The decision-maker will either **diagnose a suspected case with TB and notify** them, or will confirm the absence of infection. **SMS templates** for notifying the cases or confirming the absence of infection are included in the metadata package.
**The stage is non-repeatable**. | | **Treatment** | The stage collects the information necessary for the overview of the **patient’s regimen** and status during their course of treatment.
**The stage is repeatable** but limited to two events and one treatment regimen change. | 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__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 31836a674..b11e3b3ad 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: '2024-06-07' 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..05b56b3f3 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Utilisation - Version principale de DHIS 2.38 +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } @@ -235,3 +235,15 @@ Pour libérer de l'espace pour la liste des lignes elle-même, il existe plusieu ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 a99b7f826..ca20ce556 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 5da1a0626..a63ac371c 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 --- > **Attention** 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 20c5cb9f2..a514a7a5c 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-06-24' 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..822b4eaa9 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Utilisation - DHIS version 2.39 +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } @@ -235,3 +235,15 @@ Pour libérer de l'espace pour la liste des lignes elle-même, il existe plusieu ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 7987ab807..14173d050 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 729fb54a5..a53b7fa23 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 --- > **Attention** 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 ed930bc51..0ae732ea0 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-06-24' 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 e743c93a3..edf65a607 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..731a79a50 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Utilisation - DHIS Version 2.40 +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } @@ -235,3 +235,15 @@ Pour libérer de l'espace pour la liste des lignes elle-même, il existe plusieu ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 725b55095..dabfbfed6 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 aa20e741d..2ed297cc1 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 --- > **Attention** 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 1464f7f3b..04f0bce14 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-06-24' 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__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__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__data-visualizer-md index 961b5a4a3..5710af989 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__line-listing-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__ANALYSING-DATA__line-listing-md index d7047ecab..3b8a39c76 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Utilisation - DHIS Version 2.41 +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } @@ -235,3 +235,15 @@ Pour libérer de l'espace pour la liste des lignes elle-même, il existe plusieu ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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__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 6bda5815a..95bc108de 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__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 5c9fd61da..c3be3e13e 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__installing-applications-md b/projects/docs-full-site/fr/USE__USER-GUIDES__DHIS-CORE-VERSION-241__MAINTAINING-THE-SYSTEM__installing-applications-md index 5df8e77ba..3f6f05e50 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 --- > **Attention** 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 6d79a61b2..c15c39d95 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-06-24' 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-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 3703ece7a..fc85c921b 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: '2024-06-07' 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 921bd816d..599bb4478 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..a3b6fd7fb 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Utilisation - Version Master de DHIS2 Central +- Utilisation --- # Utilisation de l'application Line Listing { #using-the-line-listing-app } @@ -235,3 +235,15 @@ Pour libérer de l'espace pour la liste des lignes elle-même, il existe plusieu ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 019b0763c..6f6f2b954 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: '2024-06-18' 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 b5079d568..428cddb64 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 a8c0bec58..da948492d 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-06-18' 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 bbcebc732..bcda98964 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 4b6bedcd0..9a49d57c9 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 cc6320b63..5637e15bc 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 --- > **Attention** 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 81025fc6e..4f7e9bac0 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-06-24' 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 6a2f72af8..c1e421e58 100644 --- a/projects/docs-full-site/pt/.cache_timestamp +++ b/projects/docs-full-site/pt/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:23:37Z \ No newline at end of file +2024-06-27T21:22:05Z \ No newline at end of file diff --git a/projects/docs-full-site/ru/.cache_timestamp b/projects/docs-full-site/ru/.cache_timestamp index 472bae883..3b378b34a 100644 --- a/projects/docs-full-site/ru/.cache_timestamp +++ b/projects/docs-full-site/ru/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:24:24Z \ No newline at end of file +2024-06-27T21:22:15Z \ No newline at end of file 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..074642146 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Использовать - DHIS core version 2.38 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 1caa06122..2e5a54405 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-06-24' 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..664f1b3e0 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Использовать - DHIS core version 2.39 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 336a52df5..55f79a242 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-06-24' 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..6ac3d9860 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Использовать - DHIS core version 2.40 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 94df8f807..03b8b6ebd 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-06-24' 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..edb1976dd 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- Использовать - DHIS core version 2.41 +- Использовать --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 c8e8104f6..aaf44142e 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-06-24' 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 ffe055450..6aae25efa 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: '2024-06-07' 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__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ANALYSING-DATA__line-listing-md index d18e91464..095cc26e1 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: - DHIS core version master - Использовать @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + diff --git a/projects/docs-full-site/si/.cache_timestamp b/projects/docs-full-site/si/.cache_timestamp index e65d3e584..43a39f0c7 100644 --- a/projects/docs-full-site/si/.cache_timestamp +++ b/projects/docs-full-site/si/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:24:53Z \ No newline at end of file +2024-06-27T21:22:55Z \ No newline at end of file diff --git a/projects/docs-full-site/zh/.cache_timestamp b/projects/docs-full-site/zh/.cache_timestamp index e65d3e584..5d1c8712b 100644 --- a/projects/docs-full-site/zh/.cache_timestamp +++ b/projects/docs-full-site/zh/.cache_timestamp @@ -1 +1 @@ -2024-06-26T21:24:53Z \ No newline at end of file +2024-06-27T21:22:56Z \ No newline at end of file diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md index 708ff30e8..9a3f31cf8 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 数据输入{ #data-entry } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md index eb9e3ee0d..fa6e6c442 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md index db39a74de..7ce31634a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md index cf4145477..52d5f351c 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md index ed0c68e1a..5f1e0416f 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata.md" revision_date: '2024-04-26' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 元数据 { #metadata } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 77dd69413..5c8cf6f03 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/route.md" revision_date: '2023-05-09' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # Route { #route } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index 04cde2751..aaf41ad14 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-01-26' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 设置和配置 { #settings-and-configuration } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index 5725ad87a..fb8ee285d 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 追踪器 { #tracker } 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..2a207aff1 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/audit.md" -revision_date: '2023-06-23' +revision_date: '2024-06-24' tags: - Develop - DHIS核心 主版 @@ -43,29 +43,30 @@ Example: Get audits for data element `BOSZApCrBni`, org unit `DiszpKrYNg8` and c /api/33/audits/dataValue?de=BOSZApCrBni&ou=DiszpKrYNg8&co=TkDhg29x18A ### 跟踪实体数据价值审核 { #webapi_tracked_entity_data_value_audits } +**deprecated for removal in version 43 use [tracked entity data value change log endpoint](https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md#event-data-value-change-logs--webapi_event_data_value_change_logs-)** -跟踪实体数据值审核的端点位于： +The endpoint for tracked entity data value audits is located at: ``` /api/audits/trackedEntityDataValue ``` -表：跟踪实体数据值查询参数 +Table: Tracked entity data value query parameters -| 范围 | 选项 | 描述 | +| Parameter | 选项 | 描述 | |---|---|---| -| 德 | 数据元素ID | 一个或多个数据元素标识符 | -| 欧 | 组织单位ID | 已审核事件的一个或多个组织单位标识符 | -| 事件 | 事件ID | 审核事件的一个或多个事件标识符（逗号分隔） | -| 附注 | 节目阶段 ID | 审核事件程序的一位或多位程序圣人 | -| 开始日期 | 开始日期 | 仅返回该日期之后创建的审核记录 | -| 结束日期 | 结束日期 | 仅返回日期之前创建的审核记录 | -| 模式 | 组织单位选择方式 | 已选\| 后人 | -| 审计类型 | 更新|删除 | 按一种或多种审核类型过滤 | -| 跳过分页 | 假的|真的 | 打开/关闭分页 | -| 寻呼 | 错误的 \| 真正 | 是否启用或禁用分页 | -| 页 | 数 | 页码（默认1） | -| 页面大小 | 数 | 页面大小（默认 50） | +| 德 | Data element ID | One or more data element identifiers | +| 欧 | Organisation unit ID | One or more organisation unit identifiers of the audited event | +| events | Events ID | One or more event identifiers of the audited event (comma separated) | +| ps | Program stage ID | One or more program sages of the audit event program | +| 开始日期 | Start date | Return only audit records created after date | +| 结束日期 | End date | Return only audit records created before date | +| ouMode | Organisation unit selection mode | SELECTED \| DESCENDANTS | +| auditType | UPDATE | DELETE | Filter by one or more audit types | +| skipPaging | false | true | Turn paging on / off | +| paging | false \| 真正 | Whether to enable or disable paging | +| page | 数 | Page number (default 1) | +| pageSize | 数 | Page size (default 50) | Example: Get audits for data elements `eMyVanycQSC` and `qrur9Dvnyt5`: @@ -77,23 +78,25 @@ Example: Get audits for org unit `O6uvpzGd5pu` including descendant org units in ### 跟踪实体属性值审核 { #webapi_tracked_entity_attribute_value_audits } -跟踪实体属性值审核的端点位于： +**deprecated for removal in version 43 use [tracked entity attribute change log endpoint](https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md#tracked-entity-attribute-value-change-logs--webapi_tracker_attribute_change_logs-)** + +The endpoint for tracked entity attribute value audits is located at: ``` /api/audits/trackedEntityAttributeValue ``` -表：跟踪实体属性值查询参数 +Table: Tracked entity attribute value query parameters -| 范围 | 选项 | 描述 | +| Parameter | 选项 | 描述 | |---|---|---| -| 茶 | 跟踪的实体属性 ID | 一个或多个被跟踪实体属性标识符 | -| 跟踪实体 | 跟踪的实体 ID | 一个或多个跟踪实体标识符（逗号分隔） | -| 审计类型 | 更新|删除 | 按一种或多种审核类型过滤 | -| 跳过分页 | 假的|真的 | 打开/关闭分页 | -| 寻呼 | 错误的 \| 真正 | 是否启用或禁用分页 | -| 页 | 数 | 页码（默认1） | -| 页面大小 | 数 | 页面大小（默认 50） | +| tea | Tracked entity attribute ID | One or more tracked entity attribute identifiers | +| trackedEntities | Tracked entity ID | One or more tracked entity identifiers (comma separated) | +| auditType | UPDATE | DELETE | Filter by one or more audit types | +| skipPaging | false | true | Turn paging on / off | +| paging | false \| 真正 | Whether to enable or disable paging | +| page | 数 | Page number (default 1) | +| pageSize | 数 | Page size (default 50) | Example: Get audits for tracked entity attribute `VqEFza8wbwA`: @@ -111,19 +114,19 @@ Once auditing is enabled for tracked entities (by setting `allowAuditLog` of tra /api/audits/trackedEntity ``` -表：跟踪实体审核查询参数 +Table: Tracked entity audit query parameters -| 范围 | 选项 | 描述 | +| Parameter | 选项 | 描述 | |---|---|---| -| 跟踪实体 | 跟踪实体 UIDS | 一个或多个跟踪实体标识符（逗号分隔） | -| 用户 | 用户 | 一个或多个用户标识符 | -| 审计类型 | 搜索|读 | 按一种或多种审核类型过滤 | -| 开始日期 | 开始日期 | Start date for audits in `yyyy-mm-dd` format | -| 结束日期 | 结束日期 | End date for audits in `yyyy-mm-dd` format | -| 跳过分页 | 假的|真的 | 打开/关闭寻呼。 | -| 寻呼 | 错误的 \| 真正 | 是否启用或禁用分页 | -| 页 | 数 | 页码（默认1） | -| 页面大小 | 数 | 页面大小（默认 50） | +| trackedEntities | Tracked Entity UIDS | One or more tracked entity identifiers (comma separated) | +| user | 用户 | One or more user identifiers | +| auditType | SEARCH | READ | Filter by one or more audit types | +| 开始日期 | Start date | Start date for audits in `yyyy-mm-dd` format | +| 结束日期 | End date | End date for audits in `yyyy-mm-dd` format | +| skipPaging | false | true | Turn paging on / off. | +| paging | false \| 真正 | Whether to enable or disable paging | +| page | 数 | Page number (default 1) | +| pageSize | 数 | Page size (default 50) | Example: Get audits of audit type `READ` with `startDate` 2018-03-01 and `endDate` 2018-04-24 with a page size of 5: @@ -133,7 +136,7 @@ Example: Get audits for tracked entity `wNiQ2coVZ39`: /api/33/audits/trackedEntity.json?trackedEntities=wNiQ2coVZ39 -### ***已弃用*** 跟踪实体实例审核 { #webapi_tracked_entity_instance_audits } +### ***DEPRECATED*** Tracked entity instance audits { #webapi_tracked_entity_instance_audits } Once auditing is enabled for tracked entity instances (by setting `allowAuditLog` of tracked entity types to `true`), all read and search operations are logged. The endpoint for accessing audit logs is located at: @@ -141,19 +144,19 @@ Once auditing is enabled for tracked entity instances (by setting `allowAuditLog /api/audits/trackedEntityInstance ``` -表：跟踪的实体实例审核查询参数 +Table: Tracked entity instance audit query parameters -| 范围 | 选项 | 描述 | +| Parameter | 选项 | 描述 | |---|---|---| -| 跟踪实体 | 跟踪实体 UIDS | 一个或多个跟踪实体标识符（逗号分隔） | -| 用户 | 用户 | 一个或多个用户标识符 | -| 审核类型 | 搜索|读 | 按一种或多种审核类型过滤 | -| 开始日期 | 开始日期 | Start date for audits in `yyyy-mm-dd` format | -| 结束日期 | 结束日期 | End date for audits in `yyyy-mm-dd` format | -| 跳过分页 | 假的|真的 | 打开/关闭寻呼。 | -| 寻呼 | 错误的 \| 真正 | 是否启用或禁用分页 | -| 页 | 数 | 页码（默认1） | -| 页面大小 | 数 | 页面大小（默认 50） | +| trackedEntities | Tracked Entity UIDS | One or more tracked entity identifiers (comma separated) | +| user | 用户 | One or more user identifiers | +| auditType | SEARCH | READ | Filter by one or more audit types | +| 开始日期 | Start date | Start date for audits in `yyyy-mm-dd` format | +| 结束日期 | End date | End date for audits in `yyyy-mm-dd` format | +| skipPaging | false | true | Turn paging on / off. | +| paging | false \| 真正 | Whether to enable or disable paging | +| page | 数 | Page number (default 1) | +| pageSize | 数 | Page size (default 50) | Example: Get audits of audit type `READ` with `startDate` 2018-03-01 and `endDate` 2018-04-24 with a page size of 5: @@ -166,25 +169,25 @@ Example: Get audits for tracked entity `wNiQ2coVZ39`: ### 数据审批审核 { #data-approval-audits } -数据审批审核的端点位于： +The endpoint for data approval audits is located at: ``` /api/audits/dataApproval ``` -表：数据审批查询参数 +Table: Data approval query parameters -| 范围 | 选项 | 描述 | +| Parameter | 选项 | 描述 | |---|---|---| -| 达尔 | 数据审批级别ID | 一个或多个数据批准级别标识符 | -| 工作组 | 数据审批工作流程ID | 一个或多个数据审批工作流标识符 | -| 欧 | 组织单位ID | 一个或多个组织单位标识符 | -| 冠捷 | 属性选项组合 ID | 一个或多个属性选项组合标识符 | -| 开始日期 | 开始日期 | Start date for approvals in `yyyy-mm-dd` format | -| 结束日期 | 结束日期 | End date for approvals in `yyyy-mm-dd` format | -| 跳过分页 | 假的|真的 | 打开/关闭分页 | -| 页 | 数 | 页码（默认1） | -| 页面大小 | 数 | 页面大小（默认 50） | +| dal | Data approval level ID | One or more data approval level identifiers | +| wf | Data approval workflow ID | One or more data approval workflow identifiers | +| 欧 | Organisation unit ID | One or more organisation unit identifiers | +| 冠捷 | Attribute option combo ID | One or more attribute option combination identifiers | +| 开始日期 | Start date | Start date for approvals in `yyyy-mm-dd` format | +| 结束日期 | End date | End date for approvals in `yyyy-mm-dd` format | +| skipPaging | false | true | Turn paging on / off | +| page | 数 | Page number (default 1) | +| pageSize | 数 | Page size (default 50) | Example: Get audits for data approval workflow `i5m0JPw4DQi`: 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..a842390a0 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 @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/data-exchange.md" -revision_date: '2023-09-27' +revision_date: '2024-06-26' tags: - Develop - DHIS核心 主版 @@ -396,6 +396,7 @@ The aggregate data exchange data model / payload is described in the following s | source.requests.filters.items | Array/String | 不 | Item identifiers for the filter. | | source.requests.inputIdScheme | 串 | 不 | Input ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputDataElementIdScheme | 串 | 不 | Output data element ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | +| source.requests.outputDataItemIdScheme | 串 | 不 | Output data item ID scheme applies to data elements, indicators and program indicators, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputOrgUnitIdScheme | 串 | 不 | Output org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.requests.outputIdScheme | 串 | 不 | Output general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target | 目的 | 是的 | Target for aggregate data exchange. | @@ -410,6 +411,9 @@ The aggregate data exchange data model / payload is described in the following s | source.target.request.orgUnitIdScheme | 串 | 不 | Input org unit ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.categoryOptionComboIdScheme | 串 | 不 | Input category option combo ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | | source.target.request.idScheme | 串 | 不 | Input general ID scheme, can be `UID`, `CODE`, `ATTRIBUTE:{ID}`. | +| source.target.request.importStrategy | 串 | 不 | Import strategy, can be `CREATE_AND_UPDATE`, `CREATE`, `UPDATE`, `DELETE`. | +| source.target.request.skipAudit | Boolean | 不 | Skip audit, meaning audit values will not be generated. Improves performance at the cost of ability to audit changes. Requires authority "F_SKIP_DATA_IMPORT_AUDIT". | +| source.target.request.dryRun | Boolean | 不 | Whether to save changes on the server or just return the import summary. | ### Error handling { #error-handling } 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..fa7169809 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 @@ -1,12 +1,12 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" -revision_date: '2024-05-21' +revision_date: '2024-06-03' tags: - Develop - DHIS核心 主版 --- -# 元数据 { #metadata } +# Metadata { #webapi_metadata } ## 标识符方案 { #webapi_identifier_schemes } 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 930b44ec8..2934152ba 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,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/tracker.md" -revision_date: '2024-06-20' +revision_date: '2024-06-26' tags: - Develop - DHIS核心 主版 @@ -162,7 +162,6 @@ point out any exceptional cases between these two. `Relationships` are objects that link together two other tracker objects. The constraints each side of the relationship must conform to are based on the `Relationship Type` of the `Relationship`. - | Property | 描述 | 需要 | Immutable | 类型 | 例 | |---|---|---|---|---|---| | relationship | The identifier of the relationship. Generated if not supplied. | 不 | 是的 | String:Uid | ABCDEF12345 | @@ -2139,6 +2138,67 @@ An example of a json response: The response will be the same as the collection endpoint but referring to a single tracked entity, although it might have multiple rows for each attribute. +#### Tracked entity attribute value change logs { #webapi_tracker_attribute_change_logs } +`GET /api/tracker/trackedEntities/{uid}/changeLogs` + +This endpoint retrieves change logs for the attributes of a specific tracked entity. It returns a list of all tracked entity attributes that have changed over time for that entity. + +|Parameter|类型|Allowed values| +|---|---|---| +|path `/{uid}`|`String`|Tracked entity `UID`.| +|`program`|`String`|Program `UID` (optional).| + +##### Tracked entity attribute value change logs response example { #tracked-entity-attribute-value-change-logs-response-example } + +An example of a json response: + +```json +{ + "pager":{ + "page":1, + "pageSize":10 + }, + "changeLogs":[ + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:51:16.433", + "type":"UPDATE", + "change":{ + "dataValue":{ + "dataElement":"bx6fsa0t90x", + "previousValue":"true", + "currentValue":"false" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:50:32.966", + "type":"CREATE", + "change":{ + "dataValue":{ + "dataElement":"ebaJjqltK5N", + "currentValue":"0" + } + } + } + ] +} +``` + +The change log type can be `CREATE`, `UPDATE`, or `DELETE`. +`CREATE` and `DELETE` will always hold a single value: the former shows the current value, and the latter shows the value that was deleted. UPDATE will hold two values: the previous and the current. + ### Enrollments (`GET /api/tracker/enrollments`) { #enrollments-get-apitrackerenrollments } Two endpoints are dedicated to enrollments: @@ -2585,6 +2645,83 @@ The API supports CSV and JSON response for `GET /api/tracker/trackedEntities` The response will be the same as the collection endpoint but referring to a single event, although it might have multiple rows for each data element value. +#### Event data value change logs { #webapi_event_data_value_change_logs } +`GET /api/tracker/events/{uid}/changeLogs` + +This endpoint retrieves change logs for the data values of a specific event. It returns a list of all event data values that have changed over time for that particular event. + +|Parameter|类型|Allowed values| +|---|---|---| +|path `/{uid}`|`String`|Event `UID`.| + +##### Event data value change logs response example { #event-data-value-change-logs-response-example } + +An example of a json response: + +```json +{ + "pager":{ + "page":1, + "pageSize":10 + }, + "changeLogs":[ + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T15:43:36.342", + "type":"DELETE", + "change":{ + "dataValue":{ + "dataElement":"UXz7xuGCEhU", + "previousValue":"12" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T15:43:27.175", + "type":"CREATE", + "change":{ + "dataValue":{ + "dataElement":"UXz7xuGCEhU", + "currentValue":"12" + } + } + }, + { + "createdBy":{ + "uid":"AIK2aQOJIbj", + "username":"tracker", + "firstName":"Tracker demo", + "surname":"User" + }, + "createdAt":"2024-06-20T14:51:16.433", + "type":"UPDATE", + "change":{ + "dataValue":{ + "dataElement":"bx6fsa0t90x", + "previousValue":"true", + "currentValue":"false" + } + } + } + ] +} +``` + +The change log type can be `CREATE`, `UPDATE`, or `DELETE`. +`CREATE` and `DELETE` will always hold a single value: the former shows the current value, and the latter shows the value that was deleted. UPDATE will hold two values: the previous and the current. + + ### Relationships (`GET /api/tracker/relationships`) { #relationships-get-apitrackerrelationships } Relationships are links between two entities in the Tracker. These entities can be tracked entities, @@ -2868,71 +3005,138 @@ 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. +Working lists allow users to efficiently organize their workflow by saving filters and sorting +preferences for tracked entities, enrollments, and events. Each type of working list—tracked +entities, enrollments, and events—has a dedicated API for management. + +Working lists are [metadata](#webapi_metadata), making them shareable and subject to the same +[sharing](#webapi_sharing) patterns as other metadata. When using the +[`/api/sharing`](#webapi_sharing) endpoint, the type parameter should be set to the name of the +working list API. For example, use trackedEntityInstanceFilter for [tracked entity working +lists](#tracked-entity-instance-filters). + +Since working lists are metadata refer to [metadata](#webapi_metadata) on how to create, update and +delete metadata. The following sections describe the payloads of each of the working lists +endpoints. + +### Tracked entity working lists { #tracked-entity-working-lists } + +Create, update and delete tracked entity working lists using + + /api/trackedEntityInstanceFilters + +#### Payload { #payload } + +Table: Payload + +| Property | 描述 | 例 | +|---|---|---| +|名称|Name of the working list. Required.|| +|描述|A description of the working list.|| +|sortOrder|The sort order of the working list.|| +|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 + +| Property | 描述 | 例 | +|---|---|---| +|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 tracked entities enrollment status. Can be none(any enrollmentstatus) or ACTIVE|COMPLETED|CANCELLED|| +|跟进|When this parameter is true, the working list only returns tracked entities that have an enrollment with `folloWup=true`.|| +|organisationUnit|To specify the uid of the organisation unit|`{"organisationUnit": "a3kGcGDCuk7"}`| +|ouMode|To specify the organisation unit 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"`| +|programStage|To specify a programStage uid to filter on. tracked entities will be filtered based on presence of enrollment in the specified program stage.|`"programStage"="a3kGcGDCuk6"`| +|trackedEntityType|To specify a trackedEntityType filter tracked entities on.|`{"trackedEntityType"="a3kGcGDCuk6"}`| +|trackedEntities|To specify a list of trackedEntityInstances to use when querying tracked entities.|`"trackedEntityInstances"=["a3kGcGDCuk6","b4jGcGDCuk7"]`| +|enrollmentCreatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on enrollment created date.|`"enrollmentCreatedDate": { "period": "LAST_WEEK", "type": "RELATIVE" }`| +|enrollmentIncidentDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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" }`| +|eventStatus|The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED|`"status":"VISITED"`| +|eventDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on event date.|`"eventDate": {"startBuffer": -5,"endBuffer": 5, "type": "RELATIVE" }`| +|lastUpdatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on last updated date.|`"lastUpdatedDate": {"startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" }`| + +Table: Event filters definition + +| Property | 描述 | 例 | +|---|---|---| +|programStage|Which programStage the tracked entity 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|FilterPeriod 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: FilterPeriod definition + +| Property | 描述 | 例 | +|---|---|---| +|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| + +#### Query Request Parameters { #query-request-parameters } + +Table: Tracked entity instance filters query parameters + +| 查询参数 | 描述 | +|---|---| +|program|Program identifier. Restricts filters to the given program.| ### 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*. +Create, update and delete program stage working lists using /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. +|名称|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"}] | +|eventStatus|The event status. Possible values are ACTIVE, COMPLETED, VISITED, SCHEDULE, OVERDUE, SKIPPED and VISITED|`"status":"VISITED"`| +|eventCreatedAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object filtering based on the event creation date.|`{"type":"ABSOLUTE","startDate":"2020-03-01","endDate":"2022-12-30"}`| +|eventOccurredAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object filtering based on the event occurred date.|`{"type":"RELATIVE","period":"TODAY"}`| +|eventScheduledAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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](#webapi_tracker_workinglists_common_objects) object filtering based on the event enrollment date.|`"enrolledAt": {"type":"RELATIVE","period":"THIS_MONTH"}`| +|enrollmentOccurredAt|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) 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", + "description": "Test WL definition", "program": { "id": "uy2gU8kT1jF" }, "programStage": { "id": "oRySG82BKE6" }, - "description": "Test WL definition", "programStageQueryCriteria": { "eventStatus": "VISITED", "eventCreatedAt": { @@ -2982,11 +3186,98 @@ See an example payload below: } ``` -## 潜在重复 { #potential-duplicates } +### Event working lists { #event-working-lists } + +Create, update and delete event working lists using + + /api/eventFilters + +#### Payload { #payload } + +Table: Payload + +| Property | 描述 | 例 | +|---|---|---| +|名称|Name of the working list.|"name":"My working list"| +|描述|A description of the working list.|"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 + +| Property | 描述 | 例 | +|---|---|---| +|跟进|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"]| +|displayColumnOrder |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](#webapi_tracker_workinglists_common_objects) 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](#webapi_tracker_workinglists_common_objects) object date filtering based on event date.|"eventDate": { "startBuffer": -5, "endBuffer": 5, "type": "RELATIVE" }| +|dueDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on due date.|"dueDate": { "period": "LAST_WEEK", "type": "RELATIVE" }| +|lastUpdatedDate|[DateFilterPeriod](#webapi_tracker_workinglists_common_objects) object date filtering based on last updated date.|"lastUpdatedDate": { "startDate": "2014-05-01", "endDate": "2019-03-20", "type": "ABSOLUTE" }| + +See an example payload below: + +```json +{ + "name": "event working list", + "program": "VBqh0ynB2wv", + "eventQueryCriteria": { + "eventDate": { + "period": "LAST_WEEK", + "type": "RELATIVE" + }, + "dataFilters": [ + { + "ge": "35", + "le": "70", + "dataItem": "qrur9Dvnyt5" + } + ], + "assignedUserMode": "PROVIDED", + "assignedUsers": [ + "CotVI2NX0rI", + "xE7jOejl9FI" + ], + "status": "ACTIVE", + "order": "occurredAt:desc", + "displayColumnOrder": [ + "occurredAt", + "status", + "assignedUser", + "qrur9Dvnyt5", + "oZg33kd9taw" + ] + } +} +``` + +### Common Objects { #webapi_tracker_workinglists_common_objects } -Potential duplicates are records identified by the data deduplication feature as possibly being duplicates. Due to the nature of this feature, the API endpoint has certain restrictions. +Table: DateFilterPeriod object definition -A potential duplicate represents a pair of records suspected to be duplicates. +| Property | 描述 | 例 | +|---|---|---| +|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`| + + +## 潜在重复 { #potential-duplicates } + +Potential duplicates are records identified by the data deduplication feature as possibly being +duplicates. Due to the nature of this feature, the API endpoint has certain restrictions. A +potential duplicate represents a pair of records suspected to be duplicates. To retrieve a list of potential duplicates, use the following endpoint: @@ -3020,7 +3311,8 @@ To create a new potential duplicate, use this endpoint: POST / api / potentialDuplicates -The payload you provide must include the UIDs of the original and duplicate tracked entities. New potential duplicates are open by default. +The payload you provide must include the UIDs of the original and duplicate tracked entities. New +potential duplicates are open by default. ```json { @@ -3032,7 +3324,7 @@ The payload you provide must include the UIDs of the original and duplicate trac | Status code | 描述 |---|---| | 400 | Input original or duplicate is null or has invalid uid -| 403 | User do not have access to read origianl or duplicate TEs +| 403 | User do not have access to read original or duplicate TEs | 404 | TE not found | 409 | Pair of original and duplicate TEs already existing @@ -3050,9 +3342,15 @@ To update the status of a potential duplicate, use the following endpoint: | 400 | You can't update a potential duplicate that is already in a MERGED status ### Merging Tracked Entities { #merging-tracked-entities } -Tracked entities can be merged together if they are deemed viable. To initiate a merge, the first step is to define two tracked entities as a Potential Duplicate. The merge endpoint moves data from the duplicate tracked entity to the original tracked entity and deletes the remaining data of the duplicate. -To merge a Potential Duplicate, i.e. the two tracked entities the Potential Duplicate represents, use the following endpoint: +Tracked entities can be merged together if they are deemed viable. To initiate a merge, the first +step is to define two tracked entities as a Potential Duplicate. The merge endpoint moves data from +the duplicate tracked entity to the original tracked entity and deletes the remaining data of the +duplicate. + +To merge a Potential Duplicate, i.e. the two tracked entities the Potential Duplicate represents, +use the following endpoint: + POST /api/potentialDuplicates//merge | Parameter name | 描述 | 类型 | Allowed values | @@ -3062,28 +3360,47 @@ To merge a Potential Duplicate, i.e. the two tracked entities the Potential Dupl The endpoint accepts a single parameter, `mergeStrategy`, which determines the strategy used when merging. For the `AUTO` strategy, the server will attempt to merge the two tracked entities automatically without user input. This strategy only allows merging tracked entities without conflicting data (see examples below). The `MANUAL` strategy 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 evaluates the mergability of the two tracked entities and merges them if they are deemed mergable. The mergability is based on whether the two tracked entities have any conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible conflicts include: + +The automatic merge evaluates the mergability of the two tracked entities and merges them if they +are deemed mergeable. The mergability is based on whether the two tracked entities have any +conflicts. Conflicts refer to data that cannot be merged automatically. Examples of possible +conflicts include: + - The same attribute has different values in each tracked entity. - Both tracked entities are enrolled in the same program. - Tracked entities have different types. If any conflict is encountered, an error message 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 to the original. This includes attribute values, enrollments (including events), and relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is marked as `MERGED`. - -When requesting an automatic merge, a payload is not required and will be ignored. +When no conflicts are found, all data in the duplicate that is not already in the original will be +moved to the original. This includes attribute values, enrollments (including events), and +relationships. After the merge completes, the duplicate is deleted and the Potential Duplicate is +marked as `MERGED`. When requesting an automatic merge, a payload is not required and will be +ignored. #### Merge Strategy MANUAL { #merge-strategy-manual } -The manual merge is suitable when there are resolvable conflicts or when not all the data needs to be moved during the 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 involves the user explicitly requesting to move data, there are some additional checks: -- 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 entities (IE. between original and other, and duplicate and other; This would result in a duplicate relationship) + +The manual merge is suitable when there are resolvable conflicts or when not all the data needs to +be moved during the 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 involves the user explicitly requesting to move data, there are some +additional checks: + +- 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 entities (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 entities 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 was just created, but not enrolled for example. +When a manual merge is requested without a payload, we are telling the API to merge the two tracked +entities 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 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: -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"], @@ -3092,12 +3409,20 @@ Otherwise, if a manual merge is requested with a payload, the payload refers to } ``` -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. +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 entities 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 entities 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. +Currently it is not possible to merge tracked entities 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 +entities 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. 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 164b36b4d..067d694f9 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: -- Manage - DHIS核心 主版 +- Manage --- # 审核 { #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 c846b969b..2733718ff 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: -- Manage - DHIS核心 主版 +- Manage --- # 使用 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 cd5b2270b..9297c6c54 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-06-18' tags: -- Manage - DHIS核心 主版 +- Manage --- # 安装 { #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 fff94635f..a1c3fccf8 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: -- Manage - DHIS核心 主版 +- Manage --- # 监控 { #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 504c71fb8..0ba0a2fd4 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: -- Manage - DHIS核心 主版 +- Manage --- # 正在升级 { #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 af1611689..6b8ad9863 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: -- Manage - DHIS核心 主版 +- Manage --- # 使用网关进行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__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 71191b88e..39d6f5585 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/zh/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/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 070bb734f..d075af220 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/zh/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: '2024-06-07' tags: -- 使用 - DHIS core version 2.38 +- 使用 --- # DHIS2常见问题 { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md index e44a40090..530687746 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/zh/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词汇表 { #dhis2_glossary } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md index a6f28728b..f03af151b 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/zh/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教程 { #dhis2_tutorials } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 8b8bf2dcf..367de7f34 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md index 6e6286293..c8eeff4a6 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 管理仪表板 { #dashboard } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md index 800efdf8a..5521ed0e4 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用数据可视化器应用 { #data_visualizer } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md index ddc40ecf8..458cd7953 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用事件报告应用 { #event_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md index df3db5755..95c36fafd 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用事件可视化器应用 { #event_visualizer_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md index 583cf46da..2010cc649 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__line-listing-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- 使用 - DHIS core version 2.38 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md index da9d79144..f04610e23 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/zh/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_maps } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md index 2573ab6a2..c5b477443 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 报告应用程序中的报告功能 { #using_the_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md index 5e3ed478b..bab1ee20c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/zh/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/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md index af2c8786e..aa715d052 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/zh/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/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md index 2a271c339..ef44c4b00 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用数据输入应用 { #data_entry_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md index 7cff02756..48151aa9a 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index a93f4a673..d6a67dd8e 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 关于对象共享 { #sharing } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md index 01ba60cf1..e061837d2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 配置地图应用 { #gis_creating } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md index 9536c825b..f8b8b0e73 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 配置元数据 { #maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md index 263385b76..a12ae7054 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/zh/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_maintenance_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md index 6deb65484..4e629dbfc 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 配置报告功能 { #setting_up_reporting } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md index 1f6fe663f..652c829f9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 系统设置 { #settings } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md index b7b8a53c0..f45d10d5d 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index 392a248df..9e1296b12 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/zh/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_user_role_group } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md index e5aa701c8..00070069b 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md index 118680c0d..ba19ad482 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 配置元数据同步 { #metadata_sync } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md index f10a9414b..6aa20cb6f 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/zh/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/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md index d7ec38d1d..a583c214a 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/zh/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_admin } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md index 1a950a88d..5df85ec71 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/zh/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_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md index ed6da8913..9613739fc 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/zh/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/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md index 2af5344f1..2b24420bc 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md index 41c10296d..d14162341 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index fca957707..0d2d4d837 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 可视化使用情况统计 { #using_usage_analytics } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index a7548cc39..865da5df4 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/zh/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-06-24' tags: -- 使用 - DHIS core version 2.38 +- 使用 --- # 使用捕获应用 { #capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 87c042714..d4c1fcefa 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用事件捕获应用 { #event_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 7f81e7f23..dded2b922 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用Tracker Capture应用 { #tracker_capture_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 456f8b531..dc9bf12c4 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 关于数据维度 { #data_dimensions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 6706c2804..f877c14b4 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index 4f8c8a156..c1c12f014 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 32dfcb29d..3d13a85a0 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 讯息传递 { #messages } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index 504f81394..6bdb81e3a 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/zh/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/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index 70103013d..a22b44370 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-238__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 设置用户帐户首选项 { #user_account_preferences } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index c015a1987..2e5fe2fd6 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/zh/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/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index bba328039..58b6f83d2 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/zh/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常见问题 { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md index 679115ef9..aa9669198 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/zh/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词汇表 { #dhis2_glossary } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md index dd993f813..c9843fd33 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/zh/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教程 { #dhis2_tutorials } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 91ff97b1b..99edf1f14 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/zh/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 } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md index 29d4de3a5..a5e8d84ba 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 管理仪表板 { #dashboard } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md index 010026bed..be5b5faa6 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用数据可视化器应用 { #data_visualizer } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md index d977d525f..52ad36cf5 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用事件报告应用 { #event_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md index 8441c2aa7..91a8ef8a9 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 使用事件可视化器应用 { #event_visualizer_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md index d03e9c741..e12c4b5ac 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__line-listing-md @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- 使用 - DHIS core version 2.39 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md index 07bc02391..3599d303c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/zh/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_maps } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md index 0325ef12c..2701e5f88 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/zh/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 +- 使用 --- # 报告应用程序中的报告功能 { #using_the_reports_app } diff --git a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md index b894cb817..0c8f70620 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/zh/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/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md index b2688629f..e89cbd97c 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-239__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/zh/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/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 a24bbd7a7..d1730cd83 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-06-24' 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..d3fbc6504 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- 使用 - DHIS core version 2.40 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 152708df4..d779b88b9 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-06-24' 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..df34bb0ba 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- 使用 - DHIS core version 2.41 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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 c596f236b..290e52008 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-06-24' 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-frequently-asked-questions-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index a86a77b37..d3a335a18 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/zh/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: '2024-06-07' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # DHIS2常见问题 { #dhis2-frequently-asked-questions } 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..b37561fb1 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 @@ -1,9 +1,9 @@ --- edit_url: "https://github.com/dhis2/line-listing-app/blob/master/docs/line_list.md" -revision_date: '2024-01-30' +revision_date: '2024-06-26' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # Using the Line Listing app { #using-the-line-listing-app } @@ -235,3 +235,15 @@ To allow more space for the line list itself, there are various ways to hide pan ![](resources/images/view-options.png) +To provide more space for the content in the "Accessory Side Panel" it can be resized using the mouse as illustrated below: + +![](resources/images/resizable_accessory_sidebar.png) + +Resizing can also be done using the left/right arrow key on the keyboard. These keyboard shortcuts become active after giving focus to the resize-handle (by repeatedly hitting the tab key): + +![](resources/images/resizable_accessory_sidebar_keyboard.png) + +The "Accessory Side Panel" can be reset to its default width, by using the "View" menu or double clicking the resize-handle. + +![](resources/images/resizable_accessory_sidebar_reset.png) + 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-entry-md b/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md index 868a4b091..41039e6d7 100644 --- a/projects/docs-full-site/zh/USE__USER-GUIDES__DHIS-CORE-VERSION-MASTER__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/zh/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: '2024-06-18' tags: -- 使用 - DHIS核心 主版 +- 使用 --- # 使用数据输入应用 { #data_entry_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 5621de871..b984bd168 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-06-18' 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 d922061f0..d2dabdef0 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-06-24' 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 }