dhis2-devs-core team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Lars,

I think the point Rodoflo makes is actually quite important, particular in
systems which are using approvals or which are incentivized (or perhaps
dis-incentivized in the case of league tables) . The "Complete" button, at
least as I understand it, is really supposed to mimic the paper-trail
action of "putting the report in the mail". Once a paper report  has been
put into the mail, there is no longer the possibility for modification of
the data. In one instance where I have helped out with, we actually audit
the "Complete" action. The reason is, that users are incentivized based on
 timely reporting of data. There is thus the potential for a user to submit
an early, yet incomplete and incorrect report, to qualify for on-time
reporting, and thus an incentive, and then subsequently modify the report
after it has been "Completed". However, in this case incentives are
calculated based on when the user* first* pressed the complete button
(implemented with a custom trigger and table as DHIS2 does not audit the
"completedatasetregistration" table ). Users can thus modify data as they
like, up until the point they choose to "Complete" it, or "put it in the
mail", but only the first "Complete" action will count, to prevent gaming
of the system.

In systems with acceptance/approval in place, it would make sense that the
default action for completing data would be to "Complete and submit for
approval", thereby locking the data for further modification by the user.
Once all data has been completed, it would be available for approval (or
this could perhaps be overridden by the next higher approval level). This
would help to ensure that the "Complete" action actually means something.

Regards,
Jason


On Fri, Oct 2, 2015 at 7:59 PM, Rodolfo Melia <rmelia@xxxxxxxxxxxx> wrote:

> Hi Lars - between lines
>
>
> On Fri, Oct 2, 2015 at 6:48 PM, Lars Helge Øverland <larshelge@xxxxxxxxx>
> wrote:
>
>> Hi Rodolfo,
>>
>>
>> On Fri, Oct 2, 2015 at 2:36 PM, Rodolfo Melia <rmelia@xxxxxxxxxxxx>
>> wrote:
>>
>>> At certain point in the past, hitting the 'Complete' button, will lock a
>>> dataset. Currently in 2.20 (and 2.21) a completed dataset remain editable
>>> (is this a bug or a feature?). Would it be possible to:
>>>
>>> a. recover the previous behaviour (a DataSet marked 'Complete' gets
>>> locked)
>>>
>>
>> In fact I am pretty sure it has never been like that ;)
>>
>
> --> Juan Manuel also thinks that it was locking the forms at certain
> point. We believe you
>
>>
>>
>>> b. Associate the 'Incomplete' button to a single authority. You need to
>>> have this authority for the 'incomplete' button to be available to you.
>>>
>>
>> We could but I am a bit skeptical. I suspect that would being to mix up
>> the approval and the completeness feature. In my mind there is not really
>> any point in preventing a user to incomplete a form she has just completed
>> herself. If what you want to do is to have a person higher in the hierarchy
>> review and then lock the information from further modification, the
>> approval feature might be a more suitable solution?
>>
>
> --> For the IPPF implementation, we are using approvals + acceptance. The
> issue is that the complete/ incomplete button is just generating confusion
> (a lot) - it doesn't seem to mean anything if a data entry user can
> complete/incomplete whenever. I know that there is people using this in
> combination with Expiration Date.. Perhaps we could have a setting on the
> DataSet that reads like: enable complete/ incomplete? If no, then the
> buttons don't show.
>
> --> One last question: Will the approval/acceptance status make it to the
> Pivot Table? Or do we need to develop a SQL+App to be able to see them?
>
>>
>>
>> regards,
>>
>> Lars
>>
>
> regards,
>
> Rodolfo
>
>>
>>
>>
>>
>>> Rodolfo[image: Inline image 1]
>>>
>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> http://www.dhis2.org <https://www.dhis2.org>
>>
>>
>
> --
> Mailing list: https://launchpad.net/~dhis2-devs-core
> Post to     : dhis2-devs-core@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs-core
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+46764147049