Thread Previous • Date Previous • Date Next • Thread Next |
Hi Lars,sorry for the late reply but here are some more thoughts on the date dimension,
Regards, Uwe
From the point of data analysis it makes sense in the way that I am able to neglect the date dimension for my analysis, just like I am able to neglect any other dimension. Is it really necesarry to have the date dimension as a mandatory filter?Ok, that will do for the moment. Still this is a bit painfull if I want to select all the years back to the oldest birth year - all the other categories have a check box for selecting all possible values - is there a reason, that this is not possible for periods? If no, can I file a blueprint?Not sure if that makes sense. The other dimensions have a finite set of dimensional items, whereas the period dimension less so.
But I can get your point with regard to the technical imlementation (which I don't know) of filters in DHIS2: - if you implemented filters as inner joins on tables with filter-items or as item lists in the IN(a,b,c) operator of the WHERE clause, I could understand that it is not possible to include an infinite list of periods, when the users checks 'select all' - if checking 'select all' simply means not having any filter on the respective dimension, an infinite list shouldn't be an issue. In the same sense: does it make a difference for the other dimensions, if I check 'select all' or if I don't touch that dimension at all for analysis?
I think what we could do is when "Yearly" is selected as period type, we should the 20 last years, and the "previous" button could jump 20 years back in time instead of just one. Then you could use the "select all" / double-arrow button to get the years over. This would greatly reduce the number of clicks. Would that work?
That would help a bit, but only if I limit the range of valid dates when importing data by mapping them to a certain min or max date. Still I'll have to trust, that the users are not to lazy to really select all available years.
But generally I feel that it makes sense to look at the period selection again with regard to usability: e.g. sorting doesn't work on the left list after selecting and deselecting more than one batch of periods (e.g. 30 years); when switching from year to quarter, then deselecting the years, the years will be inserted on the left list into the quarters. This is quite confusing for the user and a source of error when having long value lists.
Regards, Uwe > Lars Helge Øverland <larshelge@xxxxxxxxx <mailto:larshelge@xxxxxxxxx>> hat am 3. Dezember 2015 um 15:27 > geschrieben: > > > On Thu, Dec 3, 2015 at 3:20 PM, Uwe Wahser <uwe@xxxxxxxxx <mailto:uwe@xxxxxxxxx>> wrote: > > > 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. > > > > Right. In fact you can click the "Prev year" button in the period section > several times to list any year. You can then select all the years you need, > put period as a filter under layout. > > [image: Inline image 1] -- Lars Helge Øverland Lead developer, DHIS 2 University of Oslo Skype: larshelgeoverland http://www.dhis2.org <https://www.dhis2.org>
Thread Previous • Date Previous • Date Next • Thread Next |