dhis2-devs team mailing list archive

[Calle Hedberg <calle.hedberg@xxxxxxxxx>]

Lars,

The main requirement I have - and I use that all the time - is the ability
to export only a few data elements, option sets, or any other meta-data
sub-set. It correct that the detailed meta-data export was a bit messy (the
"with dependency" option was outright dangerous), but I've been using it
extensively to ensure meta-data consistency across many different instances.

The main reason for the ability to export sub-sets is efficiency: (a)
exporting such meta-data sub-sets using api calls is cumbersome and only
for techies; (b) exporting all meta-data for a certain component can be a
nightmare to import again. As an example, I've got an instance with 45
options sets and a total of around 30,000 option values. Exporting those
are reasonably quick - importing them takes many many hours (if it works at
all). Importing OrgUnits also slowed down tremendously in recent versions
(they are being imported one by one), so the ability to export only those
few that is actually required is critical.

Regards
Calle




On 22 November 2016 at 10:33, Lars Helge Øverland <lars@xxxxxxxxx> wrote:

> Hi Calle,
>
>
>
> On Sun, Nov 20, 2016 at 8:15 PM, Calle Hedberg <calle.hedberg@xxxxxxxxx>
> wrote:
>
>> Hi
>>
>> While trying to find a way to export option sets WITH option values using
>> detailed meta-data export of an option set in 2.24, my local instance
>> bombed out with a
>> StackOverflowError
>>  so I decided to check the SL demo:
>>
>> 1. Opening Import/Export module, the first I notice is that "Meta-data
>> dependency export" is ONLY available from the left panel menu - it is not
>> listed in the main panel.
>>
>
> This has been fixed now in 2.25 > master.
>
>
>>
>> 2. The second thing I notice is that "Meta-data detailed export" is no
>> longer visible. I cannot believe it's been removed since it's highly useful
>> functionality - but where is it?
>>
>>
> We did remove this for 2.25. The reasons were that the code was buggy and
> slow (sometimes causing out of memory exceptions), and that it was hard for
> people to select the right object "graph" (i.e. when selecting a pivot
> table favorite, not selecting the right data elements, indicators,
> categories etc), leaving target databases in weird states.
>
> We are instead planning on expanding on the metadata dependency export. We
> will incorporate i) category combo + dependencies and ii) analytics
> favorites + dependencies. Let us know if you have other requirements.
>
>
> best regards,
>
> Lars
>
>
>
>
>
>
>> Regards
>> Calle
>>
>> *******************************************
>>
>> Calle Hedberg
>>
>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>
>> Tel/fax (home): +27-21-685-6472
>>
>> Cell: +27-82-853-5352
>>
>> Iridium SatPhone: +8816-315-19119
>>
>> Email: calle.hedberg@xxxxxxxxx
>>
>> Skype: calle_hedberg
>>
>> *******************************************
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> lars@xxxxxxxxx
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 

*******************************************

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA

Tel/fax (home): +27-21-685-6472

Cell: +27-82-853-5352

Iridium SatPhone: +8816-315-19119

Email: calle.hedberg@xxxxxxxxx

Skype: calle_hedberg

*******************************************