dhis2-users team mailing list archive

[Uwe Wahser <uwe@xxxxxxxxx>]

Hi Lars,

that's the plan (and it thanks to your quick replies over the last couple of
days that already works). 

The problem is not getting the date in - it's getting them out, since I import
dates back from the last millenium (actually back from 8 AD because of data
entry errors). I'd like to analyze them regardless of that date. Analysis tables
for those years were created, but in PivotTables I am only able to select up to
10 Years back.

Thanks, Uwe


> Lars Helge Øverland <larshelge@xxxxxxxxx> hat am 3. Dezember 2015 um 15:07
> geschrieben:
> 
> 
> 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
> <https://www.dhis2.org/doc/snapshot/en/developer/html/ch01s04.html>.
> 
> 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.
> 
> 
> 
> regards,
> 
> Lars
> 
> 
> 
> 
> 
> 
> 
> 
> 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>