dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

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