← Back to team overview

dhis2-users team mailing list archive

Re: Use of Periods


Hi Uwe,

to me it sounds like you could use the "daily" period type and map this to
daily periods.

The daily period format is *yyyyMMdd* as described in the docs

So for each data value record you import (as part of a regular
dataValueSet), you can format your date (as e.g. 19850401) and import as
routine data.



On Thu, Dec 3, 2015 at 2:31 PM, Uwe Wahser <uwe@xxxxxxxxx> wrote:

> Dear all,
> I understand that the period-dimension for data entry and analysis
> traditionally
> comes from the reporting periods, along which routine summary reports are
> entered into the system.
> In our setting, where we want to load aggregated data from relational data
> base
> systems into DHIS2 data-sets, we don't really have reporting periods as
> such
> (reporting frequency is daily). Nevertheless there are number of dates to
> be
> respected when reporting data-elements.
> Since the period dimension seems to be the only way to represent dates in
> the
> DHIS2 aggregate level, I can think of two options to model dates into a
> data-set:
> 1 - preferred: use the standard period-dimension and code the data-elements
> according to a reference date into the period dimension (e.g. Number of
> Births
> -> Date of Birth, Number of registrations -> date of registration) The
> problem
> here is, that I can't seem to find a way of analyzing data without
> restriction
> to a date (e.g. to get the total amount of people based registrations from
> up to
> 40 years ago) in pivot table, visualizer or dashboards. The maximum I can
> get
> out is over a time-span of 10 years as DHIS2 forcefully requires the user
> to
> chose a specific period.
> 2 - use the categories (year, month, day) for each date (e.g BirthYear,
> BirthMonth, BirthDay) combined into CategoryCombos and code the dates as
> CategoryOptions (inflating of course the number of OptionCombos) although
> this
> seems to be quite flexible, I will be missing out on the dynamic featrues
> (e.g
> current year, last 12 months) and iI might confuse the user as there will
> be a
> date-dimension which is not being used.
> How are others using the date dimension when having to aggregate across
> unlimited periods WITHIN DHIS2? Is there maybe a setting for the analysis
> module, where I can extend the number of years?
> Thanks for sharing your experiences,
> Uwe
> _______________________________________________
> 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

Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
http://www.dhis2.org <https://www.dhis2.org>

Follow ups