We are using your API to get data into our application and are facing a bit
of a challenge standardizing the data that we get from the commcare server.
Please note that We are only acquainted with the commcare api and not with
the application itself. Sorry for that.
Could someone shed some light on this bit of data that we get from the API
···
-
case:
{
@case_id: "f519350c-a3b4-490b-9702-132c70fcca3e",
@date_modified: "2015-06-26T08:05:11.189000",
@user_id: "a91de07e8e536daba8d1db2c28efa16d",
Is this[@case_id] some kind of standard field across all forms?
Also, can a field be fixed in the application that will always reflect in
the API? What is the general procedure/guideline to do that?
If a form creates or updates a case it will have a case ID for the case it
is updating.
Typically the case ID will be where you've identified, though not always
(e.g. if the application is updating parent cases).
What are you trying to accomplish with the API?
thanks,
Cory
···
On Tue, Aug 4, 2015 at 12:36 PM, harsh atal wrote:
Hi Friends
We are using your API to get data into our application and are facing a
bit of a challenge standardizing the data that we get from the commcare
server.
Please note that We are only acquainted with the commcare api and not with
the application itself. Sorry for that.
Could someone shed some light on this bit of data that we get from the API
case:
{
@case_id: "f519350c-a3b4-490b-9702-132c70fcca3e",
@date_modified: "2015-06-26T08:05:11.189000",
@user_id: "a91de07e8e536daba8d1db2c28efa16d",
Is this[@case_id] some kind of standard field across all forms?
Also, can a field be fixed in the application that will always reflect in
the API? What is the general procedure/guideline to do that?
We are fetching the form data and putting it into our application. The
problems that is coming is that forms have to be grouped by a field (we
use this grouping to import these forms into our app). case_id is doing
that grouping for us but we have found that it changes with the user. i.e.
for the same kind of form its value is different. Is there some way by
which this can be fixed for a group of forms? We are unable to import the
data due to this issue. We are getting different case_id for the same kind
of forms.
We want to do this in a dependable way i.e. have a consistent case_id for a
group of forms.
How do we want to group these forms?? Like this -
Based on the choice of the commcare app user i.e. the user should select
this field - “which facility?” and against the value of that field we
group these forms - so can we use case_id here??
Also - I recommend you create a quick app yourself in CommCare to
familiarize yourself with just a few questions and case loading / saving to
get a sense of the data you can expect from the API.
thanks,
Jonathan
Jonathan L. Jackson
Chief Executive Officer
Dimagi, Inc | 585 Massachusetts Ave | Suite 3 | Cambridge, MA 02139
t: (617) 649 2214 | m: (617) 596 6243
web: http://www.dimagi.com/
···
On Tue, Aug 4, 2015 at 7:10 AM, Cory Zue wrote:
Hey,
Cases are used to link forms together.
If a form creates or updates a case it will have a case ID for the case it
is updating.
Typically the case ID will be where you've identified, though not always
(e.g. if the application is updating parent cases).
We are using your API to get data into our application and are facing a
bit of a challenge standardizing the data that we get from the commcare
server.
Please note that We are only acquainted with the commcare api and not
with the application itself. Sorry for that.
Could someone shed some light on this bit of data that we get from the
API -
case:
{
@case_id: "f519350c-a3b4-490b-9702-132c70fcca3e",
@date_modified: "2015-06-26T08:05:11.189000",
@user_id: "a91de07e8e536daba8d1db2c28efa16d",
Is this[@case_id] some kind of standard field across all forms?
Also, can a field be fixed in the application that will always reflect in
the API? What is the general procedure/guideline to do that?
I second Jonathan's recommendation. You will need to understand both the
CommCare data model as well as the application you are working with in
order to understand how to group things.
It sounds like maybe you want to group by the answer to the "which
facility" question which should have a question ID in the form, but again,
I think the best path to understanding what to do is through getting an
understanding of the system you are working with.
Cory
···
On Tue, Aug 4, 2015 at 2:24 PM, harsh atal wrote:
Hey Cory ,
Thanks for your reply.
This is what we are trying to do -
We are fetching the form data and putting it into our application. The
problems that is coming is that forms have to be grouped by a field (we
use this grouping to import these forms into our app). case_id is doing
that grouping for us but we have found that it changes with the user. i.e.
for the same kind of form its value is different. Is there some way by
which this can be fixed for a group of forms? We are unable to import the
data due to this issue. We are getting different case_id for the same kind
of forms.
We want to do this in a dependable way i.e. have a consistent case_id for
a group of forms.
How do we want to group these forms?? Like this -
Based on the choice of the commcare app user i.e. the user should select
this field - “which facility?” and against the value of that field we
group these forms - so can we use case_id here??