Re: [Dhis2-devs] Program notifications - where to specify communication formats?

[Cecilia @dhis2]

Hi Calle,
Could you create an issue in JIRA (on project Documentation for DHIS 2
) for the doc changes you would
like to see?

Thanks!
Cecilia
DHIS2 content team

On Thu, Feb 2, 2017 at 11:39 PM, Calle Hedberg 
wrote:

> and to be even more specific: the ability to select method (Email/SMS) for
> Program notifications are only available in 2.26 -  in 2.25 there is
> nothing.
>
> Regards
> calle
>
> On 3 February 2017 at 00:13, Calle Hedberg 
> wrote:
>
>> Hi,
>>
>> Just a brief follow-up: I was reading through the user and developer
>> manuals for both program notifications and program stage notifications, but
>> I only looked at program stage notifications in the system.
>>
>> Now I noticed that
>>
>> 1.
>> In the Program notification configuration form, you can specify SMS
>> and/or email (it looks like internal messaging is compulsory?). NOTE THAT
>> THIS PART OF THE DEFINITION FORM IS NOT MENTIONED IN THE MANUALS.
>>
>> 2.
>> The same options are NOT included with the program STAGE notifications -
>> hence my question above. This type of inconsistency looks like more like a
>> bug (omission) than a deliberate design flaw.
>>
>> Halvdan is no longer working on the new messaging component - has anybody
>> else taken over?
>>
>> Regards
>> Calle
>>
>> On 2 February 2017 at 23:35, Calle Hedberg 
>> wrote:
>>
>>> Hi
>>>
>>> I've just looked through the user and developer guides for 2.25 and
>>> 2.26, but I cannot find any specific reference to how you can control how
>>> program notifications and program stage notifications are sent.
>>>
>>> In 2.24, you could specify at least whether to send notifications as
>>> SMS, Email or BOTH. That option is no longer there after that component has
>>> been refactored.
>>>
>>> 1.
>>> Is the messaging now controlled from the Systems Settings -> Messaging
>>> (by selecting email and/or SMS)? If yes, I presume that means one standard
>>> comm method for all notifications - and that you cannot turn off internal
>>> notification messaging...
>>>
>>> 2.
>>> What I'm looking for is the ability to specify internal messaging and/or
>>> email and/or SMS on a per notification basis.
>>>
>>> For instance, if you send out alerts by email or SMS to get users to
>>> access the DHIS2 for latest developments, then there is no need to fill up
>>> the messages list with a copy of the same
>>>
>>> Regards
>>> Calle
>>>
>>> ***
>>>
>>> Calle Hedberg
>>>
>>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>>
>>> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>>>
>>> Cell: +27-82-853-5352 <+27%2082%20853%205352>
>>>
>>> Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>
>>>
>>> Email: calle.hedb...@gmail.com
>>>
>>> Skype: calle_hedberg
>>>
>>> ***
>>>
>>>
>>
>>
>> --
>>
>> ***
>>
>> Calle Hedberg
>>
>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>
>> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>>
>> Cell: +27-82-853-5352 <+27%2082%20853%205352>
>>
>> Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>
>>
>> Email: calle.hedb...@gmail.com
>>
>> Skype: calle_hedberg
>>
>> ***
>>
>>
>
>
> --
>
> ***
>
> Calle Hedberg
>
> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>
> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>
> Cell: +27-82-853-5352 <+27%2082%20853%205352>
>
> Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>
>
> Email: calle.hedb...@gmail.com
>
> Skype: calle_hedberg
>
> ***
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Program notifications - where to specify communication formats?

[Calle Hedberg]

Cecilia,

Will do so, but I'm hoping to get some clarity first on what these hoodlum
developers have actually done ;-)

Regards
Calle

On 3 February 2017 at 10:25, Cecilia @dhis2  wrote:

> Hi Calle,
> Could you create an issue in JIRA (on project Documentation for DHIS 2
> ) for the doc changes you would
> like to see?
>
> Thanks!
> Cecilia
> DHIS2 content team
>
> On Thu, Feb 2, 2017 at 11:39 PM, Calle Hedberg 
> wrote:
>
>> and to be even more specific: the ability to select method (Email/SMS)
>> for Program notifications are only available in 2.26 -  in 2.25 there is
>> nothing.
>>
>> Regards
>> calle
>>
>> On 3 February 2017 at 00:13, Calle Hedberg 
>> wrote:
>>
>>> Hi,
>>>
>>> Just a brief follow-up: I was reading through the user and developer
>>> manuals for both program notifications and program stage notifications, but
>>> I only looked at program stage notifications in the system.
>>>
>>> Now I noticed that
>>>
>>> 1.
>>> In the Program notification configuration form, you can specify SMS
>>> and/or email (it looks like internal messaging is compulsory?). NOTE THAT
>>> THIS PART OF THE DEFINITION FORM IS NOT MENTIONED IN THE MANUALS.
>>>
>>> 2.
>>> The same options are NOT included with the program STAGE notifications -
>>> hence my question above. This type of inconsistency looks like more like a
>>> bug (omission) than a deliberate design flaw.
>>>
>>> Halvdan is no longer working on the new messaging component - has
>>> anybody else taken over?
>>>
>>> Regards
>>> Calle
>>>
>>> On 2 February 2017 at 23:35, Calle Hedberg 
>>> wrote:
>>>
 Hi

 I've just looked through the user and developer guides for 2.25 and
 2.26, but I cannot find any specific reference to how you can control how
 program notifications and program stage notifications are sent.

 In 2.24, you could specify at least whether to send notifications as
 SMS, Email or BOTH. That option is no longer there after that component has
 been refactored.

 1.
 Is the messaging now controlled from the Systems Settings -> Messaging
 (by selecting email and/or SMS)? If yes, I presume that means one standard
 comm method for all notifications - and that you cannot turn off internal
 notification messaging...

 2.
 What I'm looking for is the ability to specify internal messaging
 and/or email and/or SMS on a per notification basis.

 For instance, if you send out alerts by email or SMS to get users to
 access the DHIS2 for latest developments, then there is no need to fill up
 the messages list with a copy of the same

 Regards
 Calle

 ***

 Calle Hedberg

 46D Alma Road, 7700 Rosebank, SOUTH AFRICA

 Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>

 Cell: +27-82-853-5352 <+27%2082%20853%205352>

 Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>

 Email: calle.hedb...@gmail.com

 Skype: calle_hedberg

 ***


>>>
>>>
>>> --
>>>
>>> ***
>>>
>>> Calle Hedberg
>>>
>>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>>
>>> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>>>
>>> Cell: +27-82-853-5352 <+27%2082%20853%205352>
>>>
>>> Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>
>>>
>>> Email: calle.hedb...@gmail.com
>>>
>>> Skype: calle_hedberg
>>>
>>> ***
>>>
>>>
>>
>>
>> --
>>
>> ***
>>
>> Calle Hedberg
>>
>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>
>> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>>
>> Cell: +27-82-853-5352 <+27%2082%20853%205352>
>>
>> Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>
>>
>> Email: calle.hedb...@gmail.com
>>
>> Skype: calle_hedberg
>>
>> ***
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to : dhis2-devs@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 

***

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA

Tel/fax (home): +27-21-685-6472

Cell: +27-82-853-5352

Iridium SatPhone: +8816-315-19119

Email: calle.hedb...@gmail.com

Skype: calle_hedberg

***
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] release cycle: from 4 to 3 releases per year

[Lars Helge Øverland]

Hi all,

we would like to let you know that the release cycle for DHIS 2 will be be
shifting from 4 to 3 yearly releases. The upcoming releases look like this:

2.27: June 1, 2017
2.28: October 1, 2017
2.29: February 1, 2018


A few observations led to this change:

- The machinery around DHIS 2 of documentation, academy materials, release
notes, web pages and so on is getting larger and the overhead of updating
it for each release is becoming significant.

- Implementing organizations seem to be lagging a few releases behind the
latest on average in terms of testing and roll-out. This leads to a large
demand for back-porting of fixes and even features, consuming a lot of
developer time.


So by reducing the number of releases by one we hope to reduce the overhead
and free more time for new development. We promise to remain agile and
user-driven in spite of this change.


best regards,

Lars






-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
l...@dhis2.org
http://www.dhis2.org 
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Program notifications - where to specify communication formats?

[Cecilia @dhis2]

Hi Calle,
Great, thanks! In your issue, please specify what you think should be added
for each version separately. The topics explaining program and program
stage notifications are:

- 2.25: https://docs.dhis2.org/2.25/en/user/html/program_notifications.html
- 2.26:
https://docs.dhis2.org/2.26/en/user/html/manage_program_notification.html

Maybe the table in step 6 (program notification) or step 7 (program stage
notification) could help with the understanding of the delivery method?
According to the doc, this functionality has been the same for both 2.25
and 2.26.

Kind regards,
Cecilia
DHIS2 content team



On Fri, Feb 3, 2017 at 10:28 AM, Calle Hedberg 
wrote:

> Cecilia,
>
> Will do so, but I'm hoping to get some clarity first on what these hoodlum
> developers have actually done ;-)
>
> Regards
> Calle
>
> On 3 February 2017 at 10:25, Cecilia @dhis2  wrote:
>
>> Hi Calle,
>> Could you create an issue in JIRA (on project Documentation for DHIS 2
>> ) for the doc changes you would
>> like to see?
>>
>> Thanks!
>> Cecilia
>> DHIS2 content team
>>
>> On Thu, Feb 2, 2017 at 11:39 PM, Calle Hedberg 
>> wrote:
>>
>>> and to be even more specific: the ability to select method (Email/SMS)
>>> for Program notifications are only available in 2.26 -  in 2.25 there is
>>> nothing.
>>>
>>> Regards
>>> calle
>>>
>>> On 3 February 2017 at 00:13, Calle Hedberg 
>>> wrote:
>>>
 Hi,

 Just a brief follow-up: I was reading through the user and developer
 manuals for both program notifications and program stage notifications, but
 I only looked at program stage notifications in the system.

 Now I noticed that

 1.
 In the Program notification configuration form, you can specify SMS
 and/or email (it looks like internal messaging is compulsory?). NOTE THAT
 THIS PART OF THE DEFINITION FORM IS NOT MENTIONED IN THE MANUALS.

 2.
 The same options are NOT included with the program STAGE notifications
 - hence my question above. This type of inconsistency looks like more like
 a bug (omission) than a deliberate design flaw.

 Halvdan is no longer working on the new messaging component - has
 anybody else taken over?

 Regards
 Calle

 On 2 February 2017 at 23:35, Calle Hedberg 
 wrote:

> Hi
>
> I've just looked through the user and developer guides for 2.25 and
> 2.26, but I cannot find any specific reference to how you can control how
> program notifications and program stage notifications are sent.
>
> In 2.24, you could specify at least whether to send notifications as
> SMS, Email or BOTH. That option is no longer there after that component 
> has
> been refactored.
>
> 1.
> Is the messaging now controlled from the Systems Settings -> Messaging
> (by selecting email and/or SMS)? If yes, I presume that means one standard
> comm method for all notifications - and that you cannot turn off internal
> notification messaging...
>
> 2.
> What I'm looking for is the ability to specify internal messaging
> and/or email and/or SMS on a per notification basis.
>
> For instance, if you send out alerts by email or SMS to get users to
> access the DHIS2 for latest developments, then there is no need to fill up
> the messages list with a copy of the same
>
> Regards
> Calle
>
> ***
>
> Calle Hedberg
>
> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>
> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>
> Cell: +27-82-853-5352 <+27%2082%20853%205352>
>
> Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>
>
> Email: calle.hedb...@gmail.com
>
> Skype: calle_hedberg
>
> ***
>
>


 --

 ***

 Calle Hedberg

 46D Alma Road, 7700 Rosebank, SOUTH AFRICA

 Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>

 Cell: +27-82-853-5352 <+27%2082%20853%205352>

 Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>

 Email: calle.hedb...@gmail.com

 Skype: calle_hedberg

 ***


>>>
>>>
>>> --
>>>
>>> ***
>>>
>>> Calle Hedberg
>>>
>>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>>
>>> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>>>
>>> Cell: +27-82-853-5352 <+27%2082%20853%205352>
>>>
>>> Iridium SatPhone: +8816-315-19119 <+881%206%20315%2019119>
>>>
>>> Email: calle.hedb...@gmail.com
>>>
>>> Skype: calle_hedberg
>>>
>>> ***
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-devs
>>> Post to : dhis2-de

Re: [Dhis2-devs] [Dhis2-users] release cycle: from 4 to 3 releases per year

[Antonia - Pro]

wise decision!
I think 2 yearly are also ok.

best regards,
antonia

2017-02-03 10:40 GMT+01:00 Lars Helge Øverland :

> Hi all,
>
> we would like to let you know that the release cycle for DHIS 2 will be be
> shifting from 4 to 3 yearly releases. The upcoming releases look like this:
>
> 2.27: June 1, 2017
> 2.28: October 1, 2017
> 2.29: February 1, 2018
>
>
> A few observations led to this change:
>
> - The machinery around DHIS 2 of documentation, academy materials, release
> notes, web pages and so on is getting larger and the overhead of updating
> it for each release is becoming significant.
>
> - Implementing organizations seem to be lagging a few releases behind the
> latest on average in terms of testing and roll-out. This leads to a large
> demand for back-porting of fixes and even features, consuming a lot of
> developer time.
>
>
> So by reducing the number of releases by one we hope to reduce the
> overhead and free more time for new development. We promise to remain agile
> and user-driven in spite of this change.
>
>
> best regards,
>
> Lars
>
>
>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org 
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] [Bug 1518380] Re: upgrade to 2.21 database error and how we solved it

[evert.bothma]

We have the same issue however this is the error that we get:

java.lang.IllegalArgumentException: Unknown name value [unitInterval] for enum 
class [org.hisp.dhis.common.ValueType]
at 
org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)
at 
org.hibernate.type.EnumType$NamedEnumValueMapper.getValue(EnumType.java:452)
at org.hibernate.type.EnumType.nullSafeGet(EnumType.java:107)


Any ideas how we can fix this?

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1518380

Title:
  upgrade to 2.21 database error and how we solved it

Status in DHIS:
  New

Bug description:
  When changing the dhis.war file from 2.20 to 2.21 we received a database 
error message related to AVG aggregation type.  We could not even go into dhis2 
anymore.
   We solved it by going back to 2.20 restoring the database and doing an 
update sql statement on table  dataelement and setting  aggregationtype  to 
'SUM' after that we did the upgrade again to 2.21 and now it went fine.

  relevant part of the error message was:
  * ERROR 2015-11-20 16:42:02,919 java.lang.IllegalArgumentException: Unknown 
name value [AVG] for enum class [org.hisp.dhis.analytics.AggregationType]
at 
org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)
at 
org.hibernate.type.EnumType$NamedEnumValueMapper.getValue(EnumType.java:452)
at org.hibernate.type.EnumType.nullSafeGet(EnumType.java:107)
 .

  
  Hope this is any usefull

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1518380/+subscriptions

___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-devs] Program notifications - where to specify communication formats?

[Calle Hedberg]

Hi,

Those steps do not relate to the communication channel - only to
recipients. What we would like to control is how each specified program
notification is sent to the recipients: in some cases you want internal
messaging + email + SMS (and in the future Whatsapp, Skype...) - in other
cases you want to use only one or two of these channels.

As an example, if I'm using a program notification as an alert to managers
that a dangerous disease have been reported and they should view the report
(in DHIS) asap - then it might not be relevant to also send that via
internal messaging because that means a user is already in the system and
the same disease notification is already clearly visible in dashboards etc.

We need fine-grained control over
- when to trigger notifications (e.g. when a specific data element value
like a disease is reported)
- whether they might be repeated, and if yes how often or how many times
(nobody wants endless repeating alerts)
- what channels/methods that are used to send them (availability, cost, not
too much duplication)
- who the recipients are

Regards
Calle

On 3 February 2017 at 12:15, Cecilia @dhis2  wrote:

> Hi Calle,
> Great, thanks! In your issue, please specify what you think should be
> added for each version separately. The topics explaining program and
> program stage notifications are:
>
> - 2.25: https://docs.dhis2.org/2.25/en/user/html/program_
> notifications.html
> - 2.26: https://docs.dhis2.org/2.26/en/user/html/manage_
> program_notification.html
>
> Maybe the table in step 6 (program notification) or step 7 (program stage
> notification) could help with the understanding of the delivery method?
> According to the doc, this functionality has been the same for both 2.25
> and 2.26.
>
> Kind regards,
> Cecilia
> DHIS2 content team
>
>
>
> On Fri, Feb 3, 2017 at 10:28 AM, Calle Hedberg 
> wrote:
>
>> Cecilia,
>>
>> Will do so, but I'm hoping to get some clarity first on what these
>> hoodlum developers have actually done ;-)
>>
>> Regards
>> Calle
>>
>> On 3 February 2017 at 10:25, Cecilia @dhis2  wrote:
>>
>>> Hi Calle,
>>> Could you create an issue in JIRA (on project Documentation for DHIS 2
>>> ) for the doc changes you would
>>> like to see?
>>>
>>> Thanks!
>>> Cecilia
>>> DHIS2 content team
>>>
>>> On Thu, Feb 2, 2017 at 11:39 PM, Calle Hedberg 
>>> wrote:
>>>
 and to be even more specific: the ability to select method (Email/SMS)
 for Program notifications are only available in 2.26 -  in 2.25 there is
 nothing.

 Regards
 calle

 On 3 February 2017 at 00:13, Calle Hedberg 
 wrote:

> Hi,
>
> Just a brief follow-up: I was reading through the user and developer
> manuals for both program notifications and program stage notifications, 
> but
> I only looked at program stage notifications in the system.
>
> Now I noticed that
>
> 1.
> In the Program notification configuration form, you can specify SMS
> and/or email (it looks like internal messaging is compulsory?). NOTE THAT
> THIS PART OF THE DEFINITION FORM IS NOT MENTIONED IN THE MANUALS.
>
> 2.
> The same options are NOT included with the program STAGE notifications
> - hence my question above. This type of inconsistency looks like more like
> a bug (omission) than a deliberate design flaw.
>
> Halvdan is no longer working on the new messaging component - has
> anybody else taken over?
>
> Regards
> Calle
>
> On 2 February 2017 at 23:35, Calle Hedberg 
> wrote:
>
>> Hi
>>
>> I've just looked through the user and developer guides for 2.25 and
>> 2.26, but I cannot find any specific reference to how you can control how
>> program notifications and program stage notifications are sent.
>>
>> In 2.24, you could specify at least whether to send notifications as
>> SMS, Email or BOTH. That option is no longer there after that component 
>> has
>> been refactored.
>>
>> 1.
>> Is the messaging now controlled from the Systems Settings ->
>> Messaging (by selecting email and/or SMS)? If yes, I presume that means 
>> one
>> standard comm method for all notifications - and that you cannot turn off
>> internal notification messaging...
>>
>> 2.
>> What I'm looking for is the ability to specify internal messaging
>> and/or email and/or SMS on a per notification basis.
>>
>> For instance, if you send out alerts by email or SMS to get users to
>> access the DHIS2 for latest developments, then there is no need to fill 
>> up
>> the messages list with a copy of the same
>>
>> Regards
>> Calle
>>
>> ***
>>
>> Calle Hedberg
>>
>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>
>> Tel/fax (home): +27-21-685-6472 <+27%2021%20685%206472>
>>
>> C

Re: [Dhis2-devs] dhis version 2.26 is released

[Alex Tumwesigye]

Hi Lars,

Congs Lars and Dev Team.

Alex

On Wed, Feb 1, 2017 at 11:29 AM, Lars Helge Øverland  wrote:

>
> Hi all,
>
> DHIS version 2.26 is out with many new features, apps and improvements.
>
> Log in with admin/district on the demo 
> system.
>
>
> ANALYTICS FEATURES
>
> ---
>
> Enrollment analytics: Program indicators can now utilize a new aspect of
> the analytics engine for program enrollments. This implies that you can
> compare data values and dates from different stages and events within the
> an enrollment. This allows for calculation of indicators such as “average
> inpatient bed days” and “Hemoglobin improvement since first visit”.
>
> Demo  |
> Screenshot
> 
> | Docs
> 
>
>
> Daily relative periods: You can now use daily relative periods in the
> analytics apps. This is particularly useful when looking at aggregate event
> data through the pivot table app, as you can see daily aggregates of
> events, such as today, yesterday, and last 3, 7, 14 days.
>
> Demo 1  | 2
> 
> | Screenshot
> 
>
>
> Data element event clustering in GIS: Using the event layer in the GIS
> app, you can now specify which data element or attribute to use as basis
> for event analytics and clustering. The data item must be of value type
> coordinate. As an example, for a malaria case program, you can have data
> elements of type coordinate for place of infection and household location,
> and visualize those locations on the map for the malaria cases.
>
> Demo
> 
> | Screenshot
> 
> | Docs
> 
>
>
> Pivot table cell background coloring: You can now specify whether to
> color the cell text or cell background of pivot tables based on legend
> sets. This allows e.g. for creating scorecards, where high and low values
> easily can be identified. Go to Pivot table > Options > Legend display
> style.
>
> Demo
>  |
> Screenshot
> 
> | Docs
> 
>
>
> Analytics group sub-hierarchy inclusion: Org unit group sets have a new
> option for including the sub-hierarchy of organisation units in groups when
> aggregating data in analytics apps. This can simplify org unit management
> when there are many org units at the bottom of the hierarchy which should
> all belong to an org unit higher up in the hierarchy. As an example, you
> can create additional hierarchies by grouping all facilities in multiple
> districts together in a group, then assign the new groups to an org unit
> group set.
>
> Demo 1  | 2
> 
> | Screenshot 1
> 
> | 2
> 
> | Docs 1
> 
> | 2 
>
>
> GIS improvements: Labels are positioned smarter on the map to avoid
> collisions. Interactivity on boundary layer is disabled when combined with
> thematic layer. Automatic color scales for thematic maps can be flipped
> (i.e. low to high vs high to low).
>
> Demo
> 
> | Screenshot
> 
>
>
> Most viewed favorites: The opening screen of the pivot table apps now
> displays link to the top 10 most viewed favorites for the current user.
> This provides you with quick access to your most relevant data.
>
> Demo  | Screenshot
> 
>
>
> Expected reports in analytics: In reporting rate analytics in pivots and
> charts, the number of expected reports are always sh

Re: [Dhis2-devs] release cycle: from 4 to 3 releases per year

[Bob Jolliffe]

Lars, has there been any recent discussion over adopting an ubuntu-style
approach of two types of release?

I think a lot of people running large national setups with 1000's of users
would be happy to see a long-term-service release maybe once a year with at
least guaranteed security related backports for maybe two years.  Then
maybe two more bleeding edge releases in the year for those who really need
the latest functionality and have the agility to upgrade frequently.

The numbers above can be different, but I think the idea of two types of
release might have some merit.   I wonder what would be the main arguments
for and against.  We want to continue to release-often-release-early to
maintain momentum.  But also provide some stability.  These aims tend to
work against each other :-)  Anyway I'd be interested to hear what people
think.

On 3 February 2017 at 09:40, Lars Helge Øverland  wrote:

> Hi all,
>
> we would like to let you know that the release cycle for DHIS 2 will be be
> shifting from 4 to 3 yearly releases. The upcoming releases look like this:
>
> 2.27: June 1, 2017
> 2.28: October 1, 2017
> 2.29: February 1, 2018
>
>
> A few observations led to this change:
>
> - The machinery around DHIS 2 of documentation, academy materials, release
> notes, web pages and so on is getting larger and the overhead of updating
> it for each release is becoming significant.
>
> - Implementing organizations seem to be lagging a few releases behind the
> latest on average in terms of testing and roll-out. This leads to a large
> demand for back-porting of fixes and even features, consuming a lot of
> developer time.
>
>
> So by reducing the number of releases by one we hope to reduce the
> overhead and free more time for new development. We promise to remain agile
> and user-driven in spite of this change.
>
>
> best regards,
>
> Lars
>
>
>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org 
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] [Bug 1518380] Re: upgrade to 2.21 database error and how we solved it

[Dan Cocos]

https://www.dhis2.org/221-upgrade your Value Types must match exactly,
case included what is in the Web API / data model changes

Also, please use Jira for issues going forward.

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1518380

Title:
  upgrade to 2.21 database error and how we solved it

Status in DHIS:
  New

Bug description:
  When changing the dhis.war file from 2.20 to 2.21 we received a database 
error message related to AVG aggregation type.  We could not even go into dhis2 
anymore.
   We solved it by going back to 2.20 restoring the database and doing an 
update sql statement on table  dataelement and setting  aggregationtype  to 
'SUM' after that we did the upgrade again to 2.21 and now it went fine.

  relevant part of the error message was:
  * ERROR 2015-11-20 16:42:02,919 java.lang.IllegalArgumentException: Unknown 
name value [AVG] for enum class [org.hisp.dhis.analytics.AggregationType]
at 
org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)
at 
org.hibernate.type.EnumType$NamedEnumValueMapper.getValue(EnumType.java:452)
at org.hibernate.type.EnumType.nullSafeGet(EnumType.java:107)
 .

  
  Hope this is any usefull

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1518380/+subscriptions

___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] Feature roadmap for the next releases

[Vanya Seth]

Hi Devs

Thanks for the 2.26 release and the great features. Congratulations once
again!

Can you please point to the documentation for the upcoming releases? Wanted
to get a sense of features that are lined up for the coming releases.

Thanks for the help.
-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

[Dhis2-devs] Event Reports

[Stanley Kalyati]

How can one select data elements from two different stages in a program in
the same event report?

Thanks

Stanley
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp