dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

On 12 November 2010 05:15, jason.p.pickering@xxxxxxxxx <
jason.p.pickering@xxxxxxxxx> wrote:

> It certainly is time to consider some of the basics of what is needed
> urgently. I started this discussion really because I need to regularly
> trigger the refresh of the datamart and am too lazy to login and do this,
> and figure a cron job with a script would be more suited to such a task. Ola
> indicated that scheduled data mart refreshes had been scheduled for the next
> release. I started playing with curl to refresh the data mart and it or
> course is trivial to do this. What is not so simple is how I can alter
> parameters, namely the time periods of the data mart. For instance at the
> end of October 2010 I would like to add this period automatically to the
> available periods of the datamart  and some report tables .


Jason,

Have a look at the various relative periods that are available in the
datamart export definitions. When doing routinely and automated exports we
will use these relative periods to avoid having to make any changes to the
export specifications. It works the same way for manual exports, no need to
go an modify periods any more if you are using the relative periods.

Ola
--------


> I suppose I could do this with a script that inserts the appropriate period
> into the datamartexportperiods table but it seems to start to get scary
> already. Would be good though to map out a few basic functions that are
> needed but it does seem already to be challenging to replicate all the
> functions of the GUI through simple URLs.
>
> Sent from my HTC
>
> ----- Reply message -----
> From: "Ime Asangansi" <asangansi@xxxxxxxxx>
> Date: Fri, Nov 12, 2010 2:39 am
> Subject: [Dhis2-devs] [Dhis2-users]  Automating DHIS2
> To: "Jo Størset" <storset@xxxxxxxxx>, "Lars Helge Øverland" <
> larshelge@xxxxxxxxx>
>
> Cc: <dhis2-users@xxxxxxxxxxxxxxxxxxx>, "Ola Hodne Titlestad" <
> olati@xxxxxxxxxx>, "dhis2-devs" <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>
>
> Hi everyone in the discussion,
>
> Thanks for this.
> Yes, interesting to begin to look at the Data as a Service (DAAS)
> capabilities of the DHIS. Would be really useful to be able to have
> different clients handling data off DHIS, esp with this current 'enterprise
> architecture' craze.
>
> But Lars, how does your expoze webservice fit into this?
>
> Ime
>
>
> --- On Mon, 11/8/10, Lars Helge Øverland <larshelge@xxxxxxxxx> wrote:
>
> From: Lars Helge Øverland <larshelge@xxxxxxxxx>
> Subject: Re: [Dhis2-devs] [Dhis2-users]  Automating DHIS2
> To: "Jo Størset" <storset@xxxxxxxxx>
> Cc: dhis2-users@xxxxxxxxxxxxxxxxxxx, "Ola Hodne Titlestad" <
> olati@xxxxxxxxxx>, "dhis2-devs" <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
> Date: Monday, November 8, 2010, 7:13 PM
>
>
>
>
>
> Required note: As long as we don't call it REST :) REST imples a
> hypermedia-driven application, so let's stick to calling it what it would
> probably be: a simple web api.
>
>  Hey be a bit more visionary:) I think this is a great thought. We are
> getting more and more requests from people who want to use their own
> presentation layer (Ifakara folks in Tanzania will "make a web-based query
> tool on top of dhis2", Uganda folks are integrating dhis2 with a CMS etc).
> I'm envisioning methods for:
>
> - getting all data elements/indicators with (a bit extended) DXF and HTML
> format responses with embedded links to URLs pointing to a method giving you
> the full details for each as HTML or PDF.
> - getting all indicators with DXF/HTML responses with links to URLs
> pointing to a PNG chart giving the aggregated vales for the 12 last months.-
> getting all report tables as DXF/HTML with links to URLs pointing to
> SDMX-HD/HTML/PDF/Excel representations of the table.
> - getting all orgunits for a given parent as DXF/HTML with links to URLs
> pointing to GIS PNG images, and so on...
> There you have your hypermedia-driven application that moves from one state
> to the next by examining and choosing from among the alternative state
> transitions in the current set of representations.
>
> This kind of stuff will give potential users an elegant way of integrating
> dhis2 data into whatever tool they prefer and avoid hacking into the
> database or fumbling with the source code. If don't want your users to
> leave, make it easy for them to do so:)
>
>
> Lars
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>
>