Hi Jose and Morten,
Since we are relying on display[*] properties in SDK and android apps, we
will get translations as soon as api support will be there (if you are
running 2.24, it should not be a problem any more).
Best regards,
—
Araz Abishov,
Android developer, DHIS 2
University of Oslo
http
Hi Morten,
great that you guys have decided to version the API really important when
you do changes that are not backwards compatible. Just some questions.
- In DHIS 2.24 will you keep the API version 23?
- Are all endpoints versioned? I'm trying to use
http://localhost:8085/api/23/dataElements a
>
> - In DHIS 2.24 will you keep the API version 23?
>
Yes, the plan is to keep 3 versions available, for 2.24 /api/23 and /api/24
is available, for 2.25 we will add /api/25, and for 2.26 we will add
/api/26 and remove /api/23
> - Are all endpoints versioned? I'm trying to use
> http://localhost
Version:
2.23
Build revision:
22991
Build date:
2016-06-10 17:48
On Tue, Jun 14, 2016 at 10:20 AM Morten Olav Hansen
wrote:
> - In DHIS 2.24 will you keep the API version 23?
>>
>
> Yes, the plan is to keep 3 versions available, for 2.24 /api/23 and
> /api/24 is available, for 2.25 we will add /
Hi Paulo,
See Morten's note..
*All works on latest trunk*
Regards,
Jason
On Tue, Jun 14, 2016 at 10:29 AM, Paulo Grácio
wrote:
> Version:
> 2.23
> Build revision:
> 22991
> Build date:
> 2016-06-10 17:48
>
> On Tue, Jun 14, 2016 at 10:20 AM Morten Olav Hansen
> wrote:
>
>> - In DHIS 2.24 wil
Ah, ok.. so in 2.23, only /api/23/metadata endpoint is versioned.. nothing
else, everything will be part of 2.24
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Tue, Jun 14, 2016 at 3:29 PM, Paulo Grácio wrote:
> Version:
> 2.23
> Build revision:
> 2299
Ok, thanks for the clarification.
Can I use this war to build a docker image to run system tests?
https://www.dhis2.org/download/releases/trunk/dhis.war
BR,
Paulo
On Tue, Jun 14, 2016 at 10:33 AM Morten Olav Hansen
wrote:
> Ah, ok.. so in 2.23, only /api/23/metadata endpoint is versioned.. no
Yes, that should be fine
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Tue, Jun 14, 2016 at 3:36 PM, Paulo Grácio wrote:
> Ok, thanks for the clarification.
>
> Can I use this war to build a docker image to run system tests?
> https://www.dhis2.org/do
Ok, works fine with that version. Not sure if you guys are using Docker but
if you are some images can be found here
https://hub.docker.com/r/pgracio/dhis2-web/tags/
Thanks,
Paulo
On Tue, Jun 14, 2016 at 10:55 AM Morten Olav Hansen
wrote:
> Yes, that should be fine
>
> --
> Morten Olav Hansen
>
Hi Paulo
I have made a few changes to trunk and 2.23 which might help you. That
said, there are still a few cases where deletion will not be allowed.
You could also try to simple disable the user, so they are not allowed to
login.
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
Hi Morten,
As we continue with the development of the integration tetss, part of it
will be to determine what is the expected response to certain operations.
Maybe the fixes will not lead to a 500, or maybe that would be the expected
response. Maybe a 403 or something would be better than a 500, i
Hm, a 403 (Forbidden) makes it seem like the user is trying to do something
he should not be allowed. I think 500 is fine in this case, as it signals
an internal server error.
Probably we should be better at catching these exception, and returning
some kind of message to the user (not just 500 int
Hi Morten,
We discussed by chat, but just for the benefit of others and to be sure
that the test seems reasonable. The scenario is that when users which
cannot be deleted for various reasons (like associated with this object or
that object) cannot be deleted, the server returns something like
500
Hi,
We are running a TB patient tracker on dhis2.21 version and we would like
the system to support continuum of care and data capturing wherever the
patient go and also help to control movement of patients and lost to follow
up.
we have set the user role of the data managers with the following
Hi,
maybe I'm missing something but, just one more question, is there any
situation where we can delete a user?
If not maybe we can return 403 - Method Not Allowed, once DELETE is not
supported by User resource.
/Paulo
On Tue, Jun 14, 2016 at 12:56 PM Jason Pickering <
jason.p.picker...@gmail.
Hi Morten
Supporting API versioning is great but why do we want to get rid of the
previous versions as you explained in your email.
Well the whole point of supporting versioning is to let people continue to
use the older versions without the fear of breaking anything.
I can understand that we migh
Hi Lars
For the starters, there is a setting which needs to be enabled for Metadata
versioning (also highlighted in the first email that I sent). So, only if
this setting is enabled and there are actual versions in your DB (there is
a separate relation called "metadataversion" for the same) will a
On Tue, Jun 14, 2016 at 2:56 PM, Vanya Seth wrote:
> Hi Lars
>
> For the starters, there is a setting which needs to be enabled for
> Metadata versioning (also highlighted in the first email that I sent). So,
> only if this setting is enabled and there are actual versions in your DB
> (there is a
Hi Morten,
We are doing Anonymous Event data push. As part of that we are also sending
coordinates.
Coordinate object has 4 public properties which are listed below
@JsonProperty( required = true )
@JacksonXmlProperty( isAttribute = true )
public Double getLatitude()
@JsonProperty( required = t
Thanks Abyot ! - will test and get back to you if we have any problems.
*Rodolfo Meliá*
*Principal | *rme...@knowming.com
Skype: rod.melia | +44 777 576 4090 | +1 708 872 7636
www.knowming.com
On 12 June 2016 at 13:09, Abyot Asalefew Gizaw wrote:
> Hi,
>
> A fix is committed for this. Rev
Public bug reported:
Found in v2.22, using Chrome / IE / Firefox browsers.
When including an individual program indicator in reports, it displays
fine. However if you select all at the same time with the >> button, the
report will display as blank. If you select each indicator (either
individuall
Is this the pivot table app?
** Changed in: dhis2
Milestone: None => 2.24
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1592439
Title:
Adding all program indicators to a report at once disp
Hi
We usually turn off most of that Jackson auto discovery magic, I see we
haven't done that properly in Jackson*, I will add
that now (so it follows JacksonUtils, RenderService etc)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Tue, Jun 14, 2016 at 8:
Hi Vanya
It's not so much that we have to / want to remove older versions, it just
that we can't guarantee more than a few APi versions. Remember that we also
are not using DTOs yet, so within a few versions, there are bound to be
incompatibilities in the payloads. Discussions about DTOs are still
Hi Morten
That would be great. Please let us know when you commit the changes. We ll
take a merge from the trunk.
Regards
Vanya
On Wed, Jun 15, 2016 at 9:01 AM, Morten Olav Hansen
wrote:
> Hi
>
> We usually turn off most of that Jackson auto discovery magic, I see we
> haven't done that proper
Adding DTO layer makes sense :). It will simplify stuff.
But unless you are looking at versioned DTO's itself, I am not sure how
long a way this might help you with versioning support.
Regards
Vanya
On Wed, Jun 15, 2016 at 9:04 AM, Morten Olav Hansen
wrote:
> Hi Vanya
>
> It's not so much that
Already done :)
--
Morten Olav Hansen
Senior Engineer, DHIS 2
University of Oslo
http://www.dhis2.org
On Wed, Jun 15, 2016 at 11:50 AM, Vanya Seth
wrote:
> Hi Morten
>
> That would be great. Please let us know when you commit the changes. We ll
> take a merge from the trunk.
>
> Regards
> Vany
Well, there is already the case of metadata, where /api/metadata returns a
different import report than /api/{23,24}/metadata, it will make those kind
of changes easier (we have a few places where we wanted to clean up status
codes etc, which we could not do as it would break apps)
To have true ve
Hi Lars,
We are using log4j.properties file instead of 'Log4JLogConfigInitializer'
for metadata sync logging purpose. The FILE parameter of FileAppender in
log4j.properties needs the value of DHIS2_HOME environment variable to save
the metadata sync log in the same folder location as that of the o
Hi
I see you are changing some properties, I guess this is moving from one
version of DHIS to another version?
If you are using 2.23 or newer, you can also do simple data set / program
export using the new metadata endpoint:
http://dhis2.github.io/dhis2-docs/master/en/developer/html/ch01s13.html#
30 matches
Mail list logo
