dhis2-devs team mailing list archive

[Ola Hodne Titlestad <olati@xxxxxxxxxx>]

Hi,

Anything to learn/reuse from OMRS when it comes to offline data entry and
synching with server? (see email below).

"Semi-online" data entry is much needed in online user environments where
the Internet connection is unstable and data entry is sometimes better done
in bulk jobs offline + a synch with server when the connection is available
(and the cost of installing a full offline DHIS as a backup solution is too
high). This issue has come up in Kenya.

To me the easiest and most short term solution seems to be Excel data entry
offline (in restricted and standardised worksheets) and then import to
server using e.g. transforms to DXF. If there is something to reuse from
OMRS, that might speed up the process of developing a more sophisticated
solution.

What do you think?

Ola,

----------------------------------
Ola Hodne Titlestad (Mr)
HISP
Department of Informatics
University of Oslo

Mobile: +47 48069736
Home address: Vetlandsvn. 95B, 0685 Oslo, Norway. Googlemaps
link<http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Vetlandsvn.+95B,+0685+Oslo,+Norway>


---------- Forwarded message ----------
From: Ben Wolfe <ben@xxxxxxxxxxx>
Date: 23 November 2010 16:42
Subject: Re: [OPENMRS-IMPLEMENTERS] x-forms and remote formentry module
To: openmrs-implement-l@xxxxxxxxxxxxxxxxxx


If xforms was sending into the same infopath/xml/forms queue, then yes, it
will work with RFE.  RFE just works by turning off the scheduled processor
at the remote sites, moving the xml to central and doing preprocessing
before just dumping the xml into the form queue with everything else on
central.

If you made it an option of how to process the forms (with the default as
you are doing now: immediate) you could make this compatible.
Ben


On Tue, Nov 23, 2010 at 10:29 AM, Daniel Kayiwa <kayiwadaniel@xxxxxxxxx>wrote:

>
> Hi Ben,
>
> Originally, the xforms module worked like the formentry module by
> submitting the xml (which is exactly the same as that submitted by infopath
> forms) in a queue on the file system, which was later processed by a
> scheduled task.
> I just turned it off because users wanted to see the submitted data
> immediately without having to wait for when the task would run and also
> wanted to be immediately notified of any submission errors without having to
> checking the error queue.
>
> So i turned the queuing off, do you think it is worth (optionally) turning
> it back on?
> And if i did, would it work with the remote formentry module?
>
>
>
> On Tue, Nov 23, 2010 at 5:03 PM, Ben Wolfe <ben@xxxxxxxxxxx> wrote:
>
>> No, remoteformentry was designed to cache/send/sync the xml submitted by
>> the formentry module.
>>
>> You should be able to use the sync module with xforms now though:
>> http://wiki.openmrs.org/display/docs/Sync+Module (as of xforms v 3.9.6:
>> See release notes on http://wiki.openmrs.org/display/docs/XForms+Module ,
>> thanks Daniel!)
>>
>> Ben
>>
>>
>> On Tue, Nov 23, 2010 at 8:24 AM, Maurice Barasa <barazam@xxxxxxxxx>wrote:
>>
>>> Hi Ben,
>>>
>>> Can remote formentry module be used when entering data in xforms?
>>>
>>> Regards
>>>
>>> --
>>> *Maurice Barasa*
>>> ------------------------------
>>> Click here to unsubscribe<LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-implement-l>from OpenMRS Implementers' mailing list
>>
>>
>> ------------------------------
>> Click here to unsubscribe<LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-implement-l>from OpenMRS Implementers' mailing list
>>
>
>
>
> --
> If we keep uppermost in our minds the unkind and unjust acts of others, we
> shall find it impossible to love them as Christ has loved us; but if our
> thoughts dwell upon the wondrous love and pity of Christ for us, the same
> spirit will flow out to others.
>
> ------------------------------
> Click here to unsubscribe<LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-implement-l>from OpenMRS Implementers' mailing list
>

------------------------------
Click here to unsubscribe<LISTSERV@xxxxxxxxxxxxxxxxxx?body=SIGNOFF%20openmrs-implement-l>from
OpenMRS Implementers' mailing list