dhis2-users team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Dan,

sorry at the moment it is not possible. We have been hearing this
requirements a few times now and have been considering to include a time
aspect in the data set assignment. On one side it will add some complexity
and make it more challenging for users to maintain it properly, on the
other side it might simply become necessary. Will think about it.

regards, Lars





On Fri, Feb 22, 2013 at 8:51 AM, Jason Pickering <
jason.p.pickering@xxxxxxxxx> wrote:

> Hi Dan,
> I do not think this is possible at the moment. Would be good though to
> hear from the developers about this. For the national DHIS2 instance in
> Zambia, we have developed custom reports which factor in the
> startdate/enddate of the facility to determine whether or not they should
> contribute to reporting completeness. However, this means that the start
> dates and end dates must be maintained /populated correctly. This approach
> would not take into account situations (mentioned for instance by Nick from
> the Solomons on the list a week or so ago) when a facility may report on an
> infrequent basis.
>
> What you want would seem to require some sort of external analysis. You
> could extract out the reporting completeness figures, but then run this
> through an extra data set which would contain information on the dates
> which you expect the facility to report.  Not really sure there is really
> any way to get this out of the system at the moment though, unless you were
> to create yet another dataset "Expected reports" and then have a Yes/No
> data element to record whether or not you actually expect a report for a
> given facility for a given dataset. Sounds messy.
>
> Regards,
> Jason
>
>
>
> On Thu, Feb 21, 2013 at 12:32 PM, Daniel Bridges <
> dbridges@xxxxxxxxxxxxxxxxx> wrote:
>
>> Hope this hasn't been asked before, but is there any way to associate an
>> orgunit with a dataset for a defined period, or at least a start period? We
>> are migrating users from one dataset to an updated one with different
>> questions etc. The changeover will take some time so had to create a second
>> dataset rather than change the original. Anyway if you look at 'Reporting
>> rate summary' reports it gets very confusing. For example lets say orgunit
>> 'Muchila' is associated with dataset old for Dec 2012 and then is changed
>> to dataset new for Jan 2013. If you look at the reporting rate summary
>> report for dataset old, there is no information for Dec or Jan (blank /
>> empty table). Conversely if you look at dataset new for either of these
>> months then the table is populated with expected values. This is fine for
>> Jan 2013 as you are expecting data, but Dec 2012 should give a blank....
>> For creating charts this makes no difference, but it is sometimes important
>> to determine whether a 0 means the orgunit failed to report or not.... This
>> may be difficult to determine with historical data!
>>
>> Hope all of that made sense - let me know if I need to clarify.
>>
>> Cheers
>> Dan
>>
>> ______________________________**_________________
>> Mailing list: https://launchpad.net/~dhis2-**users<https://launchpad.net/~dhis2-users>
>> Post to     : dhis2-users@lists.launchpad.**net<dhis2-users@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~dhis2-**users<https://launchpad.net/~dhis2-users>
>> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>