dhis2-devs team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

On 28 May 2010 09:36, Ola Hodne Titlestad <olatitle@xxxxxxxxx> wrote:
> See what you mean Jason.
>
> We should definitely have something like a detailed data export (I  think
> ad-hoc is a better name maybe) similar to the Detailed Metadata export.
>
> This becomes useful when you need to export some of your raw data to other
> DHIS instances that are outside the reporting chain (that would not get the
> full dataset on a routinely basis).
>
> I think this will become even more evident when we start exporting data to
> external systems through sdmx.
>
> Basically what we need is to support an additional data export interface
> where the user can selected data elements, orgunits, and periods, all
> totally independent of datasets.
> Bob, does this mess up your world?

Not at all.  (My "world" is forever teetering on chaos anyway).  But
actually this is what I have been advocating for the past few weeks.
I think George Orwell said everyone writes the same book .. just using
different words :-)  What you are saying corresponds quite directly
with what I have been terming a datavalueset - I would have preferred
dataset but that word is gone already :-(

In the case you are describing, you want the user to be able to define
an adhoc datavalueset for export purposes which could be ok.

If the datavalues were already grouped as datavaluesets (by orgunit,
period, dataset and categorycombo) then the chances are that this
export requirement might be met by being able to select existing
datavaluesets to export - these would generally be of the same
categorycombo to be useful for analyses purposes.  Or rolled up on the
basis of lowest common denominator of categories as I have described
previously.

As I understand the adhoc use case described by Jason, what would be
further required is to further select a subset of datavalues (on the
basis of dataelement) from the exported sets.

Regards
Bob

PS.  You can see a small example of two sdmx datasets with differnt
categorycombos here:
http://bazaar.launchpad.net/~bobjolliffe/+junk/sdmx-hd/annotate/head:/data/Data_Multiple.xml

>
> Still for any kind of routine data export I would advise to use datasets as
> the way to organise the export, which is easier for the users I think. This
> might also be the case where you have to report only a subset of a larger
> dataset to another DHIS instance. In some places you might have different
> DHIS2 setups between some of the health programs and the HMIS office. If
> data elements are harmonised you can still export these from DHIS2 databases
> at health programs across to the DHIS2 database at the HMIS, but typically
> the health programs collect more data than what is required by HMIS, so just
> a subset of a larger program-specific data set needs to be exported. Then I
> would say it makes sense to create a new dataset on the health program
> system with all the data elements that needs to be exported to HMIS. This
> dataset would then never be used for data entry since there is a larger more
> detailed dataset used for data collection by the health program. This way
> the standard way of doing data exports by dataset is kept and that should
> simplify the user experience.
>
>
> Ola
> ----------
>
> On 28 May 2010 09:17, Jason Pickering <jason.p.pickering@xxxxxxxxx> wrote:
>>
>> Hi Ola,
>> Yes, I did not mean the metadata, but rather the actual data itself.
>>
>> This isn't really the same thing that you mention, but we probably need
>> both.
>>
>>  I have a huge dataset, and exporting the entire thing, at least for
>> my purposes, would be very impractical to export, and then only select
>> a few data elements to import. I think it is also about being able to
>> provide certain data to certain parties, who might only be authorized
>> to receive a part of the dataset, rather than the entire thing.
>>
>> Regards,
>> Jason
>>
>>
>>
>> On Fri, May 28, 2010 at 9:12 AM, Ola Hodne Titlestad <olatitle@xxxxxxxxx>
>> wrote:
>> > Sorry, after looking at the blueprint as well I realise that Jason is
>> > talking about exporting data values for two data elements, and not just
>> > their definitions.
>> >
>> > That sounds like a useful feature to me.
>> >
>> > A quick workaorind for now would be to just filter on the import side in
>> > import preview where you can easily remove individual data elements (and
>> > their data), or create a new fake data set...
>> >
>> >
>> > Ola
>> >
>> > On 28 May 2010 09:09, Ola Hodne Titlestad <olatitle@xxxxxxxxx> wrote:
>> >>
>> >> Have a look at Services->Import-Export->Detailed Metadata Export
>> >>
>> >> There you can pick any combination of data elements and/or indicators
>> >> for
>> >> export.
>> >>
>> >> On a related note, I just tested this functionality on the demo here:
>> >>
>> >>
>> >> http://dhis.uio.no/demo/dhis-web-importexport/displayDetailedMetaDataExportForm.action?exportFormat=DXF
>> >>
>> >> And noted that although the DXF file correctly only contains the two
>> >> data
>> >> elements I selected for export, it seems to come with ALL the
>> >> categorycombo
>> >> (plus plus) information (not only what is related to my two data
>> >> elements).
>> >> Not sure if all this is needed,and wouldn't that just complicate the
>> >> import
>> >> the other side? I mean it is not given that they would like to import
>> >> all
>> >> those categories etc.
>> >>
>> >> Ola
>> >> -----------
>> >>
>> >> On 28 May 2010 07:58, Jason Pickering <jason.p.pickering@xxxxxxxxx>
>> >> wrote:
>> >>>
>> >>> Hi there. Perhaps I am missing something very obvious. I wanted to
>> >>> export two data elements, only, from DHIS2, but could not really
>> >>> figure out how to do this. I can export an entire dataset, but this is
>> >>> not really what I need to do. Am I missing something, very obvious or
>> >>> is this functionality just not there yet?
>> >>>
>> >>> I have written up a specification, here
>> >>> (https://blueprints.launchpad.net/dhis2/+spec/export-specifications),
>> >>> but most of this has already been done in DHIS1.4 which can serve as a
>> >>> more refined template for this blueprint.
>> >>>
>> >>> Regards,
>> >>> Jason
>> >>>
>> >>>
>> >>> ---
>> >>> Jason P. Pickering
>> >>> email: jason.p.pickering@xxxxxxxxx
>> >>> tel:+260968395190
>> >>>
>> >>> _______________________________________________
>> >>> 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
>> >>
>> >
>> >
>>
>>
>>
>> --
>> --
>> Jason P. Pickering
>> email: jason.p.pickering@xxxxxxxxx
>> tel:+260968395190
>
>
> _______________________________________________
> 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
>
>