dhis2-devs team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

On 22 April 2010 18:12, Murodullo Latifov <murodlatifov@xxxxxxxxx> wrote:
> Hi,
>
> Good point. I was talking long before on using ETL as generic and flexible
> way to be used for import/export compared to DXP or similar initiatives
> going on. There is no one size to fit all, at least for me. Bob did you find
> any solution so far, as I know you are working on import/export module?
>

No there is no one size fits all.  I agree there will be different
approaches depending on the size of the data to be imported, the
nature of the data source and the nature of the job (one-off vs
routine data interchange).  For routine interchange then I think we
will have a reasonable solution with the dxf-centric approach.  For
bootstrapping of systems and migration from legacy systems my sense is
that it will almost always be a difficult operation where the more
skills, tools and experience the implementor has at hand the better
off he will be - kettle, sql, xslt, awk .. they will all have their
place.

What is dxp?

> regards,
> murod
>
> ________________________________
> From: Ola Hodne Titlestad <olatitle@xxxxxxxxx>
> To: DHIS 2 developers <dhis2-devs@xxxxxxxxxxxxxxxxxxx>
> Sent: Thu, April 22, 2010 3:42:09 PM
> Subject: [Dhis2-devs] Discussion from OpenMRS list related to data loading,
> legacy systems, ETL
>
> This might be useful input to our ongoing data loading work:
>
> http://openmrs-mailing-list-archives.1560443.n2.nabble.com/Re-Details-on-Data-Migration-ETL-Module-tt4867404.html#a4867404
>
>
>
> _______________________________________________
> 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
>
>