dhis2-users team mailing list archive

[Rodolfo Melia <rmelia@xxxxxxxxxxxx>]

Hi Everyone - I write on behalf of PSI (www.psi.org). We are implementing
across 30+ countries (only 5 countries live so far), all from a single
server. We have a couple of high level requirements that we would like to
share.

*1. Make Aggregate and SEwoR Smart-mobile web forms (current ones)
accessible to an App by enabling a URL Query String (or other procedure) *to
open Data Entry form on specific OU, DataSet/ Program Stage, Period/ Date.
An example will be an app for Sales, which helps the user to find the
correct outlet (OU). Then when the user selects 'add new sale' the app
should be able to pass control to the standard SEwoR form of the mobile
interface, and the user can complete the information on the standard mobile
form. On submit control gets back to the app. *2. Aggregate and SEwoR
CUSTOM form can be called from an app* - URL Query String (or similar
procedure) to open Data Entry CUSTOM form on specific OU, Period - this
will work particularly well for Tablets
Similar to request 1, we would like to be able to pass control from an APP
to a custom form which can contain all kind of JScript logic. Once the form
is completed, the control is passed back to the app. Obviously the custom
form will need to be designed targeting a particular device because space
and compatibility. *3. Allow selection of form first* (Program Stage or
Aggregated DataSet), rather than OU first.
Currently the mobile UI ask you to select the OU first (explicit to the
user) > Form > Period.
We would like: Form > OU (as available to form + User)> Period *4. Official
support to Android app* (which actually provide True Offline data capture)
*5.* Very Low priority, and it should probably wait until tracker is
redesigned: Support for MEwR on Smart Phone (low priority)


*Rodolfo, on behalf of PSI MIS group*


On Wed, Jan 29, 2014 at 4:33 PM, Peder Andreas Nergaard <andreasn@xxxxxxxxxx
> wrote:

>  All,
>
> In the last half of February we will plan the development on DHIS2 Mobile
> for the next few months. We are also expanding the mobile development team
> with senior developers, and we have new master students who will contribute
> to the mobile project. To make sure our development has the maximum impact,
> we need high quality requirements from the community.
>
> This is an invitation to present your *requirements for mobile
> functionality*, including SMS, J2ME, smartphone and mobile browser
> clients for both Tracker and aggregated data. To make sure we have as much
> as possible on the table when we do our planning, we have set a *deadline
> of February 15th* for requirements to be discussed in this round.
>
> To facilitate an open discussion around the requirements, and to allow
> everyone to learn from and be inspired by others, I would like you to
> respond to this thread in the *dhis-mobile@xxxxxxxxxxx
> <dhis-mobile@xxxxxxxxxxx>* mailing list with your requirements. If you do
> not feel comfortable with this, you can send them directly to me, and I
> will anonymise them and post them for you. I would also encourage the
> community to respond to the requirements of others, and to discuss openly
> to achieve maximum value.
>
> *Your requirements should include*:
> - Relevant setting and project
> - A short description of what you wish to accomplish - and why
> - Textual descriptions of key use cases
> - Example input and output data for the feature
> - Urgency and priority - do you need this now or long-term.
>
> We will then take it on ourselves to formalise and generalise the
> requirements. We will hold a *priority discussion call the last week of
> February* where we will let the community give feedback, and expect to be
> able to present a road map for mobile in early March.
>
> Topics that have already been mentioned are:
> - SMS feedback and automated sending of indicators
> - SMS reminders
> - Tracker clients after 2.14/2.15 version changes
> - Anonymous user features in tracker
> - Org units, roles and phone numbers
> - Error scenarios and better user feedback
> - Usability issues
>
> Some of these are already mentioned from several sources, which makes them
> higher priority. So feel free to bump other people's requirements!
>
> Cheers,
>
> _Andreas_
>
> --
> 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/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>