Hi Jason,
You are right, the system does not support direct data entry, storage or
processing of cumulative values (running totals).
These are usually (depending on the data elements defined of course)
possible to generate based on the raw monthly data and are only supported in
reports, e.g. usin
revno: 2311
committer: Tran Chau
branch nick: dhis2
timestamp: Wed 2010-12-08 14:43:46 +0700
message:
Fix bug: Cannot show paging-div when a number of objects into list is less
then default paging-size.
modified:
dhis-2/dhis-web/dh
revno: 2310
committer: Mithilesh Kumar Thakur
branch nick: trunk
timestamp: Wed 2010-12-08 12:54:10 +0530
message:
Renaming Dashboard to Data Analyser
removed:
local/in/dhis-web-dashboard/src/main/java/org/hisp/dhis/dashboard/
local
revno: 2308
committer: Hieu
branch nick: dhis2
timestamp: Wed 2010-12-08 13:08:16 +0700
message:
Excel Reporting - Fixed unable to find resource "responsePeriods.vm"
modified:
dhis-2/dhis-web/dhis-web-excel-reporting/src/main/resourc
As usual, I am probably going to go totally off topic.
I think this is a very good point and raises other similar issues
regarding data elements which should not be aggregated over time. We
have one data element which is "Current ART count" which represents
the total number of people on ART at any
revno: 2307
committer: Jo Størset
branch nick: dhis2
timestamp: Wed 2010-12-08 11:15:56 +0530
message:
Added basic json support
modified:
dhis-2/dhis-web/dhis-web-api/pom.xml
dhis-2/dhis-web/dhis-web-api/src/main/java/org/hisp/dhi
Dear Thuy Nguyen, and others,
I am not sure this is suitable for this DHIS2 or not.
In the distribution system, there are no hierarchy such as National,
District, Facility. Because they may have some stocks and shipped and
received. They are all same level for the distribution system. Them, it
Public bug reported:
When I select aggregated level attribute at level 3 of 4 levels in a
data element. When generate report in excel report, the data element
doesn't aggregated from level 3 but level 4.
** Affects: dhis2
Importance: Undecided
Status: New
--
You received this bug
Dear Johan,
> Here also I'm not 100% sure, but if you go to edit data element, you will
> find the Aggregation Level check box, which if checked will produce a
> drop-down list of all the levels you can aggregate data from. From the
> manual:
>
> "Aggregation levels: The Aggregation Levels option
revno: 2306
committer: Tran Chau
branch nick: dhis2
timestamp: Wed 2010-12-08 10:16:36 +0700
message:
Display all of details of a patient.
modified:
dhis-2/dhis-web/dhis-web-maintenance/dhis-web-maintenance-patient/src/main/resource
Several people have asked for the link to the Google doc, and I have
added them to the list of editors. I also changed the permissions to
allow anyone to read it. These are some random thoughts I have had
about the whole categories/combos/options. Your mileage may vary.
I have some more thought
revno: 2305
committer: Lars Helge Overland
branch nick: dhis2
timestamp: Tue 2010-12-07 18:02:27 +0100
message:
Impl support for totals in indicator formulas
modified:
dhis-2/dhis-api/src/main/java/org/hisp/dhis/dataelement/DataElem
revno: 2101
committer: Lars Helge Overland
branch nick: 2.0.5
timestamp: Tue 2010-12-07 15:32:44 +0100
message:
Merged r 2149
added:
dhis-2/dhis-web/dhis-web-reporting/src/main/java/org/hisp/dhis/reporting/reportviewer/action/GetRep
On 7 December 2010 12:27, Jo Størset wrote:
> Hi,
>
> seeing if we can keep this thread alive..
>
> Den 29. nov. 2010 kl. 04.11 skrev Bob Jolliffe:
>
>> 2010/11/28 Lars Helge Øverland :
>>>
>>>
>>> On Sat, Nov 27, 2010 at 6:03 PM, Bob Jolliffe wrote:
(i) authentication - currently cook
Hi,
seeing if we can keep this thread alive..
Den 29. nov. 2010 kl. 04.11 skrev Bob Jolliffe:
> 2010/11/28 Lars Helge Øverland :
>>
>>
>> On Sat, Nov 27, 2010 at 6:03 PM, Bob Jolliffe wrote:
>>>
>>> (i) authentication - currently cookies/html form based which is
>>> awkward. Watching what
2010/11/16 Lars Helge Øverland :
> In a parallel process we have a set of student projects working on the
> following blueprints:
> Project Groups
>
> Some of these are experimental while some might feed directly into DHIS 2 on
> a short term. This work can be followed on the DHIS 2 Academy Launchp
On 7 December 2010 10:17, Ola Hodne Titlestad wrote:
> On 7 December 2010 10:41, Bob Jolliffe wrote:
>>
>> there seem to be 3 primary motivations for an implementor to use
>> categories
>> (i) it can make auto-generated forms do what you want
>> (ii) it reduces the number of dataelements you have
On 7 December 2010 10:41, Bob Jolliffe wrote:
> there seem to be 3 primary motivations for an implementor to use categories
> (i) it can make auto-generated forms do what you want
> (ii) it reduces the number of dataelements you have to design
> (iii) it provides an axis for analysis
>
> In the b
On 7 December 2010 10:08, Ola Hodne Titlestad wrote:
> On 7 December 2010 09:02, Knut Staring wrote:
>>
>> On Tue, Dec 7, 2010 at 2:55 AM, Thuy Nguyen
>> wrote:
>> > Dear Johan,
>> > Thank you for your suggestions. Please scroll down to see my mail
>> >
>> >
>> >
>> > On Tue, Dec 7, 2010 at 1:59
On 7 December 2010 11:08, Ola Hodne Titlestad wrote:
> On 7 December 2010 09:02, Knut Staring wrote:
>
>> On Tue, Dec 7, 2010 at 2:55 AM, Thuy Nguyen
>> wrote:
>> > Dear Johan,
>> > Thank you for your suggestions. Please scroll down to see my mail
>> >
>> >
>> >
>> > On Tue, Dec 7, 2010 at 1:59
On 7 December 2010 09:02, Knut Staring wrote:
> On Tue, Dec 7, 2010 at 2:55 AM, Thuy Nguyen
> wrote:
> > Dear Johan,
> > Thank you for your suggestions. Please scroll down to see my mail
> >
> >
> >
> > On Tue, Dec 7, 2010 at 1:59 AM, wrote:
> >>
> >> Dear Thuy,
> >>
> >> I'm not very familiar
On Tue, Dec 7, 2010 at 10:45 AM, Bob Jolliffe wrote:
> On 6 December 2010 16:24, Knut Staring wrote:
>> Hello all, with the pagination module one can specify exactly the
>> number of items per page, for example 27. However, I think it would be
>> slightly more user friendly to replace this input
On 6 December 2010 16:24, Knut Staring wrote:
> Hello all, with the pagination module one can specify exactly the
> number of items per page, for example 27. However, I think it would be
> slightly more user friendly to replace this input field by a dropdown
> with typical choices, such as 5, 10,
On 7 December 2010 09:48, wrote:
> Dear Thuy
>
> > Dear Johan,
> > Thank you for your suggestions. Please scroll down to see my mail
>
> > on this. That's why I consult you to know what will happen in the future
> > when data base become huge if we use category options like this for data
> > elem
there seem to be 3 primary motivations for an implementor to use categories
(i) it can make auto-generated forms do what you want
(ii) it reduces the number of dataelements you have to design
(iii) it provides an axis for analysis
In the best of cases these three conspire together to produce a goo
Dear Thuy
> Dear Johan,
> Thank you for your suggestions. Please scroll down to see my mail
> on this. That's why I consult you to know what will happen in the future
> when data base become huge if we use category options like this for data
> elements? Is it affecting to retrieving information l
revno: 2304
committer: Quang
branch nick: trunk
timestamp: Tue 2010-12-07 15:30:02 +0700
message:
Apply pagination in DataMart list.
modified:
dhis-2/dhis-api/src/main/java/org/hisp/dhis/datamart/DataMartService.java
dhis-2/dhis-s
This has got me thinking once again what a category/combo/option
actually is and how the current implementation makes too many
assumptions, like that categories should add up to a total.
I would suggest we continue thinking about it in background document
I created a while back..
https://docs.g
On Tue, Dec 7, 2010 at 2:55 AM, Thuy Nguyen wrote:
> Dear Johan,
> Thank you for your suggestions. Please scroll down to see my mail
>
>
>
> On Tue, Dec 7, 2010 at 1:59 AM, wrote:
>>
>> Dear Thuy,
>>
>> I'm not very familiar with the requirements in Sri Lanka, but I have a few
>> general comments
29 matches
Mail list logo
