using CommCare forms in ODK Collect

[Natasha Lelijveld]

Hi!

Im just about to start a new research project and my institution has a secure server linked to ODK Collect for storing research data. We have been told that we must use this server for all our mHealth needs.

I was REALLY hoping to build my forms in CommCare (because I love CommCare), download the XML files, then upload to their ODK Collect system.... however, we did a trial with an old project form of mine and got an error message about syntax.

Is it possible to do what Im suggesting? Is the CommCare XML file different to the ODK Collect? Might it be multimedia images in my CommCare form that are causing the problem? Or perhaps I'm supposed to do something like deploy the whole project rather than download a form....?

Thanks for advice,

Best wishes,

Natasha

[Jonathan Jackson]

Hi Natasha - going to reach out to you offline about the server question to better understand that.

In terms of the CommCare XML files, these are not compatible with ODK Collect directly.  Many features in CommCare are not supported by ODK collect.  It maybe that some files you can author in CommCare can be used in ODK collect with slight modification.  Unfortunately, though, it is not supported so you would need to test through trial and error.  

Regards,

Jonathan

--
You received this message because you are subscribed to the Google Groups "commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeremy W.]

Hi Natasha,

I agree with Jonathan that you'll have to test things out a bit to see what works. We have a page that outlines some of the compatibility issues when taking a form built with XLSForm and using it in CommCare (https://confluence.dimagi.com/display/commcarepublic/Use+Excel+to+Build+CommCare+Forms). It may be that some of the same issues (multiple languages, labels) cause issues when moving from CommCare to ODK Collect so that could be one place to start (see the Known Limitations section)

Jeremy

--

Jeremy Wacksman

Dimagi, Inc.