dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi John,

I get your point and I think we made a mistake with the "allow future
period" property - it should instead have been an enumeration with at least
three options

- allow past periods
- allow current and past periods
- allow future, current and past periods

Blueprint here
<https://blueprints.launchpad.net/dhis2/+spec/dataset-period-data-capture-control>.
We will fix.

Lars





On Sun, Jun 15, 2014 at 12:22 PM, John Lewis <johnlewis.hisp@xxxxxxxxx>
wrote:

> Hi all,
> In Bangladesh, there is daily dataset collecting OPD and Emergancy Visit.
> They have enabled the option of allow future period because user will do
> the data entry every day at the end of OPD session, which is usually in the
> evening. Since DHIS2 dont allow to enter data for current day, as the day
> is not finished, the data set is enabled with option of allow future
> period. Thus has caused end user to enter data for the year 2042, 2024,
> 2140, 2063 etc.
>
> And when we run analytic, several tables of future years has been created.
> Is it possible to allow to solve this? may a option in dataset stating
> allow current period data entry?
>
> Regards,
> John
>
> _______________________________________________
> 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
>
>