It would be preferably to not have to go via BIRT. What is needed is an easy GUI for defining what data you want to export to StatPlanet, and then the CSV would be downloaded - though even better, StatPlanet could be included in the DHIS2 distribution and pop up as an extra window in the browser, populated from the generated CSV file.
The BIRT/Jasper job would be a one off thing where you define the full format, fill in static values, and define where to put values from the dynamic report table.
Then what you would need to do as a user would be to use the report table edit window to select indicators, periods and orgunits and then generate it, followed by an export of the report to csv.
1 report and 1 report table would be needed, as they can be reused. The user can edit the selection of indicators, periods, and orgunits.
It would be preferably to not have to go via BIRT. What is needed is an easy GUI for defining what data you want to export to StatPlanet, and then the CSV would be downloaded - though even better, StatPlanet could be included in the DHIS2 distribution and pop up as an extra window in the browser, populated from the generated CSV file.
The BIRT/Jasper job would be a one off thing where you define the full format, fill in static values, and define where to put values from the dynamic report table.
Then what you would need to do as a user would be to use the report table edit window to select indicators, periods and orgunits and then generate it, followed by an export of the report to csv.
1 report and 1 report table would be needed, as they can be reused. The user can edit the selection of indicators, periods, and orgunits.
It would be preferably to not have to go via BIRT. What is needed is an easy GUI for defining what data you want to export to StatPlanet, and then the CSV would be downloaded - though even better, StatPlanet could be included in the DHIS2 distribution and pop up as an extra window in the browser, populated from the generated CSV file.
Fine, I guess we are thinking that everyone will have the report engine. However, the next question is what happens to the generated file. The way I see it, the most user friendly use case would be for the user to not see the CSV file at all, but be presented directly with the data in the StatPlanet GUI.
···
On Thu, Jan 14, 2010 at 3:32 PM, Ola Hodne Titlestad olatitle@gmail.com wrote:
The BIRT/Jasper job would be a one off thing where you define the full format, fill in static values, and define where to put values from the dynamic report table.
Then what you would need to do as a user would be to use the report table edit window to select indicators, periods and orgunits and then generate it, followed by an export of the report to csv.
1 report and 1 report table would be needed, as they can be reused. The user can edit the selection of indicators, periods, and orgunits.
It would be preferably to not have to go via BIRT. What is needed is an easy GUI for defining what data you want to export to StatPlanet, and then the CSV would be downloaded - though even better, StatPlanet could be included in the DHIS2 distribution and pop up as an extra window in the browser, populated from the generated CSV file.
Sounds like an integration job here. Is this really a requirement?
···
On Thu, Jan 14, 2010 at 4:37 PM, Knut Staring <knutst@gmail.com> wrote:
Fine, I guess we are thinking that everyone will have the report engine.
However, the next question is what happens to the generated file. The way I
see it, the most user friendly use case would be for the user to not see the
CSV file at all, but be presented directly with the data in the StatPlanet
GUI.
On Thu, Jan 14, 2010 at 3:32 PM, Ola Hodne Titlestad <olatitle@gmail.com> > wrote:
The BIRT/Jasper job would be a one off thing where you define the full
format, fill in static values, and define where to put values from the
dynamic report table.
Then what you would need to do as a user would be to use the report table
edit window to select indicators, periods and orgunits and then generate it,
followed by an export of the report to csv.
1 report and 1 report table would be needed, as they can be reused. The
user can edit the selection of indicators, periods, and orgunits.
Sounds doable and not to complicated.
Ola
---------
2010/1/14 Knut Staring <knutst@gmail.com>
Moving discussion to the list.
It would be preferably to not have to go via BIRT. What is needed is an
easy GUI for defining what data you want to export to StatPlanet, and then
the CSV would be downloaded - though even better, StatPlanet could be
included in the DHIS2 distribution and pop up as an extra window in the
browser, populated from the generated CSV file.
Knut
On Thu, Jan 14, 2010 at 3:21 PM, Jason Pickering >>> <jason.p.pickering@gmail.com> wrote:
Looks pretty close indeed and a good start for sure. I was thinking
that BIRT might be better to take get all of those other fields and
text in there. not sure if this is needed or not however.
On Thu, Jan 14, 2010 at 4:13 PM, Ola Hodne Titlestad >>>> <olatitle@gmail.com> wrote:
> Hi,
>
> Attached a report table (filtered using display properties and then
> exported
> to csv) that could be a starting point. You probably need to add a few
> columns manually to match the StatPlanet format, but the core data is
> there.
>
> You can see the report table definition here:
>
> DHIS2 App Hub
>
> Ola
>
> 2010/1/14 Ola Hodne Titlestad <olatitle@gmail.com>
>>
>> Report table with crosstab on orgunit should do most of this.
>>
>> Ola Hodne Titlestad |Technical Officer|
>> Health Metrics Network (HMN) | World Health Organization
>> Avenue Appia 20 |1211 Geneva 27, Switzerland | Email:
>> titlestado@who.int|Tel: +41 788216897
>> Website: www.healthmetricsnetwork.org
>>
>> Better Information. Better Decisions. Better Health.
>>
>>
>> 2010/1/14 Knut Staring <knutst@gmail.com>
>>>
>>> Hi guys,
>>> Would love some ideas on whether and how we could generate this kind
>>> of
>>> file from DHIS2: Report tables? DXF export + XSLT?
>>> What should be the approach?
>>> Knut
>
>
Sounds like an integration job here. Is this really a requirement?
Perhaps not. And it can certainly wait until later - would be a great addition to DHIS2 if we could just export a StatPlanet “datamart” and explain what to do with it. As a first test, I will try to transform the table that Ola sent manually, to get more of a feel for what’s required.