Re: [Dhis2-devs] LAST AGGREGATION OPERATIONS

2018-04-28 Thread Adebusoye Anifalaje 
Hi John,

I had the same issue as you described and just concluded it was not yet 
supported at the data element definition level. 


Cheers. 
- -




Busoye Anifalaje (PhD)
Director of Services (Principal), BAO Systems
UK: +44 7901-740-757 | US: +1 682-307-0986|
 bus...@baosystems.com  | 
http://www.baosystems.com  |
Skype: busoye | 2900 K Street, Suite 406, Washington D.C. 20007

> On 28 Apr 2018, at 10:37, John Mukulu  wrote:
> 
> Hello everyone,
> 
> Has anyone tried the LAST aggregation operations for data elements in 2.29? 
> 
> Seems like impossible to create dataelements of such type and save them, and 
> if you bypass web interface with direct api posts or changing operator 
> directly on the database with query, analytics would complain of unsupported 
> aggregation operator(LAST)
> 
> Is this available in backend analytics or its just a front end feature of 
> pivot, I believe I'm missing something and it may not be a bug that needs 
> filing in JIRA.
> 
> 
> John Francis Mukulu
> Software Architect, HISPTZ
> http://hisptanzania.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] LAST AGGREGATION OPERATIONS

2018-04-28 Thread John Mukulu 
Hello everyone,

Has anyone tried the LAST aggregation operations for data elements in 2.29?

Seems like impossible to create dataelements of such type and save them,
and if you bypass web interface with direct api posts or changing operator
directly on the database with query, analytics would complain of
unsupported aggregation operator(LAST)

Is this available in backend analytics or its just a front end feature of
pivot, I believe I'm missing something and it may not be a bug that needs
filing in JIRA.


John Francis Mukulu
Software Architect, HISPTZ
http://hisptanzania.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] DHIS2 Dashboard Apps

2018-04-28 Thread John Mukulu 
These are very interesting topics,

Just weigh in on few of the issues raised.

1. Way of widgets identifying themselves, this is actually supposed to be
for all apps, to sort of have unique-app-id that'll unique like android
apps, so names and version can change but it'll stay the same, this is on
jira but not implemented yet, would help tracking and triggering of widgets
and their counterparts apps

2. Explore and going full screen limitations, at the moment, there's no
such features, explore simply opens the same widget iframe in separate
page, with scorecard we had to write widget that's actually a fully fledged
widget, so on explore we'd check if it's separate page to give you
impression of full app and impression of just a widget on small page, but
above features would definitely solve this

3. Access to global selections, at the moment iframe loaded apps have not
been provided with means of accessing anything outside, because they're
essentially brand new page running as subpage, standards could be put such
that global filters could pass selections to the iframe url of the app and
trigger reload(or abandon iframe idea all together and persue much better
one! Think web components and custom elements)

4. Rendering on native mobile apps(android & iOS), because widget are
stand-alone pages but still using utilizing same page sessions cookies and
page header contents, they are presented as a fake new page trying to
impersonate other page, this pause a security dilemma and often forces
nginx to allow such except for browser, but never torelated on native
mobile and hence never working there.

Most of these concepts are already in past jira issues awaiting priority to
be picked up, but should you have interesting in innovating there, three
major things to solve

1. Abandoning iframe in favor of web components (but keeping airframe
simplicity of integration) - solve global filters accesibility and other in
memory info, solve security for android, allow distinction of states(full
or widget)

2. Add app property in manifest for appid and make app urls use app ids
with support for accepting more parameters

3. Add property in widget for corresponding appids for widgets to allow
explore by reference to apps or prompting install when absent(app id would
guarantee this)

HISP Tanzania can help further brainstorming and potential solutions, let
me know if you're embarking on this.

And Sorry for long paragraphs!

John Francis Mukulu
Software Architect, HISPTZ
http://hisptanzania.org/


On Fri, Apr 27, 2018, 15:53 Martin Van Aken  wrote:

> Thanks for your answer - any way to specify where the "explore" link
> should lead:
>
>
> this would allow my app to show a small part as an iFrame, then be called
> in full screen on click (like the Pivot tables & chart works in the
> Dashboard right now)
>
> Martin
>
> On Fri, Apr 27, 2018 at 10:47 AM, Edoardo Sabadelli 
> wrote:
>
>> Not exactly, the content in the iframe is usable from within the box
>> in the dashboard.
>> There isn't a way of going full screen at the moment, but it can be
>> easily added.
>>
>> On Thu, Apr 26, 2018 at 5:21 PM, Martin Van Aken
>>  wrote:
>> > OK, so it will render the "main" page (as refered in the manifest) as an
>> > iframe there, with clicking on it leading to the "full page" app,
>> correct ?
>> > This being said, looks like something I could test easily.
>> >
>> > Martin
>> >
>> > On Thu, Apr 26, 2018 at 11:28 AM, Edoardo Sabadelli 
>> > wrote:
>> >>
>> >> Hi Martin,
>> >>
>> >> the dashboard widgets/apps, listed under the Apps section in the
>> >> dashboard item selector, are rendered in the same way as before.
>> >> They are loaded in an iframe in a box added to the dashboard grid.
>> >> This is also to ensure existing apps can still work in the new
>> Dashboards
>> >> app.
>> >>
>> >> As for distinguishing between a full screen and a "widget" app, there
>> >> isn't anything in place as far as I know.
>> >>
>> >> One way is to use a responsive layout in your app, to ensure the
>> >> content fits and is usable in both full screen and the small widget
>> >> box.
>> >>
>> >> I didn't work with widget apps, so hopefully someone in the community
>> >> who has done that can help.
>> >>
>> >> Cheers,
>> >>
>> >> On Thu, Apr 26, 2018 at 10:35 AM, Martin Van Aken
>> >>  wrote:
>> >> > Hi!
>> >> > We've been working with DHIS2 Apps for a while now, and found the
>> >> > general
>> >> > experience (as developers) pretty good with the d2 + React combo.
>> >> > Something
>> >> > I could not find info about is how the different kind of apps change,
>> >> > especially the DASHBOARD_WIDGET one - does that means that an app of
>> >> > this
>> >> > kind will be rendered as a box in the main view? If so, how to
>> specify
>> >> > the
>> >> > part that should go there vs for example a full sized page after once
>> >> > clicked?
>> >> >
>>

Re: [Dhis2-devs] [Dhis2-users] API for Patch dataSet and dataelement

2018-04-28 Thread stepho...@gmail.com 
Hi, try chanding the payload anf use dataSetElements instead of dataElements.

Also ensure you are using POST if you are adding dataElements to datasets.

Regards.

Sent from my HTC

- Reply message -
From: "Jean Habib" 
To: "Stephen Ocaya" 
Cc: "DHIS 2 Users list" , "DHIS 2 Developers 
list" 
Subject: [Dhis2-users] API for Patch dataSet and dataelement
Date: Sat, Apr 28, 2018 01:09

HI Ocaya for your reply.
But I got this error 
{
    "httpStatus": "Conflict",
    "httpStatusCode": 409,
    "status": "ERROR",
    "message": "Only identifiable object collections can be removed from."
}

What can be issue ?


2018-04-27 20:23 GMT+00:00 Stephen Ocaya :
Hi, You might want to look at this documentation. This is a generic metadata 
update that you can make using the API for any metadata.
You will have to prepare your payload for dataElements as below:- where id is 
UID of existing dataElements and hit the endpoints using a comand like below

1. Prepare the Payload



{
"dataElements": [
{ "id": "ID1" },
{ "id": "ID2" },
{ "id": "ID3" }
]
}

2. Make the Call to the Endpoints



curl -d @dataelements.json "http://server/api/26/dataSets/UID/dataSetElements; 
-X POST -H "Content-Type: application/json" -u user:password



https://docs.dhis2.org/2.28/en/developer/html/dhis2_developer_manual_full.html#webapi_adding_removing_objects_collections

regards


On Fri, Apr 27, 2018 at 8:45 PM, Jean Habib  wrote:

Hi all, 
Please there is a way to add dataeelement to dataset by API, like partial 
update ?

Best 



___

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





-- 
Stephen Ocaya
Health Information Systems Advisor,
Mobile: +256774558980 | +256752712007
SkypeID: stephocay











Strategic Information Systems for Actions
Plot 36 Impala Avenue, Kololo
P.O. Box 4750, Kampala___
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] [Dhis2-users] API for Patch dataSet and dataelement

2018-04-28 Thread stepho...@gmail.com 
Hi, try chanding the payload anf use dataSetElements instead of dataElements.

Also ensure you are using POST if you are adding dataElements to datasets.

Regards.

Sent from my HTC

- Reply message -
From: "Jean Habib" 
To: "Stephen Ocaya" 
Cc: "DHIS 2 Users list" , "DHIS 2 Developers 
list" 
Subject: [Dhis2-users] API for Patch dataSet and dataelement
Date: Sat, Apr 28, 2018 01:09

HI Ocaya for your reply.
But I got this error 
{
    "httpStatus": "Conflict",
    "httpStatusCode": 409,
    "status": "ERROR",
    "message": "Only identifiable object collections can be removed from."
}

What can be issue ?


2018-04-27 20:23 GMT+00:00 Stephen Ocaya :
Hi, You might want to look at this documentation. This is a generic metadata 
update that you can make using the API for any metadata.
You will have to prepare your payload for dataElements as below:- where id is 
UID of existing dataElements and hit the endpoints using a comand like below

1. Prepare the Payload



{
"dataElements": [
{ "id": "ID1" },
{ "id": "ID2" },
{ "id": "ID3" }
]
}

2. Make the Call to the Endpoints



curl -d @dataelements.json "http://server/api/26/dataSets/UID/dataSetElements; 
-X POST -H "Content-Type: application/json" -u user:password



https://docs.dhis2.org/2.28/en/developer/html/dhis2_developer_manual_full.html#webapi_adding_removing_objects_collections

regards


On Fri, Apr 27, 2018 at 8:45 PM, Jean Habib  wrote:

Hi all, 
Please there is a way to add dataeelement to dataset by API, like partial 
update ?

Best 



___

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





-- 
Stephen Ocaya
Health Information Systems Advisor,
Mobile: +256774558980 | +256752712007
SkypeID: stephocay











Strategic Information Systems for Actions
Plot 36 Impala Avenue, Kololo
P.O. Box 4750, Kampala___
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