flipside-org / aw-datacollection Goto Github PK

Models are responsible for saving entities to the database. Every time a new field is added to an entity, the save method in the model needs to be updated.

Ideally there would be a way to generalize this, maybe using public fields as fields that go in the database,.

• The admin can create new users.

Considering using the following?

• phing: http://www.phing.info/
• grunt-php: http://chrsm.org/post/using-grunt-for-php/

tests/... => tests/phpunit/....

Mind there is a casperjs subfolder that should stay there.

Having data stored in the browser poses security issues.
A user that gets access to the computer can change the data stored in the local storage.

As a cc operator starting a survey him/her should be presented with:

• A number to call;
• The text the operator has to read. (introduction)
• Option to cancel collection.
• Option to start actual collection.

When cancelling a collection the cc operator should be prompted with:

• The reason why stopping (pre-defined set of options)
• Explanatory message (when needed)

When starting collection the user should be presented with:

• The enketo form.

Set status

Scenario:
A callcenter operator is filling a big form and the call drops when he's almost finished.

Should he be able to save it as a draft and continue later on, or just discard the data.

• Assign numbers
• Update call task status

Update Build Spec with survey fields.

When a survey has a xml file a button to perform a test run should be shown.
The user should be presented with a form equal to the final one, but upon click on the submission button, only the validation should run.

Two changes are needed in pyxform.

• validate=True => validate=False [xls2xform.py - line 22]
• from pyxform import constants => import constants [survey.py - line 13]

We should consider forking pyxform and update it when needed.

Vagrant box didn't have the required OS packages and configs for this. Not sure if it solves the code igniter part of it, but we can now send emails via OS.

Steps to be replicated vagrant config:

$ sudo apt-get install coreutils mailutils sendmail 
$ sudo sendmailconfig

Test with:

$ echo "This will go into the body of the mail." | mail -s "Hello world" [email protected]

• Users should be able to see their own profile

Implement method to assign call tasks to cc operators

Right now the password is being hashed with sha1().
There are rainbow tables for these functions and we can not assume users will use safe passwords.

Implement passwords hashing with salt and a cost factor.

Right now, fields have no minimum length set.

User password, for example, should have a minimum length.

• Users should be able to change their own profile data. (Except username and email)
• Admin can change data for all users (Except username and email)

To be able to quickly test, modify and share a working version, the enketo library was added to the project just by copying files.

This library should be used as a git submodule.

CodeIgniter MongoDB Session Library

• Changes made and why!
• https://github.com/sepehr/ci-mongodb-session

A PHP MongoDB query builder library

• Changes made and why!
• https://github.com/alexbilbie/MongoQB

Create the users entity and some fixture data

Check the enketo form_model, understand what it does, how it works and implement something similar.

The text presented to the cc operator when collecting data should be set per survey, when creating/editing the survey.

Extend Users Roles.

• roles admin
• extend fixtures

Recover password functionality

• investigate phpunit testsuites
• add stress test for respondents

A callcenter operator will be able to continue to collect data even if the connection drops (Given that he has enough number to call stored.)

However if he navigates away from the page he won't be able to come back. The page will not be available offline.

Do we really need that?
The callcenter operator will only be assigned a limited amount of numbers so, even if we have offline support, he will only be able to submit data until the numbers run out.

when a call task is assigned but there's no status, unassigned it after X amount of time.

A user (A), without connection, submits data and goes away.
The data is stored in the browser's localstorage.

The next day, another user (B) logs in the same computer and does data collection. The data from the previous user (A) should not be lost.

Right now an error will be thrown because the user (B) submitting the data collected by the user (A) is not assigned to that call task.

Option 1
Do not submit the data and store it in the browser until the other user (A) comes back.

Option 2
Store in the browser the id of the user (A) that collected the data. When the data is submitted, check if who collected is assigned to that call task. Several changes needed (Ex: author of call task status)

Every option has significant security flaws. Since the data is stored in the browser whoever gets access to the browser can change the data.

There should be an option to notify an user when his account is created.

Using CasperJS http://casperjs.org/

• Create form for login.
• Show logged in status
• Logout function

Validate if status is selected when halting collection.

Implement method and validations to add status to a call task activity array.

• List call tasks to do
• List call tasks done

Add some logging throughout the code, for critical operation:

• success / info / status / notice
• warning
  -failure / error

This should be able to be controlled enabled at the following levels:

• all: saves all logs
• no-notices: only warnings and errors
• errors-only
• none

Related with #31

Move email settings (admin email and name) to a config file

Implement single data collection.
This data collection will be started from the call activity page and will be used for one respondent at a time.

Follow up from #8

Full offline support is not needed. Instead ask for confirmation when the user is leaving the page and the connection is down.

Several tasks depend on survey statuses.

• Discuss/document status implications (with @olafveerman)
• Implement status restrictions, (need thorough testing).

cf: https://flipside.mybalsamiq.com/projects/airwolf/Survey%20Moderator%20Flow

If possible use a config file to set the defaults for JsSettings.