dhis2-devs team mailing list archive

[Elmarie Claasen <elmarie@xxxxxxxx>]

Hi,

In addition to what Calle explained I found the most problematic
dependencies included are users and their user roles. We typically export
orgunits, data elements and indicators between instances that contain
similar objects but are not always exact replicas of each other and user
permissions differ. We took some time to discover why a specific superusers
account was always being changed then discovered that he did not have a
superuser account in the source system. It would be preferable for metadata
if the user information is dropped from the export and the importers user
information.attached since that is the person who imports it i to.the new
instance or as Calle suggests you get an option what to include/exclude.

Regards

Elmarie Claasen
HISP-SA

On 12 Dec 2016 23:49, "Calle Hedberg" <calle.hedberg@xxxxxxxxx> wrote:

> Hi,
>
> I hardly ever used that "with dependencies" option because I was never
> able to determine what dependencies would be included or not, and when
> using it I would often get import summaries that did not make sense.
>
> The most typical scenario for my use of the detailed export feature was to
> export specific but "clean" sub-sets of data elements, indicators, and so
> forth. So when exporting more complicated objects, I would usually
> carefully sequence a string of exports that ensured that objects would be
> imported in the same sequence you would typically define them from scratch
> (e.g. first export/import options, then option sets, then data elements
> using those option sets, etc etc).
>
> My preferred option for this functionality is that it would be a two-step,
> more transparent process:
> 1. User select a number of primary meta-data objects (e.g. a set of
> indicators).
> 2. The system will scan through the objects, determine what they directly
> depend on (like data elements), and display those for the user to accept or
> reject for inclusion.
> If the user reject to include e.g. underlying data elements in the export
> file, it is up to the user to either export them separately OR else to
> ensure that they are in the destination database already. It might also
> make sense to limit the "dependency depth" to just one level - so when
> exporting indicators you would be notified of data elements required, but
> NOT be notified of option sets required for those data elements and in turn
> options required for those option sets.
>
> Other related objects - like data element allocations to orgunits, or data
> element group memberships, should rather be separate detailed exports than
> "dependency inclusions".
>
> We can discuss this later in the week, Lars.
>
> Regards from Oslo
> Calle
>
> On 12 December 2016 at 20:54, Lars Helge Øverland <lars@xxxxxxxxx> wrote:
>
>> Hi there,
>>
>> sorry, unfortunately we will not put it back into 2.25. We removed it
>> because the feature was low-quality and lead to many problems down the road
>> since people exported and imported meta-data of invalid state (think
>> favorites without any data elements, categories without any options etc).
>>
>> We do understand that this was useful from the feedback though so we will
>> do our best to come up with a similar but better version.
>>
>> As mentioned before, please let us know about the most popular use-cases
>> and we can extend the "Metadata dependency export" feature.
>>
>> regards,
>>
>> LArs
>>
>>
>> On Mon, Dec 12, 2016 at 11:04 AM, Jose Garcia Muñoz <josemp10@xxxxxxxxx>
>> wrote:
>>
>>>
>>> Thanks Calle,
>>>
>>> That funcionality is also very important for us. I'm using it all the
>>> time.
>>>
>>> Lars & team, do you have any plans to restore it in 2.25?
>>>
>>> Best
>>> Jose
>>>
>>> On Thu, Dec 1, 2016 at 5:33 PM, Calle Hedberg <calle.hedberg@xxxxxxxxx>
>>> wrote:
>>>
>>>> Jose,
>>>>
>>>> I inquired about the same last week - and Lars responded that it was
>>>> removed in 2.25 due to it being buggy and a high risk in terms of
>>>> potentially causing database corruption. I am not happy about removing the
>>>> functionality since I found it very useful, but I guess it will have to be
>>>> completely redesigned - so not sure if or when it will be back.
>>>>
>>>> Regards
>>>> Calle
>>>>
>>>> On 1 December 2016 at 15:50, Jose Garcia Muñoz <josemp10@xxxxxxxxx>
>>>> wrote:
>>>>
>>>>>
>>>>> I can not see that in the interface (although it is presented in the
>>>>> dhis2 documentation)
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> Regards
>>>>> Jose
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *******************************************
>>>>
>>>> Calle Hedberg
>>>>
>>>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>>>
>>>> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>>>>
>>>> Cell: +27-82-853-5352 <+27%2082%20853%205352>
>>>>
>>>> Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>
>>>>
>>>> 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
>
> *******************************************
>
>
> _______________________________________________
> 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
>
>

-- 


*This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer 
<http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the 
disclaimer before opening any attachment or taking any other action in 
terms of this electronic transmission.  If you cannot access the 
disclaimer, kindly send an email to disclaimer@xxxxxxxx 
<disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to 
this e-mail or opening any attachment you agree to be bound by the 
provisions of the disclaimer.*