As I am sure many others do as well, we are expecting the CHW to enter the
date of the consultation. Since data may be backfilled using the CommCare
mobile client one or more days after the actual consultation, I'm looking
for an easy way to handle the common cases (ie. data entered in near
real-time) as well as the less common cases (ie. data backfilled several
days later). I have something working, and would like to confirm that this
is a reasonable approach.
Here is a snippet of the relevant code, with the calculation highlighted
in bold.
today
yesterday
two_days_ago
other_date
So, is this a reasonable approach to handle this? Is there a better
option? (ie. easier for the CHW)
···
On Mon, Nov 7, 2011 at 10:45 AM, Ray Brunsting wrote:
As I am sure many others do as well, we are expecting the CHW to enter the
date of the consultation. Since data may be backfilled using the CommCare
mobile client one or more days after the actual consultation, I'm looking
for an easy way to handle the common cases (ie. data entered in near
real-time) as well as the less common cases (ie. data backfilled several
days later). I have something working, and would like to confirm that this
is a reasonable approach.
Here is a snippet of the relevant code, with the calculation highlighted
in bold.
today
yesterday
two_days_ago
other_date
So, is this a reasonable approach to handle this? Is there a better
option? (ie. easier for the CHW)
Yeah, this definitely seems like the right plan to me. Thanks for sharing
with the list, I imagine this will be helpful to others trying to address
similar problems.
-Clayton
···
On Mon, Nov 7, 2011 at 10:54 AM, Drew Roos wrote:
looks good to me.
definitely needs more parenthesis, though
On Mon, Nov 7, 2011 at 10:45 AM, Ray Brunsting ray@tula.org wrote:
As I am sure many others do as well, we are expecting the CHW to enter
the date of the consultation. Since data may be backfilled using the
CommCare mobile client one or more days after the actual consultation, I'm
looking for an easy way to handle the common cases (ie. data entered in
near real-time) as well as the less common cases (ie. data backfilled
several days later). I have something working, and would like to confirm
that this is a reasonable approach.
Here is a snippet of the relevant code, with the calculation
highlighted in bold.
today
yesterday
two_days_ago
other_date
So, is this a reasonable approach to handle this? Is there a better
option? (ie. easier for the CHW)