← Back to team overview

dhis2-users team mailing list archive

Re: 1.4 and 2 migration/co-existence issues

 

Hi,

Good points Ime, I'm copying the list (Ime's reply is below my message). All
of you please notice that the default reply-to on these emails is just to
the sender and not the list, so please remember to click on reply-all if you
want to share your ideas with the whole list, which you all should of
course.

I'd like to add to Ime's good point that if you opt for co-existence of 1.4
and 2 at the same level (e.g. district), which is definitely doable I would
just mention that DHIS 2 also runs fine offline and is being just in this
way in many places. A very common scenario (and not too expensive either) is
to build up small local networks (not on Internet) at e.g a district office
with a DHIS 2 server (normal machine, and no real need for server hardware)
and a group of desktops machines all connnected on a local wireless (or
wired) network. This way many users and local departments can share reports,
charts, maps etc. and do data entry from their local desktop or laptop
directly onto a common district repository (on the district server).

However, in a transition process from 1.4 and 2 I could see such a
co-existence strategy useful if there is lack of capacity to support many
offline DHIS 2 installations, e.g. if most of the support team is 1.4
trained and new to v2. Then a more gradual transition, e.g. starting with a
few pilot districts could work fine, in order to build up support capacity
around DHIS 2.

Having a national or sub-national DHIS 2 server for web reports and other
analysis tools while 1.4 is used to enter data locally is another way (can
be done in combination with the above) to gradually move from 1.4 to 2 that
also helps to build up valuable support capacity among the software
maintenance team, and is also a way to gradually introduce the end users to
a web environment. There are many possibilities of designing hybrid 1.4 and
2 solutions and each country needs to find out what makes sense to them in
terms of human capacity and network infrastructure.

Other inputs to this would be very valuable, please share your ideas on this
new users list.

Ola
---------

2009/11/29 Ime Asangansi <asangansi@xxxxxxxxx>

> Nice :)
>
> A third scenario is similar to scenario 2 and bothers on coexistence at
> same levels. DHIS2 for data entry with internet access/WLANs and DHIS1.4 in
> areas with less capacity.
>
> The additional requirement from such is two-way import-export between 1.4
> and 2.0
>
> Cheers,
> [I]me
>
> --- On Sun, 11/29/09, Ola Hodne Titlestad <olatitle@xxxxxxxxx> wrote:
>
> > From: Ola Hodne Titlestad <olatitle@xxxxxxxxx>
> > Subject: [Dhis2-users] 1.4 and 2 migration/co-existence issues
> > To: dhis2-users@xxxxxxxxxxxxxxxxxxx
> > Date: Sunday, November 29, 2009, 6:27 PM
> > Hi Brian,
> >
> > Jason Pickering in Zambia has a lot of experience with 1.4
> > to 2 migration or co-existence and can probably provide some
> > help here on the list.
> >
> > Here is a quick overview of 1.4 and 2 issues.
> >
> > There are two scenarios as far as I can see.
> >
> >
> > Scenario 1)  One-off migration from 1.4 to 2
> >
> > Some things you need to consider (there are probably
> > more...)
> > * You can use the 1.4 database (data file) import into an
> > empty v. 2 database
> > * Consider redesigning some of the most tabular forms to
> > make use of multidimensional data elements (categories,
> > category combinations)
> >
> > * Aggregation rules are different from 1.4, so make sure
> > you understand these.
> > * You can create report tables that will look exactly like
> > your PivotViews queries in the 1.4 datamart for simple use
> > of Excel pivot tables, or create such views directly in the
> > 2 database. Pivot tables will then look exactly the same for
> > both versions (Excel is Excel).
> >
> > * You can add more dimensions to your data analysis by
> > using data element group sets and categories and retrieve
> > these through the use of report tables.
> >
> > Scenario 2)  Co-existence of 1.4 and 2, e.g. 1.4 for at
> > district level and 2 as a central server based national
> > repository for web reports, dashboards, GIS etc.
> >
> >
> > Some things you need to consider (there are probably
> > more...)
> > * Use database import from 1.4 as a first step
> > * For continuous monthly data updates use the 1.4 XML
> > import to 2.
> > * Since 1.4 dictates all meta data definitions
> > multidimensional data elements is not an option here. For
> > multidimensional data analysis you can specify date element
> > group sets (dimensions) and groups (dimension options) and
> > use these in report tables.
> >
> >
> > Some common issues for both scenarios:
> > * Be careful with aggregation of population data if you
> > have data for
> > the same data element (e.g. Total Population) on two
> > levels. Need to
> > specify aggregation levels for these data elements. You
> > will have to
> > redo this every time you overwrite your metadata from 1.4
> > (should not
> > be necessary to often though) as 1.4 has a different way of
> > dealing
> > with this.
> > * Double check aggregation operators for your data elements
> > as aggregation rules are more strict in 2 than in 1.4. Data
> > elements that should not be summarised over time when
> > aggregated must have the type average, e.g. population data,
> > equipment status, beds ++. If you set the type of e.g.
> > "Total Population" (which has annual values) to
> > SUM then a monthly indicator value will estimate a monthly
> > value from that annual value, divide by 12. If set to
> > AVERAGE it will use the annual value without any
> > modification. Such estimate or break up of annual or
> > quarterly values does not exist in 1.4 so typically all data
> > elements have type SUM although many of the strictly
> > speaking should have been set to AVERAGE. So just make sure
> > all AVERAGE data elements actually have aggregation operator
> > AVERAGE and not SUM. Also check aggregation operators for
> > your numerators and denominators for your indicators. These
> > are derived directly from the data elements, but this can
> > get messed up when doing 1.4 import because of the above
> > mentioned differences with SUM/AVG.
> >
> >
> >
> > This page provides some sort of overview of all the docs on
> > DHIS 2, which is being centralised and better organised at
> > the moment:
> > http://208.76.222.114/confluence/display/DOC/Home
> >
> >
> > Ola Hodne Titlestad |Technical Officer|
> > Health Metrics Network (HMN) | World Health Organization
> > Avenue Appia 20 |1211 Geneva 27, Switzerland | Email: titlestado@xxxxxxx
> |Tel:
> > +41 788216897
> >
> > Website: www.healthmetricsnetwork.org
> >
> > Better Information. Better Decisions. Better Health.
> >
> >
> >
> > 2009/11/28 Knut Staring <knutst@xxxxxxxxx>
> >
> > Hi, under import-export there is an option for import
> > from 1. 4
> > On Nov 28,
> > 2009 11:42 AM, "Brian Agbirogu" <pphmbagb@xxxxxxx>
> > wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi knut
> > ,
> >
> >
> >
> > Thanks for
> > your help so far. I seem to be doing quite fine with
> > the installation. Could you please enlighten me about
> > migration from dhis1.4 to
> > 2.0..What document do I need to go through?
> > Thanks
> >
> >
> >
> > Brian
> >
> >
> >
> >
> >
> > From: dhis2-users-bounces+pphmbagb=aol.com@xxxxxxxxxxxxxxxxxxx
> > [mailto:dhis2-users-bounces+pphmbagb <dhis2-users-bounces%2Bpphmbagb>=
> aol.com@xxxxxxxxxxxxxxxxxxx]
> > On Behalf
> > Of Knut Staring
> >
> > Sent: Monday, November 23, 2009 4:54 PM
> >
> > To: Lars Helge Øverland
> >
> > Cc: dhis2-users@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Dhis2-users] pphmbagb wants to
> > join
> >
> >
> >
> >
> >
> >
> >
> > Hi Brian,
> >
> >
> >
> >
> >
> > As Lars recommends, I think DHIS Live could work well for
> > you on Ubuntu. It is possible to chec...
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> >
> > Mailing list: https://launchpad.net/~dhis2-users<https://launchpad.net/%7Edhis2-users>
> >
> > Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> >
> > Unsubscribe : https://launchpad.net/~dhis2-users<https://launchpad.net/%7Edhis2-users>
> >
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
> >
> >
> >
> > -----Inline Attachment Follows-----
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~dhis2-users<https://launchpad.net/%7Edhis2-users>
> > Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~dhis2-users<https://launchpad.net/%7Edhis2-users>
> > More help   : https://help.launchpad.net/ListHelp
> >
>

Follow ups

References