Extract submission data using the API

I’ve noticed that different kobo forms have different structures thus causing the json got from submissions to have different structures according to the form structure.

Is there a generic method anyone has come up with which works with all forms? Or do I just have to stick to writing a data extractor per form?

Thanks in advance

Dear Michael,

I use R-Script to download submitted data in CSV format using API. Code and working examples are available in https://github.com/ppsapkota/kobohr_apitoolbox and https://github.com/ppsapkota/kobohrtoolbox. I hope this helps.

Best regards,

Punya

···

On Sunday, October 7, 2018 at 11:57:12 AM UTC+3, Michael Bukachi wrote:

I’ve noticed that different kobo forms have different structures thus causing the json got from submissions to have different structures according to the form structure.

Is there a generic method anyone has come up with which works with all forms? Or do I just have to stick to writing a data extractor per form?

Thanks in advance

Do the scripts work for all forms or do you have to customize it per form?

···

On Sunday, October 7, 2018 at 9:50:52 PM UTC+3, Punya Sapkota wrote:

Dear Michael,

I use R-Script to download submitted data in CSV format using API. Code and working examples are available in https://github.com/ppsapkota/kobohr_apitoolbox and https://github.com/ppsapkota/kobohrtoolbox. I hope this helps.

Best regards,

Punya

On Sunday, October 7, 2018 at 11:57:12 AM UTC+3, Michael Bukachi wrote:

I’ve noticed that different kobo forms have different structures thus causing the json got from submissions to have different structures according to the form structure.

Is there a generic method anyone has come up with which works with all forms? Or do I just have to stick to writing a data extractor per form?

Thanks in advance

It is a pretty standard approach to fetch data using KoBo API. It works for all forms. I have been using it for different KoBo projects.

···

On Sunday, October 7, 2018 at 11:57:12 AM UTC+3, Michael Bukachi wrote:

I’ve noticed that different kobo forms have different structures thus causing the json got from submissions to have different structures according to the form structure.

Is there a generic method anyone has come up with which works with all forms? Or do I just have to stick to writing a data extractor per form?

Thanks in advance

Dear Michael,
I installed KoboToolBox server version on my local computer (Ubuntu) and intend to test it as a server. When I docker-compose up,it returns

Error when try to start nginx container (Bind for 0.0.0.0:80 failed: port is already allocated.)

Then i changed port 80 to 81 (ports: - 81:81) in docker-compose.yml. After I docker-compose up and tried docker-compose ps, everything shows ‘done’, which I think means normally running. However I could not open KoboToolBox on my browsers with the address I typed in, which is ‘172.17.0.1’ and ‘127.0.0.1’. I tried a lot but unable to run on my browser

···

On Mon, Oct 8, 2018 at 1:04 AM Punya Sapkota sapkot...@gmail.com wrote:

It is a pretty standard approach to fetch data using KoBo API. It works for all forms. I have been using it for different KoBo projects.

On Sunday, October 7, 2018 at 11:57:12 AM UTC+3, Michael Bukachi wrote:

I’ve noticed that different kobo forms have different structures thus causing the json got from submissions to have different structures according to the form structure.

Is there a generic method anyone has come up with which works with all forms? Or do I just have to stick to writing a data extractor per form?

Thanks in advance

You received this message because you are subscribed to the Google Groups “KoBoToolbox Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to kobo-users+...@googlegroups.com.

To post to this group, send email to kobo-...@googlegroups.com.

Visit this group at https://groups.google.com/group/kobo-users.

For more options, visit https://groups.google.com/d/optout.

Please anyone help me out.

···

On Mon, Oct 8, 2018 at 9:04 AM palistha prajapati palis...@gmail.com wrote:

Dear Michael,
I installed KoboToolBox server version on my local computer (Ubuntu) and intend to test it as a server. When I docker-compose up,it returns

Error when try to start nginx container (Bind for 0.0.0.0:80 failed: port is already allocated.)

Then i changed port 80 to 81 (ports: - 81:81) in docker-compose.yml. After I docker-compose up and tried docker-compose ps, everything shows ‘done’, which I think means normally running. However I could not open KoboToolBox on my browsers with the address I typed in, which is ‘172.17.0.1’ and ‘127.0.0.1’. I tried a lot but unable to run on my browser

On Mon, Oct 8, 2018 at 1:04 AM Punya Sapkota sapkot...@gmail.com wrote:

It is a pretty standard approach to fetch data using KoBo API. It works for all forms. I have been using it for different KoBo projects.

On Sunday, October 7, 2018 at 11:57:12 AM UTC+3, Michael Bukachi wrote:

I’ve noticed that different kobo forms have different structures thus causing the json got from submissions to have different structures according to the form structure.

Is there a generic method anyone has come up with which works with all forms? Or do I just have to stick to writing a data extractor per form?

Thanks in advance

You received this message because you are subscribed to the Google Groups “KoBoToolbox Users” group.

To unsubscribe from this group and stop receiving emails from it, send an email to kobo-users+...@googlegroups.com.

To post to this group, send email to kobo-...@googlegroups.com.

Visit this group at https://groups.google.com/group/kobo-users.

For more options, visit https://groups.google.com/d/optout.