Writing interpretations

Writing interpretations We will start by writing an interpretation for the chart with identifier EbRN2VIbPdV. To write chart interpretations we will interact with the resource. The interpretation will be the request body. Based on this we can put together the following request using cURL: - curl -d "This chart shows a significant ANC 1-3 dropout" "https://apps.dhis2.org/demo/api/interpretations/chart/EbRN2VIbPdV" -H "Content-Type:text/plain" -u admin:district -v + curl -d "This chart shows a significant ANC 1-3 dropout" "https://apps.dhis2.org/demo/api/interpretations/chart/EbRN2VIbPdV" \ +-H "Content-Type:text/plain" -u admin:district -v Second we will write a comment on the interpretation we just wrote. By looking at the interpretation response you will see that a Location header is returned. This header tells us the URL of the newly created interpretation and from that we can read its identifier. This identifier is randomly generated so you will have to replace the one in the command below with your own. To write a comment we can interact with the like this: - curl -d "An intervention is needed" "https://apps.dhis2.org/demo/api/interpretations/j8sjHLkK8uY/comment" -H "Content-Type:text/plain" -u admin:district -v + curl -d "An intervention is needed" "https://apps.dhis2.org/demo/api/interpretations/j8sjHLkK8uY/comment" +-H "Content-Type:text/plain" -u admin:district -v You can also write interpretations for report tables in a similar way by interacting with the . For report tables you can also provide an optional ou query parameter to supply an organisation unit identifier in the case where the report table has an organisation unit report parameter: - curl -d "This table reveals poor data quality" "https://apps.dhis2.org/demo/api/interpretations/reportTable/xIWpSo5jjT1?ou=O6uvpzGd5pu" -H "Content-Type:text/plain" -u admin:district -v + curl -d "This table reveals poor data quality" "https://apps.dhis2.org/demo/api/interpretations/reportTable/xIWpSo5jjT1?ou=O6uvpzGd5pu" +-H "Content-Type:text/plain" -u admin:district -v

Creating, updating and removing interpretation comments @@ -3891,7 +3894,7 @@ api/analytics/events/query/eBAyeGv0exc.xls?startDate=2014-01-01&endDate=2014-10-31&dimension=ou:O6uvpzGd5pu&dimension=oZg33kd9taw&dimension=qrur9Dvnyt5 You can set the hierarchyMeta query parameter to true in order to include names of all ancestor organisation units in the meta-section of the response: - api/analytics/events/query/eBAyeGv0exc?startDate=2014-01-01&endDate=2014-10-31&dimension=ou:YuQRtpLP10I&dimension=oZg33kd9taw&dimension=qrur9Dvnyt5:EQ:50&hierarchyMeta=true + api/analytics/events/query/eBAyeGv0exc?startDate=2014-01-01&endDate=2014-10-31&dimension=ou:YuQRtpLP10I&dimension=qrur9Dvnyt5:EQ:50&hierarchyMeta=true The default response JSON format will look similar to this: { "headers": [ === modified file 'src/docbkx/en/resources/css/docbook_bsd.css' --- src/docbkx/en/resources/css/docbook_bsd.css 2014-07-15 20:13:22 +0000 +++ src/docbkx/en/resources/css/docbook_bsd.css 2014-07-15 20:49:16 +0000 @@ -176,6 +176,7 @@ border: 1px solid #DDD; border-radius: 3px; margin: 2.5ex 0; + line-height: 1.5em; } .CODE {