dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

On Fri, Apr 24, 2009 at 7:46 AM, Jørn Braa <jornbraa@xxxxxxxxx> wrote:

> Export of an old batch of data where some data have been changed is a very
> likely and "normal" event - also after the data has been reported/exported
> the first time. For example, errors have been detected, quality procedures
> have been put in place, many or few items may have changed - the file is
> exported to (typically) a higher level again.
>
> Re-export of the same, but sligthly changed, data file is part of normal
> data quality procedures.
>

And (as Lars suggested) by using the lastUpdated flag on data values and a
"include values changed since <date>" field in the export GUI we can create
an export files containing all of last months data plus e.g. all values
changed in the last year. This is how it's done in 1.4.


>
> When importing these data, the user should be able to compare the new and
> the old, for those items that have changed.
>
> jorn
>





>
>
> On Fri, Apr 24, 2009 at 5:26 AM, Murodullo Latifov <murodlatifov@xxxxxxxxx
> > wrote:
>
>>
>> On Thu, Apr 23, 2009 at 9:46 PM, Saptarshi Purkayastha <sunbiz@xxxxxxxxx>wrote:
>>
>>>
>>> We could definitely do this by using the timeStamp property on DataValue
>>>> and let the user specify a "since" date in the export GUI. But the user is
>>>> already specifying which months to export data for, typically only the last
>>>> month so I am not sure how much we would save on the file size...
>>>>
>>>
>>> I was suggesting times when only few datavalues were changed in a given
>>> period. Say for the last year's data, we changed only a few values and the
>>> last month's data was not exported earlier. I would then need to export 13
>>> month's of data, whereas we can just export those diff datavalues (changes
>>> from last year and this month's data)
>>>
>>>
>>>
>> Sure.
>>
>> I think Lars by saying "sure" means it is possible using dataValue
>> timeStamp field. If you modified some data for last year (don't know why? or
>> this is allowed to do so after data have been reported?) in this month
>> timeStamp will be the date of change ocured. So we need functionality which
>> allows selecting certain date periods, like from this to that and so on.
>> mesh4x proposed by Knut seems quite valuable tool, need time to look at.
>>
>> regards,
>> murod
>>
>>
>