Export specific projects via API

[sigau]

Hello,

We are running an instance of RDMO with many users, and I would like to monitor it in order to retrieve statistics and other relevant information. To do this, I'm currently using curl to access data on all projects. However, I would like to be able to export specific projects via the API, so that we can version them transparently for our users.

Is this possible using the rdmo-client?

Additionally, is there any documentation available for using the API or the client? I haven’t been able to find much, and the examples provided on the website are quite limited.

Thank you in advance for your help!

[sigau]

Hi,
We found a way to extract the different projects as JSON.
However, is there a way to extract or convert them to XML, so that we can reimport them into RDMO if necessary?

[jochenklar]

Hi @sigau , sorry for not replying in time. My idea was to update the client, but I can't find the time...

I think the solution is quite simple. You can just get the url which the users use https://example.com/projects/<id>/export/xml/. If you can access the project, which admins or site_managers can, you should be able to retrieve the XML using requests or curl etc.

Hope that helps.

[sigau]

Hi !
No problem !
The curl command I was trying for the export was curl -LH "Authorization: Token $TOKEN" "$MYRDMO/api/v1/projects/projects/2/export/xml/" but this give us the home page of our RDMO

The command i use currently and is working is the following curl -LH "Authorization: Token $TOKEN" "MYRDMO/api/v1/projects/projects/2/values" that give us the project as json (which for the moment is sufficient - we're just looking to be able to recover the questionnaire in case a user makes a mistake, but it would be simpler to be able to recover it in xml so that it can be imported directly into the rdmo instance.)

[jochenklar]

Hi @sigau , sorry I was wrong, token authentication works only with the API (/api/v1) not with the "regular" Django routes. We will add the export to the API in the not to distant future (i.e. this year). I will send you an email with a more hacky intermediate solution.