dhis-mobile-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Araz,
Thanks for your inputs. These specific issues were related to the
smartphone app (HTML5) of DHIS2, not the native android client. For various
reasons, we were not able to use your app here for one deployment, although
we are keen to do so in the future.

As for the persistent login, we cannot get it to work, even if we update to
the latest version. Not sure what the problem could be?

As for (6), it is a bit of a corner case I think, but the idea is that
people may have multiple roles. Sort of like, having multiple gmail
accounts, and being able to swtich between these. It is likely not very
common, but here (as was detailed in the mail) we have EHTs (Enviornmental
Health Technicians) who report to different ministries with different
datasets, both of whom are using DHIS2, but on different servers.

Best regards,
jason





On Wed, Feb 5, 2014 at 7:38 PM, Araz Abishov <araz.abishov.gsoc@xxxxxxxxx>wrote:

> Hi Jason,
>
> Currently I'm dev of android app - Data capture for DHIS2. (Maybe there is
> another project?)
> Regarding suggestions you've posted:
>
>
>
> 1) PIN-based authentication for smartphone client
>
> Something like on mobile java app? Where you have to set pin after first
> auth?
>
>
> 2) Persistent sessions on smartphone client
>
> It is implemented feature and we have already discussed that earlier. I
> don't understand why current implemetation doesn't fit your needs.
>
>
> 3) Linkage between visualizer and data capture clients on smartphone, so
>> no need for separate apps
>
> Looking forward to implement this feature)
>
> 4) Android widget for visualizer - or make the current Android visualizer
>> persist to make access to data simple for people like Chief Macha.
>
> As data visualization will be implemented generally, it won't be a problem
> to implement.
>
>  5) Access to URL on Java client.
>
> 6) Some way to access multiple instances from one Java client.  Use case:
>> we are trying ..
>
> As I understood this is related to server side implemenation?
>
>
>
>
>
>
>
> On Tue, Feb 4, 2014 at 2:38 PM, Peder Andreas Nergaard <
> andreasn@xxxxxxxxxx> wrote:
>
>>  Thanks, Jason, this is good stuff.
>>
>> I am sure we will have some follow-up questions for you.
>>
>> Br,
>>
>> _Andreas_
>>
>>
>> On 04. feb. 2014 11:34, Jason Pickering wrote:
>>
>> Dear Mobile Developers,
>> As a follow up to your request for new functionality, here are a few
>> issues which we would like to see addressed here in Zambia. These came from
>> Akros, who is managing several big implementations here in Zambia.
>>
>>  Best regards,
>> Jason
>>
>>
>>
>>
>> 1) PIN-based authentication for smartphone client
>>
>>  I realize that this may not be directly the mobile devs which are
>> working on the Android client, but not really sure who is managing this
>> process with the Android app developer?
>>
>> 2) Persistent sessions on smartphone client
>> Login once, and forget having to login again (sort of like facebook).
>>
>>  3) Linkage between visualizer and data capture clients on smartphone,
>> so no need for separate apps
>>
>> 4) Android widget for visualizer - or make the current Android visualizer
>> persist to make access to data simple for people like Chief Macha.
>>
>>  5) Access to URL on Java client.
>>
>>  Not sure why this was taken away, but we often train people on once
>> instance, and then swtich them to a production instance later. This is
>> troublesome with the current client.
>>
>>  6) Some way to access multiple instances from one Java client.  Use
>> case: we are trying to build a cadre of  Community health wokers
>> (CHWs)/Community Champions that feed data through to multiple ministries.
>>  Ministry of Health (MOH) gets the malaria data,  Ministry of Local
>> Government (MLGH) gets sanitation data, etc.  If we could have a wrapper
>> app that allows CHWs to select which capacity they are serving in (i.e.,
>> MLGH or MOH), then upon selection the appropriate java client opens with
>> the corresponding URL.  Otherwise, we will have multiple phones per CHW
>> which doesn't make a great deal of sense.  I have thought this through and
>> don't think it can be managed on the server side.  In the field, EHTs have
>> to report to at least two different ministries: MLGH and MOH.  Unless we
>> can convince both to use the same server instance, which seems unlikely, we
>> need to manage it from the client side.
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis-mobile-devs
>> Post to     : dhis-mobile-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis-mobile-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> --
>> Peder Andreas Nergaard, Mobile Coordinator
>> HISP/DHIS2, Department of Informatics, University of Oslohttp://www.dhis2.org/
>> p: +47 922 47 500 - s: peder.andreas.nergaard - e: andreasn@xxxxxxxxxx
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis-mobile-devs
>> Post to     : dhis-mobile-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis-mobile-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>