I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
I was hoping to use the import meta-data functionality to create a large number of org units in my own instance (about to try it out).
Are there known bugs with it? Is there an alternative UI functionality or perhaps is writing directly to the organisationunit table a viable alternative?
Thanks,
Kevin
···
On Sat, Oct 29, 2016 at 2:58 AM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Nick
Yeah, that has been removed now, it wasn’t really working well, and there would almost always be missing objects.
What are you trying to export? if its data set or program, did you have a look at our new “export with deps” functionality?
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
if you have specific needs let us know and we can consider including new objects here.
As Morten said, the previous detailed metadata export was too error prone as one would typically forget important parts when exporting things like categories and data sets.
regards,
Lars
···
On Fri, Oct 28, 2016 at 9:58 PM, Morten Olav Hansen morten@dhis2.org wrote:
Hi Nick
Yeah, that has been removed now, it wasn’t really working well, and there would almost always be missing objects.
What are you trying to export? if its data set or program, did you have a look at our new “export with deps” functionality?
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
A nice feature with the detailed one was that you could select a subset (not all the organisationunits, dataelements etc).
···
On Sat, Oct 29, 2016 at 5:07 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Nick,
if you have specific needs let us know and we can consider including new objects here.
As Morten said, the previous detailed metadata export was too error prone as one would typically forget important parts when exporting things like categories and data sets.
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
Hi, I would be interested in a “dashboard with dependencies” export.
Olav
···
On Sat, Oct 29, 2016 at 5:07 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Nick,
if you have specific needs let us know and we can consider including new objects here.
As Morten said, the previous detailed metadata export was too error prone as one would typically forget important parts when exporting things like categories and data sets.
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
On Sat, Oct 29, 2016 at 5:07 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Nick,
if you have specific needs let us know and we can consider including new objects here.
As Morten said, the previous detailed metadata export was too error prone as one would typically forget important parts when exporting things like categories and data sets.
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
I am also supporting Olav; We are also badly requires “dashboard with dependencies” export. Also if there is any mechanism to synchronize dashboard, with provision to active/deactivate the option.
Regards
···
On Sun, Oct 30, 2016 at 1:25 AM, Olav Poppe olav.poppe@me.com wrote:
Olav
Hi, I would be interested in a “dashboard with dependencies” export.
On Sat, Oct 29, 2016 at 5:07 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Nick,
if you have specific needs let us know and we can consider including new objects here.
As Morten said, the previous detailed metadata export was too error prone as one would typically forget important parts when exporting things like categories and data sets.
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
We also required detailed metadata export with dependency from where can select a subset (not all the organisationunits, dataelements etc) as Knut says. Without that we will be in deep water. We already have lots of issues with metadata.
Regards
Hannan
···
On Sat, Oct 29, 2016 at 11:56 PM, Knut Staring knutst@gmail.com wrote:
A nice feature with the detailed one was that you could select a subset (not all the organisationunits, dataelements etc).
On Sat, Oct 29, 2016 at 5:07 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Nick,
if you have specific needs let us know and we can consider including new objects here.
As Morten said, the previous detailed metadata export was too error prone as one would typically forget important parts when exporting things like categories and data sets.
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
As others have mentioned, I was also thinking about exporting a sub-set of objects (and what I would have traditionally used it for), like all dataelements, orgunits etc. within a certain group.
···
On Sun, Oct 30, 2016 at 12:14 PM, Hannan Khan hannank@gmail.com wrote:
Dear Lars
We also required detailed metadata export with dependency from where can select a subset (not all the organisationunits, dataelements etc) as Knut says. Without that we will be in deep water. We already have lots of issues with metadata.
On Sat, Oct 29, 2016 at 5:07 PM, Lars Helge Øverland lars@dhis2.org wrote:
Hi Nick,
if you have specific needs let us know and we can consider including new objects here.
As Morten said, the previous detailed metadata export was too error prone as one would typically forget important parts when exporting things like categories and data sets.
I notice in 2.25 I no longer have the option to perform a detailed meta-data export from the import-export app. Is this feature being deprecated? I couldn’t see anything related to it in the release notes and find it quite useful.
I think there are cases where you want to include data elements/indicators, and cases where you would not want to include it - so for me, the ideal would be that there was a choice.
A challenge at least as of 2.24 (was unable to test in 2.25, import failed) is that if you import a favourite into a database where the data items are missing, you can’t manually modify/add those in DV/PT/GIS favorite because the favorite won’t open. So for now, you really need the data element/indicators to be included if importing these in a database where the data items are different. If it had been possible to edit imported favorites with missing data dimension, not including the data items would have been good solution in many cases. With 2.25, you could even have used the “favorite description” to guide people in configuring the imported favorites to their database. So an additional feature request would be the ability modify “ill-defined” favorites.
Olav
···
okt. 2016 kl. 23.40 skrev Lars Helge Øverland lars@dhis2.org:
How far should the dependencies go? Stop at favorites (pivot tables, maps etc), or include data elements/categories/indicators etc?
that's actually how they do it in other systems in the commercial sector, mainly
used to forward changes from development to productive systems:
1 - you first select the type of object for the export (dashboard, map, chart,
whatever ...)
2 - then you get a list of possible objects to select from
3 - the system collects the dependencies down to the lowest detail
4 - from the resulting object-tree you can de-select single branches on any
detail level (if a de-selected dependency does not exist in the target-system,
import will fail, though - however this is great if you have manually altered
content in the target system)
This would be great for packaging user defined content for sharing best practice
with others (e.g. a template for Maternity monitoring etc.)
Candy would be also to be able to export deleted object-trees for deletion of
complete trees in other systems ...
Regards, Uwe
···
Hannan Khan <hannank@gmail.com> hat am 30. Oktober 2016 um 07:14 geschrieben:
Dear Lars
We also required detailed metadata export with dependency from where can
select a subset (not all the organisationunits, dataelements etc) as Knut
says. Without that we will be in deep water. We already have lots of issues
with metadata.
Regards
Hannan
On Sat, Oct 29, 2016 at 11:56 PM, Knut Staring <knutst@gmail.com> wrote:
> A nice feature with the detailed one was that you could select a subset
> (not all the organisationunits, dataelements etc).
>
> On Sat, Oct 29, 2016 at 5:07 PM, Lars Helge Øverland <lars@dhis2.org> > > wrote:
>
>>
>> Hi Nick,
>>
>> if you have specific needs let us know and we can consider including new
>> objects here.
>>
>> As Morten said, the previous detailed metadata export was too error prone
>> as one would typically forget important parts when exporting things like
>> categories and data sets.
>>
>> regards,
>>
>> Lars
>>
>>
>>
>>
>>
>> On Fri, Oct 28, 2016 at 9:58 PM, Morten Olav Hansen <morten@dhis2.org> > >> wrote:
>>
>>> Hi Nick
>>>
>>> Yeah, that has been removed now, it wasn't really working well, and
>>> there would almost always be missing objects.
>>>
>>> What are you trying to export? if its data set or program, did you have
>>> a look at our new "export with deps" functionality?
>>>
>>> https://dhis2.github.io/dhis2-docs/master/en/developer/html/
>>> webapi_metadata_export.html#webapi_dataset_program_export_dependencies
>>>
>>> You can also find it in the UI, under import/export module
>>>
>>> --
>>> Morten Olav Hansen
>>> Senior Engineer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Sat, Oct 29, 2016 at 12:01 AM, Shurajit Dutta < > >>> shurajitdutta@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I notice in 2.25 I no longer have the option to perform a detailed
>>>> meta-data export from the import-export app. Is this feature being
>>>> deprecated? I couldn't see anything related to it in the release notes
>>>> and
>>>> find it quite useful.
>>>>
>>>> Thanks,
>>>> Nick
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~dhis2-users
>>>> Post to : dhis2-users@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>>> More help : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-users@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> lars@dhis2.org
>> http://www.dhis2.org <https://www.dhis2.org/>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-users@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> Norway: +4791880522
> Skype: knutstar
> http://dhis2.org
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-users@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help : https://help.launchpad.net/ListHelp
>
>
--
Muhammad Abdul Hannan Khan
Secretary
HISP Bangladesh
thanks for the feedback. Based on this I have written up issues for export of dashboard with dependencies, and data elements in group with dependencies.
Note that for expert users, it is always an alternative to use the API directly with the help of the :owner keyword, e.g.: