dhis2-devs team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

On 26 April 2012 12:51, Roshan Hewapathirana
<roshanhewapathirana@xxxxxxxxx> wrote:
> Hi Bob,
> Yes, this I guess, easier in case of working with health staff.
> For eg. a scenario where all the basic data elements with categories and
> indicators with categories are created in a spreadsheet and imported to
> DHIS2 to create a essential data/indicator set and a data/indicator
> dictionary. Flexibility should come on top of the essential set.
>
> I was studying different indicator frameworks and indicator dictionaries and
> try to draw some use cases on this. Initially I was thinking of a XML but as
> you suggested, spreadsheet is more comfortable to health domain.

I'm thinking spreadsheet as an authoring tool rather than necessarily
as a format.  It is the "authoring" of large numbers of repetitive
dataelements which is problematic and which might be reasonably solved
with a well designed spreadsheet template.  Spreadsheet data is easily
exported as XML which in turn is easily importable to dhis.

>
> Other thing I noticed is, currently we create dataelements and then
> indicators (and THEN try to rationalize and to remove unused dataelements).
> Ideally it should be the other way, to decide indicators first and then to
> formulate dataelements (this of course better suite to new health
> programmes, rather than old programmes, where there is a list of
> dataelements and indicators used for many years). However, a spreadsheet
> seems to overcome what 'chicken or the egg' problem.
>
> What it your suggestion to handle 'calculated dataelements' with the
> speadsheet approach?

Calculated dataelements is another difficult discussion.  For the
moment they must be handled in the same way as indicators.  Though if
you were designing the spreadsheet you might consider creating
separate worksheets for dataelements, calculated dataelements and
indicators.  Even though the latter two would end up being implemented
similarly in DHIS2.

> Roshan
>
>
>
> On 26 April 2012 13:17, Bob Jolliffe <bobjolliffe@xxxxxxxxx> wrote:
>>
>> I suspect the route of just having a spreadsheet template for defining
>> these things and just importing off that might be easiest.
>>
>> On 26 April 2012 11:38, Johan Sæbø <johansa@xxxxxxxxxx> wrote:
>> > On 26.04.2012 12:21, Ola Hodne Titlestad wrote:
>> >>
>> >> I have mentioned this to the developers from time to time and not given
>> >> up yet...
>> >>
>> >> Both object "cloning" and batch edits are one my wish list for a more
>> >> admin-friendly DHIS 2.....
>> >
>> >
>> > Yes, that would be great! I'm just now defining DEs from a very regular
>> > pattern:
>> >
>> > "disease name" lab-confirmed, catcombo age+gender
>> > "disease name" suspected, default catcombo
>> > "disease name" epi-linked, default catcombo
>> >
>> > etc.., with 40-50 diseases
>> >
>> > Would be great to just clone earlier ones, and change the disease names.
>> > More complex though, but with even greater savings, would be some kind
>> > of
>> > pattern definition (batch edits is perhaps the same).
>> >
>> > I'm crossing my fingers for this one!
>> > Johan
>> >
>> >
>> >>
>> >>
>> >> ----------------------------------
>> >> Ola Hodne Titlestad (Mr)
>> >> HISP
>> >> Department of Informatics
>> >> University of Oslo
>> >>
>> >> Mobile: +47 48069736
>> >> Home address: Vetlandsvn. 95B, 0685 Oslo, Norway. Googlemaps link
>> >>
>> >>
>> >> <http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Vetlandsvn.+95B,+0685+Oslo,+Norway>
>> >>
>> >>
>> >>
>> >> On 26 April 2012 12:08, Ime Asangansi <asangansi@xxxxxxxxx
>> >> <mailto:asangansi@xxxxxxxxx>> wrote:
>> >>
>> >>    Thanks Roshan,
>> >>
>> >>    Yes, looks like Ola's blueprint has been there since 2009 so its
>> >>    probably not that important. Its really easy doing from
>> >>    the back-end though, good to know for those moving from 1.4
>> >>
>> >>    Ime
>> >>
>> >>
>> >>    --- On *Thu, 4/26/12, Roshan Hewapathirana
>> >>    /<roshanhewapathirana@xxxxxxxxx
>> >>
>> >>    <mailto:roshanhewapathirana@xxxxxxxxx>>/* wrote:
>> >>
>> >>
>> >>        From: Roshan Hewapathirana <roshanhewapathirana@xxxxxxxxx
>> >>        <mailto:roshanhewapathirana@xxxxxxxxx>>
>> >>
>> >>        Subject: Re: [Dhis2-devs] what do you guys think of a duplicate
>> >>        function
>> >>        To: "Ime Asangansi" <asangansi@xxxxxxxxx
>> >>        <mailto:asangansi@xxxxxxxxx>>
>> >>        Cc: dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> >>        <mailto:dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>> >>
>> >>        Date: Thursday, April 26, 2012, 10:37 AM
>> >>
>> >>
>> >>        Hi Ime,
>> >>        I think it is a useful function (even though it might not be
>> >>        used frequently).
>> >>
>> >>        Ola has submitted this blue print on Data Elements,
>> >>
>> >>  https://blueprints.launchpad.net/dhis2/+spec/data-element-cloning
>> >>
>> >>        I was wondering whether it is worth submitting a similar blue
>> >>        print for Indicators too.
>> >>        For Indicators, 'Replicate' function is there in DHIS1.4, which
>> >>        basically allow you to create an Indicator by different names,
>> >>        with more or less similar numerators, denominators and Indicator
>> >>        types.
>> >>
>> >>
>> >>        Roshan
>> >>
>> >>
>> >>
>> >>
>> >>        On 25 April 2012 22:24, Ime Asangansi <asangansi@xxxxxxxxx
>> >>        <http://mc/compose?to=asangansi@xxxxxxxxx>> wrote:
>> >>
>> >>            Hi,
>> >>
>> >>            Just a thought about making creating data elements,
>> >>            indicators, categories, etc faster.
>> >>            Would it be cool to have a new 'create xxx' form that is
>> >>            auto-filled when we hit duplicate on an existing
>> >>            element/orgunit/category etc
>> >>
>> >>            Just for convenience, especially when one wants to create a
>> >>            hundred things with just a small difference btw.
>> >>
>> >>            (As a fall back I'm having to do it with csv and loading up
>> >>            at the backend, cos its just faster to make so many from a
>> >>            sheet than from the interface)
>> >>
>> >>            Just a quick thot...
>> >>
>> >>            Ime
>> >>
>> >>            _______________________________________________
>> >>            Mailing list: https://launchpad.net/~dhis2-devs
>> >>            <https://launchpad.net/%7Edhis2-devs>
>> >>            Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> >>            <http://mc/compose?to=dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>> >>            Unsubscribe : https://launchpad.net/~dhis2-devs
>> >>            <https://launchpad.net/%7Edhis2-devs>
>> >>
>> >>            More help   : https://help.launchpad.net/ListHelp
>> >>
>> >>
>> >>
>> >>    _______________________________________________
>> >>    Mailing list: https://launchpad.net/~dhis2-devs
>> >>    Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> >>    <mailto:dhis2-devs@xxxxxxxxxxxxxxxxxxx>
>> >>
>> >>    Unsubscribe : https://launchpad.net/~dhis2-devs
>> >>    More help   : https://help.launchpad.net/ListHelp
>> >>
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> 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
>> >
>> >
>> >
>> > _______________________________________________
>> > 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
>>
>> _______________________________________________
>> 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
>
>