kobotoolbox / enketo-express Goto Github PK

I think this can be added to the external API.

New functionality where an array of file objects {filename: url} can be added to the edit API call. Enketo would then show the previews of these. Or an array.

It would be added to this: http://apidocs.enketo.org/v2/#/post-instance and this: http://apidocs.enketo.org/v2/#/post-instance-iframe API endpoint.

relates to #9

Note that this will not do anything until a server (KoBoCAT) starts consuming this updated API endpoint by adding these file url arrays.

low priority

The current media input widget is linked with fileStorage API. We need a new online-only file input widget (probably won't show previews)

like api tests

Takes care of all communication with OpenRosa server (port of PHP OpenRosa library but made asynchronous). Sends requests with the correct OpenRosa headers .e.g. for:

• maximum allowed submission size
• submission of data
• forms, manifests, media

seen with ODK Aggregate

depends on VM setup. the current req.protocol+'://'+req.host may not work if Apache or NGINX is used in front of this app

As simple as possible, probably using Redis.

Case-sensitive would be nice to keep the ID as short as possible.

14.7 million combinations with 4 characters may be sufficient.

figure out how to best do this, since filtering by record content active !== 'false cannot be done elegantly in a key-value store.

Perhaps (se: prefix stands for server) :

se:ona.io/enketo contains a set of all active enketo ids

every time a survey launches successfully use sadd to add this id (since duplicates are avoided automatically)
everytime a survey is de-activated use srem to remove this id from the set

port of PHP api (may exclude endpoints that are not used in KoBoCAT)

will give the appearance of being more responsive upon load

the current method of retrieving a response every couple of minutes is not elegant.

also add test

pass instance to special webform view for editing

getting Bad Request. Survey information not complete or invalid

http://redis.io/topics/security

This has a lot of unused code. It may be a good opportunity to refactor this using promises if polyfill is small.

either directly from client or routed via server

To have Travis build be reflected on Flowdock, we should add this to .travis.yml:

notifications:
flowdock: 7d2ea551a0757bea5b52c496f3a7ab2e

Cache prevents XSL transformations from having to be executed at every form load (very CPU-intensive and can take minutes for extreme forms).

Cache should probably survive server/VM reboot, but does not need to be migrateable and/or backupable. Maybe memcached?