Re: [Dhis2-devs] 2.23 Metadata importer rewrite and dryRuns

Since there is no rollback feature we rely on the dry run to test imports before actually importing. If you will replace with a comparable feature then great otherwise please let it live through the next season. Thanks. Busoye On 2 Feb 2016 08:19, "Pamod Amarakoon" wrote: >

Re: [Dhis2-devs] 2.23 Metadata importer rewrite and dryRuns

Hi Morten, We are using metaData import frequently when transferring data back and forth in running instances. Dry Run feature is almost always used just to check any incompatibility before actual transfer. So it's quite useful. On Tue, Feb 2, 2016 at 1:45 PM, Morten Olav Hansen

Re: [Dhis2-devs] 2.23 Metadata importer rewrite and dryRuns

Morten, Dropping the dry run is OK if, and I stress if, the import process itself becomes more transparent and step-wise. Basically this means 1. Display new records coming in, with the ability to remove all or some from import 2. Display updated records coming in and the equivalent existing

Re: [Dhis2-devs] 2.23 Metadata importer rewrite and dryRuns

Hi Calle Yeah, I think its obvious from the quick emails we are getting that we should not remove it. I would be great to have a proper rollback feature, but right now this won't be that easy to add. (I am talking about metadata only though, you seem to also mention aggregate/event data? those

[Dhis2-devs] 2.23 Metadata importer rewrite and dryRuns

Hi everyone I'm currently in the process of re-writing our DXF2 metadata importer, and was wondering if anyone is actually using the dryRun option? its adds quite a bit of complexity to the code, so it will be added only to the new importer if people are actually using it for imports -- Morten

Re: [Dhis2-devs] 2.23 Metadata importer rewrite and dryRuns

Morten, I was talking about meta-data, and I'm not suggesting a roll-back feature - I'm suggesting a more step-wise import process where the user can see and control what is being imported/updated: - what meta-data appear as new (it might not actually be new meta-data, but rather just appear as

Re: [Dhis2-devs] 2.23 Metadata importer rewrite and dryRuns

Calle Here's another take on the problem. Imagine you had a separate "metadata" instance (could variously be called facility registry, data dictionary, indicator registry etc). Basically a dhis2 instance with no data. And a staging instance which contains just a copy of the metadata instance.